ITPub博客

首页 > 数据库 > Oracle > Debug log of Cost Management

Debug log of Cost Management

原创 Oracle 作者:pan_tian 时间:2014-07-03 11:37:12 0 删除 编辑
1.Make sure to set the following profile options
MRP:Debug Mode = yes
MRP:Trace Mode = yes
CST: Cost update debug level = Full


2.Resubmit the error transactions for costing.
Uncosted/Failed transactions can be resubmitted through application itself.
Costs -> View Transactions -> Material Transactions.
From the menu, Tools Select All: Tools Submit All

Else, can use the following script to submit the records in MMT table:

update mtl_material_transactions
set costed_flag = \'N\',
error_code = NULL,
error_explanation = NULL,
transaction_group_id = NULL,
transaction_set_id = NULL
where organization_id = &organization_id
and costed_flag in (\'N\',\'E\');

commit;

3.Obtain the log file of the Cost Worker.


===Profile Details===

CST: Cost Update Debug Level

Indicates none or the level and type of debug messages to print in the cost update log file.

    Regular: Every subroutine.
    Extended: Every SQL statement.
    Full: Same as Extended and keeps any temporary data in the database.
MRP:Debug Mode
Indicates whether to enable debug messages within Oracle Master Scheduling/MRP. Available values are listed below:
Enable debug messages.
Do not enable debug messages.
This profile has a predefined value of No upon installation.


MRP:Trace Mode
Indicates whether to enable the trace option within Oracle Master Scheduling/MRP and Supply Chain Planning. Available values are listed below:
Enable the trace option within Oracle Master
Scheduling/MRP and Supply Chain Planning.
Do not enable the trace option within Oracle
Master Scheduling/MRP and Supply Chain Planning.
This profile has a predefined value of No upon installation.


<!-- Baidu Button BEGIN -->

来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/26687597/viewspace-1207443/ ,如需转载,请注明出处,否则将追究法律责任。

上一篇: APP-FND-01564: Oracle error 1403 in fdxwho
下一篇: 如何下载老版本的Oracle EBS
请登录后发表评论 登录
全部评论
暂无介绍

注册时间:2012-02-18

最新文章