Search Results check_initial_save_for_later

Overview

APPS.PQH_SS_WORKFLOW is a PL/SQL package in the Oracle E-Business Suite (EBS) Applications schema that supports the Self-Service workflow and approval infrastructure for Oracle Public Sector/HR (PQH) transactions in releases 12.1.1 and 12.2.2. Its documented API classification is OTHER, indicating it is an internal helper package rather than a public, supported API. The package orchestrates the approval lifecycle of HR self-service transactions — such as promotions, transfers, terminations, and other assignment-based actions — by starting Oracle Workflow processes, tracking step and value history, and managing transaction status transitions as an approver or HR representative acts on a pending transaction.

The package holds status VALID in the ETRM 12.2.2 registry and depends only on SYS.STANDARD at the lowest level, relying on APPS synonyms for all business tables. It is referenced by six other packages, confirming its role as a shared utility within the PQH self-service stack.

Key Procedures and Functions

The ETRM registry documents 36 procedures and functions. Representative members include:

• GET_TRANSACTION_ID and GET_TRANSACTION_INFO — retrieve the identifier and descriptive context of the transaction being approved.
• START_APPROVAL_WF — launches the Oracle Workflow approval process for a submitted transaction.
• COMPLETE_WF_ACTIVITY — marks the current workflow activity as complete once the approver acts.
• GET_NOTIFIED_ACTIVITY — identifies the activity that generated a notification, used to route the correct response.
• RETURN_FOR_CORRECTION — returns a transaction to the originator for amendment.
• REVERT_TO_LAST_SAVE and RESET_TXN_CURRENT_VALUES — restore or clear saved working values.
• CHECK_INITIAL_SAVE_FOR_LATER — validates whether an initial save-for-later is permitted.
• SET_TRANSACTION_STATUS, SET_TXN_SUBMIT_STATUS, SET_TXN_APPROVE_STATUS, SET_TXN_RFC_STATUS, SET_TXN_SFL_STATUS — set the transaction's lifecycle status for submission, approval, return-for-correction, and save-for-later states.
• CHECK_ELIGIBILITY and APPLY_OR_APPROVE_ONLY — evaluate whether the transaction may proceed.
• GET_URL_FOR_EDIT and GET_EDIT_LINK — build the navigation link back to the editable transaction.
• NOTIFY_HR_REP — send notification to the HR representative.
• SET_EFFECTIVE_DATE_AND_OPTION — record the effective date and processing option chosen.

Tables Accessed

The package reads and writes the following APPS-synonym tables:

• HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, HR_API_TRANSACTION_VALUES — the core datastore of the transaction, its steps, and its field values.
• PQH_SS_APPROVAL_HISTORY, PQH_SS_STEP_HISTORY, PQH_SS_VALUE_HISTORY — self-service audit trails recording approver actions, workflow steps, and value changes.
• PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_ASSIGNMENT_STATUS_TYPES, PER_PAY_PROPOSALS, PER_PERIODS_OF_SERVICE — the employee, assignment, status, pay, and service records the transaction affects.
• FND_APPLICATION, FND_FORM_FUNCTIONS, FND_USER — application/function registration and the acting user.
• PQH_ROLES — the role definitions governing who may approve.

Usage Notes

PQH_SS_WORKFLOW is invoked indirectly rather than called directly by end users. It is referenced by HR_APPROVAL_SS, HR_PERSON_INFO_UTIL_SS, HR_TRANSACTION_SS, HR_WORKFLOW_SS, PQH_AME_APPROVALS, and PQH_SS_HISTORY, and it recurses onto itself. These callers are the self-service OAF/forms pages and the AME (Approvals Management Engine) integration layer that drive the approval flow. The package is therefore triggered when a manager or HR representative submits, approves, rejects, returns, or saves a self-service HR transaction, and when workflow notifications are responded to. Custom code should not call it directly; extensions should be built against documented public APIs. Because procedures and functions are undocumented publicly, references should be validated against the specific patch level of 12.1.1 or 12.2.2 in use.