Search Results first_patchset

Overview

PAY_UPGRADE_DEFINITIONS_VL is a bilingual (VL, "view with language") database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY – Payroll product family. It presents payroll upgrade definitions — the metadata that describes how a payroll upgrade unit is identified, executed, qualified, and validated during patchset or legislative data upgrades. The view exposes upgrade_method and its related attributes, a term commonly searched by implementers and DBAs investigating how a particular upgrade step is performed.

Because it is a VL view, it resolves translated name and description values for the session language using the USERENV('LANG') setting, while non-translated operational attributes (such as upgrade_method, criticality, and upgrade_procedure) are inherited from the base table. In Oracle EBS 12.1.1 and 12.2.2 this object is available in the APPS schema and is typically queried for diagnostics, patch analysis, and reporting rather than being maintained directly by end users. The view is documented as VALID in ETRM metadata for 12.2.2.

Underlying Base Objects

The view is defined over three documented base objects:

• PAY_UPGRADE_DEFINITIONS (alias B) — the primary base table holding the operational upgrade attributes.
• PAY_UPGRADE_DEFINITIONS_TL (alias T) — the translation table holding language-specific NAME, DESCRIPTION, and ADDITIONAL_INFO.
• FND_APPLICATION — the Oracle Applications registry, joined to supply APPLICATION_SHORT_NAME for the owning application.

The join logic links B.UPGRADE_DEFINITION_ID to T.UPGRADE_DEFINITION_ID, filtered by T.LANGUAGE = USERENV('LANG'), and joins B.OWNER_APPLICATION_ID to F.APPLICATION_ID using an outer join (+), so upgrade definitions without a matching application are still returned. ROW_ID is derived from B.ROWID to support row identification.

Key Columns

• UPGRADE_DEFINITION_ID / SHORT_NAME — the primary key and the short identifier for the upgrade definition.
• UPGRADE_METHOD — the method by which the upgrade is performed; the attribute most frequently queried to distinguish execution strategies for an upgrade unit.
• UPGRADE_LEVEL — the level at which the upgrade applies (for example, legislation, business group, or payroll level).
• CRITICALITY / FAILURE_POINT — controls whether the step is critical and defines the point at which failure halts the upgrade.
• THREADING_LEVEL — governs parallelism when the upgrade is executed.
• UPGRADE_PROCEDURE / QUALIFYING_PROCEDURE — the PL/SQL procedures invoked to perform and to qualify the upgrade.
• LEGISLATION_CODE / LEGISLATIVE_ENABLED — identifies the legislation and whether it is enabled legislatively.
• FIRST_PATCHSET / VALIDATE_CODE — the originating patchset and validation code.
• NAME / DESCRIPTION / ADDITIONAL_INFO — language-resolved translations from the TL table.
• ROW_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard auditing columns.
• APPLICATION_SHORT_NAME — short name of the owning application from FND_APPLICATION.

Common Use Cases and Queries

A typical diagnostic queries the view to enumerate upgrade definitions and determine how each is executed. For example, to list definitions by upgrade method:

SELECT short_name, name, upgrade_method, criticality, upgrade_procedure
FROM apps.pay_upgrade_definitions_vl
WHERE upgrade_method = :p_method
ORDER BY short_name;

To inspect critical, non-legislatively-enabled definitions for a specific legislation:

SELECT ud.short_name, ud.name, ud.upgrade_level, ud.threading_level, ud.application_short_name
FROM apps.pay_upgrade_definitions_vl ud
WHERE ud.legislation_code = :p_legislation
AND ud.criticality = 'Y'
AND ud.legislatively_enabled = 'N';

These queries support patch impact analysis, troubleshooting stalled or skipped upgrade steps, and validating that the correct procedures are associated with a given upgrade unit in both 12.1.1 and 12.2.2 environments.