SAP ISU_O_ACCOUNT_INPUT Function Module for INTERNAL: Checks and Transfers Entries









ISU_O_ACCOUNT_INPUT is a standard isu o account input 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: Checks and Transfers Entries 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 o account input FM, simply by entering the name ISU_O_ACCOUNT_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_O_ACCOUNT_INPUT 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_O_ACCOUNT_INPUT'"INTERNAL: Checks and Transfers Entries
  EXPORTING
*  X_FULL_CHECK =  "
*  X_DATA =  "
*  X_USE_SCREEN_BUFFER = 'X' "
*  X_ADD_DATA =  "
*  X_BKVID =  "
*  X_CCARD_ID =  "
*  X_TAKE_AUTO =  "Indicator

 IMPORTING
   Y_MSGTYPE =  "
   Y_BANK_CCARD_OKAY =  "

CHANGING
   XY_OBJ =  "Contract account data

EXCEPTIONS
   INPUT_ERROR = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLES37_030 Before PBO Customer Subscreen
EXIT_SAPLES37_031 After PAI Customer Subscreen

IMPORTING Parameters details for ISU_O_ACCOUNT_INPUT

X_FULL_CHECK -

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

X_DATA -

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

X_USE_SCREEN_BUFFER -

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

X_ADD_DATA -

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

X_BKVID -

Data type: BUS0BK-BKVID
Optional: Yes
Call by Reference: Yes

X_CCARD_ID -

Data type: BUS0CC_DI-CCARD_ID
Optional: Yes
Call by Reference: Yes

X_TAKE_AUTO - Indicator

Data type: REGEN-KENNZX
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_O_ACCOUNT_INPUT

Y_MSGTYPE -

Data type: SY-MSGTY
Optional: No
Call by Reference: Yes

Y_BANK_CCARD_OKAY -

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

CHANGING Parameters details for ISU_O_ACCOUNT_INPUT

XY_OBJ - Contract account data

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

EXCEPTIONS details

INPUT_ERROR - Entry is not allowed

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

Copy and paste ABAP code example for ISU_O_ACCOUNT_INPUT 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 ISU03_ACCOUNT, "   
lv_y_msgtype  TYPE SY-MSGTY, "   
lv_input_error  TYPE SY, "   
lv_x_full_check  TYPE REGEN-KENNZX, "   
lv_x_data  TYPE FKK20_ACCOUNT_AUTO, "   
lv_y_bank_ccard_okay  TYPE REGEN-KENNZX, "   
lv_x_use_screen_buffer  TYPE REGEN-KENNZX, "   'X'
lv_x_add_data  TYPE ISU03_ACCOUNT_TXJCD_DATA, "   
lv_x_bkvid  TYPE BUS0BK-BKVID, "   
lv_x_ccard_id  TYPE BUS0CC_DI-CCARD_ID, "   
lv_x_take_auto  TYPE REGEN-KENNZX. "   

  CALL FUNCTION 'ISU_O_ACCOUNT_INPUT'  "INTERNAL: Checks and Transfers Entries
    EXPORTING
         X_FULL_CHECK = lv_x_full_check
         X_DATA = lv_x_data
         X_USE_SCREEN_BUFFER = lv_x_use_screen_buffer
         X_ADD_DATA = lv_x_add_data
         X_BKVID = lv_x_bkvid
         X_CCARD_ID = lv_x_ccard_id
         X_TAKE_AUTO = lv_x_take_auto
    IMPORTING
         Y_MSGTYPE = lv_y_msgtype
         Y_BANK_CCARD_OKAY = lv_y_bank_ccard_okay
    CHANGING
         XY_OBJ = lv_xy_obj
    EXCEPTIONS
        INPUT_ERROR = 1
. " ISU_O_ACCOUNT_INPUT




ABAP code using 7.40 inline data declarations to call FM ISU_O_ACCOUNT_INPUT

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 MSGTY FROM SY INTO @DATA(ld_y_msgtype).
 
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_full_check).
 
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_y_bank_ccard_okay).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_use_screen_buffer).
DATA(ld_x_use_screen_buffer) = 'X'.
 
 
"SELECT single BKVID FROM BUS0BK INTO @DATA(ld_x_bkvid).
 
"SELECT single CCARD_ID FROM BUS0CC_DI INTO @DATA(ld_x_ccard_id).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_take_auto).
 


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!