Search Results psb_account_position_sets_s




Overview

The package body APPS.PSB_ACCOUNT_POSITION_SET_PVT is a private PL/SQL API that implements the core create, read, update, and delete (CRUD) logic for Account Position Sets within the Oracle E-Business Suite 12.1.1 and 12.2.2 environment. Account Position Sets are a foundational construct in Oracle's Public Sector Budgeting and Enterprise Planning and Budgeting (EPB) modules; they define groupings of account positions that control how budget data is organized, extracted, and rolled up for reporting and allocation purposes.

The _PVT suffix indicates that this package is part of the private layer of Oracle's API architecture. It is not intended to be called directly by external code. Instead, it is invoked by the corresponding public API package (PSB_ACCOUNT_POSITION_SET_PUB) and by other internal EPB components that need to manipulate account position set records at a lower level, bypassing or supplementing the validation and error-handling conventions of the public layer.

Key Procedures and Functions

The package body exposes eight documented programs that together provide a complete lifecycle for account position set data:

  • INSERT_ROW — Creates a new row in the base account position set table, populating the primary key and initializing attribute values.
  • LOCK_ROW — Acquires a row-level lock on a specified account position set record, typically as a precursor to update or delete operations to ensure data consistency in concurrent environments.
  • UPDATE_ROW — Modifies existing account position set definitions, applying changes to the base and translation tables.
  • DELETE_ROW — Removes an account position set record and its associated child data, enforcing referential integrity rules.
  • CHECK_UNIQUE — Validates that the combination of key attributes for an account position set (such as name or code within a budget group) does not already exist, preventing duplicate definitions.
  • CHECK_REFERENCES — Tests whether the account position set is referenced by dependent objects (for example, position set lines or set relations) before permitting deletion.
  • COPY_POSITION_SETS — Duplicates one or more account position sets in bulk, supporting the common EPB scenario of replicating budget structures across periods or scenarios.
  • COPY_POSITION_SET — Duplicates a single account position set, including its associated line-level data.

Tables Accessed

The package performs DML and queries against several core PSB tables, accessed through APPS synonyms. The primary base table is PSB_ACCOUNT_POSITION_SETS, with language-specific text maintained in PSB_ACCOUNT_POSITION_SETS_S. Line-level composition is stored in PSB_ACCOUNT_POSITION_SET_LINES, and attribute metadata is drawn from PSB_ATTRIBUTES_VL and PSB_ATTRIBUTE_VALUES. Budget group associations are validated against PSB_BUDGET_GROUPS, while extract definitions reside in PSB_DATA_EXTRACTS. Position-level values are held in PSB_POSITION_SET_LINE_VALUES and PSB_POSITION_SET_LINE_VALUES_V. Hierarchical or cross-set relationships are managed through PSB_SET_RELATIONS.

Usage Notes

This package is invoked indirectly through the Public API wrapper and from Oracle Forms-based maintenance screens in the EPB/PSB module. Developers extending EPB should always call the _PUB package rather than this private body. Direct invocation risks bypassing message-stack handling (via FND_MSG_PUB) and exception translation supplied by APP_EXCEPTION and FND_API. The package relies on FND_GLOBAL for session context and FND_MESSAGE for user-facing error text. Custom concurrent programs that need to copy or migrate position set definitions may wrap COPY_POSITION_SETS, but only through the public interface to preserve API contract stability across the 12.1.1 and 12.2.2 upgrade paths.