Last updated on NOVEMBER 05, 2016
Applies to:Oracle Cost Management - Version 22.214.171.124 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
The cost manager orders the transactions for processing as follows:
1. trunc(transaction_date) - This is the transaction date without the
timestamp. We cannot include the timestamp because prior to 11.5.10, PO
transactions did not have the timestamp on it. So any transactions created
prior to 11.5.10 would not have a timestamp. Consequently, using the
timestamp would cause transactions to be costed out of order.
2. creation_date : The creation_date is used to order transactions created on
the same day.
3. transaction_id : Transaction_Ids are not guaranteed to be used in a
sequence given the RAC architecture, and are only used to break any ties.
Since the order by clause is using trunc (transaction_date) i.e time stamp is not included in
the order by clause. If the cost manager is stopped, then transactions created on the same day using
the time stamp in the transaction_date to identify the order is not possible. This leads to
incorrect average cost calculation.
The reason for the trunc(transaction_date) usage is that the PO receipts transactions prior to
11.5.10 did not have the timestamp.
However on 11.5.10 the time stamp is included in these transactions. Thus the need to remove the
trunc out of the order by clause is needed to avoid incorrect ordering or transactions perform on
the same day when the cost manager is stopped.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms