SAP ISU_S_CONTRACT_CHANGE_REMOTE Function Module for INTERNAL: Change a Contract (Including COMMIT)









ISU_S_CONTRACT_CHANGE_REMOTE is a standard isu s contract change remote 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: Change a Contract (Including COMMIT) 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 s contract change remote FM, simply by entering the name ISU_S_CONTRACT_CHANGE_REMOTE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ISU_IL_BICO_REMOTE
Program Name: SAPLISU_IL_BICO_REMOTE
Main Program: SAPLISU_IL_BICO_REMOTE
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ISU_S_CONTRACT_CHANGE_REMOTE 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_S_CONTRACT_CHANGE_REMOTE'"INTERNAL: Change a Contract (Including COMMIT)
  EXPORTING
   X_VERTRAG =  "Contract Number
*  X_UPD_ONLINE =  "Indicator: Update Online
*  X_NO_DIALOG =  "Indicator: no dialog
*  X_USE_BAPIEVERX =  "Indicator
*  X_BAPIISUCONTRACT =  "IS-U contract: general fields
*  X_BAPIISUCONTRACTX =  "IS-U contract: general fields

 IMPORTING
   YT_RETURN =  "Return parameter table
   Y_ERROR =  "Indicators
.



IMPORTING Parameters details for ISU_S_CONTRACT_CHANGE_REMOTE

X_VERTRAG - Contract Number

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

X_UPD_ONLINE - Indicator: Update Online

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

X_NO_DIALOG - Indicator: no dialog

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

X_USE_BAPIEVERX - Indicator

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

X_BAPIISUCONTRACT - IS-U contract: general fields

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

X_BAPIISUCONTRACTX - IS-U contract: general fields

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

EXPORTING Parameters details for ISU_S_CONTRACT_CHANGE_REMOTE

YT_RETURN - Return parameter table

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

Y_ERROR - Indicators

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

Copy and paste ABAP code example for ISU_S_CONTRACT_CHANGE_REMOTE 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_x_vertrag  TYPE EVER-VERTRAG, "   
lv_yt_return  TYPE BAPIRET2_T, "   
lv_y_error  TYPE KENNZX, "   
lv_x_upd_online  TYPE REGEN-UPD_ONLINE, "   
lv_x_no_dialog  TYPE REGEN-NO_DIALOG, "   
lv_x_use_bapieverx  TYPE KENNZX, "   
lv_x_bapiisucontract  TYPE BAPIISUCONTRACT, "   
lv_x_bapiisucontractx  TYPE BAPIISUCONTRACTX. "   

  CALL FUNCTION 'ISU_S_CONTRACT_CHANGE_REMOTE'  "INTERNAL: Change a Contract (Including COMMIT)
    EXPORTING
         X_VERTRAG = lv_x_vertrag
         X_UPD_ONLINE = lv_x_upd_online
         X_NO_DIALOG = lv_x_no_dialog
         X_USE_BAPIEVERX = lv_x_use_bapieverx
         X_BAPIISUCONTRACT = lv_x_bapiisucontract
         X_BAPIISUCONTRACTX = lv_x_bapiisucontractx
    IMPORTING
         YT_RETURN = lv_yt_return
         Y_ERROR = lv_y_error
. " ISU_S_CONTRACT_CHANGE_REMOTE




ABAP code using 7.40 inline data declarations to call FM ISU_S_CONTRACT_CHANGE_REMOTE

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 VERTRAG FROM EVER INTO @DATA(ld_x_vertrag).
 
 
 
"SELECT single UPD_ONLINE FROM REGEN INTO @DATA(ld_x_upd_online).
 
"SELECT single NO_DIALOG FROM REGEN INTO @DATA(ld_x_no_dialog).
 
 
 
 


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!