Wednesday Oct 24, 2012

Run Oracle E-Business Suite Period Close Diagnostic

Untitled Document

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


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].

Thursday Oct 18, 2012

Install Oracle Configuration Manager's Standalone Collector

Untitled Document


The Why and the How


If you have heard of Oracle Configuration Manager (OCM), but haven’t installed it, I’m guessing this is for one of two reasons. Either you don’t know how it helps you or you don’t know how to install it. I’ll address both of those reasons today. First, let’s take a quick look at how My Oracle Support and the Oracle Configuration Manager work together to gain a good understanding of what their differences and roles are before we tackle the install.

Oracle Configuration Manger is the tool that actually performs the data collection task. You deploy this lightweight piece of software into your system to collect configuration information about the system and OCM uploads that data to Oracle’s customer configuration repository. Oracle Support Engineers then have the configuration data available when you file a service request. You can also view the data through My Oracle Support.

The real value is that the data Oracle Configuration Manager collects can help you avoid problems and get your Service Requests solved more quickly. When you view the information in My Oracle Support’s user interface to OCM, it may help you avoid situations that create problems.

The proactive tools included in Oracle Configuration Manager help you avoid issues before they occur. You also save time because you didn’t need to open a service request. For example, you can use this capability when you need to compare your system configuration at two points in time, or monitor the system health. If you make the configuration data available to Oracle Support Engineers, when you need to open a Service Request the data helps them diagnose and resolve your critical system issues more quickly, which means you get answers more quickly too.

Quick Installation Process Overview

Before we dive into the step-by-step details, let me provide a quick overview. For some of you, this will be all you need. Log in to My Oracle Support and download the data collector from Collector tab. If you don’t see the Collector tab, click the More tab gain access. On the Collector tab, you will find a drop-down list showing which platforms are available. You can also see more ways to the Collector can help you if you click through the carousel of benefits.

After you download the software for your platform, use FTP to move that file (.zip) from your PC to the server that hosts the Oracle software. Once you have that file on the server, locate the $ORACLE_HOME directory, and unzip the file within that directory. You can then use the command line tool to start the installation process. The installation process requires the

  • My Oracle Support credential (Support Identifier, username, and password)
  • Proxy specification (Host IP Address, Port number, username and password)

Installation Step-by-Step
  1. Download the collector zip file from My Oracle Support and place it into your $Oracle_Home
  2. Unzip the zip file you downloaded from My Oracle Support – this will create a directory named CCR with several subdirectories Step 2
  3. Using the command line go to “$ORACLE_HOME/CCR/bin” and run the following command “setupCCR”
    Step 3
  4. Provide your My Oracle Support credential: login, password, and Support IdentifierStep 4
  5. The installer will start deploying the collector applicationStep 5
  6. You have installed the Collector
  7. Step 6

Post Installation

Now that you have installed successfully, the scheduler is ready to collect configuration information for the software available in your Oracle Home. If you want to run an instrumentation script to start the configuration collection of your Oracle Database server, E-Business Suite, or Enterprise Manager, you will find more details on that in the Installation and Administration Guide for My Oracle Support Configuration Manager.

Related documents available on My Oracle Support

Let the 'Get Proactive' team help you achieve resolution faster; simplify your daily operations; reduce risks and maximize uptime through preventative maintenance.

How? By sharing our own best practices, tips, and tricks. Get on the ‘Insider's Track.’

Stay Connected


« October 2012 »