SAP RFC_SHIPMENT_DEL_CONF_PROCESS Function Module for Initiate and restart complex delivery confirmation process









RFC_SHIPMENT_DEL_CONF_PROCESS is a standard rfc shipment del conf process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initiate and restart complex delivery confirmation process 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 rfc shipment del conf process FM, simply by entering the name RFC_SHIPMENT_DEL_CONF_PROCESS 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): Remote-Enabled
Update:



Function RFC_SHIPMENT_DEL_CONF_PROCESS 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 'RFC_SHIPMENT_DEL_CONF_PROCESS'"Initiate and restart complex delivery confirmation process
  EXPORTING
   SHIPMENT =  "IS-Oil Shipmnet haeder segment
*  KEY =  "Key for delivery confirmation process

 IMPORTING
   RETURN =  "Return parameter
   DCPKEY =  "Key for delivery confirmation process

TABLES
*  SHIPMENT_EVENTS =  "Shipment event segment
*  ITEM_TANKS =  "storage objekt segment for item storage objekt assignment
*  DCP =  "Delivery confirmation
*  EVENT_TEXT =  "Shipment event text lines
*  SHIPMENT_VEHICLE =  "Shipment specific vehicle data
*  SHIPMENT_STAGES =  "TD Shipment stages
*  STAGES_ASSIGN =  "Shipment assignment of doc items to stages
*  QUANTITY_ITEM =  "Shipment item from OIGSVMQ, OIGSVMQM, OIGSVMQO1
*  ITEM_AUOM =  "Additional quantities in alternative UOMs
*  SHIPMENT_ITEM =  "Shipment item data
*  ITEM_POSITION =  "Shipment item position

EXCEPTIONS
   ISO2SAP = 1    MODBAPI = 2    NOSHNUM = 3    EAN2SAP = 4    NOEVENT = 5    NOUPDATE = 6    DCPLOCK = 7    DCPSTAT = 8
.




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 RFC_SHIPMENT_DEL_CONF_PROCESS

SHIPMENT - IS-Oil Shipmnet haeder segment

Data type: BAPI_OIGS
Optional: No
Call by Reference: No ( called with pass by value option)

KEY - Key for delivery confirmation process

Data type: OIKDCPKEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RFC_SHIPMENT_DEL_CONF_PROCESS

RETURN - Return parameter

Data type: BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

DCPKEY - Key for delivery confirmation process

Data type: OIKDCPKEY
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RFC_SHIPMENT_DEL_CONF_PROCESS

SHIPMENT_EVENTS - Shipment event segment

Data type: BAPI_OIGSE
Optional: Yes
Call by Reference: Yes

ITEM_TANKS - storage objekt segment for item storage objekt assignment

Data type: BAPI_TANK
Optional: Yes
Call by Reference: Yes

DCP - Delivery confirmation

Data type: OIKDCP
Optional: Yes
Call by Reference: Yes

EVENT_TEXT - Shipment event text lines

Data type: BAPI_OIGSET
Optional: Yes
Call by Reference: Yes

SHIPMENT_VEHICLE - Shipment specific vehicle data

Data type: BAPI_OIGSV
Optional: Yes
Call by Reference: Yes

SHIPMENT_STAGES - TD Shipment stages

Data type: BAPI_OIGSS
Optional: Yes
Call by Reference: Yes

STAGES_ASSIGN - Shipment assignment of doc items to stages

Data type: BAPI_OIGSVIIS
Optional: Yes
Call by Reference: Yes

QUANTITY_ITEM - Shipment item from OIGSVMQ, OIGSVMQM, OIGSVMQO1

Data type: BAPI_OIGSVMQ
Optional: Yes
Call by Reference: Yes

ITEM_AUOM - Additional quantities in alternative UOMs

Data type: BAPI_AUOM
Optional: Yes
Call by Reference: Yes

SHIPMENT_ITEM - Shipment item data

Data type: BAPI_OIGSI
Optional: Yes
Call by Reference: Yes

ITEM_POSITION - Shipment item position

