Search Results ship_organization_id

Overview

The MTL_INTERCOMPANY_PARAMETERS table is a core data object within the Oracle E-Business Suite (EBS) Inventory (INV) module. It serves as the master repository for defining and storing inter-company relationships between different legal entities or operating units within an enterprise. Its primary role is to facilitate and control the transactional flow of goods and services between internal organizations, enabling processes like inter-company sales and transfers. By establishing these critical linkages, the table ensures that internal transactions are properly accounted for, generating the necessary purchase orders, sales orders, and invoices in the respective systems of the involved entities.

Key Information Stored

The table's structure centers on mapping a shipping organization to a selling organization and then defining the associated trading partner entities. The primary key is a composite of SHIP_ORGANIZATION_ID and SELL_ORGANIZATION_ID, enforcing unique relationships. For each defined relationship, the table stores foreign key references to the corresponding external trading partners in other modules. Key columns include VENDOR_ID and VENDOR_SITE_ID (from PO_VENDORS and PO_VENDOR_SITES_ALL), which represent the buying company from the selling organization's perspective. Conversely, CUSTOMER_ID, ADDRESS_ID, and CUSTOMER_SITE_ID (from RA_CUSTOMERS, RA_ADDRESSES_ALL, and RA_SITE_USES_ALL) represent the selling company from the shipping organization's perspective. The CUST_TRX_TYPE_ID column links to the specific transaction type in Receivables used for invoicing these internal transactions.

Common Use Cases and Queries

This table is essential for any process involving an inter-company transfer order or sale. A common reporting use case is to list all configured inter-company relationships for audit or setup verification. A typical query would join to organization and trading partner tables to present a readable summary:

• SELECT ship_org.organization_code ship_org, sell_org.organization_code sell_org, pv.vendor_name, pvs.vendor_site_code, rc.customer_name FROM mtl_intercompany_parameters mip, hr_operating_units ship_org, hr_operating_units sell_org, po_vendors pv, po_vendor_sites_all pvs, ra_customers rc WHERE mip.ship_organization_id = ship_org.organization_id AND mip.sell_organization_id = sell_org.organization_id AND mip.vendor_id = pv.vendor_id AND mip.vendor_site_id = pvs.vendor_site_id AND mip.customer_id = rc.customer_id;

Technically, the table is primarily referenced by the internal logic of the Order Management and Purchasing APIs when creating the requisite documents for an inter-company transaction. Direct data manipulation by users is rare; setup and maintenance are performed through the "Inter-company Relationships" form in the Oracle EBS front-end.

Related Objects

As indicated by its foreign key constraints, MTL_INTERCOMPANY_PARAMETERS is a central hub that integrates data from several key EBS modules. The documented relationships are:

• PO_VENDORS: Joined via MTL_INTERCOMPANY_PARAMETERS.VENDOR_ID to identify the internal Vendor record.
• PO_VENDOR_SITES_ALL: Joined via MTL_INTERCOMPANY_PARAMETERS.VENDOR_SITE_ID to identify the specific vendor site.
• RA_CUSTOMERS: Joined via MTL_INTERCOMPANY_PARAMETERS.CUSTOMER_ID to identify the internal Customer record.
• RA_ADDRESSES_ALL: Joined via MTL_INTERCOMPANY_PARAMETERS.ADDRESS_ID for the customer address.
• RA_SITE_USES_ALL: Joined via MTL_INTERCOMPANY_PARAMETERS.CUSTOMER_SITE_ID for the customer site use.
• RA_CUST_TRX_TYPES_ALL: Joined via MTL_INTERCOMPANY_PARAMETERS.CUST_TRX_TYPE_ID to determine the invoice transaction type.

These relationships underscore the table's critical function in bridging Inventory, Purchasing, and Order Management/Receivables for seamless inter-company processing.