Search Results entity_defaulting




Overview

ENG_DEFAULT_ECO is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Engineering Change Order (ECO) business flow within Oracle Engineering. Its principal responsibility is to apply defaulting logic to ECO records as they are created, copied, or validated through the public ECO APIs. The package is declared AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking user and resolves unqualified object references against that user's schema, while relying on APPS synonyms for the underlying Engineering tables.

The package header, shipped as ENGDECOS.pls version 120.0.12010000.1, exposes three procedures. These procedures operate directly on the public record types ENG_Eco_PUB.Eco_Rec_Type and ENG_Eco_PUB.Eco_unexposed_Rec_Type, which are the standard structures passed between the Engineering public APIs and their callers. This design makes ENG_DEFAULT_ECO a supporting component of the ECO public API layer rather than a standalone application program. In the context of the search term "attribute_defaulting," the package is the implementation vehicle through which ECO attributes receive their default values before persistence.

Key Procedures and Functions

  • Attribute_Defaulting — Accepts the incoming ECO record and unexposed record, applies default values to ECO attributes, and returns the modified records along with a return status and message token table. This is the procedure most directly associated with the "attribute_defaulting" search, and it is the entry point for populating attribute-level defaults such as change type, priority, and lifecycle-related values.
  • Entity_Defaulting — Accepts the incoming and prior (old) versions of the ECO and unexposed records plus an optional control record defaulted from BOM_BO_PUB.G_DEFAULT_CONTROL_REC. It computes entity-level defaults by comparing new and existing values and returns the updated records, return status, and message tokens.
  • Populate_NULL_Columns — Accepts incoming and prior ECO and unexposed records and fills NULL columns on the outgoing records. This ensures that fields not explicitly supplied by the caller are populated with meaningful values before the ECO is written.

All three procedures use NOCOPY for both IN OUT and OUT parameters, which is standard practice in EBS public API support packages to avoid unnecessary copying of large PL/SQL records. Error communication is standardized through Error_Handler.Mesg_Token_Tbl_Type, allowing calling APIs to surface user-friendly messages.

Tables Accessed

The documented table references reflect the defaulting sources consulted by this package:

Usage Notes

ENG_DEFAULT_ECO is not typically invoked directly by end users. It is called internally by the Engineering ECO public APIs and by forms and concurrent programs that create or update ECOs. The metadata notes that the package is referenced by two other packages, confirming its role as a shared defaulting utility within the Engineering module. Custom code that must replicate ECO creation behavior should invoke the public ECO APIs, which in turn drive these defaulting procedures, rather than calling ENG_DEFAULT_ECO procedures directly; direct calls bypass the surrounding validation and control-record handling performed by the API layer. Because the package executes AUTHID CURRENT_USER, callers must have appropriate grants on the referenced tables and on the public record type definitions.