Results for “psb_ws_position_cr_lines_i_pvt”

12 results




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

Overview

PSB_WS_POSITION_CR_LINES_I_PVT is an Oracle Application Object Library (APPS) PL/SQL package belonging to the Public Sector Budgeting (PSB) module of Oracle E-Business Suite. The "PVT" classification designates it as a private (internal) API package, indicating that it is intended for consumption by other PSB packages rather than being invoked directly by external or customer-facing code. In Oracle EBS 12.1.1 and 12.2.2, the PSB module supports position-based and account-based budgeting and control, and this package operates as the low-level insertion engine for change request (CR) position lines.

The package encapsulates the DML logic needed to persist individual position change request lines and their associated parent structures. Its naming convention—PSB_WS_POSITION_CR_LINES_I_PVT—reflects its role within the PSB "WS" (worksheet) family of packages, with "_I_" denoting the insertion of change request lines. Because it is a private package, it exists to centralize and reuse row-level insert operations across the PSB change request workflow, ensuring consistent validation, attribute defaulting, and referential integrity when position budget change requests are created or propagated.

Key Procedures and Functions

The ETRM metadata documents three public procedures or functions within this package:

  • INSERT_ROW — The core insertion routine. It writes a single change request line record, applying the standard PSB attribute set and managing surrogate key generation and audit columns. This is the foundational operation on which the other two procedures depend.
  • ADD_PARENT_POSITION_LINE — Creates a parent position-level change request line, establishing the hierarchical linkage between a parent position and its child lines within the change request structure.
  • ADD_PARENT_ACCOUNT_LINE — Creates a parent account-level change request line, associating the change request structure with the corresponding account dimension for budget and control purposes.

Together, these routines build the change request line hierarchy: an account-level parent, a position-level parent, and the individual line rows themselves. The package does not expose documented parameter lists in the ETRM excerpt, and none should be assumed.

Tables Accessed

The ETRM metadata for this object does not enumerate specific table references. Based on the documented dependencies and the package's functional role, it operates against the PSB change request position and account line tables (the PSB_WS_POSITION_CR_LINES family and related PSB budget structures), writing new rows to persist position and account change request lines. The absence of explicit table entries in the metadata indicates that the object's table usage is mediated through APPS synonyms or internal package calls rather than direct, statically declared references in the documented excerpt.

Usage Notes

Because PSB_WS_POSITION_CR_LINES_I_PVT is a private API, it is not designed for direct invocation from forms, concurrent programs, or custom code. The documented dependency list shows that it is referenced by exactly one other package, PSB_HR_POPULATE_DATA_PVT, which is the principal caller; that package in turn drives its execution during PSB data population and change request processing. The package itself references the standard Oracle APIs FND_API and STANDARD, confirming that it follows the EBS API programming model (with error handling and standard return conventions).

In practice, the package is invoked during PSB position change request creation and worksheet processing, when parent account and position lines must be established before child lines can be attached. Customers and implementers working in 12.1.1 or 12.2.2 should treat this object as internal infrastructure: customization or extension should target the public PSB APIs and the calling package PSB_HR_POPULATE_DATA_PVT rather than this private implementation. Because it is marked VALID in ETRM, the package is a supported, compiled component of the standard PSB schema.