SAP EXIT_SAPMOIGS_008 Function Module for TD Customer exit to check vehicle overloading after compartment planning









EXIT_SAPMOIGS_008 is a standard exit sapmoigs 008 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 to check vehicle overloading after compartment planning 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 008 FM, simply by entering the name EXIT_SAPMOIGS_008 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_008 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_008'"TD Customer exit to check vehicle overloading after compartment planning
CHANGING
   PI_OIGS =  "Internal Table for Shipment
   PI_T180 =  "Screen Sequence Control: Transaction Default Values

TABLES
   PX_OIGSH =  "Internal Table - Shipment Item
   PX_OIGSVMQ =  "Internal Table - TD Quantity item for material on vehicle
   PX_OIGSVMQM =  "Internal Table - TD On board movements references
   PX_OIGSI =  "Internal Table - Shipment Item
   PX_OIGSIH_J =  "TD Shipment delivery headers
   PX_OIGSIH_W =  "TD Shipment reservation headers
   PX_OIGSII_J =  "TD Shipment delivery items
   PX_OIGSII_W =  "TD Shipment reservation items
   PX_INDEXA_TAB =  "Structure for indexA (SAPMOIGS)
   PX_INDEX1_TAB =  "Structure for index1 (SAPMOIGS)
   PX_INDEX2_TAB =  "Structure for index1 (SAPMOIGS)
   PX_OIGSM =  "Internal Structure for material in Shipment
   PX_OIGSMV =  "Internal Table - Quantity per material/vehicle in shipment
   PX_OIGSV =  "Io/Area for Vehicle in Shipments
   PX_OIGSVC =  "Internal Table - Transport Unit in Shipment
   PX_OIGSVCC =  "Internal table for compartments in shipment
   PX_OIGSVCS =  "Internal Table - Vehicle Seals
   PX_OIGSVD =  "Internal Table - Driver on Vehicle in Shipment
   PX_OIGSMS =  "Internal Table - Material Samples
.



CHANGING Parameters details for EXIT_SAPMOIGS_008

PI_OIGS - Internal Table for Shipment

Data type: ROIGS
Optional: No
Call by Reference: Yes

PI_T180 - Screen Sequence Control: Transaction Default Values

Data type: T180
Optional: No
Call by Reference: Yes

TABLES Parameters details for EXIT_SAPMOIGS_008

PX_OIGSH - Internal Table - Shipment Item

Data type: ROIGSH
Optional: No
Call by Reference: Yes

PX_OIGSVMQ - Internal Table - TD Quantity item for material on vehicle

Data type: ROIGSVMQ
Optional: No
Call by Reference: Yes

PX_OIGSVMQM - Internal Table - TD On board movements references

Data type: ROIGSVMQM
Optional: No
Call by Reference: Yes

PX_OIGSI - Internal Table - Shipment Item

Data type: ROIGSI
Optional: No
Call by Reference: Yes

PX_OIGSIH_J - TD Shipment delivery headers

Data type: ROIGSIH_J
Optional: No
Call by Reference: Yes

PX_OIGSIH_W - TD Shipment reservation headers

Data type: ROIGSIH_W
Optional: No
Call by Reference: Yes

PX_OIGSII_J - TD Shipment delivery items

Data type: ROIGSII_J
Optional: No
Call by Reference: Yes

PX_OIGSII_W - TD Shipment reservation items

Data type: ROIGSII_W
Optional: No
Call by Reference: Yes

PX_INDEXA_TAB - Structure for indexA (SAPMOIGS)

Data type: ROIGSIXA
Optional: No
Call by Reference: Yes

PX_INDEX1_TAB - Structure for index1 (SAPMOIGS)

Data type: ROIGSIX1
Optional: No
Call by Reference: Yes

PX_INDEX2_TAB - Structure for index1 (SAPMOIGS)

Data type: ROIGSIX1
Optional: No
Call by Reference: Yes

PX_OIGSM - Internal Structure for material in Shipment

Data type: ROIGSM
Optional: No
Call by Reference: Yes

PX_OIGSMV - Internal Table - Quantity per material/vehicle in shipment

Data type: ROIGSMV
Optional: No
Call by Reference: Yes