Data type: BAPI_OIGSII
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ISO2SAP - UoM conversion from ISO to SAP not possible

Data type:
Optional: No
Call by Reference: Yes

MODBAPI - Changes to BAPI data not allowed

Data type:
Optional: No
Call by Reference: Yes

NOSHNUM - Shipment number missing

Data type:
Optional: No
Call by Reference: Yes

EAN2SAP - Material conversion from EAN to SAP not possible

Data type:
Optional: No
Call by Reference: Yes

NOEVENT - Trigger of BP Event not possible

Data type:
Optional: No
Call by Reference: Yes

NOUPDATE - Update of delivery confirmation table not possible

Data type:
Optional: No
Call by Reference: Yes

DCPLOCK - DCP data currently locked

Data type:
Optional: No
Call by Reference: Yes

DCPSTAT - Changes to BAPI data not allowed wrong status

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RFC_SHIPMENT_DEL_CONF_PROCESS 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_return  TYPE BAPIRET2, "   
lv_iso2sap  TYPE BAPIRET2, "   
lv_shipment  TYPE BAPI_OIGS, "   
lt_shipment_events  TYPE STANDARD TABLE OF BAPI_OIGSE, "   
lt_item_tanks  TYPE STANDARD TABLE OF BAPI_TANK, "   
lt_dcp  TYPE STANDARD TABLE OF OIKDCP, "   
lv_key  TYPE OIKDCPKEY, "   
lv_dcpkey  TYPE OIKDCPKEY, "   
lv_modbapi  TYPE OIKDCPKEY, "   
lt_event_text  TYPE STANDARD TABLE OF BAPI_OIGSET, "   
lv_noshnum  TYPE BAPI_OIGSET, "   
lt_shipment_vehicle  TYPE STANDARD TABLE OF BAPI_OIGSV, "   
lv_ean2sap  TYPE BAPI_OIGSV, "   
lt_shipment_stages  TYPE STANDARD TABLE OF BAPI_OIGSS, "   
lv_noevent  TYPE BAPI_OIGSS, "   
lt_stages_assign  TYPE STANDARD TABLE OF BAPI_OIGSVIIS, "   
lv_noupdate  TYPE BAPI_OIGSVIIS, "   
lt_quantity_item  TYPE STANDARD TABLE OF BAPI_OIGSVMQ, "   
lv_dcplock  TYPE BAPI_OIGSVMQ, "   
lt_item_auom  TYPE STANDARD TABLE OF BAPI_AUOM, "   
lv_dcpstat  TYPE BAPI_AUOM, "   
lt_shipment_item  TYPE STANDARD TABLE OF BAPI_OIGSI, "   
lt_item_position  TYPE STANDARD TABLE OF BAPI_OIGSII. "   

  CALL FUNCTION 'RFC_SHIPMENT_DEL_CONF_PROCESS'  "Initiate and restart complex delivery confirmation process
    EXPORTING
         SHIPMENT = lv_shipment
         KEY = lv_key
    IMPORTING
         RETURN = lv_return
         DCPKEY = lv_dcpkey
    TABLES
         SHIPMENT_EVENTS = lt_shipment_events
         ITEM_TANKS = lt_item_tanks
         DCP = lt_dcp
         EVENT_TEXT = lt_event_text
         SHIPMENT_VEHICLE = lt_shipment_vehicle
         SHIPMENT_STAGES = lt_shipment_stages
         STAGES_ASSIGN = lt_stages_assign
         QUANTITY_ITEM = lt_quantity_item
         ITEM_AUOM = lt_item_auom
         SHIPMENT_ITEM = lt_shipment_item
         ITEM_POSITION = lt_item_position
    EXCEPTIONS
        ISO2SAP = 1
        MODBAPI = 2
        NOSHNUM = 3
        EAN2SAP = 4
        NOEVENT = 5
        NOUPDATE = 6
        DCPLOCK = 7
        DCPSTAT = 8
. " RFC_SHIPMENT_DEL_CONF_PROCESS




ABAP code using 7.40 inline data declarations to call FM RFC_SHIPMENT_DEL_CONF_PROCESS

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!