SAP GET_AGGR_OF_OBJECT Function Module for Returns the Desired Hierarchy Information Depending on Object Type
GET_AGGR_OF_OBJECT is a standard get aggr of object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns the Desired Hierarchy Information Depending on Object Type processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for get aggr of object FM, simply by entering the name GET_AGGR_OF_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: STMO
Program Name: SAPLSTMO
Main Program: SAPLSTMO
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_AGGR_OF_OBJECT pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'GET_AGGR_OF_OBJECT'"Returns the Desired Hierarchy Information Depending on Object Type.
EXPORTING
ASKED_LEVEL = "Desired Result Level
OBJECT_LEVEL01 = "Input of level 01 object
OBJECT_TYP = "Object Type (Report, Transaction, Table, and so on)
* OBJECT_PGMID = 'R3TR' "=R3TR
* TO_FILL = ' ' "Subapplication NE ' ' in any case
IMPORTING
ASKED_OBJECT = "Successor of act_object with Level asked_level
EXCEPTIONS
WRONG_LEVEL = 1 WRONG_OBJECT = 2 WRONG_TYP = 3 WRONG_PGMID = 4
IMPORTING Parameters details for GET_AGGR_OF_OBJECT
ASKED_LEVEL - Desired Result Level
Data type: EWAGG-HI_LEVELOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_LEVEL01 - Input of level 01 object
Data type: EWAGG-OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_TYP - Object Type (Report, Transaction, Table, and so on)
Data type: TADIR-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_PGMID - =R3TR
Data type: TADIR-PGMIDDefault: 'R3TR'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TO_FILL - Subapplication NE SPACE in any case
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GET_AGGR_OF_OBJECT
ASKED_OBJECT - Successor of act_object with Level asked_level
Data type: EWAGG-HI_OBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_LEVEL - Unknown result level as input
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_OBJECT - Unknown object as input
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_TYP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_PGMID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_AGGR_OF_OBJECT Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_asked_level | TYPE EWAGG-HI_LEVEL, " | |||
| lv_wrong_level | TYPE EWAGG, " | |||
| lv_asked_object | TYPE EWAGG-HI_OBJNAME, " | |||
| lv_wrong_object | TYPE EWAGG, " | |||
| lv_object_level01 | TYPE EWAGG-OBJ_NAME, " | |||
| lv_wrong_typ | TYPE EWAGG, " | |||
| lv_object_typ | TYPE TADIR-OBJECT, " | |||
| lv_wrong_pgmid | TYPE TADIR, " | |||
| lv_object_pgmid | TYPE TADIR-PGMID, " 'R3TR' | |||
| lv_to_fill | TYPE TADIR. " SPACE |
|   CALL FUNCTION 'GET_AGGR_OF_OBJECT' "Returns the Desired Hierarchy Information Depending on Object Type |
| EXPORTING | ||
| ASKED_LEVEL | = lv_asked_level | |
| OBJECT_LEVEL01 | = lv_object_level01 | |
| OBJECT_TYP | = lv_object_typ | |
| OBJECT_PGMID | = lv_object_pgmid | |
| TO_FILL | = lv_to_fill | |
| IMPORTING | ||
| ASKED_OBJECT | = lv_asked_object | |
| EXCEPTIONS | ||
| WRONG_LEVEL = 1 | ||
| WRONG_OBJECT = 2 | ||
| WRONG_TYP = 3 | ||
| WRONG_PGMID = 4 | ||
| . " GET_AGGR_OF_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM GET_AGGR_OF_OBJECT
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single HI_LEVEL FROM EWAGG INTO @DATA(ld_asked_level). | ||||
| "SELECT single HI_OBJNAME FROM EWAGG INTO @DATA(ld_asked_object). | ||||
| "SELECT single OBJ_NAME FROM EWAGG INTO @DATA(ld_object_level01). | ||||
| "SELECT single OBJECT FROM TADIR INTO @DATA(ld_object_typ). | ||||
| "SELECT single PGMID FROM TADIR INTO @DATA(ld_object_pgmid). | ||||
| DATA(ld_object_pgmid) | = 'R3TR'. | |||
| DATA(ld_to_fill) | = ' '. | |||
Search for further information about these or an SAP related objects