Incorrect posting to Tran_data for Actual Landed Cost (Doc ID 2829140.1)

Last updated on OCTOBER 05, 2023

Applies to:

Symptoms

Incorrect posting to Tran_data for  Actual  Landed Cost (ALC)


Steps :

 1 - Create a cost component: Expense Type = Zone, Calculation Basis = Specific, Component Per Count = 1, Component Per Count UOM = EA (exactly like the example ILFRT_$ attached)
2 - Create a PO with several items
3 - Ensure the items have expenses estimates for the same component.
4 - Ensure that each item has a different quantity from the others (e.g.: Item 1 = 10, Item 2 = 12, Item 3 = 17 etc.). As a result, each item will have a total expense distinct from the others.
5 - Receive the items. Quantity received = quantity ordered (no qty discrepancy).
6 - Take note of the postings to GL. So far so good - the cost = ELC.
7 - Enter an Obligation
8 - Ensure that the Quantity in the obligation is the exact sum of the quantity of the PO. In the example attached, the PO has a sum of 366 EA, hence the quantity in the obligation is also 366.
9 - The cost in the obligation must be different than the total cost of the expense in the PO, in order to generate a difference. In the example provided, the cost is $300. That yields an allocation of $0.8197 actual per item in the order, regardless of the original estimate.
10 - Approve the obligation
11 - Finalize ALC
12 - Observe the postings to GL (TRAN_DATA or TRAN_DATA_HISTORY). Note that the quantities are totally off, creating a significant difference in the ALC.
13 - Note that the ALC screen looks fine - only the postings are wrong - but that causes significant accounting discrepancies
14 - Also note that the Actual Value is correct. In the example, as mentioned above, the actual cost of the expense is 0.8197 per EA, for all items, regardless of the original ELC. That is correct.

Changes

Cause

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