PX_OIGSV - Io/Area for Vehicle in Shipments

Data type: ROIGSV
Optional: No
Call by Reference: Yes

PX_OIGSVC - Internal Table - Transport Unit in Shipment

Data type: ROIGSVC
Optional: No
Call by Reference: Yes

PX_OIGSVCC - Internal table for compartments in shipment

Data type: ROIGSVCC
Optional: No
Call by Reference: Yes

PX_OIGSVCS - Internal Table - Vehicle Seals

Data type: ROIGSVCS
Optional: No
Call by Reference: Yes

PX_OIGSVD - Internal Table - Driver on Vehicle in Shipment

Data type: ROIGSVD
Optional: No
Call by Reference: Yes

PX_OIGSMS - Internal Table - Material Samples

Data type: ROIGSMS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXIT_SAPMOIGS_008 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_pi_oigs  TYPE ROIGS, "   
lt_px_oigsh  TYPE STANDARD TABLE OF ROIGSH, "   
lt_px_oigsvmq  TYPE STANDARD TABLE OF ROIGSVMQ, "   
lt_px_oigsvmqm  TYPE STANDARD TABLE OF ROIGSVMQM, "   
lt_px_oigsi  TYPE STANDARD TABLE OF ROIGSI, "   
lt_px_oigsih_j  TYPE STANDARD TABLE OF ROIGSIH_J, "   
lt_px_oigsih_w  TYPE STANDARD TABLE OF ROIGSIH_W, "   
lt_px_oigsii_j  TYPE STANDARD TABLE OF ROIGSII_J, "   
lt_px_oigsii_w  TYPE STANDARD TABLE OF ROIGSII_W, "   
lt_px_indexa_tab  TYPE STANDARD TABLE OF ROIGSIXA, "   
lt_px_index1_tab  TYPE STANDARD TABLE OF ROIGSIX1, "   
lt_px_index2_tab  TYPE STANDARD TABLE OF ROIGSIX1, "   
lv_pi_t180  TYPE T180, "   
lt_px_oigsm  TYPE STANDARD TABLE OF ROIGSM, "   
lt_px_oigsmv  TYPE STANDARD TABLE OF ROIGSMV, "   
lt_px_oigsv  TYPE STANDARD TABLE OF ROIGSV, "   
lt_px_oigsvc  TYPE STANDARD TABLE OF ROIGSVC, "   
lt_px_oigsvcc  TYPE STANDARD TABLE OF ROIGSVCC, "   
lt_px_oigsvcs  TYPE STANDARD TABLE OF ROIGSVCS, "   
lt_px_oigsvd  TYPE STANDARD TABLE OF ROIGSVD, "   
lt_px_oigsms  TYPE STANDARD TABLE OF ROIGSMS. "   

  CALL FUNCTION 'EXIT_SAPMOIGS_008'  "TD Customer exit to check vehicle overloading after compartment planning
    CHANGING
         PI_OIGS = lv_pi_oigs
         PI_T180 = lv_pi_t180
    TABLES
         PX_OIGSH = lt_px_oigsh
         PX_OIGSVMQ = lt_px_oigsvmq
         PX_OIGSVMQM = lt_px_oigsvmqm
         PX_OIGSI = lt_px_oigsi
         PX_OIGSIH_J = lt_px_oigsih_j
         PX_OIGSIH_W = lt_px_oigsih_w
         PX_OIGSII_J = lt_px_oigsii_j
         PX_OIGSII_W = lt_px_oigsii_w
         PX_INDEXA_TAB = lt_px_indexa_tab
         PX_INDEX1_TAB = lt_px_index1_tab
         PX_INDEX2_TAB = lt_px_index2_tab
         PX_OIGSM = lt_px_oigsm
         PX_OIGSMV = lt_px_oigsmv
         PX_OIGSV = lt_px_oigsv
         PX_OIGSVC = lt_px_oigsvc
         PX_OIGSVCC = lt_px_oigsvcc
         PX_OIGSVCS = lt_px_oigsvcs
         PX_OIGSVD = lt_px_oigsvd
         PX_OIGSMS = lt_px_oigsms
. " EXIT_SAPMOIGS_008




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMOIGS_008

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!