Search Results mtl_intercompany_parameters_v




Overview
Explore in AI Chat

Overview

MTL_INTERCOMPANY_PARAMETERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, associated with the INV – Inventory product. ETRM metadata flags the object with the description "10SC ONLY," indicating that its functional relevance is restricted to the discrete manufacturing intercompany flow. The view exposes configuration records from the intercompany parameters setup, which govern how inventory transfers and shipments between internal organizations are priced, invoiced, and accounted for.

The view's principal value lies in its denormalization of the base configuration table. Rather than requiring report developers to join organization, supplier, customer, transaction type, and site-use lookups manually, the view presents human-readable names alongside the underlying identifiers. This makes it suitable for intercompany setup listings, reconciliation reports, and integration extracts that must resolve raw IDs into descriptive attributes when interfacing with external systems or downstream EBS modules such as Order Management and Receivables.

The user search term "revalue_average_flag" corresponds directly to a column exposed by this view. That flag controls whether average costing is revalued when intercompany transfers are processed, and it appears in the view as MIP.REVALUE_AVERAGE_FLAG, sourced from the base table MTL_INTERCOMPANY_PARAMETERS.

Underlying Base Objects

The view is defined over a single driving table plus several supporting lookups. The primary table is MTL_INTERCOMPANY_PARAMETERS (exposed through a synonym), which stores the intercompany relationship definition between a shipping organization and a selling organization. Supporting objects include HR_ORGANIZATION_UNITS (aliased twice, HOU1 and HOU2) to resolve the ship and sell organization names; PO_VENDORS and PO_VENDOR_SITES_ALL for supplier and supplier-site details; HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_CUST_SITE_USES_ALL, and RA_CUST_TRX_TYPES_ALL for customer, address, transaction type, and site-use information.

The documented referenced objects also include the HR_SECURITY, HR_GENERAL, and FND_GLOBAL packages, which enforce organization-level security and context during query execution, and the HZ_CUST_ACCOUNTS synonym used in an inline subquery that derives the customer ID, name, and account number from HZ_PARTIES and HZ_CUST_ACCOUNTS. Supplier joins to PO_VENDORS and PO_VENDOR_SITES_ALL are outer joins (indicated by the (+) operator), reflecting that intercompany flows involving inventory transfers may not require a supplier, whereas customer-side joins are typically required.

Key Columns

Common Use Cases and Queries

Typical uses include auditing intercompany setup, verifying that the revalue average flag is correctly configured per organization pair, and feeding downstream reports or interfaces with resolved customer and supplier names. A representative query listing the relationships and the revalue average flag follows.

SELECT ship_organization_name, sell_organization_name, flow_type, customer_name, revalue_average_flag, inv_currency_code FROM apps.mtl_intercompany_parameters_v WHERE revalue_average_flag = 'Y';

To isolate flows tied to a specific supplier and transaction type:

SELECT ship_organization_name, sell_organization_name, supplier_name, transaction_name FROM apps.mtl_intercompany_parameters_v WHERE flow_type = 'SHIP' ORDER BY ship_organization_name, sell_organization_name;

When accounting configuration must be reviewed, the account combination IDs can be joined to GL_CODE_COMBINATIONS to obtain the underlying account strings. Because the view enforces organization security through HR_SECURITY, results are scoped to the organizations accessible to the querying user, which must be considered when building cross-organization reconciliation reports.