Search Results update_batch_lines_table

Overview

PAY_BEE_SS is an Oracle EBS Applications (APPS) schema PL/SQL package associated with the Payroll module's batch element entry (BEE) and batch processing infrastructure. In Oracle EBS 12.1.1 and 12.2.2, this package serves as a transaction-handling and API-support layer for the creation, validation, approval, and transfer of payroll batches — including batch headers, batch lines, and element entries — within the payroll processing workflow. The "SS" suffix and its dependency on Public Sector / HR approval history tables (PQH_SS_APPROVAL_HISTORY, PQH_SS_TRANS_STATE_HISTORY) indicate it is bound to the Oracle HRMS self-service and approval transaction framework that governs batch approvals in a workflow-enabled environment. The package is documented in ETRM with an API classification of OTHER, meaning it is not a published external API but an internally consumed utility package. It is not referenced by any other packages (0 dependents), confirming it is a leaf node invoked directly by forms, concurrent programs, or the approval engine rather than by other PL/SQL units.

Key Procedures and Functions

The ETRM metadata documents 22 procedures and functions, grouped functionally as follows:

Batch creation and line building: CREATE_BATCH, CREATE_BATCH_ASSIGNMENT_LINES, CREATE_BATCH_ELEMENT_LINES construct the batch header and populate assignment-level and element-level lines for a batch.
Input value population: SET_INPUT_VALUES and SET_ELEMENT_INPUT_VALUES populate element input values for the batch element lines, drawing from PAY_INPUT_VALUES_F definitions.
Transaction tracking and item keys: GET_TRANSACTION_ID_BATCH_NAME, GET_ITEM_KEY, SET_ITEM_KEY, and UPDATE_TRANSACTION_ID manage transaction identifiers and workflow item keys for the underlying HR_API_TRANSACTIONS record.
Table maintenance: UPDATE_DELETE_FLAG, UPDATE_BATCH_HEADER_TABLE, UPDATE_BATCH_LINES_TABLE, and UPDATE_ELEMENT_LINES_TABLE perform row-level updates, including logical deletion (delete flag) and synchronization of the batch tables.
Validation and approval: VALIDATE_BATCH and CALL_VALIDATE_BATCH execute batch validation logic; RELEASE_APPROVAL_BLOCK releases locked approval transactions; GET_PREVIOUS_PAGE supports UI navigation in the approval flow.
Cleanup and API processing: DELETE_ASSIGNMENT_INFORMATION removes assignment-related batch data; PROCESS_API and TRANSFER_BATCH drive the final API processing and transfer of the completed batch.

Tables Accessed

The package operates against the core payroll batch schema and HR API framework:

PAY_BATCH_HEADERS / PAY_BATCH_HEADERS_S — batch header definition and its translated/seed variant written by UPDATE_BATCH_HEADER_TABLE.
PAY_BATCH_LINES / PAY_BATCH_LINES_S — batch line records maintained by UPDATE_BATCH_LINES_TABLE and the CREATE_BATCH_* routines.
PAY_ELEMENT_TYPES_F — element type definitions used to resolve element entries.
PAY_INPUT_VALUES_F — valid input value definitions for elements, consumed by SET_INPUT_VALUES.
PER_ALL_ASSIGNMENTS_F — assignment data against which batch assignment lines are validated and created.
HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, HR_API_TRANSACTION_VALUES — the HR API transaction framework that records and steps the transaction lifecycle.
PQH_SS_APPROVAL_HISTORY, PQH_SS_TRANS_STATE_HISTORY — approval and state history tables used by the self-service/approval flow.
FND_CONCURRENT_REQUESTS, DBMS_LOCK, DUAL, STANDARD — Oracle foundation and locking utilities.

Usage Notes

PAY_BEE_SS is typically invoked from the Payroll Batch Element Entry forms and from the HRMS self-service approval infrastructure rather than from external custom code. The presence of CALL_VALIDATE_BATCH, RELEASE_APPROVAL_BLOCK, and GET_PREVIOUS_PAGE indicates direct use by an OAF-based or workflow-enabled approval UI, where batch approval transactions are locked and released through this package. Because it is classified as OTHER and is referenced by no other packages, it should be treated as an internal implementation utility; customizations should avoid direct dependency and instead use the supported public APIs (such as PAY_BATCH_ELEMENT_ENTRY_API or the standard batch upload interfaces). Concurrent processes that generate or transfer batch data may invoke TRANSFER_BATCH or PROCESS_API indirectly through the standard concurrent request framework.