Symptom
The Actual Execution On date in the Goods and Activity Confirmation (GAC) differs from the Shipment Date in the 3PL Outbound Delivery.
Environment
SAP Business ByDesign
Reproducing the Issue
- Go to the Third-party logistics work center.
- Open the Outbound deliveries sub-view under 3PL Outbound view.
- Search and open the relevant Outbound Delivery ID.
- Observe the Shipment Date in Outbound Delivery.
- Navigate to the document flow.
- Open the Goods and Activity Confirmation (GAC).
- Observe the Actual Execution On date is different from the Shipment date in the Outbound Delivery.
Cause
Prerequisite:
The 3PL Outbound Delivery is created via OutboundDeliveryExecutionConfirmation (ODEC) interface.
Based on the ShippingDateTimePeriod values provided in the payload:
- The system sets the StartDateTime to the Shipment Date of the outbound delivery.
- The system sets the EndDateTime to the Actual Execution On date of the GAC.
Example payload:
<ShippingDateTimePeriod>
<StartDateTime timeZoneCode=""></StartDateTime>
<EndDateTime timeZoneCode=""></EndDateTime>
</ShippingDateTimePeriod>
Resolution
Please follow the steps below to set the Shipment Date and Actual Execution On date to the same value
- Go to the Third-Party Logistics work center.
- Open the Outbound Deliveries sub-view under the 3PL Outbound view.
- Search and select the relevant Outbound Delivery.
- Choose Actions button and select Undo Release.
- Choose Edit.
- Make a small change to the Shipment Date and Delivery Date (for example, add 1 minute).
- Choose Release.
After performing these steps:
A new GAC gets created with the Actual Execution On date matching the Shipment Date in the Outbound Delivery.
Keywords
actual execution on, shipment date, outbound delivery, goods and activity confirmation, 3PL, shippingdatetimeperiod, payload, date discrepancy, logistics, SAP ByDesign, outbound logistics , KBA , AP-ODP , Outbound Delivery Processing , AP-IP-GAC , Goods and Activity Confirmation , Problem
SAP Knowledge Base Article - Public