SAP OIGI_LOADING_CREATE Function Module for TD Create loading data for bulk shipment
OIGI_LOADING_CREATE is a standard oigi loading create 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 Create loading data for bulk shipment 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 oigi loading create FM, simply by entering the name OIGI_LOADING_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIGI
Program Name: SAPLOIGI
Main Program: SAPLOIGI
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function OIGI_LOADING_CREATE 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 'OIGI_LOADING_CREATE'"TD Create loading data for bulk shipment.
EXPORTING
I_SUBRC = "General steering like function code
* I_ROLLBACK = ' ' "Rollback in function module in case of error
* I_RECURSIVE = ' ' "Only for internal use!
* I_CORRECT = ' ' "X=Correction of loading
* I_MBLNR = ' ' "Correct: revers MM document number
* I_MJAHR = ' ' "Correct: revers MM document year
* I_PSTDAT = 00000000 "Correct: revers (MM document) posting date
* I_PSTTIM = 000000 "Correct: revers (MM document) posting time
* I_DCMDAT = 00000000 "Correct: revers (MM document) document date
I_SHNUMBER = "Shipment number
* I_VEHICLE = "Vehicle number
I_LDPLT = "Loading plant
* I_LDDATE = 00000000 "Loading date = posting date in material document
* I_LDTIME = 000000 "Loading time
* I_LDCDAT = 00000000 "Material document date
* I_LOAD_AS_SCHEDULED = ' ' "Set load = scheduled
* I_VEH_NR = 000 "Vehicle number as sequence number
IMPORTING
O_SUBRC = "Return Code
TABLES
* T_OIGISVMQ = "Quantities to be loaded
* T_OIGISVMQ2 = "HPM appendages for HPM_EXTRN=3
* T_OIGISIQ = "TD RFC-Interface Document Quantity
IMPORTING Parameters details for OIGI_LOADING_CREATE
I_SUBRC - General steering like function code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
I_ROLLBACK - Rollback in function module in case of error
Data type: T180-AKTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RECURSIVE - Only for internal use!
Data type: T180-AKTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CORRECT - X=Correction of loading
Data type: T180-AKTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MBLNR - Correct: revers MM document number
Data type: OIGSH-MBLNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MJAHR - Correct: revers MM document year
Data type: OIGSH-MJAHRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PSTDAT - Correct: revers (MM document) posting date
Data type: OIGSH-PSTDATDefault: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PSTTIM - Correct: revers (MM document) posting time
Data type: OIGSH-PSTTIMDefault: 000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DCMDAT - Correct: revers (MM document) document date
Data type: OIGSH-DCMDATDefault: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SHNUMBER - Shipment number
Data type: OIGS-SHNUMBEROptional: No
Call by Reference: No ( called with pass by value option)
I_VEHICLE - Vehicle number
Data type: OIGSV-VEHICLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LDPLT - Loading plant
Data type: ROIGS0-LDPLTOptional: No
Call by Reference: No ( called with pass by value option)
I_LDDATE - Loading date = posting date in material document
Data type: ROIGS0-LDDATEDefault: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LDTIME - Loading time
Data type: ROIGS0-LDTIMEDefault: 000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LDCDAT - Material document date
Data type: ROIGS0-LDCDATDefault: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOAD_AS_SCHEDULED - Set load = scheduled
Data type: T180-AKTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VEH_NR - Vehicle number as sequence number
Data type: OIGSV-VEH_NRDefault: 000
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIGI_LOADING_CREATE
O_SUBRC - Return Code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OIGI_LOADING_CREATE
T_OIGISVMQ - Quantities to be loaded
Data type: ROIGISVMQOptional: Yes
Call by Reference: No ( called with pass by value option)
T_OIGISVMQ2 - HPM appendages for HPM_EXTRN=3
Data type: ROIGISVMQ2Optional: Yes
Call by Reference: No ( called with pass by value option)
T_OIGISIQ - TD RFC-Interface Document Quantity
Data type: ROIGISIQOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for OIGI_LOADING_CREATE 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_subrc | TYPE SY-SUBRC, " | |||
| lv_o_subrc | TYPE SY-SUBRC, " | |||
| lt_t_oigisvmq | TYPE STANDARD TABLE OF ROIGISVMQ, " | |||
| lv_i_rollback | TYPE T180-AKTYP, " SPACE | |||
| lv_i_recursive | TYPE T180-AKTYP, " SPACE | |||
| lv_i_correct | TYPE T180-AKTYP, " SPACE | |||
| lv_i_mblnr | TYPE OIGSH-MBLNR, " SPACE | |||
| lv_i_mjahr | TYPE OIGSH-MJAHR, " SPACE | |||
| lv_i_pstdat | TYPE OIGSH-PSTDAT, " 00000000 | |||
| lv_i_psttim | TYPE OIGSH-PSTTIM, " 000000 | |||
| lv_i_dcmdat | TYPE OIGSH-DCMDAT, " 00000000 | |||
| lv_i_shnumber | TYPE OIGS-SHNUMBER, " | |||
| lt_t_oigisvmq2 | TYPE STANDARD TABLE OF ROIGISVMQ2, " | |||
| lv_i_vehicle | TYPE OIGSV-VEHICLE, " | |||
| lt_t_oigisiq | TYPE STANDARD TABLE OF ROIGISIQ, " | |||
| lv_i_ldplt | TYPE ROIGS0-LDPLT, " | |||
| lv_i_lddate | TYPE ROIGS0-LDDATE, " 00000000 | |||
| lv_i_ldtime | TYPE ROIGS0-LDTIME, " 000000 | |||
| lv_i_ldcdat | TYPE ROIGS0-LDCDAT, " 00000000 | |||
| lv_i_load_as_scheduled | TYPE T180-AKTYP, " SPACE | |||
| lv_i_veh_nr | TYPE OIGSV-VEH_NR. " 000 |
|   CALL FUNCTION 'OIGI_LOADING_CREATE' "TD Create loading data for bulk shipment |
| EXPORTING | ||
| I_SUBRC | = lv_i_subrc | |
| I_ROLLBACK | = lv_i_rollback | |
| I_RECURSIVE | = lv_i_recursive | |
| I_CORRECT | = lv_i_correct | |
| I_MBLNR | = lv_i_mblnr | |
| I_MJAHR | = lv_i_mjahr | |
| I_PSTDAT | = lv_i_pstdat | |
| I_PSTTIM | = lv_i_psttim | |
| I_DCMDAT | = lv_i_dcmdat | |
| I_SHNUMBER | = lv_i_shnumber | |
| I_VEHICLE | = lv_i_vehicle | |
| I_LDPLT | = lv_i_ldplt | |
| I_LDDATE | = lv_i_lddate | |
| I_LDTIME | = lv_i_ldtime | |
| I_LDCDAT | = lv_i_ldcdat | |
| I_LOAD_AS_SCHEDULED | = lv_i_load_as_scheduled | |
| I_VEH_NR | = lv_i_veh_nr | |
| IMPORTING | ||
| O_SUBRC | = lv_o_subrc | |
| TABLES | ||
| T_OIGISVMQ | = lt_t_oigisvmq | |
| T_OIGISVMQ2 | = lt_t_oigisvmq2 | |
| T_OIGISIQ | = lt_t_oigisiq | |
| . " OIGI_LOADING_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM OIGI_LOADING_CREATE
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 SUBRC FROM SY INTO @DATA(ld_i_subrc). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_o_subrc). | ||||
| "SELECT single AKTYP FROM T180 INTO @DATA(ld_i_rollback). | ||||
| DATA(ld_i_rollback) | = ' '. | |||
| "SELECT single AKTYP FROM T180 INTO @DATA(ld_i_recursive). | ||||
| DATA(ld_i_recursive) | = ' '. | |||
| "SELECT single AKTYP FROM T180 INTO @DATA(ld_i_correct). | ||||
| DATA(ld_i_correct) | = ' '. | |||
| "SELECT single MBLNR FROM OIGSH INTO @DATA(ld_i_mblnr). | ||||
| DATA(ld_i_mblnr) | = ' '. | |||
| "SELECT single MJAHR FROM OIGSH INTO @DATA(ld_i_mjahr). | ||||
| DATA(ld_i_mjahr) | = ' '. | |||
| "SELECT single PSTDAT FROM OIGSH INTO @DATA(ld_i_pstdat). | ||||
| DATA(ld_i_pstdat) | = 00000000. | |||
| "SELECT single PSTTIM FROM OIGSH INTO @DATA(ld_i_psttim). | ||||
| DATA(ld_i_psttim) | = 000000. | |||
| "SELECT single DCMDAT FROM OIGSH INTO @DATA(ld_i_dcmdat). | ||||
| DATA(ld_i_dcmdat) | = 00000000. | |||
| "SELECT single SHNUMBER FROM OIGS INTO @DATA(ld_i_shnumber). | ||||
| "SELECT single VEHICLE FROM OIGSV INTO @DATA(ld_i_vehicle). | ||||
| "SELECT single LDPLT FROM ROIGS0 INTO @DATA(ld_i_ldplt). | ||||
| "SELECT single LDDATE FROM ROIGS0 INTO @DATA(ld_i_lddate). | ||||
| DATA(ld_i_lddate) | = 00000000. | |||
| "SELECT single LDTIME FROM ROIGS0 INTO @DATA(ld_i_ldtime). | ||||
| DATA(ld_i_ldtime) | = 000000. | |||
| "SELECT single LDCDAT FROM ROIGS0 INTO @DATA(ld_i_ldcdat). | ||||
| DATA(ld_i_ldcdat) | = 00000000. | |||
| "SELECT single AKTYP FROM T180 INTO @DATA(ld_i_load_as_scheduled). | ||||
| DATA(ld_i_load_as_scheduled) | = ' '. | |||
| "SELECT single VEH_NR FROM OIGSV INTO @DATA(ld_i_veh_nr). | ||||
| DATA(ld_i_veh_nr) | = 000. | |||
Search for further information about these or an SAP related objects