Search Results save_for_later

Overview

APPS.HR_WIP_TXNS is a server-side PL/SQL package in Oracle EBS 12.1.1 and 12.2.2 that supports the WIP (Work In Process) transaction framework used by Oracle HR and related self-service flows. It manages the lifecycle of "WIP transactions" — intermediate, lightweight records that capture a user's in-progress or pending data entry before it is committed to the underlying business entity. Rather than writing directly to the base tables on every keystroke, applications route activity through HR_WIP_TXNS so that drafts, saves, approvals, rejections, and deletes are tracked consistently and tied to an originating form function and workflow item.

The package is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user, and its header ($Header: hrwiptxn.pkh 115.2) places its origin in the Oracle HR self-service development stream. It is classified by ETRM as a general API of type OTHER, and it is referenced by one other package, indicating its role as a supporting utility rather than a standalone entry point.

Key Procedures and Functions

• CHK_TRANSACTION_CREATOR — Validates that the user attempting to create a transaction (p_creator_user_id) matches or is authorized relative to the current user (p_current_user_id), enforcing creator ownership before a transaction record is established.
• CREATE_TRANSACTION — Provided in two overloaded forms: a function and a procedure. Both accept a workflow item type/key, a form function ID, creator user ID, DML mode, a VO XML payload, and context display text. The function returns the new transaction ID; the procedure returns it via an OUT NOCOPY parameter. This is the primary entry point for registering a new WIP transaction.
• CREATE_QUERY_ONLY_TRANSACTION — Creates a transaction in a read-only/query-only mode, used where a record must be registered without permitting subsequent modification.
• SAVE_FOR_LATER — Persists the current transaction state without completing or submitting it, allowing a user to resume data entry later.
• SAVE_FOR_LATER_APPEND — Variant of the save-for-later operation that appends to an existing transaction rather than replacing its stored state.
• PENDING_APPROVAL — Moves a transaction into a pending approval status, signalling that it has been submitted and awaits a reviewer or approver.
• REJECT_FOR_CORRECTION — Returns a submitted transaction to the originator for correction, typically invoked by an approver.
• DELETE_TRANSACTION — Removes an existing WIP transaction record.
• UPDATE_TRANSACTION — Modifies the details of an existing transaction, including its payload and contextual attributes.

Tables Accessed

• HR_WIP_TRANSACTIONS / HR_WIP_TRANSACTIONS_S — The primary and shadow (audit/sequence) tables storing transaction details, DML mode, context display text, and status.
• FND_USER — Source of creator and current-user identifiers used in authorization checks.
• FND_FORM_FUNCTIONS — Identifies the originating form function tied to each transaction.
• WF_ITEMS — Links the transaction to its Oracle Workflow item type and key for process integration.
• HR_WIP_LOCKS — Supports concurrency control so that a transaction cannot be edited simultaneously by multiple users.
• DBMS_LOB — Reads and writes the large XML payload (VO XML) associated with each transaction.

Usage Notes

HR_WIP_TXNS is normally invoked indirectly by Oracle HR self-service forms and related framework code rather than called directly by end users. Customizations that need to mirror the standard save-for-later, pending-approval, or correction workflow should call the documented procedures using the same parameter conventions, ensuring creator validation and lock handling are respected. Because the package relies on APPS synonyms (FND_USER, WF_ITEMS, HR_WIP_TRANSACTIONS), custom code must execute with the appropriate APPS privileges. When integrating, always supply a valid function ID and workflow item so downstream approval and query functions behave correctly.