SAP ISU_PAYSCHEME_REQUEST_VKONT_CR Function Module for INTERNAL: Generate Request Lines per Contract Account









ISU_PAYSCHEME_REQUEST_VKONT_CR is a standard isu payscheme request vkont cr 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: Generate Request Lines per Contract Account 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 payscheme request vkont cr FM, simply by entering the name ISU_PAYSCHEME_REQUEST_VKONT_CR into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_PAYSCHEME_REQUEST_VKONT_CR 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_PAYSCHEME_REQUEST_VKONT_CR'"INTERNAL: Generate Request Lines per Contract Account
  EXPORTING
   X_DATE_FROM =  "Date
   X_DATE_TO =  "Date
   X_MASS_RUN =  "Checkbox

CHANGING
   XY_OBJ =  "
   XY_NO_LIN_CRT =  "Checkbox

TABLES
   XT_TE305 =  "Transactions for Company Code and Division
   XT_TE638 =  "Payment Scheme Category
   XYT_OPBEL =  "Transfer Structure: Document Number for Invoicing

EXCEPTIONS
   DATA_ERROR = 1    INPUT_ERROR = 2    CUST_ERROR = 3    SYSTEM_ERROR = 4
.



IMPORTING Parameters details for ISU_PAYSCHEME_REQUEST_VKONT_CR

X_DATE_FROM - Date

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

X_DATE_TO - Date

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

X_MASS_RUN - Checkbox

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

CHANGING Parameters details for ISU_PAYSCHEME_REQUEST_VKONT_CR

XY_OBJ -

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

XY_NO_LIN_CRT - Checkbox

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

TABLES Parameters details for ISU_PAYSCHEME_REQUEST_VKONT_CR

XT_TE305 - Transactions for Company Code and Division

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

XT_TE638 - Payment Scheme Category

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

XYT_OPBEL - Transfer Structure: Document Number for Invoicing

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

EXCEPTIONS details

DATA_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CUST_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_PAYSCHEME_REQUEST_VKONT_CR 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_xy_obj  TYPE ISU25_PAYMENTSCHEME, "   
lt_xt_te305  TYPE STANDARD TABLE OF TE305, "   
lv_data_error  TYPE TE305, "   
lv_x_date_from  TYPE DATUM, "   
lt_xt_te638  TYPE STANDARD TABLE OF TE638, "   
lv_x_date_to  TYPE DATUM, "   
lv_input_error  TYPE DATUM, "   
lv_xy_no_lin_crt  TYPE KENNZX_KK, "   
lt_xyt_opbel  TYPE STANDARD TABLE OF INV_OPBEL, "   
lv_cust_error  TYPE INV_OPBEL, "   
lv_x_mass_run  TYPE KENNZX_KK, "   
lv_system_error  TYPE KENNZX_KK. "   

  CALL FUNCTION 'ISU_PAYSCHEME_REQUEST_VKONT_CR'  "INTERNAL: Generate Request Lines per Contract Account
    EXPORTING
         X_DATE_FROM = lv_x_date_from
         X_DATE_TO = lv_x_date_to
         X_MASS_RUN = lv_x_mass_run
    CHANGING
         XY_OBJ = lv_xy_obj
         XY_NO_LIN_CRT = lv_xy_no_lin_crt
    TABLES
         XT_TE305 = lt_xt_te305
         XT_TE638 = lt_xt_te638
         XYT_OPBEL = lt_xyt_opbel
    EXCEPTIONS
        DATA_ERROR = 1
        INPUT_ERROR = 2
        CUST_ERROR = 3
        SYSTEM_ERROR = 4
. " ISU_PAYSCHEME_REQUEST_VKONT_CR




ABAP code using 7.40 inline data declarations to call FM ISU_PAYSCHEME_REQUEST_VKONT_CR

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



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!