My Oracle Support Banner

How Backdated Miscellaneous Transactions Are Costed on FIFO Costing. (Doc ID 2366173.1)

Last updated on JUNE 21, 2021

Applies to:

Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.


We are using FIFO method and perform following steps.

Item X On hand = 25 quantity

1- Receiving a new PO at 15-Feb-2018

 Item X new quantity 50 and 109.998 Cost

"Transaction Date": 15-02-2018 16:15:41
"System Date": 15-02-2018 16:15:59

2- Creating a miscellaneous issue for the old 25 at 1-Feb-2018

"Transaction Date": 01-02-2018 00:00:00
"System Date": 15-02-2018 16:17:58

3- Creating a miscellaneous receipt at 2-Feb-2018

50 Quantity and 100 Cost

"Transaction Date": 02-02-2018 00:00:00
"System Date": 15-02-2018 16:19:34

4- Creating a miscellaneous issue at 3-Feb-2018

"Transaction Date": 03-02-2018 00:00:00
"System Date": 15-02-2018 16:23:37

5 Quantity and left the cost field empty to take the default sequence as ordered First IN First Out.

The expected behavior that those 5 quantity who has issue at 3-2-2018 should be costed with 100. The Distribution showed that is was costed with 109.998.

Why is the system taking into consideration the sysdate not the transaction date ?


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.