Search Results bom_inventory_components_s




Overview
Explore in AI Chat

Overview

WSMPCOGI is an Oracle Application Object Library (APPS) schema PL/SQL package body classified under the ETRM API taxonomy as OTHER. It belongs to the Work in Process/Work Order Management domain, as indicated by the WSM prefix shared with the WSM_CO_PRODUCTS table, an entity associated with co-product and by-product definitions in discrete and process manufacturing. The package's principal business purpose is to resolve and return the identity of component sequence records held in Oracle Bills of Material, specifically the surrogate and business keys used to relate a component to its parent bill. In Oracle EBS 12.1.1 and 12.2.2, components of a bill of materials are stored in the intersection table BOM_INVENTORY_COMPONENTS, with the public view BOM_INVENTORY_COMPONENTS_S exposing the same logical columns in a versioned and language-independent form. WSMPCOGI encapsulates the lookup logic needed to correlate a co-product or by-product process definition against the underlying inventory component structure without requiring callers to hard-code join conditions. The package body is documented as VALID in the APPS schema and is not referenced by any other database object, indicating it is a terminal dependency invoked from outside the PL/SQL dependency graph.

Key Procedures and Functions

The ETRM metadata documents a total of five program units within the package body. Only two are named in the supplied excerpt, and the remainder are not disclosed by the metadata.

  • NAME — A program unit whose identifier suggests retrieval of a descriptive or display name associated with a component or co-product record. In EBS component-resolution packages, such a routine typically returns the concatenated or user-facing name used in forms and reports where a numeric identifier would be meaningless to the operator.
  • GET_COMPONENT_SEQUENCE_ID — The core lookup routine of the package. Its name states its purpose directly: to return the component sequence identifier for a given component relationship. In BOM_INVENTORY_COMPONENTS, COMPONENT_SEQUENCE_ID is the primary key surrogate that uniquely identifies each component row within a bill. Callers use this value to reach the specific component record for subsequent update, inquiry, or explosion operations.

No parameter lists are documented in the available metadata, and none are inferred here. The remaining three program units of the five reported are private or helper routines whose signatures are not exposed in the published excerpt.

Tables Accessed

The package references the following objects through APPS synonyms, which is the standard access pattern for EBS application code.

  • BOM_INVENTORY_COMPONENTS_S — The versioned view over the bill of materials component intersection table. This is the primary source of component sequence information and the table most directly implicated in the GET_COMPONENT_SEQUENCE_ID routine. Note that the package also references the base table BOM_INVENTORY_COMPONENTS directly per the ETRM dependency listing, so both the base table and its view participate in the package's queries.
  • BOM_BILL_OF_MATERIALS — The parent bill header table, referenced to establish the bill context under which a component is defined and to validate that the component belongs to the expected bill structure.
  • MTL_SYSTEM_ITEMS_KFV — The key flexfield view over the item master. It supplies the concatenated item number, description, and flexfield segments used to present component identity in human-readable form, most likely inside the NAME routine.
  • WSM_CO_PRODUCTS — The co-product definition table. Its presence confirms that WSMPCOGI is used to tie process manufacturing co-product and by-product definitions back to their corresponding BOM component records, a required linkage when co-products are modeled as bill components in Oracle Process Manufacturing and discrete co-product flows.
  • SYS.DUAL — Used for single-row selection and PL/SQL expression evaluation.

Usage Notes

WSMPCOGI is a supporting utility rather than a public API. It is not referenced by any database object, which means no trigger, view, or other package depends on it; invocation therefore originates outside the database, typically from Oracle Forms or OA Framework pages that maintain co-product and bill component data, from concurrent programs that populate or reconcile component structures, or from customer-written extensions. Because the ETRM classification is OTHER rather than a designated public API, Oracle does not guarantee interface stability across releases, and custom code should avoid direct dependency on this package where an equivalent documented public API exists. Application developers integrating with component sequence logic are instead directed to the standard Bills of Material public APIs. The package is valid in both 12.1.1 and 12.2.2; the 12.2.2 ETRM record confirms the same dependency set, so no behavioral divergence between the two releases is indicated by the available metadata.