Search Results eng_engineering_changes_s

Overview

The APPS.ENG_DEFAULT_ECO package body is a PL/SQL utility within the Oracle E-Business Suite engineering (ENG) module. Its principal business function is to supply defaulting logic for Engineering Change Orders (ECOs), ensuring that when an engineering change record is created or modified, mandatory attributes and entity relationships are populated consistently without requiring manual entry. The package operates inside the Oracle EBS application programming interface framework, evidenced by its dependencies on FND_API, FND_MSG_PUB, and ERROR_HANDLER, and by its classification as an "OTHER" API type in the 12.2.2 ETRM metadata. Because the object is documented as VALID and is referenced by two other packages, it functions as a supporting defaulting service rather than a standalone entry point. It is not referenced by any database object per the dependency extract, confirming that it sits at the top of the dependency chain and is invoked by client-side or other PL/SQL callers.

Key Procedures and Functions

Three documented procedures comprise the package's public interface:

• ATTRIBUTE_DEFAULTING — Applies default values to individual attributes of an engineering change order. This procedure resolves column-level defaults, drawing on profile option settings through FND_PROFILE and on organization-specific context.
• ENTITY_DEFAULTING — Handles defaulting at the entity level, establishing the relationships the ECO should carry, such as the applicable change type, lifecycle status, priority, and organization hierarchy context. It coordinates with ENG_CHANGE_STATUSES_VL, ENG_LIFECYCLE_STATUSES, and ENG_TYPE_ORG_HIERARCHIES to derive valid values.
• POPULATE_NULL_COLUMNS — Fills null columns on the ECO record after initial insert or during update processing, guaranteeing that no required field remains unset before the record is committed.

Parameter lists are not exposed in the available metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• ENG_ENGINEERING_CHANGES_S — The primary ECO intersection/base table holding engineering change header data; the defaulting procedures populate and validate its columns. This is the object the user's search term eng_engineering_changes_s most closely relates to.
• ENG_CHANGE_PRIORITIES and ENG_CHANGE_TYPE_PRIORITIES — Supply valid priority values based on change type.
• ENG_LIFECYCLE_STATUSES and ENG_CHANGE_STATUSES_VL — Provide the status values that govern ECO progression and visibility.
• ENG_REVISED_ITEMS — Links the ECO to the items under revision, supporting entity defaulting.
• ENG_TYPE_ORG_HIERARCHIES and PER_ORGANIZATION_STRUCTURES — Resolve the organizational scope of the change.
• DUAL — Used for scalar evaluations within PL/SQL logic.

Additional dependencies include ENG_ECO_PUB, BOM_BO_PUB, and ENG_GLOBALS, which provide public API and global constant support.

Usage Notes

ENG_DEFAULT_ECO is typically invoked indirectly by the Engineering Change Order forms, the ECO creation workflow, and other PL/SQL packages that need to instantiate or seed an engineering change record. Because it is referenced by two other packages and is not referenced by any database object, callers include application-tier API code and custom extensions that create ECOs programmatically. Implementers extending ECO defaulting behavior should call the documented procedures rather than inserting directly into ENG_ENGINEERING_CHANGES_S, since POPULATE_NULL_COLUMNS and the defaulting routines enforce the validation and message-handling conventions of FND_API. No direct form binding to this package is documented; invocation is through the ECO API layer.