Search Results pay_void_process_request_s2

Overview

APPS.PAY_FLOW_REQUESTS_PKG is a PL/SQL package in Oracle E-Business Suite that supports the execution of payroll processing flows. It provides the programmatic infrastructure that allows Oracle Payroll to create, stage, invoke, monitor, and clean up payroll process requests. These requests are held in the PAY_PROCESS_REQUESTS table, which acts as a persistent data model of work awaiting processing, and are subsequently submitted to the concurrent manager for execution.

The package is central to the "flow" model of payroll processing, where one or more process flows are configured in PAY_PROCESS_FLOWS and assembled into logical sequences. When a payroll run, costing run, or related process must be executed, this package translates the flow definition into concrete entries in the request table, resolves the parameter values required for each step, and drives the request through its lifecycle. In the Oracle EBS 12.1.1 and 12.2.2 releases, the ETRM classifies this object as an OTHER API, meaning it is a supporting internal package rather than a user-facing public API. The source header references the file pyprflow.pkb and indicates the object was created under ER/CR 6820127, with the dbdrv install phase set to plb.

Key Procedures and Functions

The documented interface comprises seven procedures, each addressing a distinct stage of the request lifecycle:

• CREATE_REQUEST — Creates a request in the PAY_PROCESS_REQUESTS data model so that it can be picked up for processing. The procedure accepts a process flow identifier and a parameter count, establishing the request and its associated parameter context.
• INVOKE_REQUEST — Submits or initiates a request that has already been created, moving it into active processing.
• UPDATE_PROCESS_STATUS — Maintains the status of a process flow request, reflecting progress, completion, or failure in the PAY_PROCESS_REQUESTS record.
• EXECUTE_REQUEST — Performs the processing logic required to carry out a staged request against the underlying flow definition.
• PURGE_REQUESTS — Removes obsolete request records, providing housekeeping for the request table.
• CANCEL_REQUEST — Cancels a request that has been created but is no longer required or has not yet run.
• INSERT_CHILD_REQUEST — Creates a dependent request spawned from a parent, supporting multi-step or hierarchical flows.

Together these procedures allow a flow to be decomposed into individual requests, executed sequentially or as children of a parent, and then reconciled and purged when complete.

Tables Accessed

The package reads and writes PAY_PROCESS_REQUESTS, the primary staging table for requests awaiting or undergoing processing. It references PAY_PROCESS_FLOWS and PAY_PROCESS_FLOW_SETS to obtain the definitional context of the flow being executed. Parameter values are resolved through PAY_PARAMETER_SETS, PAY_PARA_SET_VARIABLES, PAY_PARA_SET_VAR_VALUES, and the view PAY_PARA_SET_OVERRIDE_VARS, which together supply the variables, their values, and any overriding values for a given parameter set. When requests are submitted to the concurrent manager, the package interacts with FND_CONCURRENT_REQUESTS. Sequencing assistance is provided by the PAY_VOID_PROCESS_REQUEST_S1 and PAY_VOID_PROCESS_REQUEST_S2 sequences and the PAY_VOID_SET_VAR_VAL_ID_S sequence, while DUAL is used for single-row expression evaluation. Notably, PAY_VOID_SET_VAR_VAL_ID_S indicates this package also participates in the void payment process, generating request records to reverse or void payments.

Usage Notes

PAY_FLOW_REQUESTS_PKG is typically invoked indirectly by Oracle Payroll forms and concurrent programs rather than called directly by end users. The Process Flow configuration windows and payroll process submission pages rely on it to translate configured flows and parameter sets into executable concurrent requests. It is referenced by one other package, indicating an internal dependency chain within the payroll processing stack. Custom code should exercise caution: the procedures are tightly coupled to the PAY_PROCESS_REQUESTS data model, so direct invocation outside a supported payroll flow context can leave orphaned or inconsistent request records. The presence of the package body in the APPS schema and its classification as an OTHER API confirm that it is a supporting component of the payroll flow engine, intended for internal orchestration, monitoring, and cleanup of payroll process requests across both the 12.1.1 and 12.2.2 releases.