Results for “change_attribute”

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

Overview

SBC_CONTROLLER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under ETRM as an "OTHER" API type. Its name and header comment (ENGCSBCS.pls) identify it as part of the Engineering Change Order (ECO) subsystem within Oracle Bills of Material and Engineering. The package provides the server-side controller logic that processes user-entered component revisions captured on the ECO form and writes the corresponding change records into the engineering tables.

The package defines a global record type, Controller_SBC_Rec_Type, which the ECO form populates with the revised component controller information requiring processing. The record carries change notice identifiers, organization and item context, effectivity dates, operation sequence numbers, alternate BOM codes, substitute component details, change type and quantity fields, and the full DFF attribute range (Attribute1 through Attribute15, with Attributes 3, 7, and 11 declared after program_id). Several surrogate ID fields are also included to identify the organization, revised item, component, substitute component, bill sequence, and revised item sequence. The AUTHID CURRENT_USER clause means the package executes with the privileges of the invoking user rather than the defining schema.

Key Procedures and Functions

• VALIDATE_AND_WRITE — The principal processing entry point. It accepts a Controller_SBC_Rec_Type record plus a BOM_BO_PUB.Control_Rec_Typ control record, validates the submitted component change data, and writes the resulting change records. It is the procedure the ECO form calls to commit revised component information.
• DELETE_ROW — Removes a previously written component controller row, supporting the removal of a component change line from the ECO processing flow.
• CHANGE_ATTRIBUTE — Updates attribute values on the controller record, allowing descriptive flexfield and related attribute data to be modified or corrected after initial entry.

The ETRM metadata documents three procedures in total and does not expose additional private helpers, so the above descriptions are limited to documented scope. No parameter lists are reproduced here beyond the two inputs shown in the excerpted specification for VALIDATE_AND_WRITE.

Tables Accessed

The documented metadata lists no explicit base tables accessed via APPS synonyms, and the package is not referenced by any other documented package (referenced by 0). By function, the package serves the Engineering Change Order flow, and the record fields (Change_Notice, Revised_Item, Component_Item, Substitute_Component, effectivity dates, operation sequences, and DFF attributes) correspond to the ECO component tables such as the engineering change order component and substitute component tables that back the ECO form. The metadata excerpt confirms only the record structure; the specific insert, update, and delete targets are not enumerated in the documentation, so no table names are asserted here beyond the functional mapping implied by the record definition.

Usage Notes

SBC_CONTROLLER is invoked from the ECO (Engineering Change Order) form, which declares a revised component controller record of the documented type and passes user-entered information into the package for processing. The Control_Rec_Typ argument in VALIDATE_AND_WRITE follows the standard BOM_BO_PUB business object control convention, indicating the package participates in the same programmatic framework as other BOM engineering APIs.

Because the package is classified as "OTHER" rather than a public API, it is not intended as a general integration surface for custom code. Any direct invocation should be undertaken with caution, since it is an internal form-support package. The header revision (115.5, dated 2004) indicates the logic has been stable since early releases and continues to function in EBS 12.1.1 and 12.2.2 without documented change. The search term "C805 programming software" does not correspond to this object; it is unrelated to the EBS engineering controller functionality described above.