Search Results bom_cto_src_orgs_u1
Overview
BOM_CTO_SRC_ORGS is a configuration-to-order (CTO) reference table within the Oracle Bills of Material (BOM) module. Its name reflects its purpose: identifying the source organizations from which a configured item's components may be sourced during order fulfillment and assembly. In an Oracle EBS 12.1.1 or 12.2.2 environment, the table supports the sourcing rules that underpin Configure-to-Order manufacturing, allowing a single model or option class to draw components from more than one inventory or receiving organization.
The ETRM metadata documents this object with a primary key named BOM_CTO_SRC_ORGS_U1, composed of the columns LINE_ID, ORGANIZATION_ID, and RCV_ORG_ID. The metadata also notes that the object is "Not implemented in this database," indicating that in the specific environment sampled, no physical instance of the table was present. Its heuristic Data Vault classification is standalone, meaning the mined foreign-key structure revealed no outgoing relationships to other tables. As a modeling suggestion, this object would most naturally be treated as a hub-like entity whose business key is the composite of line, owning organization, and receiving organization, rather than as a link or satellite.
Key Information Stored
The documented metadata names exactly three columns, all of which participate in the unique primary key BOM_CTO_SRC_ORGS_U1. Because the primary key is composite, none of these columns is a single-column surrogate identifier; together they form the business key that guarantees uniqueness of each sourcing relationship.
- LINE_ID — A line-level identifier that distinguishes individual sourcing records. In CTO contexts, line identifiers typically correspond to a row within a sourcing definition or bill line, allowing multiple source organizations to be associated with one logical line.
- ORGANIZATION_ID — The inventory organization that owns or defines the sourcing relationship. This is the context organization in which the configured item is manufactured or planned.
- RCV_ORG_ID — The receiving (source) organization from which components are supplied. This column establishes the actual cross-organization sourcing direction.
The combination of LINE_ID, ORGANIZATION_ID, and RCV_ORG_ID enforces that a given line cannot source from the same receiving organization more than once within an owning organization. No additional columns are documented in the ETRM metadata, so no surrogate key or alternate unique index should be assumed beyond BOM_CTO_SRC_ORGS_U1.
Common Use Cases and Queries
The table is consulted during CTO order entry and manufacturing release, when the system resolves which organization should supply components for a configured assembly. Typical reporting and validation scenarios include auditing multi-organization sourcing setups, detecting duplicate or orphaned sourcing lines, and confirming that a configured model can be built in every organization in which it is orderable.
A representative query retrieves all source organizations defined for a given owning organization:
SELECT line_id, organization_id, rcv_org_id FROM bom_cto_src_orgs WHERE organization_id = :org_id ORDER BY line_id, rcv_org_id;- Uniqueness verification:
SELECT line_id, organization_id, rcv_org_id, COUNT(*) FROM bom_cto_src_orgs GROUP BY line_id, organization_id, rcv_org_id HAVING COUNT(*) > 1; - Cross-organization coverage:
SELECT DISTINCT rcv_org_id FROM bom_cto_src_orgs WHERE organization_id = :org_id;
Because the metadata classifies the object as standalone, joins to other tables must be inferred through shared organization and line identifiers rather than through documented foreign keys. Queries should therefore be validated against the specific environment before being relied upon in production reporting.
Related Objects
The ETRM metadata provides no foreign-key relationships for BOM_CTO_SRC_ORGS; the Data Vault classification of "standalone" confirms that no outgoing references were mined. Consequently, related objects must be identified through logical, shared-column association rather than documented constraints. The most significant objects that reference or depend on this data include:
- BOM_BILL_OF_MATERIALS — Owns bill headers that the sourcing lines ultimately support, joined via ORGANIZATION_ID.
- BOM_STRUCTURES_B — Defines assembly structures for configured items, associated through ORGANIZATION_ID.
- MTL_PARAMETERS — Supplies the master organization context for both ORGANIZATION_ID and RCV_ORG_ID.
- ORG_ORGANIZATION_DEFINITIONS — Resolves organization names and codes for the numeric organization identifiers.
- BOM_CTO_ORDER_LINES — Logical companion object carrying CTO order lines that may reference sourced configurations.
- MRP_SOURCING_RULES — Sourcing rules that operate alongside CTO source organization definitions.
Each of these joins is inferred from shared organization and line semantics, since no formal referential constraints are documented for BOM_CTO_SRC_ORGS.
-
Table: BOM_CTO_SRC_ORGS
12.1.1
product: BOM - Bills of Material , description: BOM_CTO_SRC_ORGS , implementation_dba_data: Not implemented in this database ,
-
Table: BOM_CTO_SRC_ORGS
12.2.2
product: BOM - Bills of Material , description: BOM_CTO_SRC_ORGS , implementation_dba_data: Not implemented in this database ,