Search Results retro_reprocess_type

Overview

APPS.PAY_RETRO_COMPONENT_USAGES_V is a reporting and integration view in the Oracle EBS Payroll (PAY) schema that presents configuration records controlling how retroactive pay processing is performed for individual payroll components. Each row describes a "retro component usage" — the association between a retro component definition and the rules governing whether that component defaults onto a retro run, how it is reprocessed, and whether it replaces a prior run. The view is defined in the APPS schema and is exposed to reporting tools, concurrent programs, and integration interfaces that need a denormalized, human-readable representation of retro component usage setup.

The view is particularly relevant when users search on the term d_reprocess_type. This is the translated (display) meaning of the coded REPROCESS_TYPE column, resolved through an HR_LOOKUPS join on lookup type RETRO_REPROCESS_TYPE. The D_ prefix follows the standard Oracle EBS convention for a descriptive, user-facing flexfield or lookup value that accompanies a stored code.

Underlying Base Objects

The view is defined over three primary source objects plus supporting references documented in the 12.2.2 ETRM metadata:

• PAY_RETRO_COMPONENT_USAGES (SYNONYM) — the driving table, aliased PRCU, supplying the usage identifier, business group, legislation code, component reference, reprocess type code, creator/audit columns, and the REPLACE_RUN_FLAG and USE_OVERRIDE_DATES attributes.
• PAY_RETRO_COMPONENTS (SYNONYM) — aliased PTR, joined on RETRO_COMPONENT_ID to supply the descriptive COMPONENT_NAME.
• HR_LOOKUPS (VIEW) — aliased HL, joined to resolve REPROCESS_TYPE into its descriptive MEANING via lookup type RETRO_REPROCESS_TYPE.
• HR_API (PACKAGE) — referenced as supporting metadata for the HR lookups and business-group-level processing used by this view.

Because the join to HR_LOOKUPS is an equality (not an outer join) on both lookup type and lookup code, a row only appears when a matching enabled lookup exists; if no lookup is defined for a given code, the usage record is suppressed from the result set.

Key Columns

• ROW_ID — the ROWID of the underlying PAY_RETRO_COMPONENT_USAGES row, useful for direct row identification.
• RETRO_COMPONENT_USAGE_ID — the primary identifier for the usage record.
• BUSINESS_GROUP_ID — the HR business group owning the record, central to multi-organization filtering.
• LEGISLATION_CODE — the legislative context governing the retro component.
• RETRO_COMPONENT_ID / COMPONENT_NAME — the referenced retro component identifier and its descriptive name from PAY_RETRO_COMPONENTS.
• REPROCESS_TYPE / D_REPROCESS_TYPE — the stored code and its translated lookup meaning for how the component is reprocessed in retro runs. This pair is the focal point of a "d_reprocess_type" search.
• DEFAULT_COMPONENT — indicates whether the component is defaulted onto retro processing.
• REPLACE_RUN_FLAG and USE_OVERRIDE_DATES — control flags governing run replacement behavior and date override handling.
• CREATOR_ID / CREATOR_TYPE — identify the origin of the usage definition.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER support auditing and optimistic locking.

Common Use Cases and Queries

Typical scenarios include auditing retro component setup, reporting default and reprocess behavior by business group or legislation, and feeding integration extracts. A representative query filtering on the reprocess type display value follows:

SELECT retro_component_usage_id,
       business_group_id,
       component_name,
       reprocess_type,
       d_reprocess_type,
       default_component,
       replace_run_flag,
       use_override_dates
FROM   apps.pay_retro_component_usages_v
WHERE  business_group_id = :p_business_group_id
AND    d_reprocess_type = :p_reprocess_meaning
ORDER BY component_name;

The view is read-only and should be queried rather than updated; maintain the underlying PAY_RETRO_COMPONENT_USAGES records through the supported Payroll setup forms and APIs.