Results for “cs_cf_flows_b”

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

Overview

CS_CF_FLOWS_B is a Service (CS) module base table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the flow instances of a particular flow type. It underpins the configurable flows framework used within the Service product family, where a "flow" represents an ordered, user-facing process definition composed of pages and steps. The _B suffix denotes the base table that holds language-independent attributes, while translatable text is maintained in the companion _TL table. The object is owned by the CS schema and is documented as VALID at ETRM 12.2.2.

From a Data Vault modeling perspective, the metadata classifies CS_CF_FLOWS_B heuristically as hub-leaning. This suggests the table functions primarily as a hub that holds the unique identity of each flow instance (via FLOW_ID), with descriptive and control attributes carried alongside. Analysts designing a Data Vault or dimensional model should treat FLOW_ID as the durable business key candidate around which satellites and links would be constructed.

Key Information Stored

The table is documented with 26 physical columns. The most significant are:

• FLOW_ID — the surrogate primary key, defined by constraint CS_CF_FLOWS_B_PK, uniquely identifying each flow instance.
• ZD_EDITION_NAME — the editioning column associated with Oracle EBS 12.2 online patching; combined with FLOW_ID it forms the unique index CS_CF_FLOWS_B_U1, the documented business-key candidate.
• FLOW_TYPE_CODE — identifies the flow type to which the instance belongs, the principal business classification attribute.
• SEEDED_FLAG — indicates whether the flow definition shipped as seed data or was user-created, an important distinction for upgrade and support analysis.
• OBJECT_VERSION_NUMBER — supports optimistic locking and concurrent update detection in the OAF framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit lineage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) columns available for customer-configured extensions.

Note the distinction between the surrogate key (FLOW_ID as PK) and the business-key candidate (FLOW_ID, ZD_EDITION_NAME as U1). In 12.2.2 multi-tenant editioning, the composite unique index enforces identity across editions.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include listing all flows of a given type, distinguishing seeded versus custom flows, and tracing the pages belonging to a flow.

To enumerate flows by type:

SELECT f.FLOW_ID, t.FLOW_NAME, f.FLOW_TYPE_CODE, f.SEEDED_FLAG
FROM CS_CF_FLOWS_B f, CS_CF_FLOWS_TL t
WHERE f.FLOW_ID = t.FLOW_ID
AND f.FLOW_TYPE_CODE = :type_code;

To identify customer-defined (non-seeded) flows:

SELECT FLOW_ID, FLOW_TYPE_CODE, CREATION_DATE
FROM CS_CF_FLOWS_B
WHERE SEEDED_FLAG = 'N';

These queries support functional configuration audits, migration validation, and troubleshooting of flow rendering issues during patching. Because ZD_EDITION_NAME participates in the unique index, queries executed under 12.2 editioned sessions should be aware of edition scoping.

Related Objects

The following objects reference CS_CF_FLOWS_B through documented foreign keys keyed on FLOW_ID:

• CS_CF_FLOWS_TL — translation table storing language-specific flow name and description; joined on FLOW_ID. This is the primary companion for display queries.
• CS_CF_FLOW_PAGES_B — base table defining the pages that compose each flow; FK FLOW_ID links pages to their parent flow.
• CS_CF_FLOW_PAGES_TL — translatable text for flow pages; FK FLOW_ID associates page translations with the flow.

Together these objects form the core of the CS configurable flows data model. When reporting on complete flow definitions, join CS_CF_FLOWS_B to CS_CF_FLOWS_TL for names and to CS_CF_FLOW_PAGES_B / CS_CF_FLOW_PAGES_TL for page-level detail, always using FLOW_ID as the join predicate. Because the relationship is hub-leaning, CS_CF_FLOWS_B sits at the center of the model, with the _TL and _PAGES tables acting as dependent satellites and links.