If you use EBS Cost Management, you process Cost Transactions. Cost Transactions are an integral part of each Period Close. We have an announcement to help make processing your Period Closures easier.
Costing Transactions can be very complicated in their set-up and management. In the past, when you had a problem with Costing Transactions, you may have used a Diagnostic, sql scripts, and/or the Apps Check provided by Oracle Support, to help diagnose the issue. A lot of the information was data-dump-details of the problem transaction(s), but it didn’t tell you what was wrong. To determine what was wrong, you needed a detailed understanding of how Costing Transaction management and troubleshooting works. You also had to log a Service Request (SR) to get Oracle Supports assistance in resolving the issue. To help make the process of diagnosing Costing Transactions easier, Oracle Costing Support is proud to announce the release of the ‘Cost Management Period Close Analyzer’ Doc ID 2315206.1. Following is an example of an erred transaction:
The EBS Cost Management Period Close Analyzer includes:
- Identification and solutions to known Inbound Transaction issues
- Transaction Summary and Details
- Proactive recommendations, code levels, and a full Diagnostic Apps Check
Have a look at the sample output in the EBS Cost Management Period Close Analyzer Doc ID 2315206.1 to learn more.
Like all EBS Analyzers, the Cost Management Period Close Analyzer is available via its own MOS document, Doc ID 2315206.1, the EBS Analyzer Index, Doc ID 1545562.1, and will be available in the May 2018 Analyzer Bundle Menu Tool, Doc ID 1939637.1.
Don’t forget to provide your Feedback on the Analyzer via Doc ID 2315206.1. We look forward to continual update and improvement of this Analyzer based on your feedback.
This analyzer has been in the works for a long time, and Costing Support is very happy to make it available. Please start using it today to help resolve your Costing Transaction issues.