Search Results get_resource_code

Overview

APPS.BOM_SUB_RESOURCES_PKG is a server-side PL/SQL package that encapsulates the data manipulation logic for substitute (substitute-group) resources attached to routing operations in Oracle Bills of Material. Within Oracle E-Business Suite, a primary resource on an operation may be replaced by one or more alternate resources grouped under a substitute group number; the table BOM_SUB_OPERATION_RESOURCES stores these alternate resource assignments, including their usage rates, scheduling flags, offset percentages, and descriptive flexfield attributes. This package provides the standard API surface for creating, locking, updating, and deleting such rows, and for validating the business rules that govern them. It is classified in ETRM as an OTHER API, meaning it is a supporting data-maintenance package rather than a public, workflow-oriented interface such as an open interface or a business event publisher. Its header signature indicates a build lineage of BOMSRESB.pls, version 120.2, last shipped in the 12.x release family.

Key Procedures and Functions

The documented procedure set comprises nine callable units, of which six are explicitly enumerated: INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW, CHECK_UNIQUE_LINK, and VALIDATE_SCHEDULE_FLAG.

• INSERT_ROW — Inserts a new row into BOM_SUB_OPERATION_RESOURCES. The documented signature accepts the operation sequence identifier, substitute group number, resource identifier, schedule sequence number, replacement group number, activity identifier, standard rate flag, assigned units, usage rate or amount and its inverse, basis type, schedule flag, the standard WHO audit columns (last update date/by/login, creation date/by), resource offset percent, autocharge type, principle flag, and the fifteen attribute columns plus attribute category.
• LOCK_ROW — Acquires a row-level lock on the target substitute resource record, typically used to serialize concurrent modifications before an update or delete.
• UPDATE_ROW — Modifies the attributes of an existing substitute resource row, preserving the audit columns appropriately.
• DELETE_ROW — Removes a substitute resource assignment from BOM_SUB_OPERATION_RESOURCES.
• CHECK_UNIQUE_LINK — Enforces the uniqueness constraint on a substitute resource link, preventing duplicate combinations of operation sequence, substitute group, and resource.
• VALIDATE_SCHEDULE_FLAG — Validates the schedule flag value against the permitted domain before the record is persisted.

Tables Accessed

The package references tables through APPS synonyms. Its principal write target is BOM_SUB_OPERATION_RESOURCES, the substitute resource detail table. Validation and lookups draw on BOM_OPERATION_RESOURCES (primary operation resource assignments), BOM_OPERATION_SEQUENCES (routing operations), BOM_RESOURCES (resource definitions), BOM_DEPARTMENT_RESOURCES (resource-to-department associations), BOM_SETUP_TYPES (setup type codes), BOM_OPERATION_NETWORKS (operation network relationships), CST_ACTIVITIES (costing activity identifiers used by the activity column), ENG_REVISED_OPERATIONS (engineering revised operation references), and DUAL for single-row SELECT expressions.

Usage Notes

BOM_SUB_RESOURCES_PKG is normally invoked indirectly. The Oracle Bills of Material routing and substitute-resource maintenance forms (for example, the Substitute Resources window reached from the Routings form) call these procedures to persist user entries, relying on CHECK_UNIQUE_LINK and VALIDATE_SCHEDULE_FLAG to enforce integrity before the INSERT_ROW, UPDATE_ROW, or DELETE_ROW action is issued. No concurrent program or published business event is documented as a direct consumer, and ETRM records zero dependent packages, indicating that custom extensions invoking it do so at their own risk against an unsupported, internal API. Custom code that must manipulate substitute operation resources should prefer supported interfaces; where this package is used, callers must supply every mandatory column, including the WHO audit fields, and should wrap calls in an explicit transaction with appropriate error handling. The "get_resource_code" search term maps conceptually to the RESOURCE_ID column maintained here and resolved through BOM_RESOURCES; a dedicated getter is not part of the documented procedure list.