SAP ISU_CHANGE_PREMISES Function Module for









ISU_CHANGE_PREMISES is a standard isu change premises SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 change premises FM, simply by entering the name ISU_CHANGE_PREMISES into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_CHANGE_PREMISES 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_CHANGE_PREMISES'"
EXPORTING
X_PREMISE_NEW = "
* X_ENQUEUE = "Single-Character Indicator

IMPORTING
Y_UPDATE_DONE = "Indicator: Change made

EXCEPTIONS
NOT_FOUND = 1 FOREIGN_LOCK = 2
.



IMPORTING Parameters details for ISU_CHANGE_PREMISES

X_PREMISE_NEW -

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

X_ENQUEUE - Single-Character Indicator

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

EXPORTING Parameters details for ISU_CHANGE_PREMISES

Y_UPDATE_DONE - Indicator: Change made

Data type: REGEN-CHANGED
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_CHANGE_PREMISES 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_not_found  TYPE STRING, "   
lv_x_premise_new  TYPE EVBS, "   
lv_y_update_done  TYPE REGEN-CHANGED, "   
lv_x_enqueue  TYPE CHAR1, "   
lv_foreign_lock  TYPE CHAR1. "   

  CALL FUNCTION 'ISU_CHANGE_PREMISES'  "
    EXPORTING
         X_PREMISE_NEW = lv_x_premise_new
         X_ENQUEUE = lv_x_enqueue
    IMPORTING
         Y_UPDATE_DONE = lv_y_update_done
    EXCEPTIONS
        NOT_FOUND = 1
        FOREIGN_LOCK = 2
. " ISU_CHANGE_PREMISES




ABAP code using 7.40 inline data declarations to call FM ISU_CHANGE_PREMISES

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.

 
 
"SELECT single CHANGED FROM REGEN INTO @DATA(ld_y_update_done).
 
 
 


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!