Create Inbound Delivery

Request to Inbound Delivery Processing to create an inbound delivery

Technical Data

Entity Type	Service Operation
Software Component Version	ESA ECC-SE 605
Release State	released
Technical Name	InboundDeliveryCreateRequest_In
Namespace	http://sap.com/xi/APPL/SE/Global
Application Component	LE-SHP
Web Service Definition (Back End)	INBOUNDDELIVERYCREATEREQUEST_I
Category	SAP A2A
Direction	inbound
Mode	asynchronous
Idempotency	not applicable
Change/Update Behavior	not applicable
P2P Communication Enabled	yes

Business Context and Use

You create inbound deliveries based on delivery proposals received from a decentralized stockholding application or an external transportation management system (TMS). You also create returns deliveries based on data received from an external TMS. The Create Inbound Delivery operation receives a delivery proposal and triggers the creation of one or more deliveries.

Examples

In a procure-to-pay process, you use an external transportation management system (TMS) to carry out transportation planning for purchase orders (for example, using the Request Transportation Request operation to send purchase orders to the external TMS). The external TMS creates optimized delivery proposals for the purchase orders and sends a request to create inbound deliveries to SAP ERP.
You use a decentralized stockholding application to process goods movements and manage stocks in your warehouse complex. You create inbound deliveries in the stockholding application and replicate them to SAP ERP for further processing, for example, invoice processing and controlling.

Features

The Create Inbound Delivery operation receives a request to create an inbound delivery for items from one or more preceding documents, for example, purchase orders or returns orders. It triggers the creation of one or more inbound deliveries for purchase order items, or one or more returns deliveries for returns order items.

Note that different document types cannot be combined in one service call (for example, purchase orders and returns 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 received by the Create Inbound Delivery operation does not automatically lead to the creation of a single delivery in SAP ERP. This also applies to delivery proposals that contain items from one preceding document.

When the operation receives a request to create a delivery, it first determines whether the request was sent by an external TMS or a decentralized stockholding application (CreationMethodCode element, which contains value 03 for an external TMS). To create a delivery, it requires the following mandatory information at item level:

The ID of the preceding document for which the delivery is to be created, that is, the ID of the purchase order or the returns order
The IDs of the items for which delivery items are to be created

It also requires information about the delivery dates and the item quantities that are to be delivered, for example.

Note that the external TMS sends a time period, but SAP ERP only uses the earliest date as the delivery date.

Error Handling

Forward Error Handling

The Create Inbound Delivery inbound operation supports Forward Error Handling (FEH). The following error categories are used:

FOE.FFE: Field Format Error
FOE.SVE: Scheme Violation Error
DCE.IKT: Internal Key Term Error
DCE.ITE: Internal Term Error
DCE.ICE: Invalid Call Error
DCE.VME: Value Mapping Error
DCE: Determination & Conversion error

For more information about the individual error categories, see the code list for the global data type LogItemCategoryCode .

Note that if you use this operation to exchange information with an external TMS, you must check the set up of the external TMS to determine whether FEH is a suitable method for restarting the service call. If FEH cannot be used with your external TMS, we recommend that you configure the required error handling procedures in your external TMS.

Message Types

InboundDeliveryCreateRequest

Notes on SAP Implementation

Information for Integration with a decentralized Stockholding Application

You have to install the Shipping ( LE-SHP ) and Service Parts Management ( LO-SPM ) application components.
For information about configuring your system landscape to use this operation with a decentralized stockholding application, see the Implementation Guide in the SAP Software Developer Network).
Hard-coded values are transferred for partner function and logical time. The numerator and denominator for converting the sales quantity to the stock keeping unit (SKU) is 1.

Information for Integration with an External TMS

To receive the ID of the external TMS, you have to activate the ERP-TMS: Order Integration (LOG_TM_ORD_INT) business function. The ID of the external TMS is required to route the confirmation message to the correct system. 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-In (BAdI) SHP_SE_INBOUNDDELIVERYCRTRQ is available for this operation.

Enhancements

The Business Add-In (BAdI) SHP_SE_INBOUNDDELIVERYCRTRQ is available for this operation.