Search Results post_any_txn

Overview

PQH_WF is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite. It provides the workflow integration layer for Oracle Public Sector/HR budgeting and transaction routing functionality, primarily in the Oracle HRMS and Public Sector Budgeting product families. The package encapsulates the business logic that drives Oracle Workflow notifications, approvals, routing, and transaction posting for HR budget and position management transactions.

The package serves as the central orchestration point that bridges application transaction data (budget, position, and people records) with the Oracle Workflow engine. It handles the lifecycle of a routing or approval event by identifying the next user, creating or updating routing history, generating notifications, processing user responses, and posting the resulting transaction. Because Oracle Workflow drives so many HR budget approval processes, PQH_WF is a foundational utility referenced by numerous other packages in the PQH family.

Key Procedures and Functions

ETRM documents 35 procedures and functions in PQH_WF. The most significant include:

• STARTPROCESS — Initiates a workflow process for a transaction, establishing the workflow context.
• FIND_NEXT_USER and SET_NEXT_USER — Determine and assign the next approver or routing recipient based on routing list configuration.
• APPROVE_TXN, APPROVE_TXN-related POST_TXN, and POST_ANY_TXN — Handle approval actions and persist the approved transaction.
• PROCESS_NOTIFICATION, PROCESS_RESPONSE, PROCESS_USER_ACTION — Interpret Oracle Workflow notification responses (approve, reject, reassign) and drive subsequent actions.
• CHECK_FYI, CHK_FYI_RESULTS, FYI_NOTIFICATION, NOTIFY_REQUESTOR — Manage FYI-style notifications and inform the transaction requester of status changes.
• CREATE_ROUTING_HISTORY and REROUTE_FUTURE_ACTION — Record routing events and redirect pending workflow steps.
• CHK_EFFECTIVE_DATE — Validate date-effective conditions tied to transactions and assignments.
• GET_DEFAULT_ROLE, GET_WORKFLOW_NAME, CHK_ROOT_NODE, COMPLETE_DELEGATE_WORKFLOW — Support workflow configuration, role resolution, routing-tree validation, and delegation completion.
• FIND_NEXT_USER — Resolves the appropriate approver for a routing step.

Tables Accessed

PQH_WF reads and writes several core tables through APPS synonyms:

• PQH_ROUTING_HISTORY, PQH_ROUTING_HIST_ATTRIBS, and PQH_ROUTING_LIST_MEMBERS — Store routing history records, their attributes, and the members of routing lists used to resolve approvers.
• PQH_FYI_NOTIFY — Tracks FYI notification records.
• PQH_TRANSACTION_CATEGORIES — Supplies the transaction category definition governing the workflow process.
• WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_PROCESS_ACTIVITIES — Oracle Workflow runtime tables used to create items, track activity status, and query process definitions.
• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — Provide date-effective assignment and person data for approver and requestor resolution.
• FND_USER — Resolves application users associated with routing and notification recipients.
• PLITBLM — A PL/SQL index-by table used for internal bulk processing of IDs.
• FND_PROFILE — Retrieves profile option values that influence workflow behavior.

Usage Notes

PQH_WF is not an end-user-facing package; it is invoked internally by other PQH packages during budget and transaction processing. The dependency metadata shows that it is referenced by at least eight packages, including PQH_APPLY_BUDGET, PQH_BUDGET, PQH_BUDGET_ANALYSIS_PKG, PQH_BDGT_REALLOC_UTILITY, PQH_PTX_UTL, PQH_WKS_BUDGET, and PQH_WF itself (for internal recursion). The views PQH_ROUTING_HISTORY_V and PQH_TRANSACTIONS_V also reference it.

Typical invocation occurs when a budget or position transaction requires approval: the calling package invokes STARTPROCESS, which drives notification and response handling through Oracle Workflow. Custom code extending PQH workflow behavior should call the documented procedures rather than manipulating the underlying WF_ITEMS and routing tables directly, since PQH_WF encapsulates the required sequencing and validation logic. Customers modifying routing, approvals, or FYI notifications in HRMS budgeting should recognize PQH_WF as the core workflow handler and treat its documented metadata as the authoritative reference for which procedures are supported in Oracle EBS 12.1.1 and 12.2.2.