SAP Function Modules

EXIT_SAPMF67A_015 SAP Function module - SAPMF67A Enhancement (PAI Modules for User Subscreen) Screen 310








EXIT_SAPMF67A_015is a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name EXIT_SAPMF67A_015 into the relevant SAP transaction such as SE37 or SE80.

Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name EXIT_SAPMF67A_015 or its description.


Pattern for FM EXIT_SAPMF67A_015 - EXIT SAPMF67A 015
Associated Function Group: XF67
Released Date: 07.04.1994
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 =                   " vdarl         Transfer of Current VDARL
*   e_checkrun =                " c             Check Run for Loan Master Data '1' Check Run '0' No Check Run
    .  "  EXIT_SAPMF67A_015

ABAP code example for EXIT_SAPMF67A_015 Function Module

The ABAP code below is a full code listing to execute function module EXIT_SAPMF67A_015 including all data declarations. The code uses the latest IN-LINE DATA DECLARATION SYNTAX but I have included an ABAP code snipet at the end to show how declarations would look using the original method of declaring data variables up front. 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).
DATA:
ld_e_geaendert TYPE STRING.

DATA(ld_e_okcode) = 'some text here'.
DATA(ld_e_vdarl) = 'Check type of data required'.
DATA(ld_e_checkrun) = 'Check type of data required'.. CALL FUNCTION 'EXIT_SAPMF67A_015' IMPORTING e_geaendert = ld_e_geaendert * CHANGING * e_okcode = ld_e_okcode * e_vdarl = ld_e_vdarl * e_checkrun = ld_e_checkrun . " EXIT_SAPMF67A_015
IF SY-SUBRC EQ 0. "All OK ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
ld_e_okcode TYPE STRING ,
ld_e_geaendert TYPE STRING ,
ld_e_vdarl TYPE VDARL ,
ld_e_checkrun TYPE C .

ld_e_okcode = 'some text here'.
ld_e_vdarl = 'Check type of data required'.
ld_e_checkrun = 'Check type of data required'..