Search Results pay_upgrade_status




Overview
Explore in AI Chat

Overview

PAY_UPGRADE_STATUS is a payroll-module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to record the status of upgrades performed against the payroll schema, providing an auditable record of which upgrade definitions have been applied and whether their execution completed. The table is classified, heuristically, as a standalone object in Data Vault terms; the mined FK structure indicates no dependent children, and the single foreign key to PAY_UPGRADE_DEFINITIONS suggests the table behaves in practice like a satellite—capturing descriptive status and execution state keyed to an upgrade definition rather than acting as a hub or link. This classification is a modeling suggestion only; the physical ETRM record confirms six documented columns in release 12.2.2.

Because payroll upgrades must be tracked per legislation and per business group, the table carries both LEGISLATION_CODE and BUSINESS_GROUP_ID, making it a multi-tenant, multi-legislative audit surface for patch and upgrade activity in the PAY product.

Key Information Stored

The documented physical schema contains six columns. The primary business relationship is expressed through UPGRADE_DEFINITION_ID, which references PAY_UPGRADE_DEFINITIONS and identifies the upgrade definition whose progress is being recorded. This column is a foreign-key business-key candidate rather than a system-generated surrogate, since the ETRM metadata documents no independent single-column primary key for PAY_UPGRADE_STATUS.

  • UPGRADE_DEFINITION_ID — foreign key to PAY_UPGRADE_DEFINITIONS; identifies the upgrade whose status is tracked.
  • STATUS — the current state of the upgrade (for example, whether it is pending, in progress, or complete).
  • EXECUTED — indicates whether the upgrade has been executed.
  • REQUEST_ID — the concurrent request identifier associated with the upgrade run, tying the record to Concurrent Manager history.
  • BUSINESS_GROUP_ID — the business group (operating unit context) under which the upgrade applies.
  • LEGISLATION_CODE — the payroll legislation to which the upgrade applies, since payroll logic is legislated.

The combination of UPGRADE_DEFINITION_ID with BUSINESS_GROUP_ID and LEGISLATION_CODE is the most likely unique business key; STATUS, EXECUTED, and REQUEST_ID are descriptive or operational attributes.

Common Use Cases and Queries

Typical uses include verifying that a payroll upgrade has been applied across all legislations, reconciling upgrade status against concurrent request output, and reporting on incomplete or failed upgrades after a patch cycle.

  • Identifying upgrades that have not been executed: 
    SELECT upgrade_definition_id, status, executed, request_id
FROM   pay_upgrade_status
WHERE  executed = 'N';
  • Reporting status by legislation and business group: 
    SELECT legislation_code, business_group_id, status, COUNT(*)
FROM   pay_upgrade_status
GROUP  BY legislation_code, business_group_id, status;
  • Joining to the definition table for descriptive detail: 
    SELECT s.upgrade_definition_id, d.upgrade_name, s.status, s.request_id
FROM   pay_upgrade_status s,
       pay_upgrade_definitions d
WHERE  s.upgrade_definition_id = d.upgrade_definition_id;

Because REQUEST_ID links to concurrent processing, DBAs commonly correlate these rows with FND_CONCURRENT_REQUESTS to determine completion timestamps and output files.

Related Objects

  • PAY_UPGRADE_DEFINITIONS — the parent definition table; joined on UPGRADE_DEFINITION_ID.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to obtain request status and timing.
  • FND_CONCURRENT_PROGRAMS — identifies the upgrade program that generated the request.
  • HR_ALL_ORGANIZATION_UNITS — resolves BUSINESS_GROUP_ID to the organization unit.
  • FND_APPLICATION and FND_PRODUCT_INSTALLATIONS — contextual reference for the PAY application and its installation state.
  • PAY_ACTION_PARAMETERS and other PAY upgrade/log tables — companion structures used during the same payroll upgrade lifecycle.

No views or PL/SQL APIs are documented as directly depending on PAY_UPGRADE_STATUS in the supplied metadata; access is typically through direct SQL or upgrade tracking concurrent programs.