SAP ISU_PRDOC_PROCESS Function Module for Process Parked Document









ISU_PRDOC_PROCESS is a standard isu prdoc process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Process Parked Document 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 isu prdoc process FM, simply by entering the name ISU_PRDOC_PROCESS into the relevant SAP transaction such as SE37 or SE38.

Function Group: EC70M
Program Name: SAPLEC70M
Main Program: SAPLEC70M
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ISU_PRDOC_PROCESS 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 'ISU_PRDOC_PROCESS'"Process Parked Document
EXPORTING
X_ECAMIOPR_COMPL = "IS-U Parked Document: Complete Data
* X_MI = "Indicator
* X_MO = "Indicator
* X_BUPA = "Indicator

IMPORTING
Y_ECAMIOPR_COMPL = "IS-U Parked Document: Complete Data
Y_MDG_SUCCESSFUL = "Indicator
.



IMPORTING Parameters details for ISU_PRDOC_PROCESS

X_ECAMIOPR_COMPL - IS-U Parked Document: Complete Data

Data type: ECAMIOPR_COMPL
Optional: No
Call by Reference: No ( called with pass by value option)

X_MI - Indicator

Data type: KENNZX
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_MO - Indicator

Data type: KENNZX
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_BUPA - Indicator

Data type: KENNZX
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_PRDOC_PROCESS

Y_ECAMIOPR_COMPL - IS-U Parked Document: Complete Data

Data type: ECAMIOPR_COMPL
Optional: No
Call by Reference: No ( called with pass by value option)

Y_MDG_SUCCESSFUL - Indicator

Data type: KENNZX
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_PRDOC_PROCESS 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_x_ecamiopr_compl  TYPE ECAMIOPR_COMPL, "   
lv_y_ecamiopr_compl  TYPE ECAMIOPR_COMPL, "   
lv_x_mi  TYPE KENNZX, "   
lv_y_mdg_successful  TYPE KENNZX, "   
lv_x_mo  TYPE KENNZX, "   
lv_x_bupa  TYPE KENNZX. "   

  CALL FUNCTION 'ISU_PRDOC_PROCESS'  "Process Parked Document
    EXPORTING
         X_ECAMIOPR_COMPL = lv_x_ecamiopr_compl
         X_MI = lv_x_mi
         X_MO = lv_x_mo
         X_BUPA = lv_x_bupa
    IMPORTING
         Y_ECAMIOPR_COMPL = lv_y_ecamiopr_compl
         Y_MDG_SUCCESSFUL = lv_y_mdg_successful
. " ISU_PRDOC_PROCESS




ABAP code using 7.40 inline data declarations to call FM ISU_PRDOC_PROCESS

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.

 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!