Orphan WIP Issue NOT Costing But Has No Error
(Doc ID 1354041.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle Bills of Material - Version 11.5.10.2 and laterInformation in this document applies to any platform.
Executable:CMCTCM - Cost Manager
Form:INVTVTXN.FMB - View Transactions
Symptoms
The costing manager runs but one transaction remains unprocessed with Costed Flag = No (meaning the costing manager has not yet picked it up).
The costing manager is running without errors every few minutes.
Just to restate -- There are No Errors.
Example Transaction Details
This is a quick review of some of the columns in the transaction table (MTL_MATERIAL_TRANSACTIONS).
| Column | Value |
|---|---|
| TRANSACTION_ID | 11742 (Unique transaction id) |
| COSTED_FLAG | N |
| ERROR_CODE | NULL |
| ERROR_EXPLANATION | NULL |
| TRANSACTION_SOURCE_TYPE_ID | 5 (WIP Job or Schedule) |
| TRANSACTION_TYPE_ID | 35 (WIP Component Issue) |
| TRANSACTION_SOURCE_ID | 4186 (Relates to Job in WIP_ENTITIES) |
Steps
1. Run Costing Manager
2. Review costed transactions
3. See one transaction is not Costed but it has no errors.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |