Results for “add_row”

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

Overview

PSP_ENC_END_DATES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite and is associated with the Oracle Enterprise Tax and Reporting Management (ETRM) product family, indicated by the PSP application prefix. The package provides the programmatic interface for maintaining encapsulation end date records held in the PSP_ENC_END_DATES table. These records govern the effective dating and period-end boundaries applied to encapsulated or consolidated reporting entities, and they determine the default organization flag, effectivity window, and descriptive attributes that drive downstream ETRM processing. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the definer, which is consistent with the standard Oracle Forms-based table handler pattern. Its source header records a version history traceable to release 11.5.x of the E-Business Suite (115.9), with the Enhancement bug 2259310 introducing the X_PREV_ENC_END_DATE parameter to support tracking of the prior encapsulation end date. The package remains a documented component in ETRM 12.2.2.

Key Procedures and Functions

The package exposes five documented procedures, following the conventional DML handler naming used throughout Oracle EBS generated table APIs:

• INSERT_ROW — Creates a new encapsulation end date record. It accepts the primary key identifier, business group, set of books, and organization context, together with the period end date, effectivity start and end dates, default organization flag, comments, and the full set of DFF attribute columns. It also supports a mode parameter and the X_PREV_ENC_END_DATE value introduced by bug 2259310.
• LOCK_ROW — Acquires a pessimistic lock on an existing row by re-querying the row using the supplied column values, ensuring that concurrent users cannot modify the same record during a form-based update.
• UPDATE_ROW — Modifies an existing encapsulation end date record, applying changes to the period end date, effectivity dates, default organization flag, comments, and attribute columns while maintaining row identity.
• ADD_ROW — Provides the combined insert-or-update handler commonly invoked from a form’s post-insert or commit logic, dispatching to the appropriate row operation based on the current record state.
• DELETE_ROW — Removes an encapsulation end date record identified by its primary key.

Tables Accessed

The package reads and writes a single documented base table, PSP_ENC_END_DATES, accessed through an APPS synonym. This table stores the encapsulation end date definitions, including the set of books, organization, period end date, effectivity range, default organization indicator, comments, and DFF attributes. All insert, lock, update, and delete operations performed by the package target this table. No other packages are documented as referencing PSP_ENC_END_DATES_PKG, so its role is confined to direct DML on this entity rather than serving as a shared API dependency.

Usage Notes

Because the package follows the standard Oracle EBS row handler signature, it is typically invoked from the ETRM setup or maintenance form associated with encapsulation end dates, where the form’s block-level triggers call INSERT_ROW, LOCK_ROW, UPDATE_ROW, and DELETE_ROW on user actions. The ADD_ROW procedure is generally called during the commit cycle to reconcile pending inserts and updates. Custom integrations that need to create or maintain encapsulation end date definitions can call these procedures directly, but should observe the AUTHID CURRENT_USER behavior and ensure the calling schema holds appropriate privileges on PSP_ENC_END_DATES and its synonym. Because the effectivity and default organization columns affect period-end and consolidation behavior, changes should normally be made through the supported form or a validated concurrent process rather than by direct DML, and the X_PREV_ENC_END_DATE parameter should be populated when prior encapsulation end dates require preservation for reporting continuity.