Search Results get_apps_sys_status

Overview

FND_OAM_EM is a PL/SQL package owned by the APPS schema that forms part of the Oracle E-Business Suite Oracle Applications Manager (OAM) framework. Its role is to provide the data extraction and status-reporting layer used by OAM's Enterprise Manager and Applications System monitoring pages. The package exposes a set of cursor-returning and scalar functions that collect runtime information about the E-Business Suite instance, including service availability, workflow agent activity, system configuration changes, web component status, and integration system alerts. In release 12.1.1 and 12.2.2 the package is classified under the ETRM "OTHER" API category, indicating it is an internal supporting package rather than a public, documented integration API. The documented ETRM metadata lists 22 procedures and functions, many of which were originally staged as "DONE FOR LEVEL 1" in the package header, and a substantial portion of the package body is commented out, reflecting the layered evolution of the OAM monitoring toolset.

Key Procedures and Functions

The package is organized around two families of entry points: functions that return a strongly typed cursor (oam_cursor_type) for consumption by monitoring screens, and functions that return simple scalar values.

• get_native_svcs — returns a table of native service records used to report on EBS service availability.
• get_wf_agent_activity — returns a cursor describing the current activity of workflow agents.
• get_apps_sys_status — returns a cursor summarizing overall Applications system status.
• get_conf_changed — returns a cursor listing configuration changes detected within the instance.
• get_web_components_status — returns a cursor reporting the status of the Web (Apache/OC4J or WebLogic) tier components.
• get_ebiz_int_sys_alerts — returns a cursor of integration system alerts generated by the eBusiness Suite.
• get_icm_status — returns a numeric status code for the ICM (Internal Concurrent Manager).
• get_apps_framework_agent — although commented out in the shipped source excerpt, this function is documented in the ETRM metadata as a cursor-returning function that reports on the Applications Framework agent. The user's search term references this procedure directly.
• get_apps_general_info, get_apps_level, get_apps_sys_metrics, get_wf_notification, get_ebiz_status, get_ebiz_activity, get_workitem_metrics, get_block_icm_crm, get_rqsts_stats, get_procs_rqsts_per_conc, get_pend_rqsts, get_web_user_last_hour, get_active_requests_by_app, get_hourly_completed_requests — additional cursor and scalar functions covering general information, application level, requested metrics, notifications, and request statistics.

Tables Accessed

The package reads from a small set of APPS-synonym base tables that hold the OAM monitoring data model:

• FND_CP_SERVICES — service definitions used by the native services and status functions.
• FND_OAM_APP_SYS_STATUS — stores Applications system status snapshots, consumed by get_apps_sys_status and related cursors.
• FND_OAM_METVAL — metric values captured by the OAM monitoring framework; the get_*metrics and activity functions read from this table.
• DUAL — used for singleton computations and constant returns.
• PLITBLM — the PL/SQL index-by table support object used in conjunction with the package's table types.

Usage Notes

FND_OAM_EM is not intended for direct invocation by customers, forms, or concurrent programs. It is invoked internally by the Oracle Applications Manager monitoring infrastructure to populate the Enterprise Manager and Applications System dashboard regions. Because the ETRM classification is OTHER and the "Referenced by" count is zero, no other documented package depends on it; callers are expected to be OAM UI components and diagnostic scripts. Custom code should not call these functions directly, as the cursor types (oam_cursor_type, oam_em_srvcs_table_type) and associated table types are private to the package and subject to change between point releases. In 12.2.2 the same package is retained for compatibility, but the surrounding OAM console has migrated to the Fusion Middleware-based Enterprise Manager stack.