SAP EXIT_SAPMWOG1_010 Function Module for User_Exit_Fdis_Liste: After FDIS Preparation for Revision
EXIT_SAPMWOG1_010 is a standard exit sapmwog1 010 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User_Exit_Fdis_Liste: After FDIS Preparation for Revision 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 sapmwog1 010 FM, simply by entering the name EXIT_SAPMWOG1_010 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XWOG
Program Name: SAPLXWOG
Main Program:
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPMWOG1_010 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_SAPMWOG1_010'"User_Exit_Fdis_Liste: After FDIS Preparation for Revision.
EXPORTING
I_KOPF = "
TABLES
T_FDIS = "
EXCEPTIONS
FIELD_CHECK_ERROR = 1
IMPORTING Parameters details for EXIT_SAPMWOG1_010
I_KOPF -
Data type: WDFR_KOPFOptional: No
Call by Reference: Yes
TABLES Parameters details for EXIT_SAPMWOG1_010
T_FDIS -
Data type: WDFR_FDISOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FIELD_CHECK_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMWOG1_010 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_i_kopf | TYPE WDFR_KOPF, " | |||
| lt_t_fdis | TYPE STANDARD TABLE OF WDFR_FDIS, " | |||
| lv_field_check_error | TYPE WDFR_FDIS. " |
|   CALL FUNCTION 'EXIT_SAPMWOG1_010' "User_Exit_Fdis_Liste: After FDIS Preparation for Revision |
| EXPORTING | ||
| I_KOPF | = lv_i_kopf | |
| TABLES | ||
| T_FDIS | = lt_t_fdis | |
| EXCEPTIONS | ||
| FIELD_CHECK_ERROR = 1 | ||
| . " EXIT_SAPMWOG1_010 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMWOG1_010
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