Results for “bom_cto_src_orgs_b”

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

Overview

BOM_CTO_SRC_ORGS_B is a Bills of Material (BOM) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas, owned by the BOM schema and documented as VALID. It belongs to the Configure-to-Order (CTO) area of Bills of Material, which governs how models, option classes, and configuration items are exploded and sourced across organizations during order fulfillment and manufacturing. This table stores the organization-level sourcing definition records associated with CTO structures, capturing which receiving or supplying organizations are eligible to source a given configuration or model line, together with the flags that control whether Bills of Material or sourcing rules are generated for that combination.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning the foreign-key structure did not surface a strong dependency on a single parent hub. A practitioner designing a warehouse layer may therefore treat BOM_CTO_SRC_ORGS_B as a candidate satellite or reference table attached to a model/configuration hub, rather than as a pure link between two hubs. This is a modeling suggestion only; the transactional semantics of the CTO sourcing process should be validated against the application before committing to a Data Vault construct.

Key Information Stored

The table carries 21 documented columns. Its surrogate primary key is defined by the unique index BOM_CTO_SRC_ORGS_B_U1, which spans four columns: LINE_ID, ORGANIZATION_ID, RCV_ORG_ID, and ORGANIZATION_TYPE. Because the unique index itself is the composite of those four attributes, the primary key is effectively a business composite rather than a single generated sequence, and those four columns are simultaneously the primary key and the principal business-key candidates.

• LINE_ID — Identifier of the CTO model or configuration line to which the sourcing definition applies.
• ORGANIZATION_ID — The inventory organization that owns or defines the sourcing record.
• RCV_ORG_ID — The receiving or sourcing organization eligible to supply the line; this is the counterpart organization in the sourcing relationship.
• ORGANIZATION_TYPE — Discriminator indicating the category of the organization entry (for example, sourcing versus receiving role).
• CONFIG_ITEM_ID — The configuration item associated with the record.
• MODEL_ITEM_ID — The parent model item for the configuration.
• TOP_MODEL_LINE_ID — The top-level model line, used to trace the record back through the configuration hierarchy.
• RANK — Ordering or priority value applied when multiple sourcing organizations exist for the same line.
• CREATE_BOM — Flag indicating whether a Bill of Material should be created for the organization combination.
• CREATE_SRC_RULES — Flag indicating whether sourcing rules should be generated for the organization combination.
• COST_ROLLUP — Indicator controlling whether the combination participates in cost rollup processing.
• GROUP_REFERENCE_ID — Grouping identifier used to associate related sourcing records.

The remaining documented columns are standard EBS audit and concurrent-program attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The table is primarily queried during CTO order sourcing, model explosion, and sourcing-rule generation. Reporting use cases include identifying which organizations are eligible to source a configured item, auditing where Bills of Material creation was suppressed, and reconciling sourcing rules against BOM setup.

• Retrieve all sourcing organizations for a specific CTO line, ordered by priority: SELECT rcv_org_id, organization_type, rank FROM bom.bom_cto_src_orgs_b WHERE line_id = :p_line_id AND organization_id = :p_org_id ORDER BY rank;
• List lines where BOM creation is enabled but sourcing rules are not: SELECT line_id, config_item_id, model_item_id FROM bom.bom_cto_src_orgs_b WHERE create_bom = 'Y' AND create_src_rules = 'N';
• Trace a configuration back to its top model line for reporting: SELECT DISTINCT top_model_line_id, model_item_id FROM bom.bom_cto_src_orgs_b WHERE config_item_id = :p_config_item_id;
• Audit concurrent program activity affecting the table using REQUEST_ID and PROGRAM_ID when investigating mass sourcing changes.

Related Objects

The documented FK structure is heuristic and standalone, so the relationships below are the principal functional joins an implementer should expect. Confirm each against the live 12.1.1 or 12.2.2 data dictionary before hard-coding.

• BOM_BILL_OF_MATERIALS — Joined via LINE_ID and ORGANIZATION_ID to obtain the bill structure that the sourcing record governs.
• BOM_INVENTORY_COMPONENTS — Joined on LINE_ID to resolve component detail for a CTO line.
• MTL_SYSTEM_ITEMS_B — Joins CONFIG_ITEM_ID, MODEL_ITEM_ID, and the organization sourcing columns to item master attributes.
• MTL_PARAMETERS — Supplies organization context for ORGANIZATION_ID and RCV_ORG_ID.
• BOM_SOURCING_RULES — Related when CREATE_SRC_RULES is set, since sourcing rules are generated from these records.
• MRP_SOURCING_RULES — Consumed downstream when sourcing rules flow into planning.
• FND_CONCURRENT_REQUESTS — Joins REQUEST_ID for audit of the program that populated or updated rows.