Search Results fnd_oam_app_sys_status_pk1

Overview

FND_OAM_APP_SYS_STATUS is a table owned by the APPLSYS schema within the Oracle E-Business Suite environment. It forms part of the Application Object Library (FND) and is described in the ETRM documentation as holding "OAM Applications System Status Information." OAM (Oracle Applications Manager) is the administrative framework used to monitor, diagnose, and manage an EBS instance, and this table serves as the persistent store for status metrics collected across the application tier and concurrent processing tier.

The table carries ten documented columns in release 12.2.2, and its status is recorded as VALID. The primary key, FND_OAM_APP_SYS_STATUS_PK1, is defined on METRIC_SHORT_NAME. From a Data Vault modeling perspective — a heuristic classification mined from the foreign key structure — this object is assessed as standalone. Because no inbound or outbound foreign keys were identified, the table does not participate in a hub, link, or satellite pattern in the strict sense. A practitioner might reasonably treat METRIC_SHORT_NAME as a natural business key and the surrounding descriptive columns as satellite-style attributes if a vault model were ever constructed around OAM telemetry.

Key Information Stored

The most significant columns captured in this table are:

• METRIC_SHORT_NAME — the primary key column. It holds the abbreviated identifier for each tracked metric, making it the sole documented unique business key candidate.
• APPLICATION_ID — identifies the EBS application (for example, an FND or product-specific application) to which the metric pertains.
• CONCURRENT_QUEUE_NAME — the name of the concurrent manager queue associated with the metric, relevant for capacity and throughput reporting.
• NAME — the descriptive or display name of the metric.
• TYPE — categorizes the metric, allowing administrators to group status information by kind.
• STATUS_CODE — the evaluated condition of the metric at the time of collection, forming the core operational signal stored here.
• NODE_NAME — the application-tier node from which the metric was gathered, enabling per-node diagnostics in multi-node deployments.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard EBS audit columns recording who last touched the row, when, and through which login session.

No unique indexes beyond the primary key are documented in the ETRM metadata, so METRIC_SHORT_NAME remains the only confirmed business-key candidate.

Common Use Cases and Queries

The primary use case is administrative monitoring through Oracle Applications Manager and custom status dashboards. DBAs and system administrators query this table to detect degraded metrics, isolate node-specific issues, or audit concurrent queue health. A typical query returns all metrics currently flagged with a non-normal status:

• SELECT METRIC_SHORT_NAME, NAME, TYPE, STATUS_CODE, NODE_NAME FROM FND_OAM_APP_SYS_STATUS WHERE STATUS_CODE <> 'NORMAL';
• SELECT APPLICATION_ID, CONCURRENT_QUEUE_NAME, COUNT(*) FROM FND_OAM_APP_SYS_STATUS GROUP BY APPLICATION_ID, CONCURRENT_QUEUE_NAME;
• SELECT NODE_NAME, MAX(LAST_UPDATE_DATE) FROM FND_OAM_APP_SYS_STATUS GROUP BY NODE_NAME;

These patterns support capacity planning, concurrent manager tuning, troubleshooting of application-tier nodes, and stale-metric detection where LAST_UPDATE_DATE has not advanced as expected. The table is also commonly joined to application and concurrent manager metadata to enrich management reports.

Related Objects

As a standalone table with no documented foreign keys, FND_OAM_APP_SYS_STATUS has no enforced referential dependencies. The following objects are nonetheless significant in practice:

• FND_APPLICATION — joined via APPLICATION_ID to resolve application names and short names.
• FND_CONCURRENT_QUEUES — joined via CONCURRENT_QUEUE_NAME to reconcile queue configuration with reported status.
• FND_NODES — joined via NODE_NAME to validate node identity and tier information.
• FND_OAM_APP_SYS_STATUS related OAM views — the Applications Manager status pages typically read this table through FND-owned views rather than directly.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — used alongside this table when correlating metric status with concurrent processing activity.

Together these objects allow technicians to move from a stored status metric to the underlying application, queue, and node definitions that give the data operational meaning.