Results for “wip_supply_type”

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

Overview

BOM_VALIDATE is a PL/SQL validation package owned by the APPS schema in Oracle E-Business Suite. It provides a centralized library of boolean and string validation functions used by the Oracle Bills of Material and Enterprise Asset Management (EAM) modules. Rather than embedding validation logic directly into forms, concurrent programs, or other packages, Oracle consolidates these checks into BOM_VALIDATE so that identical validation rules are applied consistently across every entry point that creates or maintains bill of material, alternate, and work in process supply data.

The package header (BOMSVATS.pls) carries a revision history that begins with initial creation in July 1999 by Rahul Chitko, followed by EAM-related changes in May 2001 and the addition of the IS_PREFERRED_STRUCTURE function in May 2004. This history reflects the package's evolution from a pure BOM validation utility into a shared validation layer supporting both discrete manufacturing and asset-intensive EAM flows.

Key Procedures and Functions

• ALTERNATE_DESIGNATOR — Validates that a supplied alternate BOM designator code is legitimate for a given organization. It confirms that the alternate designator exists and is usable within the specified inventory organization.
• END_ITEM_UNIT_NUMBER — Validates an end item unit number against a revised item. It returns an error text through its output parameter when validation fails, supporting EAM and unit-effective BOM scenarios.
• WIP_SUPPLY_TYPE — Validates a work in process supply type value, ensuring the supply type supplied is recognized and permissible before it is used in a WIP or BOM context.
• ASSET_GROUP_SERIAL_NUMBER — Validates a serial number for an asset group assembly within an organization. This function supports EAM asset group processing by confirming that the serial number is valid for the specified assembly.
• IS_PREFERRED_STRUCTURE — Determines whether a given assembly and alternate BOM code combination represents the preferred structure for the organization. It returns a string result and an error text, allowing callers to branch on whether the structure is preferred.
• OBJECT_EXISTS — A generic utility that returns whether a named database object of a given object type exists. It is used for existence checks prior to performing operations against optional objects.

Tables Accessed

The package reads from several tables through APPS synonyms. BOM_ALTERNATE_DESIGNATORS is queried to validate alternate designator codes. MTL_SERIAL_NUMBERS supports serial number validation for asset groups. PJM_UNIT_NUMBERS provides the unit number data used by END_ITEM_UNIT_NUMBER. ALL_OBJECTS is used by OBJECT_EXISTS to confirm object existence, and DUAL is used for simple scalar evaluations. The documented metadata indicates read-oriented validation rather than transactional writes.

Usage Notes

BOM_VALIDATE is typically invoked from Oracle BOM and EAM forms, from concurrent programs performing BOM and asset validation, and from custom PL/SQL packages that need to enforce the same rules Oracle applies internally. The metadata notes that five other packages reference this package, confirming it functions as a shared dependency. Developers extending BOM or EAM functionality should call these functions rather than reimplementing validation, because the package centralizes the supported rules for a given release. Callers should be prepared to handle the boolean return values and the error text output parameters that several functions provide. Because the package is owned by APPS and marked as OTHER in the API classification, it is not a formally published public API; custom code referencing it should be regression-tested against target release levels such as 12.1.1 and 12.2.2.