Results for “hr_s_report_format_items_f”

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

Overview

HR_S_REPORT_FORMAT_ITEMS_F is a foundation table in the Oracle E-Business Suite Human Resources (PER) module, owned by the HR schema. It defines the individual report format items that make up configurable reporting layouts used across Oracle HRMS and, by extension, other applications consuming HR reporting metadata. Each row represents a single format item — a report type, category, qualifier, and associated user entity — that controls how a given report is structured, sequenced, and displayed to end users. Because the table carries EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and OBJECT_VERSION_NUMBER columns, it is date-effectivity enabled, supporting historical tracking of format item definitions.

Under the Data Vault classification heuristic mined from its foreign key structure, this table is identified as a standalone object. In Data Vault modeling terms, it would most naturally be treated as a satellite attached to the referenced user entity hub (FF_USER_ENTITIES), holding descriptive and effectivity attributes rather than acting as a pure hub or link. This classification should be regarded as a modeling suggestion rather than a rigid architectural constraint.

Key Information Stored

The table contains 16 documented columns. The most significant for functional and reporting purposes include:

• REPORT_FORMAT_ITEM_ID — the surrogate primary key uniquely identifying each format item row.
• REPORT_TYPE — the classification of the report the item belongs to.
• REPORT_QUALIFIER and REPORT_CATEGORY — additional business-key attributes that narrow and group report definitions.
• USER_ENTITY_ID — foreign key to FF_USER_ENTITIES, linking the format item to its owning user entity.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effectivity range governing when the item is active.
• DISPLAY_SEQUENCE — controls the ordering in which the item appears in the report layout.
• UPDATABLE_FLAG — indicates whether the item may be modified by users.
• ARCHIVE_TYPE — governs archival behavior for the item.
• OBJECT_VERSION_NUMBER — supports optimistic locking and concurrent update control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns tracking creation and modification.

The business-key candidates are REPORT_TYPE, REPORT_QUALIFIER, REPORT_CATEGORY, and USER_ENTITY_ID in combination with the effectivity dates; the surrogate key REPORT_FORMAT_ITEM_ID is the technically enforced unique identifier.

Common Use Cases and Queries

Typical usage centers on resolving report formatting metadata during report generation, validating which format items are active for a given user entity, and auditing changes to report layouts. A representative query retrieving currently effective items follows:

• SELECT REPORT_FORMAT_ITEM_ID, REPORT_TYPE, REPORT_CATEGORY, DISPLAY_SEQUENCE FROM HR.HR_S_REPORT_FORMAT_ITEMS_F WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, SYSDATE+1) ORDER BY DISPLAY_SEQUENCE;
• Joining to FF_USER_ENTITIES to resolve entity names: SELECT i.REPORT_TYPE, u.USER_ENTITY_NAME FROM HR.HR_S_REPORT_FORMAT_ITEMS_F i, HR.FF_USER_ENTITIES u WHERE i.USER_ENTITY_ID = u.USER_ENTITY_ID;
• Auditing recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance reporting.
• Filtering by UPDATABLE_FLAG to identify locked versus editable format items.

Reporting use cases include building extracts of report configurations for migration between environments and reconciling format items against expected report catalogs.

Related Objects

The most significant related objects are:

• FF_USER_ENTITIES — referenced by USER_ENTITY_ID; the primary parent of this table.
• FF_USER_ENTITY_USAGES — commonly joined to resolve usage context for the user entity.
• FND_FORMATS / FND_REPORT_FORMATS — related reporting format definitions.
• HR_S_REPORT_FORMAT_ITEMS_TL — the translation table where present for multilingual descriptions.
• HR_REPORT_FORMATS and associated HR reporting views that consume format item metadata.
• FND_USER — joined via LAST_UPDATED_BY for user attribution in audit queries.

Developers should treat this table as read-mostly and rely on supported HRMS APIs for maintaining report format definitions rather than direct DML.