Results for “service_instance”

10 results




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

Overview

FND_OAM_BF_COMP is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the association between business flows and the individual components that compose them for predefined flows. Business flows in Oracle EBS represent end-to-end business processes—such as Order-to-Cash or Procure-to-Pay—that span multiple applications and are monitored through Oracle Application Manager (OAM) and related diagnostics tooling. This table defines which components (forms, concurrent programs, database objects, or other monitored entities) participate in each predefined flow.

Under a heuristic Data Vault classification mined from the foreign key structure, FND_OAM_BF_COMP is modeled as a standalone object. In practice, however, its composite primary key of business flow, component type, application, and component identifier gives it the character of a link table, since it expresses a many-to-many association between a business flow and the components it references. The standalone classification reflects the absence of enforced foreign keys to other tables rather than a lack of logical dependency.

Key Information Stored

The table contains eleven documented columns. The most significant are:

  • BIZ_FLOW_KEY — Identifies the business flow to which the component belongs. Part of the composite primary key.
  • COMPONENT_TYPE — Classifies the associated component, allowing the flow definition to distinguish forms, programs, or other monitored artifacts. Part of the primary key.
  • COMPONENT_APPL_ID — The application identifier owning the component. This is the column most commonly referenced when users search for component_appl_id, since it anchors each component to its owning application. Part of the primary key.
  • COMPONENT_ID — The internal identifier of the specific component within its application. Part of the primary key.
  • MONITORED_FLAG — Indicates whether the component is actively monitored as part of the flow.
  • DISPLAY_ORDER — Controls the sequence in which components are presented or processed within the flow.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing row creation and modification history.

The primary key FND_OAM_BF_COMP_PK1 spans BIZ_FLOW_KEY, COMPONENT_TYPE, COMPONENT_APPL_ID, and COMPONENT_ID, confirming that the four columns together form the composite business key. No separate surrogate key column is documented.

Common Use Cases and Queries

Administrators and technical consultants query this table to understand which components belong to a given predefined business flow, to verify monitoring configuration, or to troubleshoot flow validation failures. A typical query retrieves all components for a flow:

  • SELECT biz_flow_key, component_type, component_appl_id, component_id, monitored_flag FROM fnd_oam_bf_comp WHERE biz_flow_key = :flow_key ORDER BY display_order;
  • SELECT c.*, a.application_short_name FROM fnd_oam_bf_comp c, fnd_application a WHERE c.component_appl_id = a.application_id;
  • SELECT component_appl_id, COUNT(*) FROM fnd_oam_bf_comp GROUP BY component_appl_id ORDER BY 2 DESC;

Reporting use cases include auditing which applications contribute the most components to predefined flows, identifying unmonitored components, and reconciling flow definitions after patching or upgrades. The DISPLAY_ORDER column supports ordered presentation of flow steps in administrative reports.

Related Objects

Because the heuristic classification is standalone, no enforced foreign keys are documented, but logical relationships exist with several FND objects:

  • FND_APPLICATION — Joined on COMPONENT_APPL_ID = APPLICATION_ID to resolve the owning application's short name and description.
  • FND_OAM_BF_COMP related flow definition tables, referenced through BIZ_FLOW_KEY to enumerate predefined business flows.
  • FND_OAM_BF_REQ / business flow monitoring tables — Consumed by Oracle Application Manager diagnostics that evaluate flow health.
  • FND_CONCURRENT_PROGRAMS and FND_FORM — Logical targets of COMPONENT_ID where COMPONENT_TYPE indicates a concurrent program or form.
  • FND_OAM_BF_COMP-related views and OAM diagnostic APIs — Used by Application Manager to render and validate business flow definitions.

These relationships support the operational role of FND_OAM_BF_COMP as the bridge between predefined business flows and the concrete application components they monitor.