Results for “process_eco”

48 results




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

Overview

ENG_ECO_PUB is the public PL/SQL API supplied by Oracle Engineering (product code ENG) for creating and updating Engineering Change Orders (ECOs) within Oracle E-Business Suite. Its display name in the ETRM repository is "Create or Update Change," and it is classified as a public (PUB) API with an active lifecycle and a compatibility rating of S (supported). The package addresses the requirement to process a single business object per call, where a business object is defined as one Change ENG header together with all of its child entities — revisions, revised items, components, reference designators, substitute components, operations, and operation resources. All entities belonging to a business object must pertain to the same Change.

The header comment block documents that every business object entity must carry a transaction type, and that the only valid transaction types are Create and Update. The package performs integrity checking and validation through its processing routine; when validation succeeds, the base production tables are populated. When validation fails, the interface tables are populated with appropriate error messages instead, allowing the caller to diagnose and correct the payload.

Key Procedures and Functions

  • PROCESS_ECO — The single documented entry point for the package. It drives validation and integrity checking of the supplied ECO business object and then either writes the validated data to the base production tables (on success) or writes error information to the interface tables (on failure). The package also declares the Eco_Rec_Type record structure, which carries the ECO header attributes: change name and number details, organization code, description, status, priority and reason codes, engineering and manufacturing implementation costs, requestor, cancellation comments, and the descriptive flexfield attribute category and attribute columns. This record forms the payload that callers populate before invoking PROCESS_ECO.

Tables Accessed

  • ENG_ENGINEERING_CHANGES — The primary base table holding engineering change order headers; the target for validated Create and Update transactions.
  • ENG_CHANGE_ORDER_TYPES and ENG_CHANGE_ORDER_TYPES_TL — Change order type definitions and their translated names, consulted to validate the type associated with the incoming change.
  • ENG_AUTO_NUMBER_ECN — Supports automatic numbering of engineering change notices when the change notice number is system-generated rather than supplied.
  • PLITBLM — A generic EBS message/error table used during validation and error reporting.

Usage Notes

ENG_ECO_PUB is a supported public API and is referenced by 33 other packages within the applications schema, indicating broad internal reuse across Engineering and adjacent modules. It is the appropriate integration point for external or custom code that must programmatically create or update engineering change orders rather than entering them through the Engineering Change Order form. Callers should populate the Eco_Rec_Type structure and the associated child entity collections, assign a valid transaction type (Create or Update) to every entity, and invoke PROCESS_ECO. Because the package routes failed validations to interface tables with error messages, integration code should inspect those tables after each call to confirm that the production tables were actually updated.