SAP ISU_PDSCR_NEWCUST Function Module for Script for Template Category NEWCUST
ISU_PDSCR_NEWCUST is a standard isu pdscr newcust SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Script for Template Category NEWCUST 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 pdscr newcust FM, simply by entering the name ISU_PDSCR_NEWCUST into the relevant SAP transaction such as SE37 or SE38.
Function Group: EPD_SCRIPT
Program Name: SAPLEPD_SCRIPT
Main Program: SAPLEPD_SCRIPT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_PDSCR_NEWCUST 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_PDSCR_NEWCUST'"Script for Template Category NEWCUST.
EXPORTING
X_REF_PROD = "
X_REF_NEW_KEYS = "
IMPORTING
Y_ERROR = "Art des Fehlers (E, W, ' ')
IMPORTING Parameters details for ISU_PDSCR_NEWCUST
X_REF_PROD -
Data type: IF_ISU_PROD_NODE_READOptional: No
Call by Reference: Yes
X_REF_NEW_KEYS -
Data type: CL_ISU_PRODSCRIPT_NEW_KEYSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_PDSCR_NEWCUST
Y_ERROR - Art des Fehlers (E, W, ' ')
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_PDSCR_NEWCUST 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_y_error | TYPE CHAR1, " | |||
| lv_x_ref_prod | TYPE IF_ISU_PROD_NODE_READ, " | |||
| lv_x_ref_new_keys | TYPE CL_ISU_PRODSCRIPT_NEW_KEYS. " |
|   CALL FUNCTION 'ISU_PDSCR_NEWCUST' "Script for Template Category NEWCUST |
| EXPORTING | ||
| X_REF_PROD | = lv_x_ref_prod | |
| X_REF_NEW_KEYS | = lv_x_ref_new_keys | |
| IMPORTING | ||
| Y_ERROR | = lv_y_error | |
| . " ISU_PDSCR_NEWCUST | ||
ABAP code using 7.40 inline data declarations to call FM ISU_PDSCR_NEWCUST
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