Debug log of Cost Management

baobao

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.

albert.lgr

不錯，在不了解Cost Manager運作原因時，看看Debug信息。

beokc

不懂技术的漂过！~~没人顶起

lxtxgood

感谢楼主无私的分享，很不错的资料