Search Results get_pending_transaction_steps

Overview

APPS.HR_QUA_AWARDS_UTIL_SS is a server-side PL/SQL utility package in Oracle E-Business Suite that supports the Self-Service (SS) qualifications and awards functionality delivered through Oracle iRecruitment, SSHR, and Learning Management. The "_SS" suffix indicates the package was designed to serve self-service flows rather than the professional forms-based HR user interface, and its AUTHID CURRENT_USER declaration reflects that it executes under the privileges of the invoking schema, typically APPS or a self-service responsibility's secured schema.

The package's central role is to manage the qualification and awards data entered by employees through self-service pages, coordinating validation and persistence through the HR API transaction framework. It abstracts the low-level detail of creating HR_API_TRANSACTIONS records, staging transaction steps and values, and invoking the appropriate qualification API, so that higher-level self-service processes can concentrate on business logic. The header comments ($Header: hrquawrs.pkh 115.14) indicate the package originates from the HR qualifications and awards family, and the presence of constants such as EDUCATION, AWARDS, EDUCATION_CHANGED, and AWARD_CHANGED shows the package distinguishes between the education and awards sub-entities it reconciles.

Key Procedures and Functions

• CHECK_ERRORS — Evaluates the qualification, subject, and attendance collections passed in, and returns error messages via output parameters. It supports boundary-date checking and mode-based logic.
• PROCESS_API — The package's declared API entry point (via API_NAME). Accepts a validate flag, a transaction step identifier, and an effective date to drive processing of a staged self-service transaction.
• GET_PENDING_TRANSACTION_IDS — Returns qualifications, attendance records, and transaction steps that are pending for a given item type, person, process, and activity.
• IS_QUALIFICATION_IN_PENDING — Function used to determine whether a specific qualification has a pending transaction for a person and activity context.
• VALIDATE_API — Performs validation of the supplied qualification, subject, and attendance data for a person prior to saving or submitting. This is the procedure most commonly associated with validation searches.
• DECODE_VALUE — Helper function that returns one of two strings based on a boolean expression, used for concise conditional logic.
• SAVE_TRANSACTION_STEP, ROLLBACK_TRANSACTION_STEP, DELETE_TRANSACTION_STEP, START_TRANSACTION — Manage the lifecycle of HR API transaction steps, including creating, committing, rolling back, and removing staged records.
• VALIDATE_QUALIFICATION — Validates an individual qualification record before it is persisted.
• GET_PENDING_TRANSACTION_STEPS, GET_ENTIRE_QUA, GET_QUALIFICATION_ID — Retrieval helpers that fetch pending steps, the full qualification aggregate, and a qualification identifier respectively.

Tables Accessed

• HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, HR_API_TRANSACTION_VALUES — Provide the transaction framework that stages and commits qualification and awards changes.
• PER_QUALIFICATIONS, PER_QUALIFICATION_TYPES, PER_SUBJECTS_TAKEN — Store the actual qualification, type, and subject data being managed.
• PER_ESTABLISHMENTS, PER_ESTABLISHMENT_ATTENDANCES — Hold the educational establishment and attendance information associated with qualifications.
• WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES — Track the workflow item and activity status that drives the self-service approval and processing flow.
• PLITBLM — The standard Oracle Forms PL/SQL table of long messages, used for message storage and retrieval.

Usage Notes

HR_QUA_AWARDS_UTIL_SS is typically invoked indirectly through self-service qualifications and awards pages, and through concurrent or background processes that complete pending HR API transactions. The presence of WF_ITEMS and WF_ITEM_ACTIVITY_STATUSES indicates the package participates in Oracle Workflow-driven processing, so it is generally called during the business events that trigger those workflows rather than as a standalone entry point in a form. Custom development should treat VALIDATE_API and PROCESS_API as the supported entry points and avoid calling the internal transaction-step management procedures directly, since those assume workflow-state consistency. Because the package uses AUTHID CURRENT_USER and is defined in APPS, grants to custom schemas should be made explicitly and tested carefully against the invoking responsibility's data security.