More Create Blog Sign In

ORACLE APPS DBA FAQS This blog is designed to capture/compile all important,useful and real time
questions,scenarios really required for a Oracle DBA and Oracle Apps DBA. Please do comment your
comments and suggestions.

There was an error in this gadget

Sunday, March 3, 2013 Followers

Followers (7)
How To cancel/ Restart the Cost Manager :

Behavior of Cost Manager:

Cost manager is not a typical concurrent manager that it finishes after is Follow
costing some transactions.
Cost manager it is rescheduling itself based on the the process interval
Blog Archive
specified in interface managers form.
2015 (12)
Cost Manager should stay in this status : “Pending Scheduled” and will restart 2014 (19)
itself based on the process interval specified in interface managers form. It
2013 (97)
calculates the re-launch time as start time + process interval.
December (6)
But there is no change in status when this happen
November (4)
October (9)
è To cancel/ Restart the Cost Manager : use one of the following method: ß September (14)
August (6)
Note : If you want to launch a new manager, cancel earlier manager first.
July (10)
a) use 'System Administrator' responsibility June (5)
Navigate to Concurrent/Request/view May (15)
Set : specific Request=on
April (3)
Name=Cost Manager.
March (8)

In the lower part of the Find requests window there is a field "Select the Duplicating database to a new
Host without connect...
Number of Days to view" set by default to 7 days.
-> Set "Select the Number of Days to view"=9999 How to avoid a failed duplicate
to overwrite the o...
In fact this field is a filter which limits how far back it will query requests.
Java upgrade from 1.4.2_06 to
1.6_25 for Discovere...
From here Cancel the Cost Manager which is Pending Scheduled.
or Oracle E-Business Suite Pre-
install Patches Report...
2 . Stop the Cost Manager.
How to add Multi Node on
E-Business Suite Release ...
a) If the above query did not retrieve any records then there is nothing to do,
Cold & Hot Disk Backup as
the Cost Manager is already stopped.
compressed using RMAN:

b) Otherwise, if the first record is showing Phase=Completed and Suggestions for SYSAUX
Tablespace grows rapidly
Status=Warning, then review the request log. or...
If the request log is showing the following, it suggests there is an older
How To cancel/ Restart the
concurrent request in Running or Pending phase: Cost Manager :
"A Cost Manager is already launched.
February (9)

Action: If you want to launch a new manager, cancel earlier manager first. January (8)
(MODULE=CMCTCM) : "
2012 (34)
In this case, scroll down until encountering the relevant concurrent request.
2011 (9)
c) If the record is showing Phase=Completed, then there is nothing to do, the 2010 (1)
Cost Manager is already stopped.
 About Me

d) If the record is showing Phase=Running then wait and query again and appsdba4all
again using the Refresh Data button, until Phase becomes Completed or
Manjunatha's passion for Oracle
Pending.
Apps DBA
View my complete profile
e) When the record is showing Phase=Pending and Status=Scheduled, then
perform the following quickly:
i) cancel the concurrent request using the Cancel button at the bottom
ii) press button Yes to acknowledge the Decision message.

f) If the Cost Manager was running, you may have to wait for the completion
of the cost workers. There are different program names here, depending on
the costing methods used at your site.
As soon as the Cost Manager is stopped, you can monitor the costing process
by repeatedly running the following SQL:

i) cost workers:

SQL> select organization_id,costed_flag,count(*) from

mtl_material_transactions where costed_flag is not null group by
organization_id,costed_flag;

or

ii) COSTMANAGER SQL script:

SQL> SELECT request_id RequestId,

request_date RequestDt, concurrent_program_name,
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 in ('CMCTCM', 'CMCMCW', 'CMCACW') AND
fcr.concurrent_program_id = fcp.concurrent_program_id AND
fcr.program_application_id = 702 AND fcr.phase_code <> 'C'

Cancel all the requests from the above output by navigating to,
System Administrator à Concurrent à Request.
Query for the Request Id returned from the select above.

In the lower part of the Find requests window there is a field "Select the
Number of Days to view" set by default to 7 days
-> Set "Select the Number of Days to view"=9999
In fact this field is a filter which limits how far back it will query requests.

Cancel the request id other than running. Let the running request get over.

2 - Run the cmclean.sql script available from MOS Note 134007.1 //< not
required >

3 - Restart the Cost Manager

Inventory à Setup : Transactions à Interface Managers

4. The Interface Manager screen pops up . The Cost Manager should be

the “first” one and its status should be “Active”.

5. A list of organizations pops up :

Select 'Cost Manager' - choose Tools à Launch Manager

Note: Check bellow images & change Cost Manager minutes '2' to '5'
If it is not, select it then click on tools on the menu bar and select launch. It
will start and run according to its schedule.

Tools Menu à select Launch Manager

Check to see whether actual cost worker completes successfully. Also verify
using the below that there are no error records:

SQL> select * from mtl_material_transactions where costed_flag =

'E';

Note : few important points :

To verify the version :
SQL> SELECT name, text FROM dba_source
WHERE name LIKE 'CMCTCM'
AND UPPER(text) LIKE '%$HEADER%'
AND line < 7;

PROCESS INTERVAL :
select PROCESSING_TIMEOUT, WORKER_ROWS, PROCESS_INTERVAL
from mtl_interface_proc_controls
where PROCESS_NAME='CMCTCM';
process_interval is in seconds and not in minutes. To schedule the cost
manager every, say, five minutes,

a). Relink the CMCTCM executable: adrelink.sh force=y ranlib=y "bom

CMCTCM"
b). Create Accounting - Cost Management Cannot Print Report out of memory
[ID 1062578.1]
c). Data Collection Scripts for Cost Management [ID 378348.1]
d). EBS LCM - How to do Setup for Landed Cost Management LCM [ID
837161.1]
e). How to resolve Pending or Erred Cost Manager or Cost Workers [ID
748704.1]
f). Cost Manager (CMCTCM) - is Scheduled More Than Once [ID 255947.1]
g). Cost Manager not processing records [ID 217068.1]
++++++++++++Manjunatha+++++++++++++++++++++
141493.1, 373207.1, 304313.1, 1360701.1, 740039.1 ,218204.1 & 304313.1
++++++++++++Manjunatha+++++++++++++++++++++
 Posted by appsdba4all at 4:48 AM

No comments:
Post a Comment

Enter your comment...

Comment as: Google Account

Publish Preview

Newer Post Home Older Post

Subscribe to: Post Comments (Atom)

Simple theme. Powered by Blogger.