SAP IAOM_TOP_HLO_EXT_OBJ_ID_GET Function Module for NOTRANSL: Suche die Id des Top-Objekts entlang des übergeordneten Obj.
IAOM_TOP_HLO_EXT_OBJ_ID_GET is a standard iaom top hlo ext obj id get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Suche die Id des Top-Objekts entlang des übergeordneten Obj. 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 iaom top hlo ext obj id get FM, simply by entering the name IAOM_TOP_HLO_EXT_OBJ_ID_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: IAOM_MISC_SERVICES
Program Name: SAPLIAOM_MISC_SERVICES
Main Program: SAPLIAOM_MISC_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IAOM_TOP_HLO_EXT_OBJ_ID_GET 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 'IAOM_TOP_HLO_EXT_OBJ_ID_GET'"NOTRANSL: Suche die Id des Top-Objekts entlang des übergeordneten Obj..
EXPORTING
I_BUS_SCENARIO_ID = "Business Scenario for Which Controlling Is Performed
I_EXT_OBJECT_ID = "External Object Technical Key
* I_SUB_OBJ_ATTRS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
E_TOP_HLO_EXT_OBJECT_ID = "External Object Technical Key
E_TOP_HLO_BUSINESS_KEY = "Business (for Displaying Suitable) Object Keys
EXCEPTIONS
BUS_SCENARIO_UNKNOWN = 1 EXT_OBJECT_ID_UNKNOWN = 2 ERROR_OCCURRED = 3
IMPORTING Parameters details for IAOM_TOP_HLO_EXT_OBJ_ID_GET
I_BUS_SCENARIO_ID - Business Scenario for Which Controlling Is Performed
Data type: IAOM_BS_IDENTIFICATIONOptional: No
Call by Reference: No ( called with pass by value option)
I_EXT_OBJECT_ID - External Object Technical Key
Data type: IAOM_EXT_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_SUB_OBJ_ATTRS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: IAOMT_SUB_OBJECT_ATTRIBUTE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IAOM_TOP_HLO_EXT_OBJ_ID_GET
E_TOP_HLO_EXT_OBJECT_ID - External Object Technical Key
Data type: IAOM_EXT_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_TOP_HLO_BUSINESS_KEY - Business (for Displaying Suitable) Object Keys
Data type: IAOM_BUSINESS_KEYOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BUS_SCENARIO_UNKNOWN - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
EXT_OBJECT_ID_UNKNOWN - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ERROR_OCCURRED - Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IAOM_TOP_HLO_EXT_OBJ_ID_GET 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_i_bus_scenario_id | TYPE IAOM_BS_IDENTIFICATION, " | |||
| lv_bus_scenario_unknown | TYPE IAOM_BS_IDENTIFICATION, " | |||
| lv_e_top_hlo_ext_object_id | TYPE IAOM_EXT_OBJECT_ID, " | |||
| lv_i_ext_object_id | TYPE IAOM_EXT_OBJECT_ID, " | |||
| lv_ext_object_id_unknown | TYPE IAOM_EXT_OBJECT_ID, " | |||
| lv_e_top_hlo_business_key | TYPE IAOM_BUSINESS_KEY, " | |||
| lv_error_occurred | TYPE IAOM_BUSINESS_KEY, " | |||
| lv_i_sub_obj_attrs | TYPE IAOMT_SUB_OBJECT_ATTRIBUTE_TAB. " |
|   CALL FUNCTION 'IAOM_TOP_HLO_EXT_OBJ_ID_GET' "NOTRANSL: Suche die Id des Top-Objekts entlang des übergeordneten Obj. |
| EXPORTING | ||
| I_BUS_SCENARIO_ID | = lv_i_bus_scenario_id | |
| I_EXT_OBJECT_ID | = lv_i_ext_object_id | |
| I_SUB_OBJ_ATTRS | = lv_i_sub_obj_attrs | |
| IMPORTING | ||
| E_TOP_HLO_EXT_OBJECT_ID | = lv_e_top_hlo_ext_object_id | |
| E_TOP_HLO_BUSINESS_KEY | = lv_e_top_hlo_business_key | |
| EXCEPTIONS | ||
| BUS_SCENARIO_UNKNOWN = 1 | ||
| EXT_OBJECT_ID_UNKNOWN = 2 | ||
| ERROR_OCCURRED = 3 | ||
| . " IAOM_TOP_HLO_EXT_OBJ_ID_GET | ||
ABAP code using 7.40 inline data declarations to call FM IAOM_TOP_HLO_EXT_OBJ_ID_GET
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.Search for further information about these or an SAP related objects