Search Results eng_change_lines_s

Overview

ENG_DEFAULT_CHANGE_LINE is an Oracle Applications (APPS) PL/SQL package body in the Oracle E-Business Suite engineering schema. Its business purpose is to apply defaulting logic to Engineering Change Order (ECO) change lines during the creation and maintenance of engineering change orders managed by Oracle Engineering. Defaulting ensures that mandatory and derived attributes on a change line are populated consistently without requiring users to enter every value manually, preserving data integrity across the ECO lifecycle.

The package is classified as an OTHER API in the ETRM metadata for releases 12.1.1 and 12.2.2. It is a currently VALID object owned by APPS, confirming that it is a supported, active component rather than an obsolete artifact. It is not referenced by any other database object, indicating that it functions as a terminal utility package invoked directly rather than as a shared library consumed by additional PL/SQL units.

Key Procedures and Functions

The documented package exposes three procedures, each addressing a distinct layer of the defaulting process:

• ATTRIBUTE_DEFAULTING — Applies default values to individual change line attributes. This is the granular defaulting routine used to populate specific column values that the user has not supplied, typically drawn from system defaults, item attributes, or user profile options.
• POPULATE_NULL_COLUMNS — Scans a change line record for null columns and fills any remaining gaps. This acts as a fallback pass, ensuring that every required field receives a value before the record is committed.
• ENTITY_DEFAULTING — Performs defaulting at the entity level, coordinating the overall defaulting sequence for the ENG_CHANGE_LINES entity as a whole rather than on individual attributes.

Together these procedures implement a layered strategy: entity-level defaulting establishes context, attribute-level defaulting assigns specific values, and null-column population guarantees completeness. Parameter lists are not documented in the available metadata and should be confirmed against the deployed source in the target environment.

Tables Accessed

The single documented table reference is ENG_CHANGE_LINES_S, accessed through an APPS synonym. This is the base table for Engineering Change Order change lines, which stores the individual line entries associated with an ECO header. ENG_DEFAULT_CHANGE_LINE reads from and writes to this table as part of the defaulting operations, using the change line identifier to locate and update the relevant rows.

Because the package depends on ENG_CHANGE_LINES_S rather than the _TL or other related views, its operations are confined to the transactional change line records themselves. Note that the user's originating search term, "eng_change_lines_s", corresponds directly to this table, indicating that the package is commonly encountered while researching how change line records are populated.

Usage Notes

ENG_DEFAULT_CHANGE_LINE is typically invoked indirectly through the Oracle Engineering forms and the ECO application programming interfaces when a user creates or modifies a change line. The dependency list shows that the package builds upon ENG_ECO_PUB, the public ECO API, along with foundational utilities FND_API, ERROR_HANDLER, BOM_GLOBALS, and the standard DUAL and STANDARD constructs. This dependency on FND_API and ERROR_HANDLER indicates that the package follows Oracle's standard API conventions, including message-based error propagation rather than unhandled exceptions.

Because the package is not referenced by any other database object, customizations should call it directly only when deliberately extending ECO defaulting behavior. Standard practice is to let the Oracle Engineering forms and ENG_ECO_PUB drive defaulting automatically, and to treat this package as internal infrastructure. The dependency on BOM_GLOBALS further suggests that BOM profile and global settings influence the default values applied. Any modification should be evaluated against the supported 12.1.1 and 12.2.2 code lines, and the VALID status should be re-verified after patches or upgrades.