Results for “max_transfer_qty”

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

Overview

MSC_SR_SOURCE_ORG is a table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the source organization definition for Sourcing Rules and Bills of Distribution, recording the organization, trading partner, or partner site from which a supply is drawn to satisfy demand. This table is populated through the ASCP data collection and planning processes, where sourcing rules and bills of distribution defined in Oracle Purchasing and Oracle Inventory are flattened into a planning-friendly structure.

Under a heuristic Data Vault classification, MSC_SR_SOURCE_ORG is modeled as a link table, because its dominant structure is a set of foreign key relationships joining sourcing rule definitions (via MSC_SR_RECEIPT_ORG) to trading partners (MSC_TRADING_PARTNERS) and trading partner sites (MSC_TRADING_PARTNER_SITES). It carries a surrogate primary key, MSC_SR_SOURCE_ORG_PK, defined on SR_SOURCE_ID, and 49 documented columns in the 12.2.2 physical schema.

Key Information Stored

The most operationally significant columns include:

• SR_SOURCE_ID — Surrogate primary key for the source organization record.
• SR_SR_SOURCE_ID — Business-key component identifying the parent sourcing rule source; paired with SR_INSTANCE_ID in unique index MSC_SR_SOURCE_ORG_N1.
• SR_INSTANCE_ID — Planning instance identifier, isolating data collected from different source systems.
• SR_RECEIPT_ID — Foreign key to MSC_SR_RECEIPT_ORG, linking the source to its associated receipt organization definition.
• SOURCE_ORGANIZATION_ID / SOURCE_ORG_INSTANCE_ID — The actual source organization and its owning instance.
• SOURCE_PARTNER_ID — Foreign key to MSC_TRADING_PARTNERS.
• SOURCE_PARTNER_SITE_ID — Foreign key to MSC_TRADING_PARTNER_SITES.
• SOURCE_TYPE — Classifies the source (for example organization, supplier, or partner).
• ALLOCATION_PERCENT and RANK — Define the split percentage and priority ordering when multiple sources satisfy a demand.
• SHIP_METHOD — Shipping method used for the transfer.
• REPLENISHMENT_TYPE and TRANSFER_TYPE — Characterize the replenishment and transfer behavior of the source.
• MIN_TRANSFER_QTY, MAX_TRANSFER_QTY, TRANSFER_LOT_MULTIPLE, and FIXED_TRANSFER_QTY — Quantity constraints applied during sourcing.
• DELETED_FLAG and COLLECTED_FLAG — Status indicators for purge and collection.
• CIRCULAR_SRC and CIRCULAR_SRC_RANK — Detect and rank circular sourcing relationships.

The unique index MSC_SR_SOURCE_ORG_U1 (SR_SOURCE_ID) enforces the surrogate key, while MSC_SR_SOURCE_ORG_N1 (SR_INSTANCE_ID, SR_SR_SOURCE_ID) provides the business-key access path.

Common Use Cases and Queries

Planners and developers query this table to trace where supply originates for a given sourcing rule or bill of distribution, to validate allocation percentages across competing sources, and to audit circular sourcing. Typical reporting includes source ranking analysis, allocation percentage reconciliation, and transfer constraint review.

• Retrieving ranked sources for a sourcing rule: SELECT SR_SOURCE_ID, SOURCE_ORGANIZATION_ID, ALLOCATION_PERCENT, RANK FROM MSC_SR_SOURCE_ORG WHERE SR_INSTANCE_ID = :instance AND SR_SR_SOURCE_ID = :rule ORDER BY RANK;
• Joining to trading partners to resolve supplier identity: SELECT s.SR_SOURCE_ID, t.PARTNER_NAME FROM MSC_SR_SOURCE_ORG s JOIN MSC_TRADING_PARTNERS t ON s.SOURCE_PARTNER_ID = t.PARTNER_ID;
• Detecting circular sourcing using the CIRCULAR_SRC flag and CIRCULAR_SRC_RANK ordering.
• Excluding purged rows with WHERE DELETED_FLAG = 'N' in planning extracts.

Related Objects

• MSC_SR_RECEIPT_ORG — joined on MSC_SR_SOURCE_ORG.SR_RECEIPT_ID; defines the receipt-side organization for the sourcing entry.
• MSC_TRADING_PARTNERS — joined on SOURCE_PARTNER_ID; resolves the partner supplying the source.
• MSC_TRADING_PARTNER_SITES — joined on SOURCE_PARTNER_SITE_ID; resolves the specific partner site.
• Sourcing rule and bill of distribution definition tables in Purchasing and Inventory — the upstream source of collected data.
• ASCP planning engine and collection programs — consume this table during plan generation and sourcing allocation.

Together these objects support the complete sourcing topology used by ASCP to allocate supply against demand across organizations, partners, and sites.