Search Results ra_site_uses_all

Overview

MTL_INTERCOMPANY_PARAMETERS is an Oracle Inventory (INV) table that defines and governs intercompany relationships between shipping and selling organizations within a multi-organization Oracle E-Business Suite environment. Each row establishes the operational, financial, and trading-partner defaults that Oracle uses when one inventory organization ships goods to another and an intercompany invoice, payable, or receivable must be generated. The table is central to the Oracle Inventory intercompany invoicing and intercompany transfer pricing flows supported in both 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification for this object is link. The table does not function as a standalone descriptive entity; rather it resolves the many-to-many relationships among shipping organizations, selling organizations, trading partners, customers, and transaction types. This classification is a modeling suggestion derived from the foreign key structure rather than a mandatory design decision.

Key Information Stored

The table holds 36 documented columns in the 12.2.2 physical schema. The most consequential columns are:

• SHIP_ORGANIZATION_ID — identifies the inventory organization from which goods are shipped; part of the composite primary key.
• SELL_ORGANIZATION_ID — identifies the organization that sells the goods and raises the intercompany receivable; part of the composite primary key.
• FLOW_TYPE — distinguishes the direction or nature of the intercompany flow (for example, internal or external patterns). Together with the two organization IDs, this forms the unique business key candidate MTL_INTERCOMPANY_PARAMETERS_U1.
• CUSTOMER_ID — the receivables customer that receives the intercompany invoice (FK to RA_CUSTOMERS).
• ADDRESS_ID — the ship-to or bill-to address (FK to RA_ADDRESSES_ALL).
• CUSTOMER_SITE_ID — the customer site used for the intercompany invoice (FK to RA_SITE_USES_ALL).
• CUST_TRX_TYPE_ID — the receivable transaction type applied (FK to RA_CUST_TRX_TYPES_ALL).
• VENDOR_ID and VENDOR_SITE_ID — the supplier and supplier site used for the corresponding intercompany payable (FKs to PO_VENDORS and PO_VENDOR_SITES_ALL).
• REVALUE_AVERAGE_FLAG — controls whether average cost is revalued for the transfer.
• INVENTORY_ACCRUAL_ACCOUNT_ID, EXPENSE_ACCRUAL_ACCOUNT_ID, and INTERCOMPANY_COGS_ACCOUNT_ID — the accounting flexfield combinations used to post accrual and cost-of-goods entries.
• INV_CURRENCY_CODE and FREIGHT_CODE_COMBINATION_ID — the invoice currency and freight accounting reference.

The surrogate primary key is MTL_INTERCO_PARAMETERS_PK, defined on the composite of SHIP_ORGANIZATION_ID and SELL_ORGANIZATION_ID. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE columns provide who-did-what auditing and extensibility.

Common Use Cases and Queries

The user query on ship_organization_id reflects the most frequent access path: locating the intercompany parameters configured for a given shipping organization. Typical scenarios include validating that a transfer will produce a receivable and payable, diagnosing why an intercompany invoice failed to generate, and reporting on configured trading-partner defaults across organizations.

• List all intercompany relationships for a shipping organization:
  SELECT sell_organization_id, flow_type, customer_id, cust_trx_type_id FROM mtl_intercompany_parameters WHERE ship_organization_id = :p_ship_org_id;
• Resolve the trading partner pair (both directions) for reconciliation reporting by pairing SELL_ORGANIZATION_ID with SHIP_ORGANIZATION_ID.
• Trace a specific flow by joining on FLOW_TYPE to isolate internal versus external intercompany patterns.
• Confirm the receivables transaction type in effect: join CUST_TRX_TYPE_ID to RA_CUST_TRX_TYPES_ALL.

Note the unique index on (SHIP_ORGANIZATION_ID, SELL_ORGANIZATION_ID, FLOW_TYPE), which means multiple rows can exist for the same organization pair when different flow types are configured.

Related Objects

The foreign keys documented in the ETRM metadata define the principal related objects:

• PO_VENDORS joined on VENDOR_ID — supplies the intercompany supplier.
• PO_VENDOR_SITES_ALL joined on VENDOR_SITE_ID — supplies the payable site.
• RA_CUSTOMERS joined on CUSTOMER_ID — supplies the intercompany customer.
• RA_ADDRESSES_ALL joined on ADDRESS_ID — supplies the address.
• RA_SITE_USES_ALL joined on CUSTOMER_SITE_ID — supplies the customer site.
• RA_CUST_TRX_TYPES_ALL joined on CUST_TRX_TYPE_ID — supplies the receivable transaction type.

These relationships reinforce the classification of MTL_INTERCOMPANY_PARAMETERS as a link table binding organizational, customer, and supplier master data into a single intercompany configuration record.