Results for “ff_route_context_usages”

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

Overview

FF_ROUTE_CONTEXT_USAGES is a FastFormula (FF) configuration table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It records each individual usage of a context as a bind variable within the ROUTE SQL statement associated with a FastFormula route. In Oracle FastFormula, routes drive the selection and execution path of formulas by mapping database contexts (such as effective dates, business groups, or payroll identifiers) into parameterized SQL statements. FF_ROUTE_CONTEXT_USAGES captures the relationship between a route and the contexts it consumes, preserving both the identity of the context and its ordinal position within the route's SQL statement. This enables Oracle to bind context values at runtime and dynamically resolve formula execution without hard-coding context logic.

From a Data Vault modeling perspective, the heuristic classification for this table is a link. This is consistent with its structure: it joins FF_ROUTES and FF_CONTEXTS through foreign keys and carries only descriptive attributes (SEQUENCE_NO) needed to order the relationship, which is characteristic of a link entity resolving a many-to-many relationship between its referenced hubs.

Key Information Stored

The table contains four documented columns in the 12.2.2 physical schema. The most significant are:

• ROUTE_ID — Foreign key to FF_ROUTES, identifying the FastFormula route that owns this context usage.
• CONTEXT_ID — Foreign key to FF_CONTEXTS, identifying the context consumed as a bind variable.
• SEQUENCE_NO — Ordinal position of the bind variable within the route's SQL statement, ensuring deterministic parameter ordering.
• ZD_EDITION_NAME — Editioning column introduced under the 12.2 online patching (ADOP) architecture, supporting edition-based redefinition of the HR schema objects.

The surrogate identity of a row is defined by the composite primary key FF_ROUTE_CONTEXT_USAGES_PK, which in the 12.2.2 schema is (ROUTE_ID, CONTEXT_ID, ZD_EDITION_NAME). The unique index FF_ROUTE_CONTEXT_USAGES_UK2 on (ROUTE_ID, SEQUENCE_NO, ZD_EDITION_NAME) enforces the business rule that a route cannot assign the same ordinal position to two different contexts. Together, these keys distinguish the surrogate component (the edition-aware PK) from the business-key candidate (the sequence-based unique constraint).

Common Use Cases and Queries

This table is primarily interrogated during FastFormula troubleshooting, route validation, and migration projects. Typical scenarios include confirming that a route's bind-variable list is complete and correctly ordered, auditing which contexts a given formula route depends on, identifying routes affected by a context change, and reconciling configuration across environments or editions.

A representative query lists the ordered contexts for a given route:

• SELECT r.route_id, r.route_name, c.context_name, u.sequence_no FROM ff_route_context_usages u JOIN ff_routes r ON r.route_id = u.route_id JOIN ff_contexts c ON c.context_id = u.context_id WHERE u.route_id = :p_route_id ORDER BY u.sequence_no;

Another pattern reverses the view to find every route that uses a particular context, which is useful during impact analysis of a context change:

• SELECT u.sequence_no, r.route_name FROM ff_route_context_usages u JOIN ff_routes r ON r.route_id = u.route_id WHERE u.context_id = :p_context_id;

Reporting on sequence gaps or duplicates (relative to FF_ROUTE_CONTEXT_USAGES_UK2) supports route integrity checks after patching or data migration. Because route configuration is highly sensitive to release, queries are typically executed in a read-only fashion against the HR schema and filtered by ZD_EDITION_NAME in 12.2 environments.

Related Objects

The following objects are most significant when working with or reporting on FF_ROUTE_CONTEXT_USAGES, based on the documented foreign-key relationships:

• FF_ROUTES — Referenced via FF_ROUTE_CONTEXT_USAGES.ROUTE_ID; the parent entity defining each FastFormula route.
• FF_CONTEXTS — Referenced via FF_ROUTE_CONTEXT_USAGES.CONTEXT_ID; the parent entity defining each context used as a bind variable.
• FF_ROUTE_CONTEXT_USAGES_PK — Primary key index (ROUTE_ID, CONTEXT_ID, ZD_EDITION_NAME).
• FF_ROUTE_CONTEXT_USAGES_UK2 — Unique index (ROUTE_ID, SEQUENCE_NO, ZD_EDITION_NAME) enforcing ordering uniqueness.

In practice these tables are consumed alongside other FastFormula metadata such as FF_FORMULAS, FF_FORMULA_ROUTES, FF_GLOBALS, and FF_DATABASE_ITEMS when diagnosing route execution or bind-variable errors. Because the table is a configuration link rather than a transactional object, related dependencies are almost exclusively within the FastFormula schema family rather than across other EBS modules.