Manage the Cost Manager in Oracle EBS 12.2
ملخص
Pixel shares a practical guide to starting, stopping, and restarting the Cost Manager in Oracle EBS 12.2. It explains how the manager processes inventory and work in process transactions, why uncosted transactions can delay inventory period close, and what to check after restarting concurrent processing.
DEV Community
Starting, Stopping and Restarting the Cost Manager in Oracle EBS 12.2 (Inventory Interface Managers)
If inventory or work in process transactions in your Oracle E-Business Suite environment aren't being costed, one of the first things to check is whether the Cost Manager is running. This post explains what it does, why it matters, and how to start, stop and restart it in EBS 12.2. What the Cost Manager does Oracle Cost Management automatically costs and values inventory, work in process and purchasing transactions, so that inventory value matches the accounting transactions behind it. The Cost Manager is the background process that does this work for you. It runs in the background at a set process interval and passes pending transactions to worker processes. Oracle's Inventory User's Guide says the material cost transaction manager must be started for material transactions to be costed. It also covers resource transactions from work in process. Oracle recommends setting the interface manager to run at five-minute intervals. Why it matters If it isn't running, transactions stay uncosted. Inventory valuation and accounting fall behind, and uncosted transactions can stop you from closing an inventory period, since Oracle lists "no uncosted material transactions" among the period close conditions. When you would start, stop or restart it On a new environment where the transaction managers have never been launched. Launching them is part of Oracle's Cost Management setup steps. After you have fixed the cause of a costing error and want processing to resume. After maintenance that affects concurrent processing, such as bouncing the concurrent managers. These managers run as concurrent requests, so it's worth checking they are still Active afterwards. Before you start You need a user with the Inventory responsibility, or a custom responsibility that includes the Interface Managers function. In this walkthrough I used SYSADMIN, which had the Inventory responsibility assigned. Step 1: Open the Interface Managers window Option A: from the navigator (HTML home page) Log in and choose the Inventory responsibility. Then go to Setup > Transactions > Interface Managers. Option B: from Oracle Forms Use File > Switch Responsibility (or the toolbar icon) and choose Inventory. In the Navigator, press Ctrl+L and search for %launch%. Select Launch Interface Managers and click OK. Don't pick Launch Cost Collection Manager or Launch Cost Update, which are different functions. Step 2: Read the window The Interface Managers window lists the managers and their status. In this environment it showed Cost Manager, Lot Move Transaction, Material transaction and Move transaction, all Inactive. Status: Active or Inactive. Worker Rows: the maximum number of rows assigned to a worker (200 here). Process Interval: how often the manager checks for work (5 minutes here, matching Oracle's recommendation). Step 3: Start (launch) the Cost Manager Select the Cost Manager row. Choose Tools > Launch Manager. The Launch Inventory Managers window opens with the name set to Cost Manager and Run the Job set to As Soon as Possible. Click Submit. If the manager is already active, Oracle shows a warning first. I left the Schedule button alone, because the repeat interval comes from the Process Interval in the Interface Managers window. Requery the Interface Managers window. The status now shows Active. To confirm, open the Requests window. The Cost Manager request shows Phase Running and Status Normal. Step 4: Stop the Cost Manager Oracle's documentation notes that transaction managers keep running at their interval until you delete them through the concurrent manager. So to stop it: Open the Requests window and find the running Cost Manager request. Select it and click Cancel Request. Requery the Interface Managers window. The status returns to Inactive. Step 5: Restart the Cost Manager A restart is a stop followed by a start: Stop it as in Step 4. In the Requests window, check that no cost worker requests are still running, and let them finish. Launch it again as in St...

Powered by Readybot.io