Results for “type_description”

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

Overview

HR_S_FORMULA_TYPES is a Human Resources (PER) module table in the Oracle E-Business Suite database, owned by the HR schema. In the ETRM 12.2.2 documentation it is marked as retrofitted, indicating that its definition was carried forward from earlier releases (notably 12.1.1) with minimal structural change. The table functions as a reference or lookup store that catalogs the categories of formulas available within the Oracle Fast Formula framework, providing a controlled vocabulary for classifying formula definitions used across payroll, benefits, and other PER-dependent processes.

From a Data Vault modeling perspective, the mined classification for this object is standalone. This is a heuristic suggestion only: the table holds no incoming or outgoing foreign keys other than a single documented reference to FF_FORMULA_TYPES, so a modeler would most naturally treat it as a small reference hub rather than a link or satellite. Its narrow column count (eight documented columns) and stable, descriptive content reinforce that classification.

Key Information Stored

Of the eight documented columns, the most significant are:

• FORMULA_TYPE_ID — the surrogate primary key, a system-generated identifier that uniquely distinguishes each formula type row. Per the documented FK structure, this column is referenced by HR_S_FORMULA_TYPES.FORMULA_TYPE_ID, with the relationship pointing to FF_FORMULA_TYPES.
• FORMULA_TYPE_NAME — the descriptive business name of the formula type; this is the primary business-key candidate and is typically surfaced in list-of-values and lookup queries.
• TYPE_DESCRIPTION — a free-text field that elaborates on the purpose or scope of the type, useful for documentation and reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit triad recording when and by whom the row was last modified.
• CREATED_BY, CREATION_DATE — the audit pair capturing the creating user and the row's original insertion date.

No additional unique indexes are documented in the provided metadata beyond the surrogate primary key; the name column is the practical business identifier.

Common Use Cases and Queries

The table is most often queried to resolve a formula type ID into a human-readable name for reporting, or to drive parameterized lookups in custom concurrent programs and OAF/Forms extensions. Typical scenarios include auditing formula inventories, filtering formulas by category, and joining type metadata to actual formula definitions for downstream analysis. Representative SQL:

• SELECT formula_type_id, formula_type_name FROM hr.hr_s_formula_types;
• SELECT ft.formula_type_name, COUNT(*) FROM ff_formulas f JOIN hr.hr_s_formula_types ft ON f.formula_type_id = ft.formula_type_id GROUP BY ft.formula_type_name;
• SELECT * FROM hr.hr_s_formula_types WHERE last_update_date > :last_run; for incremental audit extracts.

Because the table is small and stable, it is frequently cached in reporting layers rather than joined live in high-volume transactions.

Related Objects

The documented FK relationship ties HR_S_FORMULA_TYPES to FF_FORMULA_TYPES on the FORMULA_TYPE_ID column, making FF_FORMULA_TYPES the most significant related object. Beyond that, formula definition and usage tables such as FF_FORMULAS, FF_FORMULA_ROUTES, FF_ROUTES, FF_CONTEXTS, FF_FUNCTIONS, and FF_COMPILATIONS logically interact through the shared formula-type identifier, even where not explicitly documented as FK relationships. The PER-formula public APIs that create and maintain Fast Formula metadata also depend indirectly on this reference table.