SAP BAPI_INB_DELIVERY_CONFIRM_DEC Function Module for BAPI for Inbound Delivery Verification from a Decentralized System
BAPI_INB_DELIVERY_CONFIRM_DEC is a standard bapi inb delivery confirm dec SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI for Inbound Delivery Verification from a Decentralized System 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 bapi inb delivery confirm dec FM, simply by entering the name BAPI_INB_DELIVERY_CONFIRM_DEC into the relevant SAP transaction such as SE37 or SE38.
Function Group: V50I
Program Name: SAPLV50I
Main Program: SAPLV50I
Appliation area: V
Release date: 03-Apr-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_INB_DELIVERY_CONFIRM_DEC 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 'BAPI_INB_DELIVERY_CONFIRM_DEC'"BAPI for Inbound Delivery Verification from a Decentralized System.
EXPORTING
HEADER_DATA = "Header Data
HEADER_CONTROL = "Control Data Confirmation Header Data
DELIVERY = "Inbound Del. Number
* TECHN_CONTROL = "Technical Control Data
* HEADER_CONTROL_SPL = "Inbound Delivery Confirmation - Add Header Parameters SPL
TABLES
* HEADER_PARTNER = "Delivery: Partner Change
* EXTENSION1 = "Data Container (Unstructured)
* EXTENSION2 = "Data Container (Structured)
RETURN = "Return Parameters
* TOKENREFERENCE = "Reference of CSL Token
* ITEM_DATA_SPL = "BAPIIBDLVITEMCONF Inbound Delivery Additional Item Data
* HEADER_PARTNER_ADDR = "Delivery: Address Change for Partner
* HEADER_DEADLINES = "Header Deadlines
* ITEM_DATA = "Item Data
* ITEM_CONTROL = "Control Data Confirmation Item Data
* ITEM_SERIAL_NO = "BAPI Delivery Serial Numbers Item
* HANDLING_UNIT_HEADER = "Handling Unit Header Data
* HANDLING_UNIT_ITEM = "Handling Unit Item Data
* HANDLING_UNIT_SERNO = "Handling Unit Serial Numbers
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_SAPLV50I_001 User Exit BAPI Inbound Delivery Replication
EXIT_SAPLV50I_002 User Exit BAPI Inbound Delivery Confirmation
EXIT_SAPLV50I_003 User Exit BAPI Outbound Delivery Replication
EXIT_SAPLV50I_004 User Exit BAPI Outbound Delivery Confirmation
EXIT_SAPLV50I_009 User Exit BAPI for Changing Inbound Deliveries
EXIT_SAPLV50I_010 User Exit BAPI for Changing Outbound Deliveries
IMPORTING Parameters details for BAPI_INB_DELIVERY_CONFIRM_DEC
HEADER_DATA - Header Data
Data type: BAPIIBDLVHDRCONOptional: No
Call by Reference: No ( called with pass by value option)
HEADER_CONTROL - Control Data Confirmation Header Data
Data type: BAPIIBDLVHDRCTRLCONOptional: No
Call by Reference: No ( called with pass by value option)
DELIVERY - Inbound Del. Number
Data type: BAPIIBDLVHDRCON-DELIV_NUMBOptional: No
Call by Reference: No ( called with pass by value option)
TECHN_CONTROL - Technical Control Data
Data type: BAPIDLVCONTROLOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADER_CONTROL_SPL - Inbound Delivery Confirmation - Add Header Parameters SPL
Data type: /SPE/BAPIIBDLVHDRCTRLCONFOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_INB_DELIVERY_CONFIRM_DEC
HEADER_PARTNER - Delivery: Partner Change
Data type: BAPIDLVPARTNERCHGOptional: Yes
Call by Reference: Yes
EXTENSION1 - Data Container (Unstructured)
Data type: BAPIEXTCOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSION2 - Data Container (Structured)
Data type: BAPIEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TOKENREFERENCE - Reference of CSL Token
Data type: BAPITOKENREFERENCEOptional: Yes
Call by Reference: Yes
ITEM_DATA_SPL - BAPIIBDLVITEMCONF Inbound Delivery Additional Item Data
Data type: /SPE/BAPIIBDLVITEMCONFOptional: Yes
Call by Reference: Yes
HEADER_PARTNER_ADDR - Delivery: Address Change for Partner
Data type: BAPIDLVPARTNADDRCHGOptional: Yes
Call by Reference: Yes
HEADER_DEADLINES - Header Deadlines
Data type: BAPIDLVDEADLNOptional: Yes
Call by Reference: No ( called with pass by value option)
ITEM_DATA - Item Data
Data type: BAPIIBDLVITEMCONOptional: Yes
Call by Reference: No ( called with pass by value option)
ITEM_CONTROL - Control Data Confirmation Item Data
Data type: BAPIIBDLVITEMCTRLCONOptional: Yes
Call by Reference: No ( called with pass by value option)
ITEM_SERIAL_NO - BAPI Delivery Serial Numbers Item
Data type: BAPIDLVITMSERNOOptional: Yes
Call by Reference: Yes
HANDLING_UNIT_HEADER - Handling Unit Header Data
Data type: BAPIDLVHDUNHDROptional: Yes
Call by Reference: No ( called with pass by value option)
HANDLING_UNIT_ITEM - Handling Unit Item Data
Data type: BAPIDLVHDUNITMOptional: Yes
Call by Reference: No ( called with pass by value option)
HANDLING_UNIT_SERNO - Handling Unit Serial Numbers
Data type: BAPIDLVHDUNSERNOOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_INB_DELIVERY_CONFIRM_DEC 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_header_data | TYPE BAPIIBDLVHDRCON, " | |||
| lt_header_partner | TYPE STANDARD TABLE OF BAPIDLVPARTNERCHG, " | |||
| lt_extension1 | TYPE STANDARD TABLE OF BAPIEXTC, " | |||
| lt_extension2 | TYPE STANDARD TABLE OF BAPIEXT, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_tokenreference | TYPE STANDARD TABLE OF BAPITOKENREFERENCE, " | |||
| lt_item_data_spl | TYPE STANDARD TABLE OF /SPE/BAPIIBDLVITEMCONF, " | |||
| lv_header_control | TYPE BAPIIBDLVHDRCTRLCON, " | |||
| lt_header_partner_addr | TYPE STANDARD TABLE OF BAPIDLVPARTNADDRCHG, " | |||
| lv_delivery | TYPE BAPIIBDLVHDRCON-DELIV_NUMB, " | |||
| lt_header_deadlines | TYPE STANDARD TABLE OF BAPIDLVDEADLN, " | |||
| lt_item_data | TYPE STANDARD TABLE OF BAPIIBDLVITEMCON, " | |||
| lv_techn_control | TYPE BAPIDLVCONTROL, " | |||
| lt_item_control | TYPE STANDARD TABLE OF BAPIIBDLVITEMCTRLCON, " | |||
| lv_header_control_spl | TYPE /SPE/BAPIIBDLVHDRCTRLCONF, " | |||
| lt_item_serial_no | TYPE STANDARD TABLE OF BAPIDLVITMSERNO, " | |||
| lt_handling_unit_header | TYPE STANDARD TABLE OF BAPIDLVHDUNHDR, " | |||
| lt_handling_unit_item | TYPE STANDARD TABLE OF BAPIDLVHDUNITM, " | |||
| lt_handling_unit_serno | TYPE STANDARD TABLE OF BAPIDLVHDUNSERNO. " |
|   CALL FUNCTION 'BAPI_INB_DELIVERY_CONFIRM_DEC' "BAPI for Inbound Delivery Verification from a Decentralized System |
| EXPORTING | ||
| HEADER_DATA | = lv_header_data | |
| HEADER_CONTROL | = lv_header_control | |
| DELIVERY | = lv_delivery | |
| TECHN_CONTROL | = lv_techn_control | |
| HEADER_CONTROL_SPL | = lv_header_control_spl | |
| TABLES | ||
| HEADER_PARTNER | = lt_header_partner | |
| EXTENSION1 | = lt_extension1 | |
| EXTENSION2 | = lt_extension2 | |
| RETURN | = lt_return | |
| TOKENREFERENCE | = lt_tokenreference | |
| ITEM_DATA_SPL | = lt_item_data_spl | |
| HEADER_PARTNER_ADDR | = lt_header_partner_addr | |
| HEADER_DEADLINES | = lt_header_deadlines | |
| ITEM_DATA | = lt_item_data | |
| ITEM_CONTROL | = lt_item_control | |
| ITEM_SERIAL_NO | = lt_item_serial_no | |
| HANDLING_UNIT_HEADER | = lt_handling_unit_header | |
| HANDLING_UNIT_ITEM | = lt_handling_unit_item | |
| HANDLING_UNIT_SERNO | = lt_handling_unit_serno | |
| . " BAPI_INB_DELIVERY_CONFIRM_DEC | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_INB_DELIVERY_CONFIRM_DEC
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 DELIV_NUMB FROM BAPIIBDLVHDRCON INTO @DATA(ld_delivery). | ||||
Search for further information about these or an SAP related objects