Results for “threshold_value”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_OAM_SVCI_INFO is a configuration and monitoring metadata table in the APPLSYS schema of Oracle E-Business Suite, owned by the FND – Application Object Library product. It stores information about the Service Instances monitored by the Oracle Applications Manager (OAM) Dashboard Collection Program. Each row defines a distinct concurrent processing service endpoint — identified by an application and a concurrent queue — and records whether that service is subject to health collection and alerting, together with the threshold used to raise alerts.

The table is a reference-data structure rather than a transactional one. It is populated and maintained by the OAM Dashboard Collection concurrent program and read by the OAM Dashboard user interface to render service-instance status. In Data Vault modeling terms, the ETRM metadata classifies this object heuristically as standalone, meaning it is best modeled as an independent hub-like reference entity with no documented foreign-key dependencies on other tables within the vault structure. It should be treated as a low-volatility configuration source rather than a transaction or link table.

The object is present and VALID in both EBS 12.1.1 and 12.2.2. The documented physical schema lists 10 columns under owner APPLSYS.

Key Information Stored

The composite primary key FND_OAM_SVCI_INFO_PK1 is defined on (APPLICATION_ID, CONCURRENT_QUEUE_NAME). These two columns constitute the business key: they uniquely identify a monitored service instance and are the natural join columns for reporting. There is no separate surrogate key column in the documented schema.

• APPLICATION_ID — the FND_APPLICATION identifier of the application that owns the service instance; half of the composite primary key.
• CONCURRENT_QUEUE_NAME — the name of the concurrent manager queue or service endpoint being monitored; the second half of the primary key and the column most commonly searched by administrators.
• ALERT_ENABLED_FLAG — indicates whether OAM should generate alerts when this service instance breaches its threshold.
• COLLECTION_ENABLED_FLAG — indicates whether the Dashboard Collection Program actively gathers metrics for this service instance.
• THRESHOLD_VALUE — the numeric limit against which collected service metrics are evaluated to determine whether an alert is warranted.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns recording row creation and last modification audit information.

Common Use Cases and Queries

Administrators query this table to audit which concurrent queues are being monitored, to confirm that collection and alerting are enabled for critical services, and to review configured thresholds. A typical diagnostic query lists all monitored service instances for a given application:

• SELECT application_id, concurrent_queue_name, alert_enabled_flag, collection_enabled_flag, threshold_value FROM fnd_oam_svci_info ORDER BY application_id, concurrent_queue_name;
• SELECT s.concurrent_queue_name, s.threshold_value FROM fnd_oam_svci_info s WHERE s.collection_enabled_flag = 'Y' AND s.alert_enabled_flag = 'Y';

Because the primary key is (APPLICATION_ID, CONCURRENT_QUEUE_NAME), lookups by CONCURRENT_QUEUE_NAME alone should use a range or LIKE predicate and account for the fact that the same queue name may appear for more than one application. Reporting use cases include generating an inventory of monitored services for capacity planning, verifying post-clone or post-patch configuration of the OAM dashboard, and reconciling rows against the concurrent manager definitions in FND_CONCURRENT_QUEUES.

Related Objects

No foreign keys from FND_OAM_SVCI_INFO to other tables are documented in the ETRM relationship data; it is classified as standalone. The most significant objects that reference or depend on it by shared business keys and functional association are:

• FND_APPLICATION — joined on APPLICATION_ID to resolve the application short name and description.
• FND_CONCURRENT_QUEUES — matched on CONCURRENT_QUEUE_NAME to reconcile monitored services with actual concurrent manager queues.
• FND_OAM_SVCI_RUNS (companion OAM collection table) — relates the monitored instance to collected metric runs by APPLICATION_ID and CONCURRENT_QUEUE_NAME.
• FND_OAM_SVCI_THRESHOLDS (where present in the same feature family) — supplies threshold definitions referenced by THRESHOLD_VALUE.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — used together for contextual reporting on the workloads processed by the monitored queue.
• OAM Dashboard Collection concurrent program — the FND program that populates and refreshes this table.
• FND_OAM_SVCI_INFO_PK1 — the composite primary key constraint enforcing uniqueness of APPLICATION_ID and CONCURRENT_QUEUE_NAME.