Cost Manager Concepts in Oracle Inventory

Cost Manager Concepts in Oracle Inventory

Cost Manager is a Process that scheduled to run by default after every 5 minutes. At schedule interval, it runs and spawns ‘Actual Cost Worker’ process for each Inventory Organization in which there is a transaction in past 5 minutes. The process ‘Actual Cost worker’ processes Material Transactions and creates accounting entries for the material transactions.

The Cost Manager is mandatory to be Active if the Inventory transactions are to be accounted for. If Cost manager is Inactive, no accounting entries will be generated by Inventory module.

How to Start/Stop/Find Status of Cost Manager

In order to find status of Cost Manager, Navigate to
Inventory ModuleàSetupàTransactionsà Interface Managers

If you find that it is not running (the status will be Inactive), you can run it through ToolsàLaunch Interface Managers.
You should not run Cost Manager through standard reports interface, oracle does not recommend it. It should be only scheduled through this Interface Managers Form only. As a matter of good practice, it should be run from one User and should not be scheduled by more than one person at the same time.
You might need to stop ‘Cost Manager’ for debugging or some down time etc. If you want to stop the Cost Manager, log in from the user with which it is running. Navigate to (Menu) ViewàRequestsàFind (B) and find the specific request. Select the ‘Cost Manager’ request and click ‘Cancel Request’ button to cancel the schedule request.

How to find Un-costed Transactions

To find out if there is any pending transaction, Navigate to
Inventory ModuleàAccounting Close CycleàInventory Accounting Periods
Select the particular period and click on Pending button. It should sow Zero count in Uncosted Material/WSM.

To find Uncosted Transactions through SQL, you can use this sql
selectcount(mt.transaction_id)
from mtl_material_transactions mt
where mt.costed_flag=’N

How Oracle maintains Costed Transactions.

Oracle maintains three flags for costed transactions. The flag column is named costed_flag in table mtl_material_transactions. 
N             Means the transaction is not yet costed and waiting to be costed
Null        If the transaction is costed, the costed_flag becomes null
E              If the transaction cannot be costed for any reason, the costed_flag becomes E.
If you are using Average costing and one transaction gets the flag is ‘E’, Oracle will stop all following transactions to be costed. If you find many hundreds of transactionswithcosted_flag= ‘N’ , it may depict that one or more of the transaction in that Inventory Organization has an Error and it has stopped subsequent transactions to get costed.

This entry was posted in EBS - Functional, Oracle, Supply Chain. Bookmark the permalink.
  • Oracle_learner

    hi,

    When i am using the condition costed_flag is not null the select query is taking too much time or when i am using costed_flag in (‘N’, ‘E’) in where clause,query completes in seconds.

    the meaning of both conditions are same then why table MTL_MATERIAL_TRANSACTIONS is reacting differently

  • http://profile.yahoo.com/PU5PQTAXQNHWXMQ5WLWPWDGSXI Lua Chon

     I know want what are cases generate value New_cost column different than Actual cost field of MTL_MATERIAL_TRANSACTIONS table?