Managing Orchestrator Health and Exception Records in EnterpriseOne

Important: Before managing health and exception records in EnterpriseOne, make sure an administrator has enabled access to the Orchestrator Health and Orchestrator Exceptions program (P980060). See Setting Up Orchestrator Health and Exception Monitoring (Release 9.2.3)

EnterpriseOne stores Orchestrator health and exception records in the Health (F980061) and Exception (F980060) tables. EnterpriseOne provides the Orchestrator Health and Orchestrator Exceptions program (P980060) so you can access these records outside of the Orchestrator Monitor. This program enables you to:

• Delete health and exception records for which you no longer want to see data in the Orchestrator Monitor. This essentially resets the data displayed in the Orchestrator Monitor.

• Create a watchlist over a query of exception records so that you can be alerted of new exceptions. For example, you can create a basic watchlist over a query of exceptions in the Orchestrator Exceptions program. You can configure the watchlist with an error threshold of 1 so you are alerted to any failures that occur through the Watchlist feature. For more information on how to create queries and watchlists, see:

  • "Creating and Saving Queries to Search for Data" in the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide.

  • "Adding a One View Watchlist" in the JD Edwards EnterpriseOne Applications One View Watchlists Implemenation Guide.

"Exceptions Since Yesterday" UDOs

Oracle provides downloadable "Exceptions Since Yesterday" query and watchlist UDOs for P980060 so you can be alerted to Orchestrator exceptions in EnterpriseOne. You can also create a notification based on these UDOs. If you do not have access to these UDOs, contact your system administrator or see Downloading and Installing the Orchestrator Monitor in this guide for download instructions.