Search Results get_message_count

Overview

APPS.ENG_INVOKE_ECO_BO is a business object wrapper package body within the Oracle E-Business Suite Engineering (ENG) module. Its name — "Invoke ECO Business Object" — reflects its primary role: providing a programmatic entry point through which callers can submit an Engineering Change Order (ECO) for processing against the engineering and Bills of Material data model. The package sits above the public ECO API layer (ENG_Eco_PUB) and the BOM and routing public APIs, orchestrating the flow of all the entity collections that together constitute a complete ECO transaction.

The package header is an intelligent wrapper designed to accept the full range of ECO-related tables — header, revisions, change lines, revised items, revised components, reference designators, sub-components, revised operations, operation resources, and sub-resources — thereby allowing a single call to carry an entire engineering change across the product structure and routing. The $Header comment indicates the source file is ENGBIVKB.pls, last shipped at version 115.6 in 2003, which places this object in the long-lived engineering API family that has remained stable across the 11i, 12.1.1, and 12.2.2 releases.

Key Procedures and Functions

ETRM documents 12 procedures and functions in this package. The central procedure is PROCESS_ECO, which accepts the ECO record and all associated detail tables as input, invokes the underlying validation and persistence logic, and returns the processed collections along with a standard API return status and message count. It uses the canonical EBS API signature conventions: an API version number defaulting to 1.0, an optional message-list initialization flag, NOCOPY OUT parameters for performance, and G_MISS_* default record values that signal "not applicable" to the API layer.

The remaining documented procedures form the standard message-handling and lifecycle support set common to EBS business object packages:

• INITIALIZE — establishes package-level state before a processing call.
• RESET — clears accumulated state so the package can be reused.
• APPS_INITIALIZE — sets the Oracle Applications session context (user, responsibility, application) required for FND-based operations.
• GET_MESSAGE_LIST — returns the full list of messages generated during processing.
• GET_MESSAGE — retrieves an individual message by index.
• GET_ENTITY_MESSAGE — retrieves messages associated with a specific entity instance.
• GET_MESSAGE_COUNT — returns the number of messages currently held in the list.
• DELETE_MESSAGE — removes a message from the list.
• DUMP_MESSAGE_LIST — emits the message list for debugging or logging.

Tables Accessed

The ETRM metadata excerpt does not enumerate the concrete base tables behind the referenced APPS synonyms. Functionally, the package operates on the engineering and manufacturing structures represented by its parameter types: ECO header and revision data (ENG_ECO_HEADERS, ENG_ECO_REVISIONS and related change objects), revised item and component structures (ENG_REVISED_ITEMS, ENG_REVISED_COMPONENTS), reference designators, and routing operations and resources from the BOM routing API family. It reads and writes these structures indirectly through ENG_Eco_PUB, BOM_BO_PUB, and BOM_RTG_PUB rather than issuing direct DML, which preserves the validation, versioning, and audit behavior enforced by those APIs.

Usage Notes

ENG_INVOKE_ECO_BO is typically invoked from Oracle Forms within the Engineering module, from concurrent programs, or from custom PL/SQL that needs to create or revise an ECO without reimplementing the ECO business object logic. Because ETRM records no other packages referencing it, it functions as a terminal, public-facing wrapper rather than a dependency of other shipped code. Callers should always check x_return_status for success, warning, or error, then drain the message list via GET_MESSAGE_COUNT and GET_MESSAGE to surface diagnostics. When the user searches for "eng_eco_pub.process_eco(", the relevant entry points are the underlying public API ENG_Eco_PUB and this business object wrapper, whose PROCESS_ECO procedure forms the supported invocation path for full ECO transactions in 12.1.1 and 12.2.2.