Search Results mtl_intercompany_parameters_u1




Overview

MTL_INTERCOMPANY_PARAMETERS is an Oracle Inventory (INV) seed table that stores the relationship parameters and default accounting/party attributes for inter-company transactions between two operating units. It is the authoritative configuration source that drives internal sales order flows, intercompany invoicing, and the automatic generation of Receivables and Payables transactions. For a given shipping organization and selling organization pair, the table defines the customer and customer site used by the shipping organization for AR invoicing, and the supplier and supplier site used by the selling organization for AP invoicing. It also carries the default account identifiers used for freight, inventory accrual, expense accrual, and intercompany cost of goods sold, along with a currency code and revaluation flag.

The table resides in the APPS_TS_SEED tablespace, denoting seed/reference configuration data. The ETRM documentation classifies it heuristically as a link object in Data Vault modeling terms, which is appropriate: the table resolves relationships among organizations (shipping and selling), customers, suppliers, and accounts rather than capturing descriptive history for a single entity. The primary-key constraint MTL_INTERCO_PARAMETERS_PK is defined over (SHIP_ORGANIZATION_ID, SELL_ORGANIZATION_ID).

Key Information Stored

The most significant columns are:

The surrogate primary key is the composite (SHIP_ORGANIZATION_ID, SELL_ORGANIZATION_ID). The unique business-key candidate is documented separately as MTL_INTERCOMPANY_PARAMETERS_U1 over (SHIP_ORGANIZATION_ID, SELL_ORGANIZATION_ID, FLOW_TYPE), which enforces that only one parameter set exists per organization pair per flow type. Standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) are also present, together with a Descriptive Flexfield structure column (ATTRIBUTE_CATEGORY) and fifteen attribute segments.

Common Use Cases and Queries

Typical scenarios include validating that every shipping/selling organization pair has complete invoicing and accounting defaults before enabling intercompany flows, and reporting the accounts used in intercompany cost rolls.

  • Retrieve all parameters for a given organization pair:
    SELECT ship_organization_id, sell_organization_id, flow_type, customer_id, vendor_id FROM mtl_intercompany_parameters WHERE ship_organization_id = :ship AND sell_organization_id = :sell;
  • Detect missing or incomplete configuration (e.g., null customer or supplier) for auditing.
  • Report account assignments: INTERCOMPANY_COGS_ACCOUNT_ID, INVENTORY_ACCRUAL_ACCOUNT_ID, EXPENSE_ACCRUAL_ACCOUNT_ID by organization pair.
  • Identify all flows for a shipping organization to understand downstream AR/AP setups.

Related Objects

The table references master data in several modules through documented foreign keys, supporting join-based reporting:

Accounting account identifiers (FREIGHT_CODE_COMBINATION_ID, INVENTORY_ACCRUAL_ACCOUNT_ID, EXPENSE_ACCRUAL_ACCOUNT_ID, INTERCOMPANY_COGS_ACCOUNT_ID) resolve to GL_CODE_COMBINATIONS. Organization identifiers resolve to HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS for the shipping and selling operating units.