Create Outbound Delivery as Bulk 
To create multiple outbound deliveries.
Technical Data
Entity Type |
Service Operation |
Software Component Version |
SAP APPL 6.06 |
released |
|
OutboundDeliveryBulkCreateRequest_In |
|
http://sap.com/xi/APPL/Global2 |
|
LE-SHP-GF-ES |
|
Web Service Definition (Back End) |
OUTBOUNDDELIVERYBULKCRTEREQ |
SAP A2A |
|
inbound |
|
asynchronous |
|
not applicable |
|
not applicable |
|
yes |
Business Context and Use
You create outbound deliveries in SAP ERP based on delivery proposals received, for example, from an external transportation management system (TMS). The Create Outbound Delivery as Bulk operation receives requests to create outbound deliveries and triggers the creation of the deliveries.
Example In a sell-from-stock process, you use an external transportation management system (TMS) to carry out transportation planning for sales orders (for example, using the Request Transportation Request operation to send the sales orders to the external TMS). The external TMS creates optimized delivery proposals for the sales orders and sends a request to create deliveries to SAP ERP. The Create Outbound Delivery as Bulk operation receives the request and creates the outbound deliveries.
Related Operations
The Confirm Outbound Delivery as Bulk operation informs the requesting system whether delivery creation was successful, and provides information about the items for which deliveries could not be created.
Features
The Create Outbound Delivery as Bulk operation receives a request to create outbound deliveries for a preceding document, for example, a purchase order or a sales order. It can trigger the creation of the following delivery types, based on the corresponding order data:
Outbound deliveries for sales orders
Replenishment deliveries for stock transport orders
Returns orders for returns stock transport orders (for returning stock to the plant that sent the goods)
Returns order for returns purchase orders (for returning stock to the vendor)
Note that different document types cannot be combined in one service call (for example, sales orders and purchase orders), but it is possible to combine orders of the same type, for example, several purchase orders. Split criteria and combination criteria can affect the creation of deliveries in SAP ERP. As a result, a single delivery proposal that is received by the Create Outbound Delivery as Bulk operation does not automatically lead to the creation of a single delivery in SAP ERP.
The Create Outbound Delivery as Bulk operation receives the following information about the outbound delivery:
The ID of the outbound delivery document that is to be created (ID element)Although this element is mandatory, it is only filled if external numbering is used. Otherwise, the element is ignored in SAP ERP and can be filled with a temporary ID in the requesting system (for example, the external TMS).
Optional information about the type of document to be created (TypeCode element) and the reason for creating the outbound delivery (OutboundDeliveryCreationReasonCode element, which contains value 4 for an external TMS, for example)
The operation can also receive the following optional information:
The parties involved in the delivery, for example, the buyer party and the product recipient party.Addresses can be supplied for the buyer party and the product recipient party. If SAP ERP recognizes the party, it updates the address in the system. Otherwise, the system creates a new document-specific business partner. All business partners are identified by a mandatory internal ID (InternalID element).
The dates agreed on by the customer and the seller, including the following:
The date and time the goods are expected to arrive at the customer site (PlannedArrivalDateTime element)
The date and time the goods have to be picked up at the warehouse so that they are ready for packing, loading, and delivery (PickingPeriod element)
The actual point in time the goods leave the seller (IssuePeriod element)
Note that the external TMS sends a time period, but SAP ERP only uses the earliest date as the delivery date.
Although items are not mandatory from a technical perspective, they are required from a business perspective. If items are provided, the following information is mandatory:
Unique number for an item (ID element)Note that this number does not indicate a hierarchy or imply any reference or relationship to predecessor documents. Instead document references and hierarchy information are provided separately in the corresponding nodes.
The item type, for example, product item or packaging item (TypeCode element)
The following information is mandatory and enables the system to identify the sales order items for which delivery items are to be created:
The ID of the preceding sales order in SAP ERP (SalesOrderReferenceID)
The ID of the item in the sales orders (ItemID)
The operation can also receive information about weight and volume, for example, the gross weight and volume of the goods to be delivered (GrossWeightMeasure and GrossVolumeMeasure elements).
Error Handling
Errors that occur during delivery creation are returned to the requesting system by the Confirm Outbound Delivery as Bulk operation. Forward Error Handling (FEH) is not used for this purpose. This is because delivery creation is a time-critical process and problems with a small number of items, for example, cannot be allowed to stop delivery creation for the other items. By returning the error messages and the corresponding items in the confirmation operation, delivery creation can continue and the user can correct the items with errors and send them in a new service call.
Message Types
OutboundDeliveryBulkCreateRequest
Constraints
This operation is not compatible with SAP Transportation Management 7.0 (SAP TM 7.0).
Notes on SAP Implementation
The collective processing functions provided by this operation enable several orders of one type to be processed in one service call (for example, several sales orders or several purchase orders). This is similar to the functions provided by transaction VL10 in the SAP ERP back-end system.
Business Functions
If you use this operation in a sell-from stock process or a procure-to-pay process in which transportation planning is carried out in an external TMS, you have to activate the ERP-TMS: Order Integration (LOG_TM_ORD_INT) business function. You can also activate the following business functions:
Advanced Returns Management (OPS_ADVRETURNS_1)This enables you to use advanced returns management for returns processing.
SOA Reuse Functions (FND_SOA_REUSE_1)This enables you to use Web Services Reliable Messaging (WSRM) for direct point-to-point communication between the SAP ERP system and the external TMS.
Enhancements
The Business Add-Ins (BAdI) SHP_BADI_FILL_XI_MESSAGE and SHP_APPL_SE_OBDLV_BULK_CRT_RQ are available for this operation.