SAP SRS_PDC_GR_DATA_PREP Function Module for Retail Store: MDE Goods Receipt: Download
SRS_PDC_GR_DATA_PREP is a standard srs pdc gr data prep SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retail Store: MDE Goods Receipt: Download 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 srs pdc gr data prep FM, simply by entering the name SRS_PDC_GR_DATA_PREP into the relevant SAP transaction such as SE37 or SE38.
Function Group: WOSE_PDC_OUT
Program Name: SAPLWOSE_PDC_OUT
Main Program: SAPLWOSE_PDC_OUT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SRS_PDC_GR_DATA_PREP 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 'SRS_PDC_GR_DATA_PREP'"Retail Store: MDE Goods Receipt: Download.
EXPORTING
* PARALLEL = "Indicator: Parallel processing yes/no
* REF_DOC_NO = "Reference Document Number
I_EXIT_PDC_GR_OUT = "BAdI Interface IF_EX_SRS_PDC_GM_OUTBOUND
BADI_IMP_ACTIV = "BAdI activ
* MAX_PROZESS = "Maximum number of parallel tasks
* SERVERGRP = "Name of Logon/Server Group for Parallel Processing
* DATE1 = "Goods Receipt Date
* DATE2 = "Goods Receipt Date
* PURORDER = "Reference Document Type
* MATDOC = "Reference Document Type
* DELIVERY = "Reference Document Type
* HANDUNIT = "Reference Document Type
TABLES
P_T_PLANT = "Formatted Plants
RETURN = "Return Parameter(s)
IMPORTING Parameters details for SRS_PDC_GR_DATA_PREP
PARALLEL - Indicator: Parallel processing yes/no
Data type: BDFIELDS-PARALLELOptional: Yes
Call by Reference: Yes
REF_DOC_NO - Reference Document Number
Data type: XBLNROptional: Yes
Call by Reference: Yes
I_EXIT_PDC_GR_OUT - BAdI Interface IF_EX_SRS_PDC_GM_OUTBOUND
Data type: IF_EX_SRS_PDC_GR_OUTBOUNDOptional: No
Call by Reference: Yes
BADI_IMP_ACTIV - BAdI activ
Data type: CHAR1Optional: No
Call by Reference: Yes
MAX_PROZESS - Maximum number of parallel tasks
Data type: SRS_PDC_HELP-SRS_ANZPPOptional: Yes
Call by Reference: Yes
SERVERGRP - Name of Logon/Server Group for Parallel Processing
Data type: WPSTRUC-SERVERGRPOptional: Yes
Call by Reference: Yes
DATE1 - Goods Receipt Date
Data type: SRS_WEDATOptional: Yes
Call by Reference: Yes
DATE2 - Goods Receipt Date
Data type: SRS_WEDATOptional: Yes
Call by Reference: Yes
PURORDER - Reference Document Type
Data type: SRS_DOCUMENTOptional: Yes
Call by Reference: Yes
MATDOC - Reference Document Type
Data type: SRS_DOCUMENTOptional: Yes
Call by Reference: Yes
DELIVERY - Reference Document Type
Data type: SRS_DOCUMENTOptional: Yes
Call by Reference: Yes
HANDUNIT - Reference Document Type
Data type: SRS_DOCUMENTOptional: Yes
Call by Reference: Yes
TABLES Parameters details for SRS_PDC_GR_DATA_PREP
P_T_PLANT - Formatted Plants
Data type: SRS_PDC_PLANTOptional: No
Call by Reference: Yes
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SRS_PDC_GR_DATA_PREP 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_parallel | TYPE BDFIELDS-PARALLEL, " | |||
| lt_p_t_plant | TYPE STANDARD TABLE OF SRS_PDC_PLANT, " | |||
| lv_ref_doc_no | TYPE XBLNR, " | |||
| lv_i_exit_pdc_gr_out | TYPE IF_EX_SRS_PDC_GR_OUTBOUND, " | |||
| lv_badi_imp_activ | TYPE CHAR1, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_max_prozess | TYPE SRS_PDC_HELP-SRS_ANZPP, " | |||
| lv_servergrp | TYPE WPSTRUC-SERVERGRP, " | |||
| lv_date1 | TYPE SRS_WEDAT, " | |||
| lv_date2 | TYPE SRS_WEDAT, " | |||
| lv_purorder | TYPE SRS_DOCUMENT, " | |||
| lv_matdoc | TYPE SRS_DOCUMENT, " | |||
| lv_delivery | TYPE SRS_DOCUMENT, " | |||
| lv_handunit | TYPE SRS_DOCUMENT. " |
|   CALL FUNCTION 'SRS_PDC_GR_DATA_PREP' "Retail Store: MDE Goods Receipt: Download |
| EXPORTING | ||
| PARALLEL | = lv_parallel | |
| REF_DOC_NO | = lv_ref_doc_no | |
| I_EXIT_PDC_GR_OUT | = lv_i_exit_pdc_gr_out | |
| BADI_IMP_ACTIV | = lv_badi_imp_activ | |
| MAX_PROZESS | = lv_max_prozess | |
| SERVERGRP | = lv_servergrp | |
| DATE1 | = lv_date1 | |
| DATE2 | = lv_date2 | |
| PURORDER | = lv_purorder | |
| MATDOC | = lv_matdoc | |
| DELIVERY | = lv_delivery | |
| HANDUNIT | = lv_handunit | |
| TABLES | ||
| P_T_PLANT | = lt_p_t_plant | |
| RETURN | = lt_return | |
| . " SRS_PDC_GR_DATA_PREP | ||
ABAP code using 7.40 inline data declarations to call FM SRS_PDC_GR_DATA_PREP
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 PARALLEL FROM BDFIELDS INTO @DATA(ld_parallel). | ||||
| "SELECT single SRS_ANZPP FROM SRS_PDC_HELP INTO @DATA(ld_max_prozess). | ||||
| "SELECT single SERVERGRP FROM WPSTRUC INTO @DATA(ld_servergrp). | ||||
Search for further information about these or an SAP related objects