SAP BAPI_ACTIVTY_GETDIAGRAMIDS Function Module for Read diagram
BAPI_ACTIVTY_GETDIAGRAMIDS is a standard bapi activty getdiagramids SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read diagram 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 bapi activty getdiagramids FM, simply by entering the name BAPI_ACTIVTY_GETDIAGRAMIDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BEACTIVITY
Program Name: SAPLBEACTIVITY
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_ACTIVTY_GETDIAGRAMIDS 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 'BAPI_ACTIVTY_GETDIAGRAMIDS'"Read diagram.
EXPORTING
* LANGUAGE = SY-LANGU "Language key
* LANGUAGEISO = "Language according to ISO 639
* ADDON = "Industry sector
* LOCKPROCDIA = "Lock diagram module
* LOCKDIAVAR = "Lock diagram variant
* LOCKOCCDIAVAR = "Lock occurrence diagram variant
TABLES
* ACTIVITIES_ALL = "Process modeling activity
* PROCDIAHEADER = "Diagram header data
* DIAVARHEADER = "Diagram variant header
* OCCDIAVARHEADER = "Diagram variant header
* RETURN = "Return parameter
IMPORTING Parameters details for BAPI_ACTIVTY_GETDIAGRAMIDS
LANGUAGE - Language key
Data type: BAPI_LAISO-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGUAGEISO - Language according to ISO 639
Data type: BAPI_LAISO-LANGU_ISOOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDON - Industry sector
Data type: BAPIBEGEN-ADDONOptional: Yes
Call by Reference: No ( called with pass by value option)
LOCKPROCDIA - Lock diagram module
Data type: BAPIBEGEN-FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
LOCKDIAVAR - Lock diagram variant
Data type: BAPIBEGEN-FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
LOCKOCCDIAVAR - Lock occurrence diagram variant
Data type: BAPIBEGEN-FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_ACTIVTY_GETDIAGRAMIDS
ACTIVITIES_ALL - Process modeling activity
Data type: BAPIBEACTOptional: Yes
Call by Reference: Yes
PROCDIAHEADER - Diagram header data
Data type: BAPIBEDIXOptional: Yes
Call by Reference: Yes
DIAVARHEADER - Diagram variant header
Data type: BAPIBEDVXOptional: Yes
Call by Reference: Yes
OCCDIAVARHEADER - Diagram variant header
Data type: BAPIBEDOXOptional: Yes
Call by Reference: Yes
RETURN - Return parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_ACTIVTY_GETDIAGRAMIDS 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_language | TYPE BAPI_LAISO-LANGU, " SY-LANGU | |||
| lt_activities_all | TYPE STANDARD TABLE OF BAPIBEACT, " | |||
| lv_languageiso | TYPE BAPI_LAISO-LANGU_ISO, " | |||
| lt_procdiaheader | TYPE STANDARD TABLE OF BAPIBEDIX, " | |||
| lv_addon | TYPE BAPIBEGEN-ADDON, " | |||
| lt_diavarheader | TYPE STANDARD TABLE OF BAPIBEDVX, " | |||
| lv_lockprocdia | TYPE BAPIBEGEN-FLAG, " | |||
| lt_occdiavarheader | TYPE STANDARD TABLE OF BAPIBEDOX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_lockdiavar | TYPE BAPIBEGEN-FLAG, " | |||
| lv_lockoccdiavar | TYPE BAPIBEGEN-FLAG. " |
|   CALL FUNCTION 'BAPI_ACTIVTY_GETDIAGRAMIDS' "Read diagram |
| EXPORTING | ||
| LANGUAGE | = lv_language | |
| LANGUAGEISO | = lv_languageiso | |
| ADDON | = lv_addon | |
| LOCKPROCDIA | = lv_lockprocdia | |
| LOCKDIAVAR | = lv_lockdiavar | |
| LOCKOCCDIAVAR | = lv_lockoccdiavar | |
| TABLES | ||
| ACTIVITIES_ALL | = lt_activities_all | |
| PROCDIAHEADER | = lt_procdiaheader | |
| DIAVARHEADER | = lt_diavarheader | |
| OCCDIAVARHEADER | = lt_occdiavarheader | |
| RETURN | = lt_return | |
| . " BAPI_ACTIVTY_GETDIAGRAMIDS | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_ACTIVTY_GETDIAGRAMIDS
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 LANGU FROM BAPI_LAISO INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| "SELECT single LANGU_ISO FROM BAPI_LAISO INTO @DATA(ld_languageiso). | ||||
| "SELECT single ADDON FROM BAPIBEGEN INTO @DATA(ld_addon). | ||||
| "SELECT single FLAG FROM BAPIBEGEN INTO @DATA(ld_lockprocdia). | ||||
| "SELECT single FLAG FROM BAPIBEGEN INTO @DATA(ld_lockdiavar). | ||||
| "SELECT single FLAG FROM BAPIBEGEN INTO @DATA(ld_lockoccdiavar). | ||||
Search for further information about these or an SAP related objects