Results for “eng_default_change_line”

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

Overview

The APPS.ENG_DEFAULT_CHANGE_LINE package is an Engineering Change Order (ECO) utility within the Oracle E-Business Suite Engineering module. Its function is to apply defaulting rules to change line records so that mandatory and derived attribute values are systematically populated when engineering change lines are created or modified. In the Oracle EBS data model, engineering change lines reside in the ENG_CHANGE_LINES_S table and represent the individual item, component, or operation records affected by an engineering change order. Because users frequently create change lines without supplying every attribute, the application relies on defaulting logic to fill in values drawn from related entities, seeded system defaults, and user-defined attribute defaults. The package also exposes a population routine that ensures null columns are populated before a change line is committed, preserving data integrity and preventing downstream processes from encountering incomplete rows. The package is classified as an OTHER API, meaning it is proprietary Oracle code rather than a published interface intended for external callers, although it is invoked internally throughout the Engineering transaction flow.

Key Procedures and Functions

Three documented program units are exposed by the package:

• ATTRIBUTE_DEFAULTING — Applies default values to the attribute columns of a change line, deriving values from user-defined attribute defaulting setup and from related engineering entities. It is the routine that resolves value sets and flexfield defaults for change line attributes.
• POPULATE_NULL_COLUMNS — Scans a change line record for columns that remain null after entry and populate them with appropriate defaults, ensuring the row is complete before it is written to ENG_CHANGE_LINES_S.
• ENTITY_DEFAULTING — Performs defaulting at the entity level, propagating values from the parent engineering change order or related item/component context onto the change line so that the line inherits consistent attributes.

No published parameter lists or return signatures are documented in the ETRM metadata; the procedures should be treated as internal program units whose signatures are not guaranteed for public use.

Tables Accessed

The package operates against ENG_CHANGE_LINES_S, the base table and sequence-backed entity for engineering change lines. Defaulting routines read the current line attributes and write the populated values back into the same structure. The use of the _S suffix indicates the table pairs with a sequence and typically has a corresponding _TL or view layer used by the Engineering forms, so changes applied by this package become visible to the change line user interface and to subsequent processing. By centralizing defaulting and null-column population against this single table, the package guarantees that any code path creating a change line produces a consistently populated record.

Usage Notes

Because ENG_DEFAULT_CHANGE_LINE is a private Oracle package (API classification OTHER), it is invoked indirectly rather than by customer code. The Engineering Change Order forms and the surrounding ECO transaction logic call it during change line creation and update to default attributes and backfill null columns. The dependency metadata identifies ENG_ECO_PVT and ENG_ECO_PUB as related API packages, and ENG_DEFAULT_CHANGE_LINE is referenced by one other package, ENG_ECO_PVT, which coordinates the broader engineering change workflow. The package also depends on FND_ERROR_HANDLER/ERROR_HANDLER and the SYS STANDARD package, indicating that errors raised during defaulting are passed through the standard error-handling mechanism. Consultants and developers should not call this package directly in customizations; instead they should use the supported public APIs in ENG_ECO_PUB. When troubleshooting defaulting or incomplete change line data, this package is a primary diagnostic target, and any modification to its logic must be carried out through Oracle-supported patching in both 12.1.1 and 12.2.2 environments.