SAP ISU_O_ACCOUNT_ACTION Function Module for INTERNAL: Subscreen Actions

Search SAP Function Modules

ISU_O_ACCOUNT_ACTION is a standard isu o account action 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: Subscreen Actions 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 action FM, simply by entering the name ISU_O_ACCOUNT_ACTION 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_ACTION 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_ACTION'"INTERNAL: Subscreen Actions
  EXPORTING
   X_OKCODE =  "OK Code (from IEOKCODE)
*  X_NO_CLOSE =  "
*  X_NO_MESSAGE =  "Indicator: Do Not Print Message (SAVE)
*  X_OTHER_ACCOUNT =  "

 IMPORTING
   Y_NEW_ACC =  "
   Y_FKKVKP1 =  "
   Y_FKKVK =  "Contract Account

CHANGING
   XY_OBJ =  "Contract account data

TABLES
*  TY_FKKVKP =  "Contract Account
*  XT_NEW_CONTRACTS =  "Structure for Contract (Front Office)

EXCEPTIONS
   CANCELLED = 1    FAILED = 2    ACTION_NOT_SUPPORTED = 3 

.

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_ACTION

X_OKCODE - OK Code (from IEOKCODE)

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

X_NO_CLOSE -

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

X_NO_MESSAGE - Indicator: Do Not Print Message (SAVE)

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

X_OTHER_ACCOUNT -

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

EXPORTING Parameters details for ISU_O_ACCOUNT_ACTION

Y_NEW_ACC -

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

Y_FKKVKP1 -

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

Y_FKKVK - Contract Account

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

CHANGING Parameters details for ISU_O_ACCOUNT_ACTION

XY_OBJ - Contract account data

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

TABLES Parameters details for ISU_O_ACCOUNT_ACTION

TY_FKKVKP - Contract Account

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

XT_NEW_CONTRACTS - Structure for Contract (Front Office)

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

EXCEPTIONS details

CANCELLED - Action terminated by the user

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

FAILED -

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

ACTION_NOT_SUPPORTED -

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

Copy and paste ABAP code example for ISU_O_ACCOUNT_ACTION 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.

ABAP code using 7.40 inline data declarations to call FM ISU_O_ACCOUNT_ACTION

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