Search Results apply_sit




Overview

APPS.PQH_PTX_UTL is a valid PL/SQL utility package in the Oracle E-Business Suite HRMS schema, classified under the API classification OTHER. Its name reflects its role as a support utility for Position Transaction (PTX) and Position Extra Information (PTE) processing within Oracle Position Management (PQH). The package centralizes the logic required to apply, refresh, and notify on position transactions — the records generated in PQH_POSITION_TRANSACTIONS when positions are created, updated, or relieved. It handles shadow-record maintenance, budget and deployment-factor population, transaction category resolution, worksheet interaction, and the generation of workflow notifications for the position-management approval process. Because it is an internal utility rather than a public API, it is primarily invoked by other HRMS components, concurrent processes, and forms-based position management flows.

Key Procedures and Functions

The package exposes 23 documented procedures and functions. These group into several functional areas:

No parameter signatures are documented in ETRM; consumers should treat these as internal entry points rather than a stable public interface.

Tables Accessed

Documented table references (through APPS synonyms) include: PQH_POSITION_TRANSACTIONS (the transaction being applied), PQH_TRANSACTION_CATEGORIES (category resolution), PQH_WORKSHEETS (worksheet context), PQH_PTE_SHADOW and PQH_PTX_DPF_DF (shadow and deployment-factor staging), the budget tables PQH_BUDGETS, PQH_BUDGET_DETAILS, PQH_BUDGET_PERIODS, and PQH_BUDGET_VERSIONS (funding validation and refresh), PER_DEPLOYMENT_FACTORS, PER_JOB_REQUIREMENTS and PER_JOB_REQUIREMENTS_S, PER_POSITION_EXTRA_INFO, HR_ALL_POSITIONS_F, and FND_ATTACHED_DOCUMENTS. These provide the position definitions, requirement rules, funding data, and attachments needed during apply and refresh operations.

Usage Notes

PQH_PTX_UTL is referenced by zero other packages per ETRM, indicating it is called internally by Oracle position-management modules — forms, concurrent programs, and workflow background processes — rather than by customer code. It is invoked when:

  • A position transaction is submitted, applied, or refreshed through the Position Management forms.
  • A workflow approval or rejection occurs, triggering the notification routines.
  • Budget or requirement data must be validated before a transaction is committed.
  • A concurrent process rebuilds shadow records for PTX or PTE.

Because the interface is undocumented and internal, customizations should avoid direct calls to these procedures; any extension should instead use supported HRMS or Position Management APIs. In 12.1.1 and 12.2.2 the package remains VALID in the APPS schema in both single- and multi-organization deployments.