Search Results pn_var_constr_defaults_s

Overview

APPS.PN_VAR_CONSTR_DEFAULTS_PKG is a PL/SQL package body in the Oracle E-Business Suite Property Manager (PN) module. Its business function is to manage the rows that define variable constraint defaults for space and property configurations. These records determine the default constraint values that are applied during property and space definition, so the package serves as the data access and validation layer behind the PN_VAR_CONSTR_DEFAULTS entity within a 12.1.1 or 12.2.2 environment. The package body is documented as VALID and is classified as an OTHER API, which indicates that it is an internal support package rather than a formally published public interface. It encapsulates the standard insert, lock, update, and delete operations for the constraint defaults tables and adds a specific validation routine for the maximum constraint setting. Because the package is owned by APPS and listed as not referenced by any database object, its entry points are normally called from Oracle Forms, from other PL/SQL packages, or from custom code rather than from database triggers.

Key Procedures and Functions

The ETRM documentation identifies five procedures or functions in the package body:

• INSERT_ROW — Creates a new variable constraint defaults record. It is the entry point used when a new default constraint configuration must be established for the relevant properties or spaces.
• LOCK_ROW — Obtains a row-level lock on an existing constraint defaults record that is about to be modified or deleted, preserving concurrency control within the Forms transaction.
• UPDATE_ROW — Modifies an existing constraint defaults record, typically after LOCK_ROW has secured the row.
• DELETE_ROW — Removes an existing constraint defaults record from the underlying tables.
• CHECK_MAX_CONSTR — Validates the maximum constraint value against the applicable business rules, returning or raising an error when the value is not permitted.

No parameter lists are published in the available metadata; the procedures should be treated as internal and invoked only in the documented sequence appropriate to the operation being performed.

Tables Accessed

The package performs DML against the APPS synonym for PN_VAR_CONSTR_DEFAULTS and the associated table PN_VAR_CONSTR_DEFAULTS_ALL. The _ALL table holds the multi-organization or translation-level rows, while PN_VAR_CONSTR_DEFAULTS holds the base records. PN_VAR_CONSTR_DEFAULTS_S is the sequence used to generate primary key values during INSERT_ROW. DUAL is referenced for single-row expressions used in validation and default handling. All access is mediated through APPS synonyms, which is the expected pattern for an APPS-owned package in an EBS 12.1.1 or 12.2.2 installation. The package also depends on standard error and message infrastructure, specifically APP_EXCEPTION, FND_MESSAGE, and PNP_DEBUG_PKG, which provide exception handling, message retrieval, and diagnostic output.

Usage Notes

PN_VAR_CONSTR_DEFAULTS_PKG is an internal package and is not referenced by any database object, so it is not invoked automatically by triggers or constraints. It is normally called from Oracle Forms when a user defines or maintains variable constraint default records in the Property Manager responsibility. Custom extensions that need to create, update, or remove constraint defaults programmatically should call the same procedures rather than issuing direct DML, so that the CHECK_MAX_CONSTR validation and any debug logging through PNP_DEBUG_PKG are applied consistently. The package is referenced by three other packages in the documented metadata, confirming its role as a shared utility layer. Because it is classified as an OTHER API rather than a public API, Oracle does not guarantee backward compatibility at the same level as published interfaces; custom code should be validated against both 12.1.1 and 12.2.2 before deployment, because the underlying seed data and table structures can differ between those releases.