Search Results eng_eco_prior_pkg




Overview
Explore in AI Chat

Overview

ENG_ECO_PRIOR_PKG is a validation utility package within the Oracle E-Business Suite Engineering (ENG) module, owned by the APPS schema and defined with AUTHID CURRENT_USER. Its business function is to enforce data integrity for Engineering Change Order (ECO) priorities — the configurable ranking codes that determine the relative urgency or sequencing of engineering change orders processed through the Engineering Change Management (ECM) workflow. Rather than exposing a broad public API, the package provides a narrow pair of validation routines that guard the ENG_CHANGE_PRIORITIES setup data and the foreign-key relationships that depend on it. The header comment ($Header: engpecps.pls 115.2 2003/02/07) indicates the package has been stable in the codebase since at least Release 11i and remains shipped, essentially unchanged, into 12.1.1 and 12.2.2. The package contains no persistent state, no transactional DML of its own, and no outbound dependencies on other custom packages; it is a pure validation helper invoked before inserts, updates, or deletes against priority definitions.

Key Procedures and Functions

  • CHECK_UNIQUE — Validates that a given priority code is unique within an operating unit. It accepts an organization identifier and a priority code, and is intended to be called before inserting or updating a row in the priorities table so that duplicate priority codes are rejected before the database constraint is violated. The procedure is used to produce a user-friendly validation outcome in the calling form or program rather than relying solely on a unique index violation.
  • CHECK_REFERENCES — Validates whether a priority code is already referenced by dependent records, typically before a delete or a redefinition is permitted. By taking the organization identifier and priority code, it allows the caller to determine whether the priority is in use and therefore must not be removed. This protects referential integrity between priority definitions and the engineering changes that consume them.

Both procedures return no documented OUT parameters; validation outcomes are surfaced through the standard Oracle EBS exception or message-handling conventions used by the calling layer. Consistent with the ETRM classification of OTHER, this package is not a public, supported integration API and should be treated as an internal utility.

Tables Accessed

  • ENG_CHANGE_PRIORITIES — The primary reference table holding ECO priority definitions per organization. CHECK_UNIQUE queries it to detect existing codes, and CHECK_REFERENCES queries it to confirm the requested priority exists in the caller's organization context.
  • ENG_ENGINEERING_CHANGES — The engineering change order header table, which stores the priority assigned to each change. CHECK_REFERENCES examines it to determine whether any ECO currently references the priority code, thereby preventing deletion of an in-use priority.
  • DUAL — Used for single-row PL/SQL evaluations and lightweight existence checks where no table join is required, a common pattern in this generation of validation packages.

Usage Notes

ENG_ECO_PRIOR_PKG is invoked indirectly through the Engineering Change Management setup and maintenance flows — most typically from the Oracle Forms-based priority definition window when a user creates, modifies, or deletes an ECO priority, and from any concurrent or batch load that maintains the priorities table. Because the package is not classified as a public API and is referenced by zero other packages in the documented dependency graph, custom integrations should avoid calling it directly; instead, perform equivalent queries against ENG_CHANGE_PRIORITIES and ENG_ENGINEERING_CHANGES using the standard APPS synonyms. Where custom code must reproduce this behavior, note that both procedures require the organization identifier (X_Org_id) so that validation respects multi-org partitioning. The package is identical in 12.1.1 and 12.2.2; the 12.2 online-patching architecture does not alter its behavior, and no editioning or AD_ZD-based customization should be applied to it.