Professional Documents
Culture Documents
Lot Expiration Date
Lot Expiration Date
Why Material Transactions Shows Latest Expiry Date Always For The Transactions Happened In
The Past? (Doc ID 2339862.1)
In this Document
Goal
Solution
APPLIES TO:
GOAL
Why material transactions shows latest expiry date always for the transactions happened in the past?
STEPS
SOLUTION
The lot expiration is tied to the lot itself and not to the transaction. So, if you do a transaction on November 1st with one lot
expiration and then on November 15th, you change the lot expiration to a later date, the lot expiration in the historical
transaction will change.
You will note that the lot transaction table (MTL_TRANSACTION_LOT_NUMBERS) does not track the expiration date so
has no way to keep a historical view of the lot. Instead, the transaction directly writes expiration to the lot table
(MTL_LOT_NUMBERS). When querying too, the transaction shows and pulls the data from the lot itself
(MTL_LOT_NUMBERS). As a result, the latest lot expiration will show when you query past transactions. You can see
that this is part of the design because the lot transaction table does not even have a place to store expiration date.
Instead, when you query lot transactions a view (MTL_TRANSACTION_LOT_VAL_V) is used to join to the lot table and
pull the lot expiration.
Also note that the lot expiration is only entered on new lots. If you are transacting a new lot, you enter the expiration
date either when you create the lot, or on the first transaction that creates the lot. The subsequent transactions on the
same lot will see the expiration date but not have access to update it.
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=4ic4y4scp_4#FIX 1/2
4/26/2018 Document Display
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=4ic4y4scp_4#FIX 2/2