SAP EXIT_SAPLES37_030 Function Module for Before PBO Customer Subscreen

Search SAP Function Modules

EXIT_SAPLES37_030 is a standard exit saples37 030 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Before PBO Customer Subscreen 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 exit saples37 030 FM, simply by entering the name EXIT_SAPLES37_030 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLES37_030 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 'EXIT_SAPLES37_030'"Before PBO Customer Subscreen
  EXPORTING
   X_ACTIVE =  "Indicator Screen is Active
   X_DISPLAY =  "Indicator to Display Data
   X_FKKVK =  "Partner-Independent Data
   X_FKKVKP =  "Partner-Dependent Data
*  X_WMODE =  "

TABLES
*  TY_FIELDNAMES =  "Fields to be Hidden

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISU_ACCOUNT_FIELD_CHECK Check Field Names of Structure EHAU for Changability
ISU_O_ACCOUNT_ACTION INTERNAL: Subscreen Actions
ISU_O_ACCOUNT_CLOSE INTERNAL: Ends Processing of a Contract Account
ISU_O_ACCOUNT_INPUT INTERNAL: Checks and Transfers Entries
ISU_O_ACCOUNT_OPEN INTERNAL: Opens Processing of a Contract Account
ISU_O_ACCOUNT_PAI_AFTER INTERNAL: Closes the CALL SUBSCREEN PAI
ISU_O_ACCOUNT_PAI_BEFORE INTERNAL: Prepares the CALL SUBSCREEN PAI
ISU_O_ACCOUNT_PAI_MOD_BEFORE INTERNAL: Transfer Data to Contract Account Object Before FB PAI_BEFORE
ISU_O_ACCOUNT_PAI_MOD_SAVE INTERNAL: Transfer Business Partner to Contract Acct Object Before Saving
ISU_O_ACCOUNT_PBO INTERNAL: Prepares the CALL SUBSCREEN PBO
ISU_O_ACCOUNT_PREPARE_CLOSE INTERNAL: Prepares for Closing of Contract Account
ISU_S_ACCOUNT_CHANGE INTERNAL: Change Contract Account
ISU_S_ACCOUNT_CREATE INTERNAL: Create Contract Account
ISU_S_ACCOUNT_DISPLAY INTERNAL: Change Contract Account
ISU_S_ACCOUNT_PROVIDE INTERNAL: Prepare Partner for Processing
ISU_S_ACCOUNT_SAVEREPLICA INTERNAL: Create Contract Account

IMPORTING Parameters details for EXIT_SAPLES37_030

X_ACTIVE - Indicator Screen is Active

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

X_DISPLAY - Indicator to Display Data

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

X_FKKVK - Partner-Independent Data

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

X_FKKVKP - Partner-Dependent Data

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

X_WMODE -

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

TABLES Parameters details for EXIT_SAPLES37_030

TY_FIELDNAMES - Fields to be Hidden

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

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

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