Using Oracle Applications Manager (OAM), you can monitor components of your Oracle E-Business Suite instance.
For more information on setting up OAM, as well as other features, see the Oracle E-Business Suite System Administrator's Guide - Configuration.
The Applications Dashboard provides a "snapshot" of your Oracle E-Business Suite system. Information is grouped under the following tabs: Overview, Performance, Critical Activities, Diagnostics, Business Flows, Security, and Software Updates.
For information on Software Updates, see: Software Updates, Oracle E-Business Suite Patching Procedures.
From the Dashboard you can navigate to the Site Map, or use the drop-down menu to navigate to any of the following pages:
Application Services
Configuration - Overview
Forms Sessions
Database Status
Applied Patches
Patch Wizard
Workflow Manager
Oracle Applications Manager uses the collection program OAM Applications Dashboard Collection (short name: FNDOAMCOL) to gather the information displayed. The default repeat interval for this program is 10 minutes. To immediately regather the data and update the display for a particular region, click the corresponding Refresh icon. If the OAM Applications Dashboard Collection request is not running when you log in to the Oracle Applications Manager, a request will be submitted automatically under your username.
Note: The status of Web Components is collected manually from the Dashboard.
This page provides an overview of the general status of your system. It includes the following regions:
Use this region to view the status of each host machine in your system. The display shows which services are installed on which host machine and the statuses of these services.
Services displayed that represent more than one service component (such as Forms) indicate the status of the worst-case component. For example, if the Forms Listener is down, but the other Forms components are running, the down status will be indicated on this page.
The Database, Concurrent Processing, Forms, and Web status indicators drill down to the Applications System Status page where you can view the status of each individual service.
Host - the host name.
Platform - the host's operating system.
Admin - indicates whether the Admin server has been installed on the host machine.
Database - indicates the status of the database instance installed on the host machine.
Concurrent Processing- indicates the status of the Internal Concurrent Manager and the services managed by the ICM.
Forms - indicates the status of the Forms Server components: Forms Listener, Metrics Server, Metrics Client, and OAM Generic Collection Service.
Web - indicates the status of the Apache Web Listener.
The purpose of this region is to alert you to system-level changes that have occurred in the last 24 hours. Use this data to help diagnose sudden changes in the functioning of your applications system.
To see the list of Patches Applied, click on the number to drill down to the Patch Summary page.
To see the list of Site Level Profile Options, click on the number to drill down to the Site Level Profile Settings page.
To see the list of Applications Context Files Edited, click on the number to drill down to the Applications Configuration Parameters page. Changes made to context files can impact your overall processing configuration and the functioning of business processes.
This region lists the number of system alerts in the categories listed below. If your system is functioning well, there should be no new alerts reported. When an alert of a particular type first occurs, it is counted as a new alert. It remains new until the status is manually changed by the administrator. If an alert of the same type occurs again while the original alert is still in open or new status, it is counted as a new occurrence.
New Alerts - alerts that have not yet been acknowledged by the administrator. An alert is acknowledged when it is manually moved from a status of "New" to a status of "Open" or "Closed."
New Occurrences - additional occurrences of alerts that are in new status.
Open Alerts - all alerts that are in an open status. An alert must be manually moved from the new to open status.
Open Occurrences - all occurrences of alerts that are currently open. Click on the number for any of these to drill down to the System Alerts and Metrics page.
This region lists the status of the web components. Status values may be "Up," "Down," or "Warning".
The status of each Web component is determined by testing the corresponding URL as defined in the component's Web agent profile option. The Warning status will be displayed if the profile option is not set. Otherwise, a status of Up or Down will be returned based on the success of the URL test. The profile options are listed with their corresponding components below.
PL/SQL Agent - Uses profile option APPS_WEB_AGENT (Applications Web Agent). Look for errors in the Apache error log ($LOG_HOME/ora/10.1.3/Apache).
Servlet Agent - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If down, the Self-Service Framework-based Applications will not function, as well as all other servlet-based features. Look for errors in the Apache error and access logs (see above for location). Also, execute the Servlet Ping from the System Administration Diagnostics menu.
JSP Agent - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If down, execute the JSP Ping from the System Administration Diagnostics menu.
JTF - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent).
Discoverer (if installed) - Uses profile option ICX_DISCOVERER_VIEWER_LAUNCHER (ICX: Discoverer Viewer Launcher). If down, you will not be able to run BIS reports.
Personal Homepage - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If down, you cannot log on through the Personal Homepage.
TCF - Uses profile option APPS_SERVLET_AGENT (Apps Servlet Agent). If down, try running the AOL/J Diagnostic or the Servlet Ping utilities from the System Administration Diagnostics menu.
This page lists each Applications Server and its status. Each server type expands to display the host name, which expands to display the status of each server component.
Navigation: Applications Dashboard (Overview page) > (drill down on) Database, Concurrent Processing, Forms, or Web column (under Applications System Status)
Administration
Database- expands to display the instance name and status. Drill down on the instance name to display the Database Status Details page. Concurrent Processing - expands to display concurrent managers and services controlled by the Internal Concurrent Manager. These expand to display the instances of the managers and services and their statuses. Drill down on the instance names to display the Service Instances page.
Forms - expands to display the Forms server components: the Forms Listener, the Metrics Server, the Metrics Client, and the OAM Generic Collection Service. The component names expand to display the service instances. Drill down on the instance name to display the Service Instances page.
Web - expands to display the web component: the Apache Web Listener. The component name expands to display the service instance name. Drill down on the instance name to display the Service Instances page.
Click on the Focus icon for an item to display only its status and the status of its children.
The Performance region lists Activity and System Throughput indicators. Each of the values listed for Activity and System Throughput links to the related detail page.
Forms Sessions - the number of running Forms sessions. Drills down to the Forms Sessions page.
Database Sessions - the number of active database sessions. Clicking the value runs the Show Active Database Sessions request and returns the results page.
Running Concurrent Requests - drills down to the Search for Requests Results page showing all currently running requests.
Service Processes - drills down to the System Activity page. Service processes include all concurrent manager processes and all processes managed by the ICM. If you have set up your system to have other services managed by the GSM, those services are included as well.
Services Up - the number of service instances whose target services match the actual services. Services Down - the number of service instances whose target services do not match the actual services.
Invalid Database Objects - drills down to the Invalid Database Objects page displaying the search results for invalid objects owned by the APPS schema.
Unsent Workflow E-Mail
Completed Concurrent Requests - the percentage of concurrent requests submitted in the last 24 hours that have completed.
Sent Workflow E-Mail - the percentage of Workflow e-mail sent successfully.
The Critical Activities region lists concurrent programs that perform maintenance activities. The programs are grouped by activity type and by application. To display only a particular group, click the group’s Focus icon.
To add or delete a program to the critical activities list, click the Modify Monitored Program List button to access the Modify Monitored List page.
To change the frequency that a monitored program is run, click the Update Frequency button.
For each critical activity, the following are displayed:
Program Name - Drills down to the Activity Summary page showing work metrics for those programs that have been instrumented to compute them.
Request ID - The last run request ID. Drills down to display the request in the concurrent request Search Results screen.
Last Run Date
Outcome - indicates the completion status of the request.
Oracle Recommended Frequency - The frequency that Oracle recommends a critical program be run (if applicable).
On Schedule (Oracle Recommended) - indicates whether the Oracle recommended schedule has been met (if applicable).
Onsite Frequency - the frequency that the program is currently scheduled to run. To change the frequency, use the Update Frequency button to access the Update Frequency for Monitored Critical Activities page.
On Schedule (Onsite Frequency) - indicates whether the onsite schedule has been met.
Success Rate - the percentage of completed requests that completed with a status of normal. Drill down on the value to display a success rate chart showing completion status percentage rates of Normal, Warning, and Error. Mouse over the chart to display the numeric values.
Navigation: Applications Dashboard > Critical Activities (B) Modify Monitored Program List
Use this page to add or remove programs to the critical activities list.
To add a program to the Monitored list, select the program from the Not Monitored list and click the Move shuttle button.
To add all programs from the Monitored list, click the Move All shuttle button.
To remove a program from the Monitored list, select the program from the Monitored list and click the Remove shuttle button.
To remove all programs from the Monitored list, click the Remove All shuttle button.
Click OK to apply your changes.
Navigation: Applications Dashboard > Critical Activities (B) Update Frequency
Use this screen to update the frequency that your critical activity programs are run.
The following are listed for each critical activity program:
Program Name
Application
Program Type
Oracle Recommended Frequency - the run frequency recommended by Oracle (if applicable).
Onsite Frequency - the frequency that the program is currently scheduled to run. To change the run schedule for a program, update the Onsite Frequency field and click OK. Note that this is the target frequency and may not be the frequency that the program actually runs. Monitor the success of the target frequency with the On Schedule (Onsite Frequency) field on the Applications Dashboard - Critical Activities page.
Navigation: Applications Dashboard > Critical Activities > [Program Name]
This page displays work metrics for those maintenance programs that have been instrumented to compute them. The display can be filtered by the table name or value.
Name - the name of the table that will be purged by the program.
Value - the number of rows in the table that will be purged if the program is run.
Oracle Applications Manager allows you to monitor and support business flows within Oracle E-Business Suite. User-defined key business flows are correlated with the system components responsible for the execution of those flows.
Navigation: Applications Dashboard > Business Flows tab
From the OAM console you can:
View the hierarchical representation of the business flows.
Monitor system alerts, errored requests, and errored work items for a business flow.
View the setup status for the business flows and associated subflows.
The Key Business Flows region displays the current listing of business flows, with these columns:
Status - Indicates the setup status of the business flow. Business flows that are not fully set up are listed as unavailable
Edit
To create a new business flow, click Create. Click View Details for a selected business flow to view additional information for that business flow. Click the Edit icon for a selected business flow to update it.
Use these pages to create or edit a business flow.
Navigation: Applications Dashboard > Business Flows tab > Create (B) or Edit icon for a selected business flow
Enter a name and description for the business flow.
Enter in a child flow or component for the business flow. Choose from the following:
New Business Flow - If you select New Business Flow you are prompted for a name and description of the new business flow. You can later update the new subflow with children of its own.
Existing Business Flow - You are prompted to choose a business flow from a list of values.
Work Item Type - You are prompted to choose a workflow item type from a list of values.
Component - Select from Concurrent Program, Service, Form or Function. You are prompted for a component name from a list of values.
This page displays details for a selected business flow.
Navigation: Applications Dashboard > Business Flows tab > View Details (B) for selected business flow
Subflows and components of the business flow are shown in hierarchical format. You can expand or collapse nodes on the hierarchical tree.
Maintain your business flow monitoring from this page.
Navigation: Setup (global icon) > Business Flows (side navigation)
OAM provides the following concurrent program to help you maintain your business flow setup. Schedule requests for the concurrent program from the link provided.
Metrics Refresh - schedule requests for the OAM: KBF Metrics Rollup Program to update the setup status of your business flows.
For each of the business flows listed, you can view whether monitoring is enabled and enable or disable monitoring.
Select a business flow and click Update to enable or disable monitoring. Click View Details to view if monitoring is enabled.
Information on this page helps you detect and diagnose security issues on your Oracle E-Business Suite System.
Navigation: Applications Dashboard > Security (tab)
Click the Manage Security Options button to manage SQL*Net access for your middle-tier hosts.
Security Alerts can be raised either at runtime by the application code, or at the failure of security-related diagnostic tests. The table is organized by severity, which can be Critical, Error, or Warning. It provides numerical counts of new and open alerts. Where enabled, you can drill down on the numerical links to view and manage the details of an alert and any associated diagnostic test reports. Alert details and test reports can be added to the Support Cart.
This table shows security-related diagnostic tests that failed when they were executed. The table specifies the most recent time that the test failed, and provides links that open detailed test reports. For a specific test, clicking the Diagnose icon will re-execute the test -- this is useful to verify that the error still exists. For a specific application, clicking the Diagnose icon allows you to re-execute all failed tests in that application for the chosen security level.
Links to security-related documents on My Oracle Support are located here. Documents include:
Best Practices for Securing Oracle E-Business Suite
Oracle Support Services Security Alert - Frequently Asked Questions
Security Announcements and Notes
You can manage Oracle E-Business Suite Diagnostics tests from the dashboard.
For more information on Oracle E-Business Suite Diagnostics, see: Oracle Diagnostics Framework User's Guide.
Use this button to access Security Options.
These pages allow you to restrict SQL*Net access to the database from your middle-tier hosts. If you enable the SQL*Net Access security option, you can select which hosts have SQL*Net access to the database. If you disable the SQL*Net Access security option, then all middle-tier hosts have SQL*Net access to the database.
Use the View SQL*Net Access page to see how SQL*Net Access is currently configured for your middle-tier hosts.
Navigation: Applications Dashboard > Security (tab) > Manage Security Options (B)
If the Manage SQL*Net Access security option is disabled, a message here indicates that it is disabled. All hosts have SQL*Net access to the database in this case.
If this feature is enabled, the table of hosts indicates which hosts have SQL*Net access and which do not.
Note: In order for the information on this page to be accurate, the following steps must be run in addition to enabling or disabling the Manage SQL*Net security option:
Run AutoConfig on the database tier
Bounce the TNS Listener
The table shows the hosts that have SQL*Net access and includes the following columns:
Name
Platform
Oracle Applications Host - Indicates whether the host is an Oracle E-Business Suite host or not. Application services (Concurrent Processing, Oracle Forms, Web, Admin, and Database services) can run on Oracle E-Business Suite hosts.
Use the Manage SQL*Net Access wizard to enable or disable SQL*Net access to the middle-tier hosts. You can register a new host and grant it access as well from this wizard.
When you disable the SQL*Net Access security option, you allow SQL*Net access to the database from your middle-tier hosts.
Oracle Applications Manager uses the program OAM Applications Dashboard Collection (short name: FNDOAMCOL) to gather the information displayed on the Dashboard under the Overview and the Performance tabs.
The Dashboard Collection Program can selectively enable and disable monitoring of various metrics, and to raise alerts for services when the service has a specified status. The Dashboard Collection Program can collect data for a metric and then raise an alert when a metric reaches a specified threshold. Note that for most components, you can collect data for monitoring purposes in two different ways: (1) through the Dashboard Collection Program, or (2) manually refreshing the data from a Dashboard page.
Metrics for the following data can be monitored for the following using the Dashboard Collection Program. In addition, data for web components can be collected manually in the dashboard.
Forms Sessions
Database Sessions
Running concurrent requests
Service processes
Services up
Services down
Invalid database objects
Unsent Oracle Workflow e-mail
Patches applied
Site level profile options
Applications context files edited
New alerts
New occurrences of an alert
Open alerts
Alerts can be raised for the following services. When a service attains a specified status, an alert is raised.
Service instances listed under Applications System Status
Web Components
Completed concurrent requests
Sent Oracle Workflow e-mail
From the Monitoring tab on the OAM Site Map, you can access these utilities.
Navigation: Site Map > Monitoring > Forms (under Availability)
This page lists the service instances for the Forms Listeners. From this page you can edit information for a selected service instance. You can also view its status, view processes, and view information on its Forms Runtime Processes. Also, you can start, stop, abort, or restart the instance.
Navigation: Site Map > Monitoring > SQL Activity (under Performance)
This page provides data regarding SQL Activity:
SQL_HASH
Physical Reads
Logical Reads
Total Sorts
Execs
Total Loads
Load
For more information on these columns, see the Oracle database documentation.
Main Navigation Path: Site Map > Monitoring (subtab) > Performance (heading) > Concurrent Request Runaways (link)
System performance can potentially be affected by database sessions that should have ended when their corresponding concurrent requests were canceled, but for some reason did not.
If any such database sessions are currently active, they will be reported on this page. The table supplies context information for each session: request ID, AUDSID, program, user name, start time, phase, status, Oracle SPID, and PID. You can delete a session by selecting it in the table and clicking Terminate. You can drill down on the links in the request ID, AUDSID, program, and user name columns to view the respective details.
The following information is shown:
Navigation: Site Map - Monitoring > Forms Sessions (under Current Activity)
This page shows information on the current forms sessions. Every open form has its own database session, or “form session.”
The profile option "Sign-On:Audit Level" should be set to 'Form' to use this feature. If this profile option is not set to 'Form', the Forms Sessions table will show an empty table even when there are active forms sessions.
To filter the display by Form Name, Username, Responsibility, or Application, make the appropriate selection from the drop-down menu, enter the search string in the field provided, and click Go.
The following data is shown for each session:
Form Name
AUDSID - The auditing session ID. Click on the value to drill down to the Database Session information page.
RTI_PID - The runtime instance process ID. Click on the value to drill down to the Forms Sessions for Process ID page.
Username
Responsibility
Application
LRs (Session Logical Reads) - Input/output (I/O) is one of the most expensive operations in a database system. SQL statements that are I/O-intensive can monopolize memory and disk use and cause other database operations to compete for these resources. To prevent single sources of excessive I/O, Oracle lets you limit the logical data block reads per call and per session. Logical data block reads include data block reads from both memory and disk. The limits are set and measured in number of block reads performed by a call or during a session.
PRs (Physical Reads) - The total number of data blocks read from the disk for the session.
CPU
PGA (Session Program Global Area memory) - The PGA is a memory buffer that contains data and control information for a server process. A PGA is created by Oracle when a server process is started. The information in a PGA depends on the configuration of Oracle
UGA - User Global Area memory used by the session.
Duration - in HH:MM:SS
Click on the Session Details button or the AUDSID to view database information for the selected forms session.
Use the Diagnostics On/Off button to turn on or off the Forms Runtime Diagnostics (FRD) for the runtime process. If this button is disabled, make sure your Forms patchset level is 12 or higher (that is, 6.0.8.20 or higher) and then set the environment variable FORMS60_OAM_FRD for the Forms Listener process.
If you click on the RTI_PID from the Forms Session window, or if you click on the PID from the Forms Runtime Processes window you will see the fields described above as well as the following data for the Process ID:
Client IP Address
Server Host Name
CPU Time
Memory Usage (KB)
Diagnostics (On/Off)
Log File Name
Use the View Diagnostics button to view the Forms Runtime Diagnostics (FRD) log file. The log file can be added to the Support Cart.
Navigation: Site Map - Monitoring > Forms Runtime Processes (under Current Activity)
This page shows information about Forms runtime processes. You must first register and start a service instance of the OAM Generic Collection Service to collect this information. The Generic Collection Service must be running for the information to be collected.
You can filter your view by Node or Username.
The following columns are shown for each session:
PID - The ID of the runtime process for the user session. Click this value to drill down to the Forms Sessions for Process ID page.
Node
Port - The Apache port of the servlet listener, if any.
Memory (KB) - The memory used by the runtime process in kilobytes. For HP and AIX platforms, this is the virtual memory size. For all other platforms, this is the resident set size.
CPU
Duration
Client IP Address - The IP address of the client machine used to connect to the Forms Services.
Username - The database username used by the Forms application for the user session.
Diagnostics - On/Off
Last Update Time
Use the Upload button to refresh the data on this page.
Use the Terminate button to end a selected process.
Click on the Sessions button or click on the PID to view the Forms Sessions for Process ID page.
This page also shows the runtime processes from the Forms Servlet Listener, if any. The Port column for such processes indicates the Apache Listener port.
The Forms Listener is a process running on a specific port on the server machine. When the connection between the client and the Forms runtime process is established, the client and the runtime process requires that the connection be persistent.
The Forms Listener Servlet is a Java servlet running in a servlet engine. The Web server routes the client requests for the Forms Listener Servlet directly to the servlet instance. Because the web server acts like the end point for the client, the other server machines and ports are no longer exposed to the firewall.
In the Forms Runtime Processes page, the node name and the port are shown for each runtime process. You can distinguish between the Forms Listener process and Forms Listener Servlet process by examining the port numbers. For the Forms Listener process, the port is the Forms server machine port. For the Forms Listener Servlet process, the port is the web server port.
Navigation: Site Map > Activity Monitors (under Activity)
This region displays information on the system's activity.
A Database Sessions graph displays the number of database sessions related to the following:
Login sessions
Oracle E-Business Suite forms sessions
Services
Requests
A Concurrent Requests graph displays the number of requests with the following statuses:
Pending
Running
Waiting on a lock
Inactive
Completed in the last hour
Click on the bar for any status to drill down to more information on requests of each status.
Navigation: Site Map - Monitoring > Forms Sessions (under Current Activity) > (B) Session Details
This page displays detailed information about the selected database session. Click Terminate to end the database session.
Form or Service Name
Username
Responsibility
Logon Time
Serial Number
OS PID
Status
Session ID
Oracle SPID
User
SQL Hash - If the value shown is a link, you can click on it to view a page showing the SQL statement that is currently executing, as well as an execution plan for the statement. For more information on execution plans, see the Oracle database documentation.
OS User
Machine
Process
Terminal
Module
Module Hash
Action
Program
Event
Wait Time
Timeouts
Average Wait
Total Wait
Maximum Wait
Set the trace options to the level desired. Options available are:
Normal Trace
Trace with Waits
Trace Off
Trace with Binds
Trace with Binds and Waits
Click Apply to apply any changes made to the Tracing Options. Click View Trace to view the current trace information.
The following information is shown:
Navigation: Site Map > Monitoring > Invalid Objects (under Current Activity)
This page lists invalid objects in the database. To remove invalid objects, you can compile the APPS schema (for invalid objects in the APPS schema) or run a script provided with the database (for other invalid objects). See the Maintaining Oracle E-Business Suite Documentation Set for more information on compiling objects.
Navigation: Site Map > Monitoring (subtab) > Current Activity (heading) > Forms Runaway Processes (link) Overview
You can also access this page by clicking the View Runaways button on the Forms Runtime Processes page.
Running Oracle E-Business Suite requires the creation of many system-level processes. On occasion, processes can behave incorrectly and have a negative impact on system performance. In Oracle Applications Manager, you can:
Configure thresholds (maximum memory size, maximum CPU percent, maximum duration in minutes) for tracking runaway processes. These settings take immediate effect as soon as you click Apply. These settings are used to raise system alerts on the Applications Dashboard.
See the user name and IP address of runaway processes.
Terminate processes.
See the parameters of the OAM Generic Collection Service (the background process which runs on all Forms nodes).
Open the associated log file.
You can define memory, CPU, and duration thresholds. Memory refers to process memory size, resident set size, or total virual memory size based on the platform. On a UNIX system, CPU refers to the cumulative execution time of the process. On a Windows NT system, CPU is, CPMemory - Process memory size, Kb, resident set size or total virtual memory size based on the platform. CPU - On UNIX, it is the percentage of CPU use. If the system has both UNIX and Windows NT nodes, then CPU refers to the percentage of CPU use. In all cases Duration refers to the total time elapsed since a connection was established.
The default values of the thresholds are as follows:
Maximum memory: 1.0 MB
Maximum CPU: 25%
Maximum duration: 20.0 minutes
Navigation: Site Map > Monitoring (tab) > Applications Usage Reports (under Usage)
The Applications Usage page contains links to the following pages:
Products Installed
Applications Users Per Module Summary
Page Access Tracking and Sign-On Audit: Configuration, Reports
Applications Usage Reports: Purchase Lines Processed, Order Entry Lines Processed, and more
Navigation:
Applications Systems > (B) Configuration > Products Installed
or
Applications Systems > (menu) Applications Usage > (B) Go > Products Installed
This page lists the following information for Oracle E-Business Suite products:
Application Short Name
Application Name
Version
Status - A product's status can be Installed, Shared, or Inactive. Installed indicates that the product has been licensed and installed. The Shared status is used for products that other products are dependent upon. Products that are neither Installed nor Shared have an Inactive status.
Navigation: All Applications Systems > (pull down menu) Applications Usage > (B) Go > Application Users Per Module Summary
This page lists the following information for Oracle E-Business Suite modules:
Application Short Name
Module Name
Count - number of current users
You can view details for a particular module by selecting its radio button on the left and clicking the View Details button. This takes you to a page that lists the following:
Module Name
User Name
Description of User
Creation Date of User
Last Log On Date
Click Show All to see a format suitable for printing that lists all users. Within the Show All format, click on Show Set to see the table format of the list.
Page Access Tracking and Sign-on Audit tracks the accesses of Oracle E-Business Suite JSPs and Oracle Forms for usage pattern analysis and performance statistics. The Reports screen displays the complete flow of accesses across technology stacks within a user session. It also aggregates collected metrics and display summary statistics.
Use these reports to collect information on specific applications usage. Your License Management Services analyst may ask you to collect such information, or you can use these reports for your own monitoring.
The following reports can generate information on various licensing metrics in a time period you specify. However, for the purposes of License Management, a twelve (12) month period is used.
These reports generate information for the licensing metric Purchase Line. Purchase Line is defined as the total number of purchase line items processed by the application during a 12 month period. Multiple purchase lines may be created on either a requisition or purchase order or may be automatically generated by other Oracle E-Business Suite programs. For iProcurement, Purchase Lines are counted as all line items on an approved requisition created in iProcurement. For iSupplier Portal and Purchasing Intelligence, Purchase Lines are counted as the line items on purchase orders processed through each of those applications. This does not include communication on the same Purchase Order. For each application, you may not exceed the licensed number of Purchase Lines during any 12-month period unless you acquire additional Purchase Line licenses from us. You may acquire a different number of Purchase Line licenses for each program (Number of Purchase Lines for iProcurement could be a smaller number than for iSupplier Portal).
For iSupplier Portal, use the Suppliers script to generate a list of suppliers and their IDs. You can then use this information when running the Purchase Line Items Processed report for iSupplier Portal.
This report is used for the licensing metric Order Line, which is defined as the total number of order entry line items processed by the program during a 12 month period. Multiple order entry line items may be entered as part of an individual customer order or quote and may also be automatically generated by the Oracle Configurator. You may not exceed the licensed number of Order Lines during any 12 month period.
This report is used for the licensing metric Expense Report, which is defined as the total number of expense reports processed by the iExpenses during a 12 month period. You may not exceed the licensed number of Order Lines during any 12 month period.
This report is used for the licensing metric Invoice Line, which is defined as the total number of invoice line items processed by the program during a 12 month period. You may not exceed the licensed number of Invoice Lines during any 12 month period unless you acquire additional Invoice Line licenses from us.
Use this page to run seeded and custom scripts.
Navigation: Site Map > SQL Extensions (under Others)
Click on the icon in the Focus column to display only those reports from the selected group.
Use the Hide/Show icon next to the group name to hide or display the reports contained in the group.
The following columns are shown for each report:
Name - Click on the name of the report to display the report details.
Description
Protected - A "locked" icon indicates that a password is required to submit the report.
Run Report - Click on the icon in this column to run the report. If a password or parameters are required, the SQL File Details page will display. Otherwise, the output of the report will display in the Results page.
Use the Reload button to reload the displayed reports from the metadata file.
You can have your custom scripts automatically discovered by Oracle Applications Manager and available to run from the SQL Extensions page.
Create a new SQL script. Multiple SQL statements are allowed within the same file. For example: a report called "Get Sysdate": sysdate.sql
Create a directory called /custom/sql for your custom SQL files under <APPL_TOP>/admin. Your directory structure should look like <APPL_TOP>/admin/custom/sql.
Copy your SQL files to <APPL_TOP>/admin/custom/sql directory.
Now log in to Oracle Applications Manager and navigate to Site Map > SQL Extensions.
The discovered SQL files will be under the "DefaultC" group.
After the files are discovered, you can customize the grouping, protection, and execution method of these scripts.
To customize the grouping, protection, report format, or drill-downs for your automatically discovered scripts, you must edit oamcustext.amx located under <APPL_TOP>/admin/custom/xml.
For each discovered script, the oamcustext.amx file will contain an entity similar to the following example that defines the grouping, protection, and report format:
<cReport type="SQL" group="DefaultC">
<title>sysdate.sql</title> <script name="sysdate.sql" protected="yes" execMode="SQLPLUS" parameters="unknown">
</script>
</cReport>
You can change the group that your report displays under.
In the oamcustext.amx file, change the value of "group" to the name of the group you want your report to appear in. For example, to change the group to "Custom Reports", the result would be:
<cReport type="SQL" group="Custom Reports">
<title>sysdate.sql</title>
<script name="sysdate.sql" protected="yes" execMode="SQLPLUS"
parameters="unknown">
</script>
</cReport>
Log in to Oracle Applications Manager and navigate to the SQL Extensions page (Site Map > SQL Extensions).
Click the Reload button to reload the metadata. Your script will appear under the new group.
You can change the password protection that is set on your report.
In the oamcustext.amx file set the value of "protected" to "yes", if you want password protection enabled on your script. Set it to "no" to remove password protection. For example, to set the protection to "no", the result would be:
<cReport type="SQL" group="Custom Reports">
<title>sysdate.sql</title>
<script name="sysdate.sql" protected="no" execMode="SQLPLUS" parameters="unknown">
</script>
</cReport>
Log in to Oracle Applications Manager and navigate to the SQL Extensions page (Site Map > SQL Extensions).
Click the Reload button to reload the metadata. Your script will appear with the "unlocked" icon.
In the oamcustext.amx file set the value of "execMode" to "SQLPLUS" text format, or set it to JDBC for HTML format. For example, to set the report format to HTML, the result would be:
<cReport type="SQL" group="Custom Reports">
<title>sysdate.sql</title>
<script name="sysdate.sql" protected="no" execMode="JDBC" parameters="unknown">
</script>
</cReport>
Log in to Oracle Applications Manager and navigate to the SQL Extensions page (Sitemap > SQL Extensions).
Click the Reload button to reload the metadata.
For reports defined in HTML format, you can provide drill-downs from the results of your script to other Oracle Applications Manager pages. Currently drill-downs are supported for requests based on REQUEST_ID and database session information based on AUDSID.
Example:
Suppose your SQL script returns REQUEST_ID as the first column of the report, you can link it to the Request Details page as follows:
Ensure that execMode="JDBC"
Add the following to the entry for your SQL script:
<keyColumns>
<column position="1" key="REQUEST_ID"/>
</keyColumns>
Here, position="1" indicates that the REQUEST_ID column is the first column reported by your select statement. Currently the possible values for the key attribute are REQUEST_ID and AUDSID.
The new full entry for your SQL script will look like the following:
<cReport type="SQL 'group="Custom Reports">
<title>sysdate.sql</title> <script name="sysdate1.sql" protected="no" execMode="JDBC"
parameters="unknown">
</script>
<keyColumns>
<column position="1" key="REQUEST_ID"/>
</keyColumns>
</cReport>
If you try to execute a SQL script and encounter the following error message:
An error has occurred!
<filename>(No such file or directory)
The SQL file does not exist under <APPL_TOP>/admin/custom/sql. Make sure you have copied the file into this directory.
If your SQL script takes input parameters, ensure that you provide the parameters one per line in the Input Parameters text field. The result will contain errors if you do not provide the necessary parameters.
Navigation: Site Map > SQL Extensions >(select report name)
This page displays information based on the report definition. Information may include:
Description
Report Format - HTML or Text
Applications Schema Password - If the report is password-restricted, enter the password here.
Input Parameters - Enter any required or optional parameters.
You can run the report from this window by clicking the Run Report button.
Navigation: Site Map > SQL Extensions (Run Report)
The contents and format of this page will vary depending on the report run.
Report results returned in HTML allow you to filter the report by a specific Column value.
Use the Refresh button to rerun a report from this page.
Click Add to Support Cart to add your report results to the Support Cart.
The System Alerts, Metrics, and Logs screens provide information that can help you diagnose potential problems. For example, configuration issues, overdue routine maintenance tasks, and invalid data can cause serious problems requiring either an automated response or manual intervention.
Oracle E-Business Suite applications can report these potential problems as system alerts to Oracle Applications Manager. These alerts can then be tracked in OAM, and administrators can classify alerts as open or closed, as well as keep notes on the steps taken to resolve underlying problems.
In addition, some problems may be more easily detected through external analysis of performance metrics. External analysis allows for easier comparison of current and historical metric values, consideration of metrics from multiple products and components, and end-user defined exception triggers. Such exceptions could include decreasing transaction throughput for a component or excessive completion times for a business process.
Navigation: Site Map > >Monitoring > System Alerts (under Current Activity)
Components in an Applications System such as concurrent programs, forms, service instances, or functions can post exception messages during specific error conditions as defined by the developer of the component. The term "System Alert" denotes a grouping of such exceptions having the same message. The term "Occurrence" is used to denote each member exception of such a group. Each alert is associated with a Severity (Critical, Error or Warning) and a Category (System or Product).
This page shows a summary of the system alerts as well as a list of new alerts.
Alerts are classified by Severity level:
Critical - the alert indicates that an important business flow is impeded, or that a large number of users is affected.
Error - the alert indicates a less severe, more isolated issue.
Warning - the alert indicates that there may be a negative impact on users or business processes.
Alerts are also marked as New or Open. "New" indicates that the alert has just been posted in the system. "Open" indicates the alert is being resolved.
In the Summary region, Alerts are grouped according to their severity and status of New or Open. The New or Open column indicates how many alerts of the given severity exist. You can click on the number to drill down to details on the alerts.
When a new exception is posted, if an alert already exists with the same message and is in New or Open state, then the new exception is considered an occurrence of the existing alert. If an alert with the same message does not exist then a new one is created (with the state New) and this exception becomes the first occurrence of this alert. A notification is also sent to subscriptions for the newly created alert.
You can change the state of alerts (along with the associated occurrences) in OAM. You can change the state of a new alert to Open to indicate the exception has been acknowledged and the problem is being resolved. Once the problem is resolved you can change the state of the alert to Closed. You can also add notes to alerts; for example, to indicate how the problem was resolved.
You can search for alerts, search for occurrences, and view the notification setup for alerts using the buttons provided.
Oracle Applications Manager provides the System Alerts feature to inform system administrators of potential problems in Oracle E-Business Suite. For the Oracle Application Object Library messages logged at the level of Unexpected, OAM can raise system alerts. Ideally, system administrators should actively look at these alerts and close them once issue is resolved. However if for some reason, the alerts are not closed, too many new system alerts can flood the system with alerts, occurrences, business events, and notifications. Oracle E-Business Suite provides a mechanism to control the count of new system alerts to avoid a system alert flood.
By default, the system will raise only 500 new alerts. Once this limit is reached for new system alerts, no new alerts or notifications will be raised and a message will be displayed on System Alert and Metric page. To re-enable the alerting, a system administrator should change the status of existing new alerts from OAM. Oracle E-Business Suite also allows system administrators to change the default threshold by using the System Alert Setup button from System Alert and Metrics page can access this page. From the setup page you can also change the number of occurrences per alert. By default only 50 occurrences per alert is logged.
The setup page also provides control to enable the system alert for a particular severity. If critical severity is selected, only critical alerts will be logged. “None” selection will disable the system alert completely and no new alert will be raised.
This page displays the details associated with a particular system alert. This page includes the summary information for the alert such as severity, category, state, creation date, and the exception message. The occurrences table summarizes the individual occurrences for this alert. You can select an occurrence and click View Details to drill down to the context details for an individual occurrence.
From this page, you can also change the state of the alert as well as navigate to the Add Notes page to add notes to the alert.
This page allows you to search for alerts by Severity, Category, State and Posted Date. The search results are displayed in the same tabular format as in the New Alerts section in the System Alerts page. You can also add notes or change the state of the alerts displayed in the results table.
To search for occurrences from this page, click Search Occurrences.
This page allows the user to search for occurrences of alerts by various criteria. The query criteria are categorized into the following groups:
System Alert - The criteria in this section pertain to the alert to which the occurrence belongs.
Component - The criteria in this section pertain to the component that logged the occurrence.
User and Responsibility - The criteria in this section pertain to the user and responsibility that used the component that generated the alert.
Database Session - The criteria in this section pertain to the database session associated with the transaction during which the exception was logged.
Others - Additional criteria related to the occurrence.
From the results table on this page, users can drill down to view the context details for each occurrence. In addition, the users can also drill down to view the details for the alert to which each occurrence belongs.
To search for alerts from this page, click Search Alerts.
This page displays the entire context information associate with an individual alert occurrence. This page is divided into the following three sections:
Summary - This section displays information associated with the alert to which the occurrence belongs.
Context - This section displays all the context information and is further categorized into the following subsections:
Component - Name and application of the component that posted the alert occurrence.
User and Responsibility - Username, responsibility, and application for the user who ran the Component that posted the alert occurrence.
Database Session - Database session ID, database instance, session module, and session action associated with the database session for the transaction during which the alert was posted.
Others - Miscellaneous information such as session ID, node, security group, processes ID, thread ID (if applicable) and JVM ID (if applicable).
The third section on this page varies based on the type of the transaction during which the alert occurrence was posted. The following types are possible:
Concurrent Request - Request ID, concurrent program name, a link to the request log, and a link to the output file are available if the transaction is a concurrent request. You can use the Request ID link to drill down to the request details. In addition, you can drill down to view related system logs to view other log messages that were posted during the same transaction.
Concurrent Process - If the transaction type was a concurrent process (belonging to a service instance), the service instance name, concurrent process ID, and a link to the manager log can be viewed from this section.
Form - If the transaction was from a Form, the form name is displayed in this section.
ICX - If the transaction was of type ICX, then the ICX transaction ID is displayed in this section.
In addition, regardless of the transaction type, users can also drill down to view related system logs to view other log messages that were posted during the same transaction.
Navigation: Site Map > Monitoring > System Alerts (under Current Activity) > Metrics (tab)
Not all exception conditions can be immediately detected directly within an Oracle E-Business Suite component, but are best detected through external analysis. Some are detected by measuring certain criteria, such as decreasing transaction throughput for a component or excessive completion times for a business process. External analysis allows for easier comparison of current and historical metric values, consideration of metrics from multiple products and components, and end-user defined exception triggers. These exceptions are analogous to "events" in Oracle Enterprise Manager where the use specifies the specific conditions that will trigger an alert.
You can search for metrics based on Application, Component, Posted After date, or Posted Before date.
Click on the Advanced Search button to search for metrics based on detailed criteria.
This page allows the users to search for metrics based on the context information associated with the metrics. The query criteria are categorized into the following groups:
Metrics - The criteria in this section pertain to the metric itself such as metric code, metric value and date on which the metric was posted.
Component - These criteria pertain to the component that logged the metric.
User and Responsibility - These criteria pertain to the user and responsibility that used the component that generated the metric.
Database Session - These criteria pertain to the database session associated with the transaction during which the metric was logged.
Others - This group contains miscellaneous criteria such as node, security group, process ID, Thread ID, and JVM ID.
From the results table, users can drill down to view the context details for each metric.
The System Metrics results table shows information on:
Component - the application component. A component is a functional unit, such as a concurrent program, form, or Web Application function.
Application - the owning application of the metric.
Metric Code - the internal name of the metric.
Value - the value of the metric.
Metric Type - the data type of the metric.
Time - the time the metric was taken.
This page shows the following:
Summary
Metric Code
Metric Type
Metric Value
Time Posted
Context
Component:
Name
Application
Database Session
AUDSID
DB Instance
Session Module
Session Action
User and Responsibility
User
Responsibility
Application
Others
Session ID
Node
Security Group
Process ID
Thread ID
JVM ID
Request Summary
Request ID - Click on the request ID to view details for the request.
Request Log - Click View to view the request log.
Program Name - the program name.
Output file - click View to view the output file.
Navigation: Site Map > Monitoring > Logs (under Current Activity)
System Logs are messages that are logged by Oracle E-Business Suite system components.
Log messages contain a comprehensive set of context information and are useful for pinpointing and diagnosing system problems. They can have the following levels (listed from most serious to least serious):
6 - Unexpected: Used for the failure reporting of internal unhandled software failures. Example: Failed to place order due to NullpointerException
5 - Error: Used for the failure reporting of external end user errors. Example: Invalid username/password
4 - Exception: Used for the failure reporting of internal handled software failures. Example: User Session timed out
3 - Event: Used for high-level progress reporting. Example: Order placed successfully
2 - Procedure: Used for API-level progress reporting. Example: Entering or exiting an API
1 - Statement: Used for low-level progress reporting. Example: Processing records within an API
The system logs screens allow you to work with log messages that have been saved to the database. Please note that if logging has been configured to store messages in a middle tier file, such log messages will not be visible on the UI screens. Also, if a log message would normally raise a system alert but the message is sent to a file instead of the database, then the system alert will not be raised.
The following topics describe how to work effectively with the system logs screens:
Performing a Simple Search
Performing an Advanced Search
Working With Search Results
Viewing Log Message Details
Setting Up Logging
In a simple search, you can search for log messages based on the following criteria:
Posted After date
The default value is today's date.
Posted Before date
The default value is tomorrow's date.
Component Application
Component
Module
Level
Enter values into the fields as desired and click Go to perform a search.
To run an advanced search, click the Advanced Search button. You can use any combination of the following search criteria:
Logged From
Logged To
The default time interval is from 12:00 AM today to 12:00 AM tomorrow.
Application
Responsibility
User
Log Level
Module
Message
Host
Java Virtual Machine
Database Session ID
Security Group
Database Instance
On this page, the LOVs only display values that are reflected in existing log messages. For example, the User LOV only shows users who are specified in one or more log messages. It does not show the entire list of Oracle E-Business Suite users. Furthermore, the LOVs are also filtered by any other search criteria you have entered on the page.
Optionally, you can perform searches that depend on the Component Type. In the Component region, select a Type from the drop-down list. The page will refresh to offer additional search fields. For example, for Concurrent Programs, you can search by Concurrent Program Application or Concurrent Program Name.
When you perform a search, the System Log Summary table shows how many log messages were returned and how many are at each log level.
Individual log messages are listed in the System Log Details table. For each log message, the sequence number, module, log level, user, and time are displayed. You can drill down on an individual message or on a user to view details.
To download all returned log messages, click the Download All button. (This includes the full range of log messages, not only those displayed on the current page.) The downloadable file is a comma-delimited CSV file.
To download your choice of currently displayed log messages, select them in the table and click the Download button.
Additionally, you can save all search results by clicking the Add to Support Cart button.
Module: The unit of code specified in the FND_LOG API call. A module might be a PL/SQL stored procedure, a C file, or a Java class.
Level
Time Posted
Message Text
Component: Name, Application
User and Responsibility: User, Responsibility, Application
Database Session: AUDSID, DB Instance
Others: Session ID, Node, Security Group, Process ID, Thread ID, JVM ID
Request ID
Request Log
Program Name
Output File
In the Attachment region, additional context information (such as environment variables or file versions) may be available in some cases.
Optionally, you can add this page to the Support Cart.
Navigation: Site Map > Monitoring > Logs (under Current Activity ) > Log Setup (button)
On the Log Setup screen, you can configure logging according to user, responsibility, application, or site. Additionally, you can view any Java System Property settings for the current JVM that may be active. Note that Java System Property settings override all other settings.
The following procedure explains how to set up logging for a particular user. The steps are the same for responsibilities or applications. Note that user settings override responsibility settings, responsibility settings override application settings, and application settings override site settings. In the table, null values indicate that the setting is to be inherited from the next higher profile level.
If the User table is not currently displayed, then click the icon to show it.
If there is a blank User Name field, then click the flashlight icon to select a user name. If there is not a blank User Name field, then click the Add Another Row button to add an empty row to the table, then select a user name.
In the Log Enabled field, select null, Yes, or No. A null value means that the setting will be inherited from a higher level profile value.
In the Log Level field, select a log level. Log messages greater than or equal to the specified level will be stored.
(Optional) In the Midtier Log File Name field, type in a valid middle-tier file path. If this field is blank, then log messages will be stored in the database. Note: Server PL/SQL messages are always logged to the database.
(Optional) In the Module field, enter the module for which you want to enable logging. For example, "fnd%".
Click Apply to save your work.
The following procedure explains how to set up logging for your entire site.
In the Log Enabled field, select null, Yes, or No. (A null value means that the setting will be inherited from a higher level profile value.)
In the Log Level field, select a log level. Log messages greater than or equal to the specified level will be stored. It is strongly recommended that you choose 4 - Exception, 5 - Event, or 6 - Unexpected. Significant system performance issues may arise if logging is enabled at less than 4 - Exception.
(Optional) In the Midtier Log File Name field, type in a valid middle-tier file path. If this field is blank, then log messages will be stored in the database. Note: Server PL/SQL messages are always logged to the database.
(Optional) In the Module field, enter the module for which you want to enable logging. For example, "fnd%".
Click Apply to save your work.