In this Document

APPLIES TO:

PURPOSE

The purpose of this document is to understand the scheduling and working of the Cost Manager and debugging a few errors in the Cost Manager log.

TROUBLESHOOTING STEPS

--- Scope and Application ---

This note is applicable to all versions.

--- Understanding Cost Manager ---

COST MANAGER FUNCTIONING

A Cost Manager runs in every scheduled to run as per the setting in the Process Interval. The process interval is set in the Interface Managers form.

The navigation is as follows:

Inventory -- Setup -- Transactions -- Interface Managers

In case a Cost Manager does not run then perform the following:

• Standard Costing
  1. To cancel the Cost Manager: 
     System Administrator -- Requests -- View -- Go To Specific Request and in the Name give Cost Manager.From here cancel the Cost Manager that is Pending Scheduled.
  2. To Reschedule the Cost Manager 
     Inventory -- Setup -- Transactions -- Interface Managers From here Change the Process Interval to the time, as you want the time interval when the Cost Manager should run.
  3. To launch the Cost Manager Tools (Menu Bar) -- Launch Manager --Submit (No scheduling for the Cost Manager should be done in the Request Form) 
     
     The most important thing to be noted is that the Cost Manager should not be scheduled from the Schedule button in the request form by which the Cost Manager is launched.
     Cost Manger should be scheduled through Interface managers only.
     
     

• Average Costing
  
  In an Average Costing run the BDEprdcls.sql available in <Note 246467.1>. Check for the erred transactions. Resolve the erred transaction and then perform the above steps as the Standard Costing. Along with erred transactions also check that there should not be any Pending Average Cost Update. To check for pending Average Cost update, Go to Request and select specific request. Query for Average Cost Update. In case there is any pending Average Cost Update. Kill 
  the process and then perform the above steps as in Standard Costing. 
  
  Launching of actual cost workers is done by cost manager exclusively. Cost manager assigns transactions to different actual cost workers based on pre-defined rules. Hence, one MUST NOT launch actual cost workers by some other means. This will lead to data corruption.

  Cost Manager spawns one Actual Cost Worker per Inventory Organization

  
  
  If the Cost Manager is still not running, run the following query:

  SELECT request_id RequestId, 
  request_date RequestDt, 
  phase_code Phase, 
  status_code Status FROM 
  fnd_concurrent_requests fcr, 
  fnd_concurrent_programs fcp 
  WHERE fcp.application_id = 702 AND 
  fcp.concurrent_program_name = 'CMCTCM' AND 
  fcr.concurrent_program_id = fcp.concurrent_program_id AND 
  fcr.program_application_id = 702 AND fcr.phase_code <> 'C'
  
  The output of the above query would be Request Id and its Status Code and Phase Code. Kill any process that is in Pending status or any old request that you can still see as running. 
  
  The lookup for the output would be: 

PHASE CODE: 

 
STATUS CODE: 

Now launch the Cost Manager again, it should work fine. 

If still there are issue, please Contact Oracle Support. When logging a service request with Oracle Support, Please provide the output of the following:

The output of the following scripts available in <Note:246467.1>

• CstCheck.sql
• BDEprdcls.sql
• Output of the Query 
  
  SELECT request_id RequestId, 
  request_date RequestDt, 
  phase_code Phase, 
  status_code Status FROM 
  fnd_concurrent_requests fcr, 
  fnd_concurrent_programs fcp 
  WHERE fcp.application_id = 702 AND 
  fcp.concurrent_program_name = 'CMCTCM' AND 
  fcr.concurrent_program_id = fcp.concurrent_program_id AND 
  fcr.program_application_id = 702 AND fcr.phase_code <> 'C'

GENERAL ISSUES and ERRORS

ERROR #1:

The cost manager schedule requests end in error log:

APP-FND-01564: ORACLE error 1017 in AFPCOA 
Cause: AFPCOA failed due to ORA-01017: invalid username/password; logon denied

  

SOLUTION:

1. Check what the value of this variable is when the managers are started.
2. Make sure it points to a valid directory and that it is writable by the owner of the Database.
3. Make sure that this directory is listed in the database initialization parameter utl_file_dir.
4. Resubmit:     Inventory Responsibility > Transactions > Material Transactions, in the find window set fields as follows:
   1) The Transaction dates = 
   2) Costed = Error 
   Click Find > In Material Transactions Form > click tools > Select All > click tools Submit All 
5. If this does not cost the transactions, please log a datafix SR with Support.

ERROR #2:

This error has been introduced on 11.5.9. Prior to 11.5.9, the Cost Manager would error out only by saying Cost Manager is already running. In 11.5.9 you would get the following error:

APP-00126: This request has previously been run by the concurrent manager and 
cannot be rerun. 
Please submit a new request with the required parameters. 
/application1/prodmgr/bom/11.0.28/bin/CMCTCM 
Program exited with status 1

  

SOLUTION:
Find the request_id already running by the select statement on fnd_concurrent_requests. Kill the request and re-launch the Cost Manager