SAP ISU_M_EQUI_INSERT Function Module for INTERNAL: IS-U Migration: Create Equipment

Search SAP Function Modules

ISU_M_EQUI_INSERT is a standard isu m equi insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: IS-U Migration: Create Equipment 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 m equi insert FM, simply by entering the name ISU_M_EQUI_INSERT into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_M_EQUI_INSERT 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_M_EQUI_INSERT'"INTERNAL: IS-U Migration: Create Equipment
  EXPORTING
*  X_CONV = 'X' "Indicator for (ALPHA, MATN1) Conversion
*  X_INDIV = 'X' "Always Maintain Changed Fields Individually
*  X_UPDATE = 'X' "Write Update Record for Commit
*  X_DIRECT = 'X' "Update Record Direct or in Update Task
*  X_COMMIT = ' ' "Commit Modus ('X' async, 'S' sync, else none)m

 IMPORTING
   Y_UPDATE =  "

CHANGING
   X_AUTO =  "

EXCEPTIONS
   ERR_INSERT = 1    ERR_FUBA = 2 

.

IMPORTING Parameters details for ISU_M_EQUI_INSERT

X_CONV - Indicator for (ALPHA, MATN1) Conversion

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

X_INDIV - Always Maintain Changed Fields Individually

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

X_UPDATE - Write Update Record for Commit

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

X_DIRECT - Update Record Direct or in Update Task

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

X_COMMIT - Commit Modus ('X' async, 'S' sync, else none)m

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_M_EQUI_INSERT

Y_UPDATE -

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

CHANGING Parameters details for ISU_M_EQUI_INSERT

X_AUTO -

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

EXCEPTIONS details

ERR_INSERT -

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

ERR_FUBA -

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

Copy and paste ABAP code example for ISU_M_EQUI_INSERT 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.

ABAP code using 7.40 inline data declarations to call FM ISU_M_EQUI_INSERT

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