My Oracle Support Banner

OTM Order Base Line Delivery Dates are Not The Same as PO Promised Dates from EBS (Doc ID 740115.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5 to 5.5
This problem can occur on any platform.


-- Problem Statement:
On 5.5.04:
A purchase order is submitted containing dates, for example:
Promised Need by
-------- -------
15.05.2008 26.05.2008
10.15.2008 16.08.2008

These data are submitted as part of the payload to a BPEL process. Looking at the flow of the BPEL process it can be seen that the dates are correct in the activity called GetOtmDocument, e.g.

NEED_BY_DATE = 2008-05-26T14:59:52.000+04:00
PROMISED_DATE = 2008-05-15T15:52:20.000+04:00

Later in the flow, a Transform activity is called. After the transformation, the dates have been modified, so they now look like this:

EarlyDeliveryDate = 20080505155220
LateDeliveryDate = 20080525155220
i.e. 05.05.2008 and 25.05.2008.

These modified dates are still retained in the target application and can be verified in the OTM Transmission Manager as follows:

EarlyDeliveryDate = 20080505155220
LateDeliveryDate = 20080525155220

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:

1- Setup an EBS (PO) - OTM integration.
2- Create Standard Purchase Order in Purchasing > approve it.
3- Search in OTM corresponding Order Base.

-- Business Impact:
The issue has the following business impact:
Due to this issue, OTM order base dates are different than the PO dates.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.