SAP ISU_OPENING_DATA_UPDATE Function Module for INTERNAL: update of creation/change data ISU_ADMINL

Search SAP Function Modules

ISU_OPENING_DATA_UPDATE is a standard isu opening data update 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: update of creation/change data ISU_ADMINL 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 opening data update FM, simply by entering the name ISU_OPENING_DATA_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: EE00
Program Name: SAPLEE00
Main Program: SAPLEE00
Appliation area: E
Release date: 12-Oct-1995
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_OPENING_DATA_UPDATE 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_OPENING_DATA_UPDATE'"INTERNAL: update of creation/change data ISU_ADMINL
  EXPORTING
*  X_ERDAT =  "Creation date
*  X_ERZET =  "Time Created
*  X_ERNAM =  "Creation name
   X_UPD_MODE =  "Update Mode

 IMPORTING
   Y_ERDAT =  "Creation date
   Y_ERNAM =  "Creation name
   Y_ERZET =  "Time Created
   Y_AEDAT =  "Change date
   Y_AENAM =  "Changed by
   Y_AEZET =  "Time Last Change Was Made

EXCEPTIONS
   NOT_CHANGED = 1    MODUS_INCORRECT = 2 

.

IMPORTING Parameters details for ISU_OPENING_DATA_UPDATE

X_ERDAT - Creation date

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

X_ERZET - Time Created

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

X_ERNAM - Creation name

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

X_UPD_MODE - Update Mode

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

EXPORTING Parameters details for ISU_OPENING_DATA_UPDATE

Y_ERDAT - Creation date

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

Y_ERNAM - Creation name

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

Y_ERZET - Time Created

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

Y_AEDAT - Change date

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

Y_AENAM - Changed by

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

Y_AEZET - Time Last Change Was Made

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

EXCEPTIONS details

NOT_CHANGED - Data was not changed

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

MODUS_INCORRECT - Current update mode is not supported

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

Copy and paste ABAP code example for ISU_OPENING_DATA_UPDATE 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_OPENING_DATA_UPDATE

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