SAP EXIT_SAPMOIGS_010 Function Module for TD Customer exit for alternative meter calculation
EXIT_SAPMOIGS_010 is a standard exit sapmoigs 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 TD Customer exit for alternative meter calculation 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 sapmoigs 010 FM, simply by entering the name EXIT_SAPMOIGS_010 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XOIG
Program Name: SAPLXOIG
Main Program: SAPLXOIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPMOIGS_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_SAPMOIGS_010'"TD Customer exit for alternative meter calculation.
EXPORTING
PI_MTR_TYPE = "Meter type
PI_MTRNR = "Meter number
CHANGING
PX_TRQTY = "TD transaction quantity
IMPORTING Parameters details for EXIT_SAPMOIGS_010
PI_MTR_TYPE - Meter type
Data type: ROIGS0-MTR_TYPEOptional: No
Call by Reference: Yes
PI_MTRNR - Meter number
Data type: OIGRM-RACK_METEROptional: No
Call by Reference: Yes
CHANGING Parameters details for EXIT_SAPMOIGS_010
PX_TRQTY - TD transaction quantity
Data type: OIGSVMQ-TRQTYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPMOIGS_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_px_trqty | TYPE OIGSVMQ-TRQTY, " | |||
| lv_pi_mtr_type | TYPE ROIGS0-MTR_TYPE, " | |||
| lv_pi_mtrnr | TYPE OIGRM-RACK_METER. " |
|   CALL FUNCTION 'EXIT_SAPMOIGS_010' "TD Customer exit for alternative meter calculation |
| EXPORTING | ||
| PI_MTR_TYPE | = lv_pi_mtr_type | |
| PI_MTRNR | = lv_pi_mtrnr | |
| CHANGING | ||
| PX_TRQTY | = lv_px_trqty | |
| . " EXIT_SAPMOIGS_010 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMOIGS_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.| "SELECT single TRQTY FROM OIGSVMQ INTO @DATA(ld_px_trqty). | ||||
| "SELECT single MTR_TYPE FROM ROIGS0 INTO @DATA(ld_pi_mtr_type). | ||||
| "SELECT single RACK_METER FROM OIGRM INTO @DATA(ld_pi_mtrnr). | ||||
Search for further information about these or an SAP related objects