SAP OM_API_GENERATE_DEPENDENCIES Function Module for NOTRANSL: API zum Anlegen von Beziehungswissen (iPPE)
OM_API_GENERATE_DEPENDENCIES is a standard om api generate dependencies 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: API zum Anlegen von Beziehungswissen (iPPE) 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 om api generate dependencies FM, simply by entering the name OM_API_GENERATE_DEPENDENCIES into the relevant SAP transaction such as SE37 or SE38.
Function Group: OM_API
Program Name: SAPLOM_API
Main Program: SAPLOM_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OM_API_GENERATE_DEPENDENCIES 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 'OM_API_GENERATE_DEPENDENCIES'"NOTRANSL: API zum Anlegen von Beziehungswissen (iPPE).
EXPORTING
* IM_MSG_HANDLING = 'A' "Message Handling
* IM_MODE_ALL = 'X' "Checkbox
IM_GENERATE_CONFIG = "Checkbox
TABLES
TAB_POSVID = "DE-EN-LANG-SWITCH-NO-TRANSLATION
TAB_DEPENDENCYDATA = "iPPE/BAPI: Object Dependencies - Basic Data
TAB_DEPENDENCYSOURCES = "iPPE/BAPI: Object Dependencies - Source Code Relationship
EXCEPTIONS
ERROR_DEPENDENCY_CREATION = 1 ERROR_CONFIG_CREATION = 2 ERROR_GENERAL = 3
IMPORTING Parameters details for OM_API_GENERATE_DEPENDENCIES
IM_MSG_HANDLING - Message Handling
Data type: PPET_MSG_OPTDefault: 'A'
Optional: Yes
Call by Reference: Yes
IM_MODE_ALL - Checkbox
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
IM_GENERATE_CONFIG - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
TABLES Parameters details for OM_API_GENERATE_DEPENDENCIES
TAB_POSVID - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: PPET_POSVID_LI_TABOptional: No
Call by Reference: Yes
TAB_DEPENDENCYDATA - iPPE/BAPI: Object Dependencies - Basic Data
Data type: BAPI1176_CMP_DEPDATAOptional: No
Call by Reference: Yes
TAB_DEPENDENCYSOURCES - iPPE/BAPI: Object Dependencies - Source Code Relationship
Data type: BAPI1176_CMP_DEPSOURCEOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_DEPENDENCY_CREATION - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ERROR_CONFIG_CREATION - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ERROR_GENERAL - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OM_API_GENERATE_DEPENDENCIES 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: | ||||
| lt_tab_posvid | TYPE STANDARD TABLE OF PPET_POSVID_LI_TAB, " | |||
| lv_im_msg_handling | TYPE PPET_MSG_OPT, " 'A' | |||
| lv_error_dependency_creation | TYPE PPET_MSG_OPT, " | |||
| lv_im_mode_all | TYPE XFELD, " 'X' | |||
| lt_tab_dependencydata | TYPE STANDARD TABLE OF BAPI1176_CMP_DEPDATA, " | |||
| lv_error_config_creation | TYPE BAPI1176_CMP_DEPDATA, " | |||
| lv_error_general | TYPE BAPI1176_CMP_DEPDATA, " | |||
| lv_im_generate_config | TYPE XFELD, " | |||
| lt_tab_dependencysources | TYPE STANDARD TABLE OF BAPI1176_CMP_DEPSOURCE. " |
|   CALL FUNCTION 'OM_API_GENERATE_DEPENDENCIES' "NOTRANSL: API zum Anlegen von Beziehungswissen (iPPE) |
| EXPORTING | ||
| IM_MSG_HANDLING | = lv_im_msg_handling | |
| IM_MODE_ALL | = lv_im_mode_all | |
| IM_GENERATE_CONFIG | = lv_im_generate_config | |
| TABLES | ||
| TAB_POSVID | = lt_tab_posvid | |
| TAB_DEPENDENCYDATA | = lt_tab_dependencydata | |
| TAB_DEPENDENCYSOURCES | = lt_tab_dependencysources | |
| EXCEPTIONS | ||
| ERROR_DEPENDENCY_CREATION = 1 | ||
| ERROR_CONFIG_CREATION = 2 | ||
| ERROR_GENERAL = 3 | ||
| . " OM_API_GENERATE_DEPENDENCIES | ||
ABAP code using 7.40 inline data declarations to call FM OM_API_GENERATE_DEPENDENCIES
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.| DATA(ld_im_msg_handling) | = 'A'. | |||
| DATA(ld_im_mode_all) | = 'X'. | |||
Search for further information about these or an SAP related objects