Search Results project_reference_enabled




Overview
Explore in AI Chat

Overview

MTL_PARAMETERS_ALL_V is an Oracle E-Business Suite inventory view owned by the APPS schema within the INV (Inventory) product module. It is documented in ETRM as a retrofitted view, meaning it was retrofitted from an earlier release into the 12.1.1 / 12.2.2 code line as a standardized, multi-organization-aware access layer over the inventory organization parameters. The view presents the full parameter definition of every inventory organization — master and child — including cost method defaults, ATP and picking rule defaults, locator and subinventory sequencing, negative inventory controls, serial and lot number generation attributes, and, most importantly for the user's query, the complete set of inter-organization accounting accounts used by the inter-organization transfer process.

Because many inventory and cost management reports, concurrent programs, and integrations must resolve organization-level setup without hard-coding the base table, MTL_PARAMETERS_ALL_V serves as the canonical reporting and integration surface for inventory parameters. The "_ALL_" designation indicates that the view is intended to return rows for all organizations accessible from the read paradigm, rather than a single operating unit or organization context.

Underlying Base Objects

Per the documented ETRM metadata, the sole referenced base object for this view is the synonym MTL_PARAMETERS, which resolves to the APPS.MTL_PARAMETERS base table. The view text confirms this: it is a simple projection (SELECT of named columns) over the base table, exposing the entire row structure of MTL_PARAMETERS — including its audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), the DFF flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15, GLOBAL_ATTRIBUTE_CATEGORY), and the request context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE). No joins to organization, ledger, or other parameter tables are embedded in the documented view text, so referential lookups such as organization code or operating unit must be made separately by the caller when required.

Key Columns

Common Use Cases and Queries

The most frequent use is resolving an organization's setup for validation, reporting, or integration. The query that motivated this search retrieves the inter-organization transfer credit account for a given organization:

  • SELECT organization_id, organization_code, interorg_transfer_cr_account, interorg_receivables_account, interorg_payables_account FROM mtl_parameters_all_v WHERE organization_id = :p_org_id;
  • Cost accounting reconciliation joining the view to GL code combinations to confirm account validity across all organizations.
  • Setup audit listings — e.g., listing all organizations with negative inventory permitted or with the Average cost method.
  • Inter-organization transfer configuration reports that combine INTERORG_TRANSFER_CR_ACCOUNT, INTERORG_RECEIVABLES_ACCOUNT, and INTERORG_PAYABLES_ACCOUNT with MATL_INTERORG_TRANSFER_CODE to verify complete transfer accounting.

Because the view has no embedded joins, callers typically link it to HR_ALL_ORGANIZATION_UNITS or ORG_ORGANIZATION_DEFINITIONS when operating unit or legal entity context is required.