Search Results replace_run_flag

Overview

PAY_RETRO_COMPONENT_USAGES_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the PAY (Payroll) product family and is documented in ETRM with the description "Used to support user interface." The view surfaces configuration data that defines how retroactive payroll components are used during retroactive processing, including which components are enabled by default, how reprocessing is performed, and whether the previous payroll run is replaced or a new run is created.

Because the object is a view rather than a table, it exists purely as a query layer. Its principal role is to resolve foreign-key identifiers into user-meaningful descriptions for the Payroll retroactive component setup forms and related self-service pages. It does not store data. The view joins the retro component definition to its usage rule and decodes the REPROCESS_TYPE code through HR_LOOKUPS. The column named in the user's search, REPLACE_RUN_FLAG, is exposed directly from the underlying PAY_RETRO_COMPONENT_USAGES table and indicates whether a retro component usage replaces the original payroll run when it is reprocessed.

Underlying Base Objects

The documented base objects are PAY_RETRO_COMPONENT_USAGES (SYNONYM), PAY_RETRO_COMPONENTS (SYNONYM), HR_LOOKUPS (VIEW), and HR_API (PACKAGE). The view definition is a three-table join:

• PAY_RETRO_COMPONENT_USAGES PRCU — the driving table holding the usage configuration records.
• PAY_RETRO_COMPONENTS PTR — the parent retro component definition, joined on RETRO_COMPONENT_ID.
• HR_LOOKUPS HL — the lookup table, filtered to LOOKUP_TYPE = 'RETRO_REPROCESS_TYPE' and joined on LOOKUP_CODE = REPROCESS_TYPE.

The HR_API package is a documented dependency but is not referenced in the view's SQL text, indicating it is used by the calling user-interface logic rather than by the view itself. The synonyms resolve to the underlying PAY tables in the APPS schema.

Key Columns

• ROW_ID — the ROWID of the base usage row; useful for identifying a single record.
• RETRO_COMPONENT_USAGE_ID — primary key of the usage record.
• RETRO_COMPONENT_ID / COMPONENT_NAME — the retro component and its display name from PAY_RETRO_COMPONENTS.
• BUSINESS_GROUP_ID / LEGISLATION_CODE — the business group and legislative context of the usage.
• DEFAULT_COMPONENT — flag indicating whether the component is included by default in retro processing.
• REPROCESS_TYPE / D_REPROCESS_TYPE — the reprocess code and HR_LOOKUPS.MEANING decoded value.
• REPLACE_RUN_FLAG — controls whether reprocessing replaces the existing payroll run.
• USE_OVERRIDE_DATES — controls whether override dates are applied.
• CREATOR_ID / CREATOR_TYPE — identifies whether the record was created by Oracle seed data or by a user.
• Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER).

Common Use Cases and Queries

The view is typically queried to audit or report on retro component configuration. To inspect the replace-run behaviour for a business group:

• SELECT retro_component_usage_id, component_name, d_reprocess_type, replace_run_flag, use_override_dates FROM pay_retro_component_usages_v WHERE business_group_id = :bg_id;
• SELECT component_name, replace_run_flag FROM pay_retro_component_usages_v WHERE replace_run_flag = 'Y';
• SELECT d_reprocess_type, COUNT(*) FROM pay_retro_component_usages_v GROUP BY d_reprocess_type;

These queries support configuration verification, migration comparison between environments, and troubleshooting of retro processing behaviour. All access is read-only.