SAP PROCEDURE_MODEL_EXIT Function Module for
PROCEDURE_MODEL_EXIT is a standard procedure model exit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 procedure model exit FM, simply by entering the name PROCEDURE_MODEL_EXIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SVGM
Program Name: SAPLSVGM
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PROCEDURE_MODEL_EXIT 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 'PROCEDURE_MODEL_EXIT'".
EXPORTING
DOC_CLS = "
DOC_OBJ = "
ACTION = "
DOC_TITLE = "
IMPORTING Parameters details for PROCEDURE_MODEL_EXIT
DOC_CLS -
Data type: DSYAD-CHILD_CLSOptional: No
Call by Reference: No ( called with pass by value option)
DOC_OBJ -
Data type: DSYAD-CHILD_OBJOptional: No
Call by Reference: No ( called with pass by value option)
ACTION -
Data type: CUSASTRUC-MARKEDOptional: No
Call by Reference: No ( called with pass by value option)
DOC_TITLE -
Data type: DSYST-DOKTITLEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PROCEDURE_MODEL_EXIT 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_doc_cls | TYPE DSYAD-CHILD_CLS, " | |||
| lv_doc_obj | TYPE DSYAD-CHILD_OBJ, " | |||
| lv_action | TYPE CUSASTRUC-MARKED, " | |||
| lv_doc_title | TYPE DSYST-DOKTITLE. " |
|   CALL FUNCTION 'PROCEDURE_MODEL_EXIT' " |
| EXPORTING | ||
| DOC_CLS | = lv_doc_cls | |
| DOC_OBJ | = lv_doc_obj | |
| ACTION | = lv_action | |
| DOC_TITLE | = lv_doc_title | |
| . " PROCEDURE_MODEL_EXIT | ||
ABAP code using 7.40 inline data declarations to call FM PROCEDURE_MODEL_EXIT
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 CHILD_CLS FROM DSYAD INTO @DATA(ld_doc_cls). | ||||
| "SELECT single CHILD_OBJ FROM DSYAD INTO @DATA(ld_doc_obj). | ||||
| "SELECT single MARKED FROM CUSASTRUC INTO @DATA(ld_action). | ||||
| "SELECT single DOKTITLE FROM DSYST INTO @DATA(ld_doc_title). | ||||
Search for further information about these or an SAP related objects