SAP PPEEXPL_GET_ACT_DATA Function Module for NOTRANSL: Lesen der ACT Objekte unter einem Plan
PPEEXPL_GET_ACT_DATA is a standard ppeexpl get act data 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: Lesen der ACT Objekte unter einem Plan 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 ppeexpl get act data FM, simply by entering the name PPEEXPL_GET_ACT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: PPEEXPL
Program Name: SAPLPPEEXPL
Main Program: SAPLPPEEXPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PPEEXPL_GET_ACT_DATA 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 'PPEEXPL_GET_ACT_DATA'"NOTRANSL: Lesen der ACT Objekte unter einem Plan.
EXPORTING
* IV_MSG_OPT = 'A' "
* IV_WRITE_SH_MEMORY = PPET_TRUE "Generic Type
* IV_MSG_CONTEXT = "Application Context of Message
IV_PLANID = "Internal Number of iPPE Node
* IV_BYPASS_LIBUFFER = ' ' "Generic Type
* IV_WITH_ASSIGN_DATA = PPET_TRUE "Generic Type
* IV_WITH_MODUS_DATA = PPET_TRUE "Generic Type
* IV_WITH_SEQUENC_DATA = PPET_TRUE "Generic Type
* IV_WITH_PVBASS_DATA = PPET_TRUE "Generic Type
* IS_MEMORY_HANDLE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
ES_ACT_MEM = "
IMPORTING Parameters details for PPEEXPL_GET_ACT_DATA
IV_MSG_OPT -
Data type: PPET_MSG_OPTDefault: 'A'
Optional: Yes
Call by Reference: Yes
IV_WRITE_SH_MEMORY - Generic Type
Data type: CDefault: PPET_TRUE
Optional: Yes
Call by Reference: Yes
IV_MSG_CONTEXT - Application Context of Message
Data type: PPE_MSG_CONTEXTOptional: Yes
Call by Reference: Yes
IV_PLANID - Internal Number of iPPE Node
Data type: PNODID-PNGUIDOptional: No
Call by Reference: Yes
IV_BYPASS_LIBUFFER - Generic Type
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_WITH_ASSIGN_DATA - Generic Type
Data type: CDefault: PPET_TRUE
Optional: Yes
Call by Reference: Yes
IV_WITH_MODUS_DATA - Generic Type
Data type: CDefault: PPET_TRUE
Optional: Yes
Call by Reference: Yes
IV_WITH_SEQUENC_DATA - Generic Type
Data type: CDefault: PPET_TRUE
Optional: Yes
Call by Reference: Yes
IV_WITH_PVBASS_DATA - Generic Type
Data type: CDefault: PPET_TRUE
Optional: Yes
Call by Reference: Yes
IS_MEMORY_HANDLE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: PPET8_MEMORY_HANDLEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PPEEXPL_GET_ACT_DATA
ES_ACT_MEM -
Data type: PPET8_ACT_MEMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPEEXPL_GET_ACT_DATA 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_es_act_mem | TYPE PPET8_ACT_MEM, " | |||
| lv_iv_msg_opt | TYPE PPET_MSG_OPT, " 'A' | |||
| lv_iv_write_sh_memory | TYPE C, " PPET_TRUE | |||
| lv_iv_msg_context | TYPE PPE_MSG_CONTEXT, " | |||
| lv_iv_planid | TYPE PNODID-PNGUID, " | |||
| lv_iv_bypass_libuffer | TYPE C, " SPACE | |||
| lv_iv_with_assign_data | TYPE C, " PPET_TRUE | |||
| lv_iv_with_modus_data | TYPE C, " PPET_TRUE | |||
| lv_iv_with_sequenc_data | TYPE C, " PPET_TRUE | |||
| lv_iv_with_pvbass_data | TYPE C, " PPET_TRUE | |||
| lv_is_memory_handle | TYPE PPET8_MEMORY_HANDLE. " |
|   CALL FUNCTION 'PPEEXPL_GET_ACT_DATA' "NOTRANSL: Lesen der ACT Objekte unter einem Plan |
| EXPORTING | ||
| IV_MSG_OPT | = lv_iv_msg_opt | |
| IV_WRITE_SH_MEMORY | = lv_iv_write_sh_memory | |
| IV_MSG_CONTEXT | = lv_iv_msg_context | |
| IV_PLANID | = lv_iv_planid | |
| IV_BYPASS_LIBUFFER | = lv_iv_bypass_libuffer | |
| IV_WITH_ASSIGN_DATA | = lv_iv_with_assign_data | |
| IV_WITH_MODUS_DATA | = lv_iv_with_modus_data | |
| IV_WITH_SEQUENC_DATA | = lv_iv_with_sequenc_data | |
| IV_WITH_PVBASS_DATA | = lv_iv_with_pvbass_data | |
| IS_MEMORY_HANDLE | = lv_is_memory_handle | |
| IMPORTING | ||
| ES_ACT_MEM | = lv_es_act_mem | |
| . " PPEEXPL_GET_ACT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM PPEEXPL_GET_ACT_DATA
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_iv_msg_opt) | = 'A'. | |||
| DATA(ld_iv_write_sh_memory) | = PPET_TRUE. | |||
| "SELECT single PNGUID FROM PNODID INTO @DATA(ld_iv_planid). | ||||
| DATA(ld_iv_bypass_libuffer) | = ' '. | |||
| DATA(ld_iv_with_assign_data) | = PPET_TRUE. | |||
| DATA(ld_iv_with_modus_data) | = PPET_TRUE. | |||
| DATA(ld_iv_with_sequenc_data) | = PPET_TRUE. | |||
| DATA(ld_iv_with_pvbass_data) | = PPET_TRUE. | |||
Search for further information about these or an SAP related objects