SAP EXIT_SAPMF67A_015 Function Module for SAPMF67A Enhancement (PAI Modules for User Subscreen) Screen 310
EXIT_SAPMF67A_015 is a standard exit sapmf67a 015 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAPMF67A Enhancement (PAI Modules for User Subscreen) Screen 310 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 sapmf67a 015 FM, simply by entering the name EXIT_SAPMF67A_015 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XF67
Program Name: SAPLXF67
Main Program: SAPLXF67
Appliation area: F
Release date: 07-Apr-1994
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMF67A_015 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_SAPMF67A_015'"SAPMF67A Enhancement (PAI Modules for User Subscreen) Screen 310.
IMPORTING
E_GEAENDERT = "Master Data Change Flag for Saving
CHANGING
* E_OKCODE = "OK Code for Further Processing
* E_VDARL = "Transfer of Current VDARL
* E_CHECKRUN = "Check Run for Loan Master Data '1' Check Run '0' No Check Run
EXPORTING Parameters details for EXIT_SAPMF67A_015
E_GEAENDERT - Master Data Change Flag for Saving
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPMF67A_015
E_OKCODE - OK Code for Further Processing
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
E_VDARL - Transfer of Current VDARL
Data type: VDARLOptional: Yes
Call by Reference: No ( called with pass by value option)
E_CHECKRUN - Check Run for Loan Master Data '1' Check Run '0' No Check Run
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMF67A_015 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_e_okcode | TYPE STRING, " | |||
lv_e_geaendert | TYPE STRING, " | |||
lv_e_vdarl | TYPE VDARL, " | |||
lv_e_checkrun | TYPE C. " |
  CALL FUNCTION 'EXIT_SAPMF67A_015' "SAPMF67A Enhancement (PAI Modules for User Subscreen) Screen 310 |
IMPORTING | ||
E_GEAENDERT | = lv_e_geaendert | |
CHANGING | ||
E_OKCODE | = lv_e_okcode | |
E_VDARL | = lv_e_vdarl | |
E_CHECKRUN | = lv_e_checkrun | |
. " EXIT_SAPMF67A_015 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMF67A_015
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