SAP ISU_S_PAYSCHEME_AUTO_CREATE Function Module for Create Payment Scheme from Move-In/Out









ISU_S_PAYSCHEME_AUTO_CREATE is a standard isu s payscheme auto create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Payment Scheme from Move-In/Out 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 payscheme auto create FM, simply by entering the name ISU_S_PAYSCHEME_AUTO_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_S_PAYSCHEME_AUTO_CREATE 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_PAYSCHEME_AUTO_CREATE'"Create Payment Scheme from Move-In/Out
EXPORTING
X_EDATUM = "Collection Date
* X_CREATION_TYPE = "Creation type: budget billing plan

IMPORTING
Y_DB_UPDATE = "Database Updated (X) or not (' ')

TABLES
* XT_EVER = "IS-U Contract
* XT_VERTRAG = "Contract
YT_EABP = "

EXCEPTIONS
EXISTING = 1 FOREIGN_LOCK = 2 INPUT_ERROR = 3 SYSTEM_ERROR = 4 BILLING_ERROR = 5 NOT_AUTHORIZED = 6 TERMINATED = 7
.



IMPORTING Parameters details for ISU_S_PAYSCHEME_AUTO_CREATE

X_EDATUM - Collection Date

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

X_CREATION_TYPE - Creation type: budget billing plan

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

EXPORTING Parameters details for ISU_S_PAYSCHEME_AUTO_CREATE

Y_DB_UPDATE - Database Updated (X) or not (SPACE)

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

TABLES Parameters details for ISU_S_PAYSCHEME_AUTO_CREATE

XT_EVER - IS-U Contract

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

XT_VERTRAG - Contract

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

YT_EABP -

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

EXCEPTIONS details

EXISTING -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BILLING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: Yes

TERMINATED - Processing Terminated

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_S_PAYSCHEME_AUTO_CREATE 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:
lt_xt_ever  TYPE STANDARD TABLE OF EVER, "   
lv_existing  TYPE EVER, "   
lv_x_edatum  TYPE DATUM, "   
lv_y_db_update  TYPE REGEN-DB_UPDATE, "   
lt_xt_vertrag  TYPE STANDARD TABLE OF EVERTRAG, "   
lv_foreign_lock  TYPE EVERTRAG, "   
lv_x_creation_type  TYPE EABP-ART, "   
lt_yt_eabp  TYPE STANDARD TABLE OF EABP, "   
lv_input_error  TYPE EABP, "   
lv_system_error  TYPE EABP, "   
lv_billing_error  TYPE EABP, "   
lv_not_authorized  TYPE EABP, "   
lv_terminated  TYPE EABP. "   

  CALL FUNCTION 'ISU_S_PAYSCHEME_AUTO_CREATE'  "Create Payment Scheme from Move-In/Out
    EXPORTING
         X_EDATUM = lv_x_edatum
         X_CREATION_TYPE = lv_x_creation_type
    IMPORTING
         Y_DB_UPDATE = lv_y_db_update
    TABLES
         XT_EVER = lt_xt_ever
         XT_VERTRAG = lt_xt_vertrag
         YT_EABP = lt_yt_eabp
    EXCEPTIONS
        EXISTING = 1
        FOREIGN_LOCK = 2
        INPUT_ERROR = 3
        SYSTEM_ERROR = 4
        BILLING_ERROR = 5
        NOT_AUTHORIZED = 6
        TERMINATED = 7
. " ISU_S_PAYSCHEME_AUTO_CREATE




ABAP code using 7.40 inline data declarations to call FM ISU_S_PAYSCHEME_AUTO_CREATE

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 DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update).
 
 
 
"SELECT single ART FROM EABP INTO @DATA(ld_x_creation_type).
 
 
 
 
 
 
 


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!