Results for “g_atch_level”

6 results




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

Overview

APPS.ECO_ERROR_HANDLER is a PL/SQL package belonging to the Oracle Engineering (ENG) module of Oracle E-Business Suite. Its business function is to provide a centralized, reusable error logging and status-tracking mechanism for the Engineering Change Order (ECO) processing stack and its associated bill of materials objects. Engineering change management in EBS involves multi-level parent/child structures — an ECO header, revisions, revised items, components, reference designators, sub-components, routing operations, resources, and substitute items. Each of these levels can encounter validation, warning, unexpected, error, or fatal conditions during processing. ECO_ERROR_HANDLER standardizes how those conditions are captured, categorized, and reported so that calling packages do not each invent their own error-capture logic.

The package constants reveal the design intent directly. Level constants (G_BO_LEVEL through G_ATCH_LEVEL, including ECO, revision, revised item, component, reference designator, routing operation, resource, substitute, class, and attachment levels) identify which object in the ECO hierarchy the error relates to. Status constants (G_STATUS_WARNING = 'W', G_STATUS_UNEXPECTED = 'U', G_STATUS_ERROR = 'E', G_STATUS_FATAL = 'F', G_STATUS_NOT_PICKED = 'N') classify severity. Scope constants (G_SCOPE_ALL, G_SCOPE_RECORD, G_SCOPE_SIBLINGS, G_SCOPE_CHILDREN) determine how far an error condition propagates through the affected structure. The package header notes the package name as 'Error_Handler'. The header header string references ENGBOEHS.pls, confirming it is part of the Engineering Business Object Error Handling family, and the annotated comments ("Added by MK on 08/23/2000", "Added by MK on 08/13/2002") document its incremental extension over time.

Key Procedures and Functions

The ETRM metadata documents three procedures/functions in total, with LOG_ERROR identified as the primary externally callable routine:

  • LOG_ERROR — The core error logging entry point. It accepts ECO-related records and collections (ECO record, ECO revision table, revised item table, revised component table, reference designator table, and sub-component table, among others) so that a single call can register an error against one or more levels of the ECO structure simultaneously. It records the level, status, and scope of the condition so downstream processing or UI layers can present or act upon it. The procedure preserves default-value semantics via the G_MISS_* package constants from ENG_ECO_PUB and BOM_BO_PUB, meaning callers may supply only the record types relevant to the current error.
  • Additional documented procedures — ETRM records three documented procedures/functions in this package; the excerpt exposes LOG_ERROR in detail. The remaining routines are internal/logging helpers that support the same error-handling contract (level, status, and scope bookkeeping).

No parameter lists are reproduced beyond the documented signature excerpt; names and purposes above reflect only what ETRM exposes.

Tables Accessed

ETRM documents the package as referencing the table PLITBLM (via APPS synonyms). PLITBLM is a standard EBS message-table style object used to hold log/error text. ECO_ERROR_HANDLER uses it as the persistence target for messages accumulated through LOG_ERROR, keeping error text queryable and reportable rather than trapping it only in memory. No other application tables are documented for this package, which is consistent with its role as a handler that delegates business validation to other engineering packages and simply records outcomes.

Usage Notes

ECO_ERROR_HANDLER is referenced by seven other packages, confirming it is a shared utility rather than a top-level entry point. It is normally invoked from within engineering change processing code — the ECO Business Object packages and their routing/component counterparts — whenever a validation or processing step produces a warning, unexpected result, error, or fatal condition. Typical callers are the ECO, revision, revised item, component, reference designator, operation, resource, and substitute-item processing layers that need to attach a message to a specific record, its siblings, or its children. Customizations that extend ECO or BOM processing should call LOG_ERROR rather than writing directly to PLITBLM, thereby preserving consistent severity and scope semantics. Because the package is not a concurrent program or form-level API, it is invoked programmatically in backend PL/SQL, batch processing, and API-driven ECO workflows; any user-visible error reporting is expected to read the logged entries rather than call the handler directly. The search token "00000QW MK" does not correspond to a documented routine in this metadata; it is most likely an incidental identifier or internal reference rather than an API name.