Results for “updatable_flag”

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

Overview

The PAY_REPORT_FORMAT_ITEMS_X view is a date-effective (surrogate) view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product module. It is a public, VALID database object present in both Oracle EBS 12.1.1 and 12.2.2. Its primary role is to present the currently-effective rows of the underlying report format items entity, hiding the date-effective filtering logic from calling forms, concurrent programs, and integrations.

In Oracle EBS, date-effective business entities are typically modelled as a pair of objects: a base (_F) table that stores every version of a row across a range of effective dates, and a view (often suffixed _X) that exposes only the version whose effective date range brackets the current date. PAY_REPORT_FORMAT_ITEMS_X follows this convention exactly. By wrapping the base table, it shields consumers from having to add date-range predicates to every query, ensuring that only the row valid for TRUNC(SYSDATE) is returned. This is central to consistent reporting of payroll report-format definitions in forms and integration extracts.

Underlying Base Objects

The view is defined over a single documented base object: the synonym PAY_REPORT_FORMAT_ITEMS_F, which resolves to the date-effective base table holding all versioned rows. The relationship is a strict one-to-many filter — every row in the view corresponds to exactly one effective row of the base table, selected by the predicate:

WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE

The view therefore carries no data of its own; it is a non-materialized, deterministic projection. Because the filter is based on the current date, the set of rows returned changes over time as effective-dated versions begin and end. Writes are not supported directly against the view; changes flow through the base table using the date-effective API or forms logic.

Key Columns

The documented columns exposed by the view are consistent with the base table and include:

• REPORT_TYPE — the report type classification for the format item, forming part of the logical key.
• REPORT_QUALIFIER — further qualifies the report type.
• REPORT_CATEGORY — categorises the report format item.
• USER_ENTITY_ID — the identifier of the owning user entity (for example, a business group or legislative context).
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective-date range that governs which version is currently visible.
• ARCHIVE_TYPE — indicates the archival behaviour associated with the format item.
• UPDATABLE_FLAG — indicates whether the item is user-updatable.
• DISPLAY_SEQUENCE — the ordering value that controls the sequence in which format items are displayed. This is the column most relevant to ordering results in reports and on-screen lists, and is the attribute frequently targeted by users searching for display_sequence.

Common Use Cases and Queries

The view is used wherever the currently-effective report format items must be read for a report definition, including seeding display order in forms, driving concurrent report generation, and extracting configuration into external systems. A typical query retrieving effective items in display order is:

SELECT report_type, report_qualifier, report_category, user_entity_id, display_sequence
FROM apps.pay_report_format_items_x
WHERE user_entity_id = :p_user_entity_id
ORDER BY report_category, display_sequence;

A second useful pattern derives the display ordering governed by DISPLAY_SEQUENCE for a specific report type:

SELECT report_qualifier, display_sequence, updatable_flag
FROM apps.pay_report_format_items_x
WHERE report_type = :p_report_type
AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
ORDER BY display_sequence;

Because the view already applies the effective-date predicate, callers need not repeat the date range; however, historical or future-dated analysis must query the base table PAY_REPORT_FORMAT_ITEMS_F directly. Integrations should treat the view as read-only and respect that the returned row set is date-dependent.