Search Results get_tenure_details




Overview

PQH_PROCESS_TENURE_STATUS is an Oracle EBS HRMS package in the APPS schema that supports the tenure-status tracking requirements of the Public Sector/HRMS (PQH) product family, which governs position management, tenure, and related HR transactions. The package operates within Oracle Workflow's business event and transaction framework. It exposes a small, focused API surface designed to evaluate whether a given tenure-related transaction step is valid, to retrieve and persist tenure detail information stored against a person, and to support transactional control callbacks such as rollback handling and routing checks. The package is compiled with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking schema rather than as the definer.

Key Procedures and Functions

  • GET_TENURE_STATUS — A function returning a REF CURSOR, keyed by a transaction step identifier. It provides the caller with the tenure status result set for a given workflow transaction step, allowing a client to inspect the outcome or state of tenure evaluation.
  • GET_TENURE_DETAILS — A procedure that retrieves the descriptive tenure information (a set of information columns plus the person extra information identifier) for a transaction step, returning the values through OUT parameters.
  • SET_TENURE_DETAILS — A procedure that writes tenure detail values against a person's extra information record. It accepts the login person, the subject person, item type and key, activity, object version, and the person extra information identifier, together with the six information attributes to be stored.
  • PROCESS_API — The principal processing entry point. It takes a validation flag and a transaction step identifier and performs the core tenure-status logic, optionally in validation-only mode.
  • ROLLBACK_TRANSACTION — A workflow transaction callback that returns a result indicator. This is the procedure most commonly associated with the rollback_transaction search term; it is invoked by the Workflow engine when a transaction must be undone, allowing the package to signal success or failure of the rollback.
  • SELF_OR_SUBORDINATE — A routing/authorization function used within workflow activity processing to determine whether the acting user is the subject of the transaction or a subordinate of that subject, returning the outcome through an IN OUT result parameter.

Tables Accessed

The package references two documented tables through APPS synonyms: HR_API_TRANSACTION_STEPS and HR_API_TRANSACTION_VALUES. HR_API_TRANSACTION_STEPS holds the workflow transaction step records that identify which business object is being processed and at which stage; the tenure-status procedures use the transaction step identifier to locate the correct step. HR_API_TRANSACTION_VALUES stores the individual attribute values associated with a transaction, and is the store from which tenure detail attributes are read and to which they are written. Together these tables provide the persistence layer underpinning the validation, retrieval, and rollback operations.

Usage Notes

This package is typically invoked indirectly rather than by end users. It is called by Oracle Workflow function activities configured against HRMS tenure business processes, and by the HR API transaction infrastructure when processing or reversing tenure-related transactions. Forms within the PQH product family may call the submission and query procedures when a user initiates or reviews a tenure action. Custom code extending tenure behavior should treat PROCESS_API and the rollback callback as the supported entry points and avoid direct manipulation of the underlying transaction tables. Because the package subscribes to the standard HR API transaction pattern, callers must supply a valid transaction step identifier and, where applicable, appropriate item type, item key, and activity context so that commit and rollback callbacks can resolve correctly. The metadata records no inbound package dependencies, indicating the package is a leaf-level utility rather than a shared service.