SAP BAPI_OUTB_DELIVERY_SPLIT_DEC Function Module for BAPI for Subsequent Outbound-Delivery Split from a Decentralized System

Search SAP Function Modules

BAPI_OUTB_DELIVERY_SPLIT_DEC is a standard bapi outb delivery split 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 Subsequent Outbound-Delivery Split 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 outb delivery split dec FM, simply by entering the name BAPI_OUTB_DELIVERY_SPLIT_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-Feb-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_OUTB_DELIVERY_SPLIT_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_OUTB_DELIVERY_SPLIT_DEC'"BAPI for Subsequent Outbound-Delivery Split from a Decentralized System
  EXPORTING
   DELIVERY =  "Delivery
   DELIVERYNEW =  "New Delivery That Was Created as a Result of the Split
*  DELIVERYITEMSBELONGTO = 'N' "Split Items Are Part of Existing/New Delivery
   BUSINESSPROCESS =  "Business Admin. Transaction in Which Split Is To Take Place
*  TECHNCONTROL =  "

TABLES
   ITEMDATA =  "Outbound Delivery Split from Decentralized System: Item Data
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
   RETURN =  "Return Parameters
*  ITEM_SERIAL_NO =  "Serial Numbers
*  HEADER_DEADLINES =  "Delivery Deadlines
*  ITEM_DEADLINES =  "
*  HANDLING_UNIT_SPLIT_REQ =  "

.

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_OUTB_DELIVERY_SPLIT_DEC

DELIVERY - Delivery

Data type: BAPIOBDLVHDRDSP-DELIVERY
Optional: No
Call by Reference: No ( called with pass by value option)

DELIVERYNEW - New Delivery That Was Created as a Result of the Split

Data type: BAPIOBDLVHDRDSP-DELIVERYNEW
Optional: No
Call by Reference: No ( called with pass by value option)

DELIVERYITEMSBELONGTO - Split Items Are Part of Existing/New Delivery

Data type: BAPIOBDLVHDRDSP-ITEMSBELONGTO
Default: 'N'
Optional: No
Call by Reference: No ( called with pass by value option)

BUSINESSPROCESS - Business Admin. Transaction in Which Split Is To Take Place

Data type: BAPIOBDLVHDRDSP-BUSINESSPROCESS
Optional: No
Call by Reference: No ( called with pass by value option)

TECHNCONTROL -

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

TABLES Parameters details for BAPI_OUTB_DELIVERY_SPLIT_DEC

ITEMDATA - Outbound Delivery Split from Decentralized System: Item Data

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

EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

RETURN - Return Parameters

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

ITEM_SERIAL_NO - Serial Numbers

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

HEADER_DEADLINES - Delivery Deadlines

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

ITEM_DEADLINES -

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

HANDLING_UNIT_SPLIT_REQ -

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

Copy and paste ABAP code example for BAPI_OUTB_DELIVERY_SPLIT_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.

ABAP code using 7.40 inline data declarations to call FM BAPI_OUTB_DELIVERY_SPLIT_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.

Search for further information about these or an SAP related objects