Results for “per_sp_stage”

26 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PER_SP_STAGE is a valid PL/SQL package body in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, owned by the APPS schema. It belongs to the Oracle Succession Planning module (identified by the PER_SP_ prefix, where SP denotes Succession Planning) and is classified as an "OTHER" API. The package orchestrates the staging and transactional movement of succession plan data, bridging stored succession plan definitions with HR API transactions and Oracle Workflow-driven approval logic. Its central purpose is to take staged successor/plan records, convert them into HR API transactions, submit them through an approval workflow, and commit or reject those transactions based on approver action.

The package name and its dependency chain indicate that PER_SP_STAGE operates as the staging and transaction engine for succession plan changes, coordinating with plan APIs, successor-in-plan APIs, and copy-entity utilities. It is a self-referencing package (it references itself), reflecting internal helper calls between staging and transaction routines.

Key Procedures and Functions

The documented API exposes ten procedures/functions. Their roles, based on the ETRM metadata, are:

  • CREATEHRAPITRANSACTION — Creates an HR API transaction record, likely wrapping HR_API_TRANSACTIONS via HR_API.
  • CREATE_SP — Creates the succession plan staging entity that subsequent routines operate on.
  • STAGE_TO_SP — Moves data from the staging area into the succession plan (PER_SP_PLAN).
  • SP_TO_STAGE — The inverse operation, extracting succession plan data back into the staging structure.
  • LAUNCH_WF — Initiates the Oracle Workflow process for approval of the staged transaction.
  • REJECT_TRANSACTION — Handles rejection of a transaction, presumably reversing or invalidating staged changes.
  • GET_APPROVAL_REQ — Retrieves the approval requirement/status for a given transaction.
  • COMMIT_TRANSACTION / COMMIT_TXN — Commits the validated and approved transaction to the underlying HR/plan tables.
  • REFRESH_TXN — Refreshes transaction state, likely re-synchronizing workflow item status.

No parameter lists are documented, and none should be assumed.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms:

Usage Notes

PER_SP_STAGE is not referenced by any other database object, indicating it is invoked top-down rather than called by downstream packages. In practice it is triggered from the Oracle Succession Planning application forms and concurrent programs when a user stages, submits, or approves succession plan changes. The workflow routines (LAUNCH_WF, GET_APPROVAL_REQ) integrate with Oracle Workflow, meaning transaction movement is coupled to approval routing rather than executing immediately. The presence of BEN_COPY_ENTITY_RESULTS_S links this package to the copy-entity mechanism, so custom code copying succession plans may indirectly rely on it. The user's search term ben_copy_entity_results_s corresponds to a referenced synonym documented within this package's dependency list.