Search Results bom_resources_s

Overview

APPS.BOM_RESOURCES_PKG is a server-side PL/SQL package body within the Oracle E-Business Suite Bills of Material (BOM) module. Its documented purpose is to encapsulate the core database maintenance logic for the BOM_RESOURCES entity, the table that stores the machinery, labor, and outside-processing resources assignable to a bill of material routing. The package provides the programmatic interface used to insert, lock, and update resource records while enforcing referential and business validation rules, most notably uniqueness of resource codes per organization and the validity of the unit of measure assigned to a resource.

The object is owned by the APPS schema and carries a status of VALID in both the 12.1.1 and 12.2.2 code lines. Because the package body is a private implementation vehicle, it is not itself referenced by any other database object; instead, it is invoked directly by Oracle Forms and by dependent application logic that maintains BOM resources.

Key Procedures and Functions

• INSERT_ROW — Creates a new row in the resources table, applying defaulting and validation before the physical insert.
• LOCK_ROW — Obtains a row-level lock on an existing resource record, typically invoked when a form initiates an update to prevent concurrent modification.
• UPDATE_ROW — Applies changes to an existing resource record after validation, writing the modified attributes back to the base table.
• CHECK_UNIQUE — Verifies that the resource code (or the relevant key combination) does not already exist, enforcing uniqueness within the organization.
• GET_UOM_FROM_GL_SETS_OF_BOOKS — Derives a default or valid unit of measure from the chart of accounts / set of books context, used during resource creation.
• CHECK_VALID_UOM — Confirms that a supplied unit of measure is valid by validating it against the units-of-measure table.

The metadata documents nine procedures and functions in total; the list above covers the principal documented entries. Parameter lists are not reproduced here and should be derived from the package specification (BOM_RESOURCES_PKG) rather than the body.

Tables Accessed

• BOM_RESOURCES — The primary transactional table holding resource definitions, rates, and capacity attributes. Read and written by the insert, update, and lock routines.
• BOM_RESOURCES_S — The corresponding sequence/identifier table used to generate or store surrogate keys; this is the object commonly referenced when users search for "bom_resources_s" or "BOM_RESOURCES_PKG".
• MTL_UNITS_OF_MEASURE — Validates that the unit of measure associated with a resource exists and is active.
• GL_SETS_OF_BOOKS — Supplies the accounting context used to resolve default units of measure.
• ORG_ORGANIZATION_DEFINITIONS — Provides organization-level context and validation for the resource's owning organization.
• DUAL — Used for single-row arithmetic and lookups such as identifier retrieval.
• APP_EXCEPTION and FND_MESSAGE — Support error raising and user-facing message retrieval.

Usage Notes

BOM_RESOURCES_PKG is invoked indirectly through the Bills of Material setup forms where resources are defined for a routing, and through any custom or concurrent logic that programmatically maintains resource records. The package is not referenced by other database packages in the ETRM dependency listing, confirming that it is a leaf-level maintenance API rather than a shared utility. When extending or troubleshooting resource maintenance, developers should call the documented procedures rather than issuing direct DML against BOM_RESOURCES, so that the uniqueness and UOM validations enforced by CHECK_UNIQUE and CHECK_VALID_UOM are applied consistently. The specification package BOM_RESOURCES_PKG should be consulted for exact signatures, while this body confirms the implementation and its dependencies.