Search Results eco_error_handler




Overview
Explore in AI Chat

Overview

ECO_ERROR_HANDLER is an Oracle EBS Engineering (ENG) module PL/SQL package body owned by the APPS schema. Its primary business function is to centralize error collection, message buffering, and status propagation for Engineering Change Order (ECO) processing. The package operates against the public ENG and BOM package structures that carry ECO and BOM revision data, and it maintains a global error table (G_ERROR_TABLE of type Error_Handler.Error_Tbl_Type) along with message counters (G_Msg_Index, G_Msg_Count) that accumulate diagnostic messages during a transaction.

The package header comment identifies an internal procedure, setSubComponents, which updates the status of reference designator records based on a revised item key, revised component key, or reference designator key. This is directly relevant to the search term revised_item_name: the package declares a package-level global, G_REVISED_ITEM_TBL of type Eng_Eco_Pub.Revised_Item_Tbl_Type, which holds the revised item rows (including the revised item identity/name) collected during ECO validation and processing. Error conditions that arise while processing a revised item are routed into the error table using the revised item index as part of the error scope, so callers can correlate a message back to the specific revised item.

The source header shows a baseline version of 120.1 dated 2006, with later additions for Engineering Change lines (g_change_line_tbl), routing revisions (g_rev_operation_tbl, g_rev_op_resource_tbl, g_rev_sub_resource_tbl), and reference designators (g_ref_designator_tbl). These globals make the package a shared scratchpad for the ECO validation flow rather than a standalone API.

Key Procedures and Functions

  • LOG_ERROR — The single documented public procedure. It records an error entry into the package's error table, capturing the message text, status, and error scope, and updates the internal message counters (G_Msg_Index, G_Msg_Count). It is the mechanism by which ECO validation failures and BOM revision conflicts are surfaced to the calling program.
  • setSubComponents — An unexposed (private) procedure referenced in the source. It sets reference designator record status to an "other status" value by locating rows through the revised item index, revised component index, or reference designator index; if no key is supplied, all related records are updated.

Tables Accessed

The documented table referenced through an APPS synonym is PLITBLM (PL/SQL Interpreter / temporary message storage), used by the error handler to buffer and manage messages generated during a run. The package also works extensively with the in-memory PL/SQL record types from Eng_Eco_Pub and Bom_Bo_Pub (Eco_Rec_Type, Eco_Revision_tbl_Type, Revised_Item_Tbl_Type, Rev_Component_Tbl_Type, Sub_Component_Tbl_Type), which mirror the underlying BOM and ECO base tables but are not directly named as database tables in the metadata.

Usage Notes

ECO_ERROR_HANDLER is not typically invoked directly by end users. It is called from Engineering Change Order forms, ECO validation and approval concurrent programs, and from custom extensions that invoke the ENG ECO public APIs. The metadata records that it is referenced by seven other packages, confirming its role as a low-level utility in the ECO/BOM processing chain.

Because the package relies on package-global state (the record tables and message counters), it must be used within a single session and is not suited to parallel or multi-threaded execution. Custom code should call LOG_ERROR during ECO processing to collect diagnostics, then inspect the accumulated error table to decide whether to abort or continue. Applications built on 12.1.1 and 12.2.2 should treat this package as an internal implementation detail and prefer the supported ENG ECO and BOM public APIs for new development.