Results for “hr_s_ftype_context_usages”

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

Overview

HR_S_FTYPE_CONTEXT_USAGES is a Human Resources (PER) module table in the Oracle E-Business Suite, residing in the HR schema. It is documented as a retrofitted object within the ETRM 12.2.2 reference set and remains VALID in the EBS 12.1.1 / 12.2.2 code lines. The name indicates an association between a formula type (FTYPE) and one or more contexts in which that type is permitted or applicable — a supporting relationship table rather than a transactional fact store.

The documented physical schema is deliberately minimal: only two columns, FORMULA_TYPE_ID and CONTEXT_ID. This confirms the table's role as a pure intersection/assignment entity that binds a formula type definition to a context value. Based on the supplied foreign-key structure, the heuristic Data Vault classification is link. That classification should be treated as a modeling suggestion: the object resolves a many-to-many relationship between formula types and contexts, and the ETRM analysis records no child tables depending on it, which is consistent with a terminal link with no further satellite fan-out in the documented model.

Key Information Stored

Only two columns are documented for this table, and both are significant:

• FORMULA_TYPE_ID — The identifier of the formula type. This is the sole documented foreign key and points to HR_S_FTYPE_CONTEXT_USAGES.FORMULA_TYPE_ID → FF_FORMULA_TYPES. It anchors each row to a specific formula type definition used by the Fast Formula engine.
• CONTEXT_ID — The identifier of the context associated with the formula type. This is the second half of the composite business key and typically references a context lookup or context definition used to scope formula evaluation.

The metadata does not expose a separate surrogate primary key column. In practice the effective key is the composite of FORMULA_TYPE_ID and CONTEXT_ID, which reflects the intersection semantics of the table. No alternate unique indexes are documented in the supplied ETRM extract, so no additional business-key candidates can be asserted beyond the two identifying columns. Consumers should not assume the presence of audit columns (WHO columns, dates, or flags), as none are documented for this object in 12.2.2.

Common Use Cases and Queries

The principal use case is determining which contexts a given formula type is allowed to be used in, which is relevant when configuring Fast Formula behavior, validating formula setup, and troubleshooting why a formula type is unavailable for a particular context. Typical reporting patterns include listing all contexts per formula type, checking whether a specific pairing exists, and reconciling formula type configuration across environments during upgrades or retrofits.

• Contexts for one formula type: SELECT CONTEXT_ID FROM HR.HR_S_FTYPE_CONTEXT_USAGES WHERE FORMULA_TYPE_ID = :formula_type_id;
• Resolving the formula type name: join to FF_FORMULA_TYPES on FORMULA_TYPE_ID to surface a readable type name alongside each context row.
• Existence check: a simple SELECT of both columns filtered by FORMULA_TYPE_ID and CONTEXT_ID confirms whether a pairing is configured before enabling it in a test or production instance.
• Coverage reporting: aggregate COUNT(*) grouped by FORMULA_TYPE_ID to identify formula types with few or no context assignments.

Related Objects

The most significant related object is the target of the documented foreign key relationship:

• FF_FORMULA_TYPES — referenced via FORMULA_TYPE_ID; the primary parent table supplying formula type definitions.
• FF_FORMULAS — stores formula definitions that ultimately rely on the formula type identified here.
• FF_FORMULA_TYPES_VL / _TL — the translatable views over formula types commonly joined for reporting.
• FF_CONTEXTS — the conventional source of context definitions referenced by CONTEXT_ID.
• FND_LOOKUP_VALUES — frequently used to resolve context or type codes into user-facing meanings.

Given that the ETRM Data Vault classification is standalone with only the single FF_FORMULA_TYPES foreign key, integrators should treat HR_S_FTYPE_CONTEXT_USAGES as a narrow configuration link table and avoid assuming undocumented dependencies.