SAP ISU_SUPPLAC_SWITCH Function Module for









ISU_SUPPLAC_SWITCH is a standard isu supplac switch 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 supplac switch FM, simply by entering the name ISU_SUPPLAC_SWITCH into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_SUPPLAC_SWITCH 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_SUPPLAC_SWITCH'"
EXPORTING
* X_NO_DIALOG = 'X' "
* X_SSWTCREASON = ' ' "
* X_ACCOUNT = "

IMPORTING
Y_DB_UPDATE = "
Y_EINZBELEG = "
Y_AUSZBELEG = "

TABLES
TXY_CONTRACT = "

EXCEPTIONS
EXISTING = 1 FOREIGN_LOCK = 2 NUMBER_ERROR = 3 GENERAL_FAULT = 4 INVALID_KEY = 5 PARAM_ERROR = 6 INPUT_ERROR = 7 NOT_AUTHORIZED = 8 ACTION_FAILED = 9
.



IMPORTING Parameters details for ISU_SUPPLAC_SWITCH

X_NO_DIALOG -

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

X_SSWTCREASON -

Data type: EAUS-SSWTCREASON
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_ACCOUNT -

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

EXPORTING Parameters details for ISU_SUPPLAC_SWITCH

Y_DB_UPDATE -

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

Y_EINZBELEG -

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

Y_AUSZBELEG -

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

TABLES Parameters details for ISU_SUPPLAC_SWITCH

TXY_CONTRACT -

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

EXCEPTIONS details

EXISTING -

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

FOREIGN_LOCK -

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

NUMBER_ERROR -

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

GENERAL_FAULT -

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

INVALID_KEY -

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

PARAM_ERROR -

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

INPUT_ERROR -

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

NOT_AUTHORIZED -

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

ACTION_FAILED -

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

Copy and paste ABAP code example for ISU_SUPPLAC_SWITCH 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_existing  TYPE STRING, "   
lv_x_no_dialog  TYPE STRING, "   'X'
lv_y_db_update  TYPE REGEN-DB_UPDATE, "   
lt_txy_contract  TYPE STANDARD TABLE OF EVERSW, "   
lv_y_einzbeleg  TYPE EEIN-EINZBELEG, "   
lv_foreign_lock  TYPE EEIN, "   
lv_x_sswtcreason  TYPE EAUS-SSWTCREASON, "   SPACE
lv_x_account  TYPE VKONT_KK, "   
lv_y_auszbeleg  TYPE EAUS-AUSZBELEG, "   
lv_number_error  TYPE EAUS, "   
lv_general_fault  TYPE EAUS, "   
lv_invalid_key  TYPE EAUS, "   
lv_param_error  TYPE EAUS, "   
lv_input_error  TYPE EAUS, "   
lv_not_authorized  TYPE EAUS, "   
lv_action_failed  TYPE EAUS. "   

  CALL FUNCTION 'ISU_SUPPLAC_SWITCH'  "
    EXPORTING
         X_NO_DIALOG = lv_x_no_dialog
         X_SSWTCREASON = lv_x_sswtcreason
         X_ACCOUNT = lv_x_account
    IMPORTING
         Y_DB_UPDATE = lv_y_db_update
         Y_EINZBELEG = lv_y_einzbeleg
         Y_AUSZBELEG = lv_y_auszbeleg
    TABLES
         TXY_CONTRACT = lt_txy_contract
    EXCEPTIONS
        EXISTING = 1
        FOREIGN_LOCK = 2
        NUMBER_ERROR = 3
        GENERAL_FAULT = 4
        INVALID_KEY = 5
        PARAM_ERROR = 6
        INPUT_ERROR = 7
        NOT_AUTHORIZED = 8
        ACTION_FAILED = 9
. " ISU_SUPPLAC_SWITCH




ABAP code using 7.40 inline data declarations to call FM ISU_SUPPLAC_SWITCH

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.

 
DATA(ld_x_no_dialog) = 'X'.
 
"SELECT single DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update).
 
 
"SELECT single EINZBELEG FROM EEIN INTO @DATA(ld_y_einzbeleg).
 
 
"SELECT single SSWTCREASON FROM EAUS INTO @DATA(ld_x_sswtcreason).
DATA(ld_x_sswtcreason) = ' '.
 
 
"SELECT single AUSZBELEG FROM EAUS INTO @DATA(ld_y_auszbeleg).
 
 
 
 
 
 
 
 


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!