Transportation Order Loading Appointment Request In

Use this service to create transportation unit activities (TUs) and assign deliveries to them. Additionally, the creation of vehicle assignments for the TUs is possible.

Technical Data

Entity Type	Service Operation
Software Component Version	EWM 9.10
Release State	Released with Restrictions
Technical Name	TransportationOrderLoadingAppointmentRequest_In
Namespace	http://sap.com/xi/EWM/Global
Application Component	SCM-EWM
Category	B2B
Direction	Inbound
Mode	Asynchronous
Idempotency	Not Applicable
Change/Update Behavior	Not Applicable
P2P Communication Enabled	Yes

Business Context and Use

Receive transportation planning information to create transportation units/vehicles and to assign deliveries to transportation units.

The TransportationOrderLoadingAppointmentRequest inbound operation (TransportationOrderLoadingAppointmentRequest_In) is used to receive transportation planning information from a transportation planner or an external transportation planning system. Based on the message content – in particular, based on the item structure – the system creates transportation unit activities and assigns deliveries to the transportation unit activities (TUs) created. The creation of vehicle activities and assignment of the created TUs to vehicle activities is optional.

This service operation is used in the integration for Inbound Processing: Transportation Planning in TM-EWM.

Related Operations

After warehouse execution for transport (loading, goods issue, and departure from yard) the service operation TransportationOrderLoadingAppointmentNotification sends the actual TU loading information (that is, deliveries and handling units loaded onto the TU).

Error Handling

The TransportationOrderLoadingAppointmentRequest inbound operation (TransportationOrderLoadingAppointmentRequest_In) supports Forward Error Handling. In the table below is a list of categorized errors that might occur.

Error Catagory	Description	Possible Occurrences
DCE	Determination and Conversion Error	Error on identification of EWM deliveries or access to deliveries
PRE	—	Not possible to derive EWM master data or configuration from the message input
PRE.VAE	Value Error	—
PRE.CVE	Cross Validation Error	Input data does not conform to EWM configuration or master data; also, invalid input data for creation of TU or errors during delivery assignment. For example, the means of transport in the message is unknown in EWM.
PRE.IDE.KEY	Key Error	EWM entity referenced by the ID provided could not be found. For example, the EWM delivery could not be determined. This might occur because the delivery was not yet distributed. Messages with this error should be scheduled for regular repeating.
FOE	Format Error	Format inside message data does not conform to the expected format of the data type.
CON.CMC	Unequal Context	Mismatch between the item that should be assigned to a TU and the characteristics of the TU: for example, when attempt made to assign inbound delivery to a TU for outbound or, a mismatch made in the warehouse number of a TU and warehouse number of delivery to assign to the TU.
CON.URC	Unknown Reference Conflict	Examples: Logical systems contained in the message were not configured in the system landscape. Reference documents could not be determined (that is, referenced ERP delivery). Items that are references in the message are not contained in the message itself.

Notes on SAP Implementation

For more information about SAP implementation requirements, see the configuration guide on the integration of TM-EWM .

Enhancements

For information about the Business Add-In (BAdI) available for this service operation, see the documentation on BAdI: TransportationOrderLoadingAppointmentRequest_IN (/SCWM/EX_SR_BIF_TOLDAP_RQIN). In Customizing for Extended Warehouse Management, choose Start of the navigation path Business Add-Ins (BAdIs) for Extended Warehouse Management Next navigation step Interfaces Enterprise Services TM-EWM-Integration Enhancements to TM-EWM-Integration BAdI: TransportationOrderLoadingAppointmentRequest_IN End of the navigation path .