PAC Costing Problem: Transaction Stuck in the MTI MTL_Transactions_interface: The PAC Periodic Update Transaction Fails with Error Message 'NO OPEN PERIOD FOUND FOR DATE ENTERED'
(Doc ID 2023514.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 and R12.2.4 versions, Inventory Costing
While upgrading the R11 instance to R12.2.4. We use "Oracle EMEA Add-on Localizations User Guide for Turkey – Discrete Manufacturing"document to setup Turkey localization.
Oracle EMEA Add-on Localizations
User Guide for Turkey Discrete Manufacturing
Part No. E15565-01
The PAC Costs are calculating incorrectly.
The costs to be calculated correctly
The issue can be reproduced at will with the following steps:
1- Create new item
2- Open PO with this item (Quantitiy: 10, unit_price: 10)
3- Match PO to Invoice (Quantitiy: 10, unit_price: 15)
4- System create an IPV on invoice as 50 TL( Turkish Lira).
5- Run costing programs.
6- System calculate unit cost as 10TL.
The correct cost is 15TL for one sample.
1. Run Periodic Cost Update
2. Find that the transactions inserted into the Transaction Open Interface mtl_transactions_interface table
are failing with error = No Open Period
Note: Customer working with PAC since 2008. Customer updates Periodic Cost
Update for closed inventory periods. The update is taking place in customer
master organization GLO (organization_id = 103) for which customer never
opened any period.
Customer notes: " transaction open interface is Periodic Cost Update which
should evaluate the transaction date against the periodic period and not the
Support Notes: Inventory Code inspected and should be skipped over for PAC
process when transaction type is for a PAC interface row.
The issue has the following business impact:
Due to this issue, users cannot cost transactions in error
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|