SAP ISU_PRODUCT_IMPLEMENT Function Module for Process Master Data Template









ISU_PRODUCT_IMPLEMENT is a standard isu product implement 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 Master Data Template 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 product implement FM, simply by entering the name ISU_PRODUCT_IMPLEMENT into the relevant SAP transaction such as SE37 or SE38.

Function Group: EPRODCUST
Program Name: SAPLEPRODCUST
Main Program: SAPLEPRODCUST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_PRODUCT_IMPLEMENT 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_PRODUCT_IMPLEMENT'"Process Master Data Template
  EXPORTING
   X_PRODID =  "Product description nodes
*  X_CONTAINER =  "Parameter container
*  X_RAISE_NO_EVENT =  "
*  X_NO_BPCONTACT =  "
*  X_CONTRACTDATA =  "MDG: Transfer Structure for CRM Contract Items to IS-U
*  X_NO_ENV_SELECT =  "
*  X_INDUSTRY =  "Industry Sector (MDG)

 IMPORTING
   Y_LOGID =  "GUID in 'CHAR' Format in Uppercase
   Y_SCRIPT_INFO_TAB =  "Standard Table for Structure ISU_SCRIPT_INFO
   Y_IDE_STARTED =  "
   Y_MDG_COMPLETED =  "

CHANGING
*  XY_NEW_KEYS_TAB =  "Standard Table for ISU_PROD_NEWOBJECT_KEYS
*  XY_DONE_NODE_TAB =  "Table of Template Node keys

EXCEPTIONS
   GENERAL_FAULT = 1    INPUT_ERROR = 2    AMBIGUOUS_ENVIRONMENT = 3
.



IMPORTING Parameters details for ISU_PRODUCT_IMPLEMENT

X_PRODID - Product description nodes

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

X_CONTAINER - Parameter container

Data type: CCMCONT_T
Optional: Yes
Call by Reference: Yes

X_RAISE_NO_EVENT -

Data type: EBA_FLAG
Optional: Yes
Call by Reference: Yes

X_NO_BPCONTACT -

Data type: EBA_FLAG
Optional: Yes
Call by Reference: Yes

X_CONTRACTDATA - MDG: Transfer Structure for CRM Contract Items to IS-U

Data type: ANY
Optional: Yes
Call by Reference: Yes

X_NO_ENV_SELECT -

Data type: EBA_FLAG
Optional: Yes
Call by Reference: Yes

X_INDUSTRY - Industry Sector (MDG)

Data type: EMDGEN_INDUSTRY
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_PRODUCT_IMPLEMENT

Y_LOGID - GUID in 'CHAR' Format in Uppercase

Data type: GUID_32
Optional: No
Call by Reference: Yes

Y_SCRIPT_INFO_TAB - Standard Table for Structure ISU_SCRIPT_INFO

Data type: ISU_SCRIPT_INFO_TAB
Optional: No
Call by Reference: Yes

Y_IDE_STARTED -

Data type: EBA_FLAG
Optional: No
Call by Reference: Yes

Y_MDG_COMPLETED -

Data type: EBA_FLAG
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ISU_PRODUCT_IMPLEMENT

XY_NEW_KEYS_TAB - Standard Table for ISU_PROD_NEWOBJECT_KEYS

Data type: ISU_PROD_NEWOBJECT_KEYS_TAB
Optional: Yes
Call by Reference: Yes

XY_DONE_NODE_TAB - Table of Template Node keys

Data type: ISU_EPDNODE_TAB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

GENERAL_FAULT -

Data type:
Optional: No
Call by Reference: Yes

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

AMBIGUOUS_ENVIRONMENT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_PRODUCT_IMPLEMENT 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_logid  TYPE GUID_32, "   
lv_x_prodid  TYPE EPD_PRODID, "   
lv_general_fault  TYPE EPD_PRODID, "   
lv_xy_new_keys_tab  TYPE ISU_PROD_NEWOBJECT_KEYS_TAB, "   
lv_input_error  TYPE ISU_PROD_NEWOBJECT_KEYS_TAB, "   
lv_x_container  TYPE CCMCONT_T, "   
lv_xy_done_node_tab  TYPE ISU_EPDNODE_TAB, "   
lv_y_script_info_tab  TYPE ISU_SCRIPT_INFO_TAB, "   
lv_y_ide_started  TYPE EBA_FLAG, "   
lv_x_raise_no_event  TYPE EBA_FLAG, "   
lv_ambiguous_environment  TYPE EBA_FLAG, "   
lv_x_no_bpcontact  TYPE EBA_FLAG, "   
lv_y_mdg_completed  TYPE EBA_FLAG, "   
lv_x_contractdata  TYPE ANY, "   
lv_x_no_env_select  TYPE EBA_FLAG, "   
lv_x_industry  TYPE EMDGEN_INDUSTRY. "   

  CALL FUNCTION 'ISU_PRODUCT_IMPLEMENT'  "Process Master Data Template
    EXPORTING
         X_PRODID = lv_x_prodid
         X_CONTAINER = lv_x_container
         X_RAISE_NO_EVENT = lv_x_raise_no_event
         X_NO_BPCONTACT = lv_x_no_bpcontact
         X_CONTRACTDATA = lv_x_contractdata
         X_NO_ENV_SELECT = lv_x_no_env_select
         X_INDUSTRY = lv_x_industry
    IMPORTING
         Y_LOGID = lv_y_logid
         Y_SCRIPT_INFO_TAB = lv_y_script_info_tab
         Y_IDE_STARTED = lv_y_ide_started
         Y_MDG_COMPLETED = lv_y_mdg_completed
    CHANGING
         XY_NEW_KEYS_TAB = lv_xy_new_keys_tab
         XY_DONE_NODE_TAB = lv_xy_done_node_tab
    EXCEPTIONS
        GENERAL_FAULT = 1
        INPUT_ERROR = 2
        AMBIGUOUS_ENVIRONMENT = 3
. " ISU_PRODUCT_IMPLEMENT




ABAP code using 7.40 inline data declarations to call FM ISU_PRODUCT_IMPLEMENT

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!