SAP OIKDC_CREATE_ORDER_DELIVERY Function Module for Create sales order and/or delivery
OIKDC_CREATE_ORDER_DELIVERY is a standard oikdc create order delivery SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create sales order and/or delivery 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 oikdc create order delivery FM, simply by entering the name OIKDC_CREATE_ORDER_DELIVERY into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIKDC
Program Name: SAPLOIKDC
Main Program: SAPLOIKDC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIKDC_CREATE_ORDER_DELIVERY 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 'OIKDC_CREATE_ORDER_DELIVERY'"Create sales order and/or delivery.
EXPORTING
I_OIGIS = "TD RFC-Interface Shipment Header
I_OIKDCH = "TD RFC-Interface Shipment Header
I_OIKDCS = "Delivery confirmation status
IMPORTING
E_SUBRC = "Return value, return value after ABAP statements
E_WAIT = "Single-character flag
E_OIKDCS = "Delivery confirmation status
TABLES
T_OIKDCSV = "TD RFC-Interface Vehicles in Shipment
T_OIGISE = "TD RFC-Interface Events in Shipment
T_OIGISET = "TD RFC-Interface Event Texts in Shipment
T_OIGISS = "TD RFC-Interface Shipment Stages
T_OIGISVIIS = "TD-RFC Interface Shipment assigmt of doc items to stages
T_OIGISPA = "TD RFC-Interface Shipment Partners
T_OIGISVD = "TD RFC-Interface Drivers in Shipment
T_OIGISI = "TD RFC-Interface Shipment Items
T_OIKDCSI = "TD RFC-Interface Shipment Items Positions
T_OIKDCSII = "TD RFC-Interface Shipment Item Positions
T_OIKDCS4 = "storage objekt segment for item storage objekt assignment
T_OIGISIQ = "TD RFC-Interface Document Quantity
T_OIGISVMQ = "TD RFC-Interface Quantity Item for Material on Vehicle
T_OIGISVMQ2 = "TD Interface to shipment handling HPM quantities
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOIKDC_100 DCP read shipment details
EXIT_SAPLOIKDC_110 DCP change data before Delivery Confirmation is called
IMPORTING Parameters details for OIKDC_CREATE_ORDER_DELIVERY
I_OIGIS - TD RFC-Interface Shipment Header
Data type: ROIGISOptional: No
Call by Reference: No ( called with pass by value option)
I_OIKDCH - TD RFC-Interface Shipment Header
Data type: ROIKDCHOptional: No
Call by Reference: No ( called with pass by value option)
I_OIKDCS - Delivery confirmation status
Data type: OIKDCSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIKDC_CREATE_ORDER_DELIVERY
E_SUBRC - Return value, return value after ABAP statements
Data type: SYSUBRCOptional: No
Call by Reference: Yes
E_WAIT - Single-character flag
Data type: CHAR1Optional: No
Call by Reference: Yes
E_OIKDCS - Delivery confirmation status
Data type: OIKDCSOptional: No
Call by Reference: Yes
TABLES Parameters details for OIKDC_CREATE_ORDER_DELIVERY
T_OIKDCSV - TD RFC-Interface Vehicles in Shipment
Data type: ROIKDCSVOptional: No
Call by Reference: Yes
T_OIGISE - TD RFC-Interface Events in Shipment
Data type: ROIGISEOptional: No
Call by Reference: Yes
T_OIGISET - TD RFC-Interface Event Texts in Shipment
Data type: ROIGISETOptional: No
Call by Reference: Yes
T_OIGISS - TD RFC-Interface Shipment Stages
Data type: ROIGISSOptional: No
Call by Reference: Yes
T_OIGISVIIS - TD-RFC Interface Shipment assigmt of doc items to stages
Data type: ROIGISVIISOptional: No
Call by Reference: Yes
T_OIGISPA - TD RFC-Interface Shipment Partners
Data type: ROIGISPAOptional: No
Call by Reference: Yes
T_OIGISVD - TD RFC-Interface Drivers in Shipment
Data type: ROIGISVDOptional: No
Call by Reference: Yes
T_OIGISI - TD RFC-Interface Shipment Items
Data type: ROIGISIOptional: No
Call by Reference: Yes
T_OIKDCSI - TD RFC-Interface Shipment Items Positions
Data type: ROIKDCSIOptional: No
Call by Reference: Yes
T_OIKDCSII - TD RFC-Interface Shipment Item Positions
Data type: ROIKDCSIIOptional: No
Call by Reference: Yes
T_OIKDCS4 - storage objekt segment for item storage objekt assignment
Data type: ROIKDCS4Optional: No
Call by Reference: Yes
T_OIGISIQ - TD RFC-Interface Document Quantity
Data type: ROIGISIQOptional: No
Call by Reference: Yes
T_OIGISVMQ - TD RFC-Interface Quantity Item for Material on Vehicle
Data type: ROIGISVMQOptional: No
Call by Reference: Yes
T_OIGISVMQ2 - TD Interface to shipment handling HPM quantities
Data type: ROIGISVMQ2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIKDC_CREATE_ORDER_DELIVERY 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_e_subrc | TYPE SYSUBRC, " | |||
| lv_i_oigis | TYPE ROIGIS, " | |||
| lt_t_oikdcsv | TYPE STANDARD TABLE OF ROIKDCSV, " | |||
| lt_t_oigise | TYPE STANDARD TABLE OF ROIGISE, " | |||
| lt_t_oigiset | TYPE STANDARD TABLE OF ROIGISET, " | |||
| lt_t_oigiss | TYPE STANDARD TABLE OF ROIGISS, " | |||
| lt_t_oigisviis | TYPE STANDARD TABLE OF ROIGISVIIS, " | |||
| lt_t_oigispa | TYPE STANDARD TABLE OF ROIGISPA, " | |||
| lv_e_wait | TYPE CHAR1, " | |||
| lv_i_oikdch | TYPE ROIKDCH, " | |||
| lt_t_oigisvd | TYPE STANDARD TABLE OF ROIGISVD, " | |||
| lv_e_oikdcs | TYPE OIKDCS, " | |||
| lv_i_oikdcs | TYPE OIKDCS, " | |||
| lt_t_oigisi | TYPE STANDARD TABLE OF ROIGISI, " | |||
| lt_t_oikdcsi | TYPE STANDARD TABLE OF ROIKDCSI, " | |||
| lt_t_oikdcsii | TYPE STANDARD TABLE OF ROIKDCSII, " | |||
| lt_t_oikdcs4 | TYPE STANDARD TABLE OF ROIKDCS4, " | |||
| lt_t_oigisiq | TYPE STANDARD TABLE OF ROIGISIQ, " | |||
| lt_t_oigisvmq | TYPE STANDARD TABLE OF ROIGISVMQ, " | |||
| lt_t_oigisvmq2 | TYPE STANDARD TABLE OF ROIGISVMQ2. " |
|   CALL FUNCTION 'OIKDC_CREATE_ORDER_DELIVERY' "Create sales order and/or delivery |
| EXPORTING | ||
| I_OIGIS | = lv_i_oigis | |
| I_OIKDCH | = lv_i_oikdch | |
| I_OIKDCS | = lv_i_oikdcs | |
| IMPORTING | ||
| E_SUBRC | = lv_e_subrc | |
| E_WAIT | = lv_e_wait | |
| E_OIKDCS | = lv_e_oikdcs | |
| TABLES | ||
| T_OIKDCSV | = lt_t_oikdcsv | |
| T_OIGISE | = lt_t_oigise | |
| T_OIGISET | = lt_t_oigiset | |
| T_OIGISS | = lt_t_oigiss | |
| T_OIGISVIIS | = lt_t_oigisviis | |
| T_OIGISPA | = lt_t_oigispa | |
| T_OIGISVD | = lt_t_oigisvd | |
| T_OIGISI | = lt_t_oigisi | |
| T_OIKDCSI | = lt_t_oikdcsi | |
| T_OIKDCSII | = lt_t_oikdcsii | |
| T_OIKDCS4 | = lt_t_oikdcs4 | |
| T_OIGISIQ | = lt_t_oigisiq | |
| T_OIGISVMQ | = lt_t_oigisvmq | |
| T_OIGISVMQ2 | = lt_t_oigisvmq2 | |
| . " OIKDC_CREATE_ORDER_DELIVERY | ||
ABAP code using 7.40 inline data declarations to call FM OIKDC_CREATE_ORDER_DELIVERY
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