SAP SYSTEM-CALL OO ABAP Statements

Get Example source ABAP code based on a different SAP table
  


SECRET

SYSTEM-CALL - Object Manager Calls
ABAP Code Snippet

ABAP_VARIANTS:
1 SYSTEM-CALL OBJMGR SET TRACELEVEL f1.
2 SYSTEM-CALL OBJMGR SET NODELETE MODE f1.
3 SYSTEM-CALL OBJMGR SET MS-MODE INCREMENTAL f1.
4 SYSTEM-CALL OBJMGR SET INITIAL TRIGGERLEVEL f1.
5 SYSTEM-CALL OBJMGR SET GC STEPTIME f1.
6 SYSTEM-CALL OBJMGR SET OVERALLOCATION FRACTION f1.
7 SYSTEM-CALL OBJMGR PERFORM GARBAGE COLLECTION.
8 SYSTEM-CALL OBJMGR PERFORM MARK.
9 SYSTEM-CALL OBJMGR CLONE f1 TO f2.
10 SYSTEM-CALL OBJMGR EQUAL f1 = f2 INTO f3.
11 SYSTEM-CALL OBJMGR GET STATE OF f1 INTO f2.
12 SYSTEM-CALL OBJMGR SET STATE OF f1 INTO f2.
13 SYSTEM-CALL EVENTS GET NUM_HANDLERS FOR f1 OF CLASS f2 INTO f3.
14 SYSTEM-CALL EVENTS GET NUM_HANDLERS FOR f1 OF INST f2 INTO f3.

ABAP_VARIANT_1 SYSTEM-CALL OBJMGR SET TRACELEVEL f1. What does it do? Sets the TRACE LEVEL. Level 1: Performance statistics and GC phases are recorded in the log file (dev_w*). The higher levels are for internal testing purposes only.

ABAP_VARIANT_2 SYSTEM-CALL OBJMGR SET NODELETE MODE f1. What does it do? Does not delete objects completely in NODELETE MODE but retains the header. When such an object is accessed, a runtime error occurs. This mechanism is used for troubleshooting purposes if you assume that the Garbage Collector has wrongly deleted an object. The nodelete mode can also be switched on using the Debugger.

ABAP_VARIANT_3 SYSTEM-CALL OBJMGR SET MS-MODE INCREMENTAL f1. What does it do? Sets the garbage collector to sequential (0) or incremental (1). The default setting is incremental. This call is only designed for kernel tests.

ABAP_VARIANT_4 SYSTEM-CALL OBJMGR SET INITIAL TRIGGERLEVEL f1.

What does it do? The 'initial trigger level' is the memory limit (in bytes) at which the garbage collector is started for the first time. This call is only designed for kernel tests.

ABAP_VARIANT_5 SYSTEM-CALL OBJMGR SET GC STEPTIME f1. What does it do? No longer supported -> runtime error. ABAP_VARIANT_6 SYSTEM-CALL OBJMGR SET OVERALLOCATION FRACTION f1.

What does it do? No longer supported -> runtime error. ABAP_VARIANT_7 SYSTEM-CALL OBJMGR PERFORM GARBAGE COLLECTION. What does it do? Only designed for kernel tests. Performs a garbage collection. You can also start a garbage collection from within the Debugger.

ABAP_VARIANT_8 SYSTEM-CALL OBJMGR PERFORM MARK. What does it do? Only designed for kernel tests. Must never occur in other programs.

ABAP_VARIANT_9 SYSTEM-CALL OBJMGR CLONE f1 TO f2. What does it do? Only available to ensure compatibility ABAP_VARIANT_10 SYSTEM-CALL OBJMGR EQUAL f1 = f2 INTO f3. What does it do? Only available to ensure compatibility ABAP_VARIANT_11 SYSTEM-CALL OBJMGR GET STATE OF f1 INTO f2. What does it do? Copies the state (of all instance attributes) from object f1 to a dynamically created data structure and returns a data reference f2 (TYPE REF TO DATA) to that structure. You can use this call to save the current state of an object. The variant SET STATE then allows you to reassign the state saved to the object (the object state is reset to its saved state). These calls should only be used by Object Services .

ABAP_VARIANT_12 SYSTEM-CALL OBJMGR SET STATE OF f1 INTO f2. What does it do? Copies an object state f1 saved with GET STATE back to object f2. The type compatibility is checked. This call should only be used by Object Services.

ABAP_VARIANT_13 SYSTEM-CALL EVENTS GET NUM_HANDLERS FOR f1 OF CLASS f2 INTO f3.

What does it do? Returns the current number of registered handlers for CLASS-EVENT f1 of the class f2 and stores it in the integer variable f3.

ABAP_VARIANT_14 SYSTEM-CALL EVENTS GET NUM_HANDLERS FOR f1 OF INST f2 INTO f3.

What does it do? Returns the current number of registered handlers for the instance event (EVENT) f1 of the instance f2 and stores it in the integer variable f3.



Return to menu