Results for “delete_position_transaction”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQH_POSITION_TRANSACTIONS_API is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Public Sector/HR position management product family (the PQH prefix identifies the Position Management module), and it exposes a formal application programming interface for creating, maintaining, and removing position transactions. The package is classified as an API in the ETRM metadata, confirming that it is intended for programmatic invocation rather than internal-only use.

Position transactions are the records that capture changes to a position's definition, such as an update to a position's attributes or the eventual closure of a position. The package provides a controlled, validated entry point so that these changes are written consistently against the underlying position transaction table, allowing the HR and position management infrastructure to apply business rules, date tracking, and validation logic that would otherwise be bypassed by direct DML.

Key Procedures and Functions

The documented interface consists of three procedures, each addressing a distinct lifecycle operation:

• CREATE_POSITION_TRANSACTION — Inserts a new position transaction record. It is the entry point for registering a position-related change or event that does not yet exist in the system.
• UPDATE_POSITION_TRANSACTION — Modifies an existing position transaction record, allowing corrections or revisions to information already captured.
• DELETE_POSITION_TRANSACTION — Removes a position transaction record, used when a transaction must be reversed or is no longer valid.

The ETRM documentation does not publish parameter lists for these procedures, and the specific argument signatures should be confirmed against the package specification in the target instance before use. A typical design convention for EBS APIs of this class is to accept a primary key or surrogate identifier, the attribute values to be applied, an effective date, and a validation mode flag. Callers should not assume such parameters exist solely on the basis of this pattern.

Tables Accessed

The package operates against the PQH_POSITION_TRANSACTIONS table, accessed through an APPS synonym. This table stores the individual position transaction rows that the three procedures insert, amend, or delete. Because the API centralizes access to this table, direct inserts and updates by custom code should be avoided; the API is the supported path for maintaining the data and any dependent derived values or audit columns.

Usage Notes

The package is referenced by other position management components, including PQH_PTX_UTL and PQH_UTILITY, which indicates that it is a foundational building block used by higher-level utilities as well as by external callers. It also has a package-level self-reference, which is consistent with internal helper invocations within the same package body.

At the database level the package depends on HR_API and the SYS STANDARD package, so it participates in the standard EBS HR API error-handling and validation framework. Custom integrations, concurrent programs, and forms-based flows that manage position transactions should invoke these procedures rather than performing direct DML against PQH_POSITION_TRANSACTIONS. As with any EBS API, callers should follow the standard commit and error-checking conventions: inspect the returned status, commit explicitly only after success, and roll back on failure. Because the procedures are documented in ETRM as VALID at 12.2.2, the interface is considered current for both 12.1.1 and 12.2.2 deployments.