Run Oracle E-Business Suite Period Close Diagnostic

Posted by Get Proactive Customer Adoption Team on Oracle Blogs See other posts from Oracle Blogs or by Get Proactive Customer Adoption Team
Published on Thu, 25 Oct 2012 04:32:26 +0000 Indexed on 2012/10/25 11:09 UTC
Read the original article Hit count: 292

Filed under:
Untitled Document

Be Proactive & Save Time—Use the Period Close Diagnostic During the Month

RedPath

Have you ever closed your books at the end of the month and, due to problems with your Oracle E-Business Suite Period Close, you found yourself working all night or all weekend to resolve your issues?

You can avoid issues by running the Oracle E-Business Suite Period Close Diagnostics throughout the month, prior to closing Oracle Financial Assets, General Ledger, Payables, and/or Receivables. You can identify issues that will interfere with your period close early, preventing last minute fire drills. Correct your errors or, if you need Oracle Support’s assistance, attach the output to a service request for faster resolution by the support engineer.

Oracle E-Business Suite Diagnostics are included in your Oracle Premier Support agreement at no extra charge. They are proactive, easy to use, tools provided by Oracle Support to ease the gathering and analyzing of information from your E-Business Suite, specific to an existing issue or setup. Formatted output displays the information gathered, the findings of the analysis, and the appropriate actions to take if necessary. These tools are designed for both the functional and technical user, providing no EBS administration features, so you can safely assign this responsibility to users who are not administrators.

A good place to start with the Support Diagnostics is the install patch Note 167000.1. Everything you need is in this patch and you install it on top of your E-Business Suite. If you are on EBS 12.0.6 or below, Oracle delivers the diagnostic tests in a standard Oracle patch and you apply it using the adpatch utility. If you are on EBS release 12.1.1 or above, your diagnostics are already there.

Oracle E-Business Suite Diagnostics:

  • Prevent Issues—resolving configuration and data issues that would cause processes to fail
  • Identify Issues Quickly—resolving problems without the need to contact Oracle Support
  • Reduce Resolution Time—minimizing the time spent to resolve an issue by increasing support engineer efficiency

In the example below, you will see how to run the EBS Period Close Diagnostic step-by-step using an SQLGL Period Closing Activity Test. This allows you to check throughout the month to identify and resolve any issue that might prevent closing the period in the General Ledger on schedule.

 

  1. Click the Select Application button. Select your Application. In this example, we will use the Period Close test. Scroll down to Period Close


  2. Step 1

  3. Place a check mark in the Period Closing box in the Select column. Click the Execute button at the bottom of the page

  4. Step 2

  5. Input the parameters. Click the Submit button


  6. Step 3



  7. Click the Refresh button, until the Status of the test changes from “In Progress” to “Completed”


  8. Step 4

  9. Click the icon under, View Report to view the test results


  10. Step 5

 

The report will complete successfully or show completed with errors. The report will show where the error is located, what the error is, and what action(s) to take for resolution. Remember, if you need to work with Oracle Support to resolve your issue, attach the report to your Service Request so the engineer can start working the issue.

With errors Completed with errors

Without errors Completed successfully with no errors

If you have questions, please ask in the E-Business Suite Category’s Diagnostic Tools Community. You may find the answer waiting for you in a prior community discussion or in one of the resources posted by an Oracle Support moderator.

Oracle’s Period Close Diagnostic, and the other E-Business Suite Diagnostics, save you time and help keep you on schedule. If you run the Period Close Diagnostic throughout the month, you can identify issues to resolve and get help, if needed. When opening a Service Request, attaching the output from the diagnostic report, speeds resolution. With the issues resolved ahead of time, your Period Close should complete without errors. Avoiding the unexpected, helps to close your books on time and without late nights or working through your weekend.

Recommended Reads

E-Business Suite Diagnostics Period / Year End Close [ID 402237.1] lists all of the Closing Period Diagnostic Tests. I highly recommend that customers execute these tests prior to closing a period. The period closing tests listed in this document help you identify known issues that prevent a successful period close. Use these tests prior to closing a period. To learn about all the available EBS Diagnostics, please review the E-Business Suite Diagnostics Overview [ID 342459.1].

© Oracle Blogs or respective owner

Related posts about /Get Proactive