Functionality
This method allows outbound deliveries that were split in a WarehouseManagement (WM) system from an original outbound delivery to be splitin the Enterprise Resource Planning (ERP) system as well. This methodis normally carried out immediately before the WM system confirms theoutbound delivery. If they are carried out asynchronously using IDocs,both methods must be serialized using the object type.
Once the outbound delivery is created in the ERP system (referred to asthe "original delivery" in the following) and replicated in the WMsystem, you can process it normally. If several other outbounddeliveries (referred to as "split deliveries" in the following) arecreated from this original delivery by way of a subsequent deliverysplit, you must use this method to create these split deliveries in theERP system.
In the SAP standard system, this method is linked to the followingscenario:
As goods issue is posted for an outbound delivery, the systemdetermines whether this delivery was involved in a split process. Thisis the case if this outbound delivery is the original delivery itself,which was already created in the ERP system, or if this outbounddelivery was created in the WM system as a result of a split. In bothcases, it does not matter whether the delivery was split directly fromthe original delivery or from a delivery that was split previously.
If a split delivery is posted goods issue, this method is used tocreate the new delivery from the original delivery (or referencedelivery--see below).
The DELIVERYITEMSBELONGTO parameter contains value 'N' in thiscase and the items in the split delivery are listed in the ITEMDATA table.
If the original delivery is posted goods issue, this method is used tocreate one of the new deliveries (result of the split in the WM system)in the ERP system at this point, for use with future calls. Once theoriginal delivery is posted goods issue in the ERP system, the newdelivery assumes the role of the original delivery and serves as areference delivery for splitting other outbound deliveries in allfuture calls.
In this case, the DELIVERYITEMSBELONGTO parameter contains value'O' and the items in the original delivery that are to be postedgoods issue are listed in the ITEMDATA item table.
You must specify a split profile in the BUSINESSPROCESSparameter in the interface for the subsequent outbound-deliverysplit that is to be carried out in sequence. In the SAP standardsystem, this split profile is the same one that is used to split theoutbound delivery in the WM system. Split profiles must bemaintained in the ERP system inCustomizing for subsequent deliveries, but not necessarily the same wayas they are maintained in the WM system.
The system overrides and deactivates the following Customizing settingsin this method during the delivery split:

• Renumber item numbers in old deliveries


• Renumber Items in New Delivery


• Delete Normal Items with Quantity 0


• Delivery Group Splits Not Allowed


• Delete Items from Delivery Groups if Quantity
is 0

• Check Complete Delivery Indicator During
Delivery Split

• Check Number of Partial Deliveries During
Split

• Control when Correlated Bills of Material are
Split

• Copy Text Item with Quantity 0 Automatically



• If Split Results Same as Orignial
Delivery, Then No Split
At item level, a quantity is specified for each item number. Thisquantity reflects the quantity of the item that is to be included inthe split delivery or the quantity that is to remain in the originaldelivery. The quantity to be split is limited by the existingquantity. If the OutboundDelivery.ConfirmDecentral method iscalled up following this process, the quantities in the delivery thatwas posted goods issue are corrected. If the original delivery isposted goods issue after these methods were called up, the referencedelivery contains all items in the original delivery, including theones with a quantity of zero.
The CURR_QTY field controls which field the structure of theITEMDATA parameter will appear in:

• 'A':,,DLV_QTY (Quantity to be split, given in
sales units)

• 'B':,,DLV_QTY_STOCK (Quantity to be split, given
in base units)
Both of these values must be able to be converted to one another byusing SALES_QTY_NUM andSALES_QTY_DENOM , however. The unit of measurecan be specified in SAP units (SALES_UNIT,BASE_UNIT) or in ISO units(
ISOCODE_SALES_UNIT, BASE_UOM_ISO
).
Handling Units cannot be split, meaning that the items/quantities thatare to be split may not be packed.

Description
The split profile that controls the subsequent outbound-delivery splitand refers to Customizing.
In the SAP standard, this value is the same as the one that is used tosplit the delivery in the decentralized Warehouse Management (WM)system. The split profile must also exist in the Enterprise ResourcePlanning (ERP) System. However, settings in the ERP system may differfrom those in the WM system.
The system overrides and deactivates the following settings in anycase:


• Renumber item numbers in old deliveries


• Renumber Items in New Delivery


• Delete Normal Items with Quantity 0


• Delivery Group Splits Not Allowed


• Delete Items from Delivery Groups if Quantity

is 0

• Check Complete Delivery Indicator During

Delivery Split

• Check Number of Partial Deliveries During

Split

• Control when Correlated Bills of Material are
Split

• Copy Text Item with Quantity 0 Automatically



• If Split Results Same as Orignial
Delivery, Then No Split

Description
This delivery number refers to the existing delivery in the ERP systemfrom which the new delivery DELIVERYNEW is split off.
If the parameter DELIVERYITEMSBELONGTO has the value N, only theitems from the table ITEMDATA are created from the existingdelivery (in the standard SAP scenario, the new delivery is posted togoods issue afterwards with the method OutboundDelivery.ConfirmDecentral in the ERP system).
If the parameter DELIVERYITEMSBELONGTO has the value O, the newdelivery is created with all the items from the old delivery (in thestandard SAP scenario, this existing delivery is posted afterwards togoods issue with the method OutboundDelivery.ConfirmDecentral inthe ERP system.

Description
Control indicator for items in the table ITEMDATA belonging tothe existing delivery (DELIVERY) or to the new delivery
(DELIVERYNEW).

Value range
'N'
The items belong to the new delivery. The split copies only thespecified items into the new delivery.
'O'
The items belong to the old delivery. The split copies all the items ofthe old delivery into the new delivery. The quantity is the result fromthe difference between the existing quantity and the specifiedquantity.
Under certain conditions, this quantity can even be zero.

Default
'N'

Description
Delivery number of the delivery from which the delivery DELIVERYwas split.
Depending on the value of the DELIVERYITEMSBELONGTO parameter,it contains the items that are included in the table ITEMDATA ('N') or all the items that are also contained in the originaldelivery DELIVERY ( 'O').

Description
This text similar to function module text
BAPI_OUTB_DELIVERY_SPLIT_DEC TECHN_CONTROL
You can use this system to cause a cancellation in the receiving systemby setting the DEBUG_FLG field (X). This cancellation makes it possibleto re-import the corresponding BREAK-POINTS into the IDoc in thereceiving system.

Description
Table for customer-specific extensions
For further information about BAPI table extensions and extensionparameters, see the BAPI programmer guide in the SAP Library.

Description
Items to be split
Refer to the general description of this function module or the dataelement documentation for the component of the data structure thisfunction module is based on.

Description
Messages are collected here and returned to the calling program.