Search Results plsql_compile_error

Overview

APPS.ENG_ICMDB_APIS_UTIL is a utility package body that serves as a bridge between the Oracle E-Business Suite Engineering Change Management (ECM) module and the Advanced Product Catalog / Change Management (AMW) schema. Its principal business role is to allow Engineering Change Order (ECO) processing to optionally delegate the creation of change lines and the update of approval status to the AMW package AMW_CREATE_LINES_PKG, without creating a hard, compile-time dependency on that package. This is achieved through dynamic PL/SQL (EXECUTE IMMEDIATE), which means the package compiles successfully in environments where the AMW schema objects are absent, and fails gracefully at runtime if they are not installed.

The header comment ($Header: ENGUICMB.pls 120.3 2006/11/08) identifies this as a legacy utility aligned with the Engineering Change Management database APIs. Because it is classified as a UTIL object, it is not intended to be called directly by end users but rather by other ECM packages, forms, or workflow components that need a stable interface to change line creation and approval status maintenance. Users encountering a plsql_compile_error against this object are typically seeing the consequence of a missing synonym, an invalid AMW installation, or a stale invalid object in the APPS schema rather than a defect in this source itself.

Key Procedures and Functions

• CREATE_LINES — Wraps a call to amw_create_lines_pkg.create_lines using a dynamically built PL/SQL block. It accepts the change identifier as input and returns the standard FND_API three-part return status (status, message count, message data). Its purpose is to create the change lines associated with a given change. If AMW is not installed, the raised PLSQL_COMPILE_ERROR (-6550) is caught and a null success-style return is produced so the calling process can continue.
• UPDATE_APPROVAL_STATUS — Updates the approval status of a change, taking the change identifier, the base change management type code, the new approval status code, and the workflow status code as inputs, and returning the standard FND_API return status, message count, and message data. It initialises the return status to FND_API.G_RET_STS_SUCCESS and is used to synchronise ECM approval state with the workflow-driven approval lifecycle.

Both procedures follow the Oracle Application Object Library API convention of returning status through x_return_status, x_msg_count, and x_msg_data. Errors are logged through FND_MSG_PUB, and the package uses PRAGMA EXCEPTION_INIT to trap error -6550, allowing it to tolerate an uninstalled AMW schema.

Tables Accessed

The ETRM metadata does not document direct table access by this package body. All data manipulation for line creation and approval status is performed inside the dynamically invoked AMW_CREATE_LINES_PKG, not within ENG_ICMDB_APIS_UTIL itself. The package therefore holds no direct DML against ECM or AMW base tables, and it operates purely as a delegating utility. Any table dependencies will appear in the underlying AMW package rather than here.

Usage Notes

This package is invoked from within the Engineering Change Management application layer — typically from ECO form logic, ECM workflow activities, or higher-level ECM APIs that need line creation or approval status maintenance. It is referenced by at least one other package, confirming its role as a shared internal utility rather than a public API. Because it uses dynamic SQL to reach AMW, it is safe to install and compile in instances where AMW is not present; in such cases CREATE_LINES silently returns null status, and callers should not interpret that as confirmation that lines were created. When diagnosing a plsql_compile_error on this object, verify that the AMW schema and its synonym are valid, recompile all invalid dependencies such as FND_API and FND_MSG_PUB, and confirm that no stale invalid spec of AMW_CREATE_LINES_PKG is being resolved at runtime.