Search Results process_eco

Overview

APPS.ENG_FORM_ECO_PVT is a private PL/SQL package within the Oracle E-Business Suite Engineering (ENG) module. It functions as the form-level private API layer that supports Engineering Change Order (ECO) processing initiated from the Oracle Engineering forms. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the package owner, which is standard practice for private APIs in the EBS application schema.

The package exists to receive the user-entered ECO data from the form layer and marshal it into the public API structures defined by ENG_Eco_PUB and supporting packages such as BOM_BO_PUB and BOM_RTG_PUB. Its header documentation explicitly identifies ENG_Eco_PUB as the public counterpart against which the private package is validated, and the compiled output references the public package body for error reporting. The package therefore occupies the boundary between the Oracle Forms user interface and the public ECO business logic.

Key Procedures and Functions

The ETRM metadata for release 12.2.2 documents two procedures in this package.

• PROCESS_ECO — The primary entry point for submitting an Engineering Change Order for processing. It accepts the standard EBS API return status and message count parameters, together with a control record from BOM_BO_PUB and an extensive set of ECO, revision, component, reference designator, sub-component, and routing records. These parameters correspond to the unexposed and table-based record types declared in ENG_Eco_PUB, BOM_BO_PUB, and BOM_RTG_PUB. The procedure validates and forwards the assembled ECO definition to the public processing logic, returning status information to the caller. This is the procedure most commonly associated with the "process_eco" search term.
• LOCK_ECO — A supporting procedure that locks the ECO record prior to processing, ensuring that concurrent form sessions cannot modify the same ECO simultaneously. This is consistent with standard EBS locking conventions used to protect against lost updates during multi-step form transactions.

No parameter-level details beyond the documented header excerpt should be assumed; callers must consult the actual package specification for exact signatures.

Tables Accessed

The package references the following tables through APPS synonyms:

• ENG_REVISED_ITEMS — Stores the revised item information associated with an ECO, including the item revisions generated or affected by the change. This is central to the ECO processing workflow.
• BOM_OPERATION_SEQUENCES — Holds routing operation sequence data. Its presence confirms that ECO processing extends to routing and operation revisions, consistent with the routing record parameters accepted by PROCESS_ECO.
• PLITBLM — A PL/SQL index-by table used internally by the EBS APIs, typically for message handling and error stack management. It is not an application data table but supports the API's error reporting infrastructure.

Usage Notes

ENG_FORM_ECO_PVT is a private package and is not intended for direct invocation by customers or third-party code. It is invoked primarily from the Oracle Engineering forms during ECO entry and submission, where the form coordinates user input and passes the assembled records down to the private layer. The package is referenced by nine other packages in the EBS schema, which reflects its role in the internal call graph surrounding ECO processing.

Because the procedures rely on parameter structures owned by ENG_Eco_PUB and related public packages, any extension or troubleshooting work should target the public APIs (ENG_Eco_PUB) rather than this private layer. The header also notes the historical source revision (115.9, dated 2003), indicating the interface has been stable across the 12.1.1 and 12.2.2 releases and that the documented procedures remain the authoritative entry points for form-driven ECO processing.