Search Results bom_cto_model_orgs




Overview

BOM_CTO_MODEL_ORGS is a Bills of Material (BOM) module table in the Oracle E-Business Suite that supports Configure-to-Order (CTO) model definition and organization-level configuration processing. It stores the association between a configuration model item and the organizations in which that model may be built, costed, or sourced. In Oracle EBS 12.1.1 and 12.2.2, this table is central to the model/organization mapping used by the CTO and ATO (Assemble-to-Order) flows, enabling the same model item to behave differently across inventory organizations with respect to bill creation, sourcing rule creation, and cost rollup behavior.

The ETRM metadata classifies this object heuristically as standalone under the Data Vault classification scheme. In practice, it can be modeled as a link-like bridge between a model item and an organization, since it carries the relationships between configuration/group references and organization identifiers. The table resides in the BOM schema and is documented with 20 physical columns.

Key Information Stored

The primary key of the table is the unique index BOM_CTO_MODEL_ORGS_U1, defined on the REFERENCE_ID column. REFERENCE_ID is the surrogate identifier for each row; the documentation lists no additional unique business-key indexes beyond this one, so there is no documented natural-key constraint and the model-item/organization pairing is not enforced as a single unique business key by the schema as documented.

The most significant columns include:

  • REFERENCE_ID — Surrogate primary key from BOM_CTO_MODEL_ORGS_U1.
  • GROUP_REFERENCE_ID — Groups related model-organization rows, typically used to tie configuration or model group processing together.
  • CONFIG_ITEM_ID — The configuration item to which the organization mapping applies.
  • MODEL_ITEM_ID — The CTO model item being mapped into an organization.
  • ORGANIZATION_ID — The inventory organization associated with the model.
  • ORGANIZATION_TYPE — Distinguishes the organization context (for example, shipping versus manufacturing classification).
  • RCV_ORG_ID — Receiving organization reference used when the model is sourced or received.
  • COST_ROLLUP — Controls whether cost rollup is performed for the model in that organization.
  • CREATE_BOM — Indicates whether a bill of material should be created for the model in the organization.
  • CREATE_SRC_RULES — Controls whether sourcing rules are generated for the model/organization combination.
  • RANK — Priority sequence applied when multiple organization mappings exist.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit context for the run that created or updated the row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying which organizations have a given CTO model enabled, determining whether BOM creation or sourcing rule generation is active for a model, and auditing cost rollup flags across organizations. A representative query joins the table to organization and item master views:

  • SELECT m.MODEL_ITEM_ID, m.ORGANIZATION_ID, m.CREATE_BOM, m.CREATE_SRC_RULES FROM BOM.BOM_CTO_MODEL_ORGS m WHERE m.MODEL_ITEM_ID = :p_model_item_id;
  • Filtering by GROUP_REFERENCE_ID to retrieve all organization rows generated by the same processing group.
  • Joining ORGANIZATION_ID to ORG_ORGANIZATION_DEFINITIONS or HR_ALL_ORGANIZATION_UNITS for organization names.
  • Joining MODEL_ITEM_ID to MTL_SYSTEM_ITEMS_B for item descriptions and segment values.
  • Auditing rows by REQUEST_ID to trace concurrent program output for model organization generation.

Related Objects

Because the ETRM metadata classifies this table as standalone, no foreign key relationships are documented to external tables. The most frequently referenced related objects in practice are: