Search Results pa_work_type_upgrade




Overview

PA_WORK_TYPE_UPGRADE is an Oracle Applications (APPS) schema PL/SQL package within the Oracle E-Business Suite Projects (PA) module. Its status is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The package serves as a data migration and upgrade utility rather than as a runtime business API. Its central purpose is to populate and reconcile work type assignments on existing project transactions and related cost, expenditure, and distribution records during an upgrade or patch cycle.

Work types classify the nature of labor and non-labor transactions within Oracle Projects, and their correct attribution is essential for burdening, costing, invoicing, and reporting. When a new work type structure is introduced, or when existing transaction tables lack a valid work type reference, the upgrade package is responsible for deriving the appropriate value and writing it back to the affected records. The ETRM classifies the package as API classification OTHER, confirming that it is not a public, supported integration interface and is intended for internal, controlled execution.

Key Procedures and Functions

The documented metadata identifies a single entry point:

  • UPGRADE_WT_MAIN — The main driver procedure of the package. It orchestrates the work type upgrade process, coordinating the identification of transactions requiring a work type assignment, the derivation or lookup of the correct value, and the propagation of that value to the target transaction and distribution tables. As the primary and only documented routine, it encapsulates the package's upgrade logic and is the procedure invoked by the calling concurrent program or patch driver.

No parameter lists are documented in the ETRM metadata, and none should be assumed.

Tables Accessed

The package references a broad set of APPS synonyms spanning Projects, Payables, Purchasing, and Inventory. The documented tables and their likely roles are:

Usage Notes

PA_WORK_TYPE_UPGRADE is an internal upgrade utility. It is typically invoked by Oracle-supplied patch drivers or concurrent programs during the application of a Projects patch or release upgrade, and it is referenced by zero other packages, confirming it sits at the outer edge of the dependency chain rather than within it. It is not designed to be called from Oracle Forms or from customer-written integration code. Because the package reads and writes high-volume costing and distribution tables, execution should be restricted to the controlled upgrade window, preceded by a validated backup and followed by the standard data verification steps for Projects transactions. Custom implementations should not invoke UPGRADE_WT_MAIN directly; any need to regenerate work type values should be routed through supported Oracle Projects processes and Oracle Support guidance.