Results for “bill_sequence_id”

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

Overview

APPS.BOM_VAL_TO_ID is a PL/SQL package body in the Oracle E-Business Suite Applications schema that supports the Oracle Bills of Material (BOM) product family. Its central business function is the translation of value-based identifiers into their corresponding internal numeric identifiers within the BOM data model. In Oracle EBS Release 12.1.1 and 12.2.2, the BOM schema retains legacy surrogate keys (numeric IDs) while increasingly exposing unique and value-based identifiers through the user interface and public APIs. This package bridges that gap by resolving textual or value-form inputs — organization codes, bill sequence values, revision identifiers, component values, reference designators, and routing operation references — into the primary keys used by the underlying BOM tables.

The package is classified as a supporting (OTHER) API rather than a public interface. It is not referenced by any database object and instead functions as a utility layer invoked by other BOM packages, forms, and custom extensions. Its dependency list confirms a close relationship with BOM_BO_PUB, BOM_GLOBALS, FND_API, ERROR_HANDLER, and INVPUOPI, indicating that it participates in the standard BOM validation and error-handling framework.

Key Procedures and Functions

The documented interface exposes 22 procedures and functions, largely arranged as paired conversions. The core conversion routines include:

• ORGANIZATION — resolves an organization value to its internal organization identifier for use in BOM queries.
• BILL_SEQUENCE_ID — converts a bill sequence value into the corresponding bill sequence identifier.
• BOM_HEADER_VID — returns the header value identifier for a bill of materials.
• BOM_HEADER_UUI_TO_UI — maps a BOM header unique identifier to its internal unique identifier.
• BOM_REVISION_UUI_TO_UI2 — maps a revision unique identifier to the internal revision identifier.
• BOM_COMPONENT_VID, BOM_COMPONENT_UUI_TO_UI, and BOM_COMPONENT_UUI_TO_UI2 — resolve component value identifiers and unique identifiers to internal component identifiers.
• REV_COMPONENT_VID, REV_COMPONENT_UUI_TO_UI, and REV_COMPONENT_UUI_TO_UI2 — perform the equivalent resolution for revision-specific component records.
• SUB_COMPONENT_UUI_TO_UI and SUB_COMPONENT_UUI_TO_UI2 — resolve sub-component unique identifiers to internal identifiers.
• REF_DESIGNATOR_UUI_TO_UI and REF_DESIGNATOR_UUI_TO_UI2 — convert reference designator unique identifiers to internal identifiers.
• COMP_OPERATION_SEQ_ID and BOM_COMP_OPERATION_UUI_TO_UI / BOM_COMP_OPERATION_UUI_TO_UI2 — resolve component operation and operation sequence references to internal operation identifiers.

The paired "2" variants typically accommodate a secondary or alternate key context, such as revision-aware lookups, without altering the calling convention.

Tables Accessed

The package reads from the principal BOM and inventory tables through APPS synonyms. BOM_BILL_OF_MATERIALS and BOM_INVENTORY_COMPONENTS provide the header and component records whose identifiers are being resolved. BOM_ALTERNATE_DESIGNATORS and BOM_STRUCTURE_TYPES_B supply alternate and structure type context. BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, and BOM_COMPONENT_OPERATIONS support routing and operation sequence resolution. MTL_SYSTEM_ITEMS_KFV and MTL_PARAMETERS provide item and organization validation context, while MTL_ITEM_LOCATIONS_KFV supports location resolution relevant to component placement. PO_VENDORS and MFG_LOOKUPS supply vendor and lookup validation, and PLITBLM is used for PL/SQL table handling within the package.

Usage Notes

BOM_VAL_TO_ID is normally invoked indirectly. It is referenced by six other packages, which call its conversion routines before performing inserts, updates, or validations on BOM structures. Typical invocation paths include the Bill of Materials and Engineering forms, BOM-related concurrent programs, and the public BOM APIs (BOM_BO_PUB). Custom code extending BOM functionality may call these routines directly when accepting value-based input from external systems and requiring internal identifiers. Because the package is an internal utility, Oracle does not guarantee its interface as a public API; developers should prefer documented public BOM APIs where available and treat BOM_VAL_TO_ID conversions as implementation details subject to change across releases.