SAP PPEEXPL_GET_HDR Function Module for NOTRANSL: Suche der Einstiege für die Planungsvormerkung
PPEEXPL_GET_HDR is a standard ppeexpl get hdr 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 der Einstiege für die Planungsvormerkung 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 hdr FM, simply by entering the name PPEEXPL_GET_HDR 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_HDR 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_HDR'"NOTRANSL: Suche der Einstiege für die Planungsvormerkung.
EXPORTING
* IV_MSG_HANDLING = 'A' "
* IV_MSG_CONTEXT = "Application Context of Message
IS_POSVID = "
* IV_CMPID = "Internal Identification of the Component (Material/Product)
* IV_FOCUSID = "Internal Identification for Focus Record
* IV_UPPER_HDR_ONLY = PPET_FALSE "Generic Type
* IV_OWN_HDR_ONLY = PPET_FALSE "Generic Type
* IV_BYPASS_LIBUFFER = PPET_FALSE "Generic Type
IMPORTING
ET_PPEHDR_LOW = "
ET_PPEHDR_HIGH = "
ET_PPEOBJ_HIGH = "
ET_PHANTOM_HDR_HIGH = "
ET_PHANTOM_OBJ_HIGH = "
ET_PHANTOM_REF = "
IMPORTING Parameters details for PPEEXPL_GET_HDR
IV_MSG_HANDLING -
Data type: PPET_MSG_OPTDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSG_CONTEXT - Application Context of Message
Data type: PPE_MSG_CONTEXTOptional: Yes
Call by Reference: Yes
IS_POSVID -
Data type: PPET_POSVID_LIOptional: No
Call by Reference: Yes
IV_CMPID - Internal Identification of the Component (Material/Product)
Data type: PVCMPD-CMPIDOptional: Yes
Call by Reference: Yes
IV_FOCUSID - Internal Identification for Focus Record
Data type: PPFOC_PFOCID-PFGUIDOptional: Yes
Call by Reference: Yes
IV_UPPER_HDR_ONLY - Generic Type
Data type: CDefault: PPET_FALSE
Optional: Yes
Call by Reference: Yes
IV_OWN_HDR_ONLY - Generic Type
Data type: CDefault: PPET_FALSE
Optional: Yes
Call by Reference: Yes
IV_BYPASS_LIBUFFER - Generic Type
Data type: CDefault: PPET_FALSE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PPEEXPL_GET_HDR
ET_PPEHDR_LOW -
Data type: PPET4_PPEHDR_TABOptional: No
Call by Reference: Yes
ET_PPEHDR_HIGH -
Data type: PPET4_PPEHDR_TABOptional: No
Call by Reference: Yes
ET_PPEOBJ_HIGH -
Data type: PPET4_PPEOBJ_TABOptional: No
Call by Reference: Yes
ET_PHANTOM_HDR_HIGH -
Data type: PPET4_PPEHDR_TABOptional: No
Call by Reference: Yes
ET_PHANTOM_OBJ_HIGH -
Data type: PPET4_PPEOBJ_TABOptional: No
Call by Reference: Yes
ET_PHANTOM_REF -
Data type: PPET_GUID_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPEEXPL_GET_HDR 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_et_ppehdr_low | TYPE PPET4_PPEHDR_TAB, " | |||
| lv_iv_msg_handling | TYPE PPET_MSG_OPT, " 'A' | |||
| lv_et_ppehdr_high | TYPE PPET4_PPEHDR_TAB, " | |||
| lv_iv_msg_context | TYPE PPE_MSG_CONTEXT, " | |||
| lv_is_posvid | TYPE PPET_POSVID_LI, " | |||
| lv_et_ppeobj_high | TYPE PPET4_PPEOBJ_TAB, " | |||
| lv_iv_cmpid | TYPE PVCMPD-CMPID, " | |||
| lv_et_phantom_hdr_high | TYPE PPET4_PPEHDR_TAB, " | |||
| lv_iv_focusid | TYPE PPFOC_PFOCID-PFGUID, " | |||
| lv_et_phantom_obj_high | TYPE PPET4_PPEOBJ_TAB, " | |||
| lv_et_phantom_ref | TYPE PPET_GUID_TAB, " | |||
| lv_iv_upper_hdr_only | TYPE C, " PPET_FALSE | |||
| lv_iv_own_hdr_only | TYPE C, " PPET_FALSE | |||
| lv_iv_bypass_libuffer | TYPE C. " PPET_FALSE |
|   CALL FUNCTION 'PPEEXPL_GET_HDR' "NOTRANSL: Suche der Einstiege für die Planungsvormerkung |
| EXPORTING | ||
| IV_MSG_HANDLING | = lv_iv_msg_handling | |
| IV_MSG_CONTEXT | = lv_iv_msg_context | |
| IS_POSVID | = lv_is_posvid | |
| IV_CMPID | = lv_iv_cmpid | |
| IV_FOCUSID | = lv_iv_focusid | |
| IV_UPPER_HDR_ONLY | = lv_iv_upper_hdr_only | |
| IV_OWN_HDR_ONLY | = lv_iv_own_hdr_only | |
| IV_BYPASS_LIBUFFER | = lv_iv_bypass_libuffer | |
| IMPORTING | ||
| ET_PPEHDR_LOW | = lv_et_ppehdr_low | |
| ET_PPEHDR_HIGH | = lv_et_ppehdr_high | |
| ET_PPEOBJ_HIGH | = lv_et_ppeobj_high | |
| ET_PHANTOM_HDR_HIGH | = lv_et_phantom_hdr_high | |
| ET_PHANTOM_OBJ_HIGH | = lv_et_phantom_obj_high | |
| ET_PHANTOM_REF | = lv_et_phantom_ref | |
| . " PPEEXPL_GET_HDR | ||
ABAP code using 7.40 inline data declarations to call FM PPEEXPL_GET_HDR
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_handling) | = 'A'. | |||
| "SELECT single CMPID FROM PVCMPD INTO @DATA(ld_iv_cmpid). | ||||
| "SELECT single PFGUID FROM PPFOC_PFOCID INTO @DATA(ld_iv_focusid). | ||||
| DATA(ld_iv_upper_hdr_only) | = PPET_FALSE. | |||
| DATA(ld_iv_own_hdr_only) | = PPET_FALSE. | |||
| DATA(ld_iv_bypass_libuffer) | = PPET_FALSE. | |||
Search for further information about these or an SAP related objects