Search Results lot_number_length




Overview
Explore in AI Chat

Overview

APPS.MTL_PARAMETERS_ALL_V is an operational reporting view in Oracle E-Business Suite that exposes inventory organization setup and control parameters. In the 12.1.1 and 12.2.2 data models, the view presents the columns of the MTL_PARAMETERS table, the core table that stores per-organization configuration for Oracle Inventory. The "ALL" naming convention signals that the view is not filtered by organization or responsibility context; it returns parameter rows for every inventory organization defined in the instance, subject only to the privileges of the querying user. This makes the view suitable for cross-organization reporting, data extraction, and integration scenarios where a complete picture of inventory parameterization is required. Because inventory parameters govern negative stock control, locator and subinventory defaults, lot and serial numbering behavior, inter-org transfer accounting, and mandatory account assignments used by cost management, the view is frequently consulted by technical consultants administering or auditing an EBS instance.

Underlying Base Objects

The ETRM documentation for 12.2.2 records a single referenced base object: MTL_PARAMETERS, exposed in the APPS schema as a synonym. MTL_PARAMETERS holds one row per inventory organization, keyed principally by ORGANIZATION_ID, and is maintained through the Inventory Organization Parameters window. Because the view is defined directly over the table synonym without additional joins, it preserves the one-row-per-organization grain and the complete column set of the base table. As a result, the view behaves as a read-only projection of MTL_PARAMETERS; it does not aggregate, filter, or derive values. In 12.1.1 the definition is functionally equivalent, and the same column inventory applies, with the caveat that Multi-Org access control (MOAC) semantics must be understood: the underlying table is an organization-level table and is subject to the operating unit and organization security profile settings applied at runtime.

Key Columns

Common Use Cases and Queries

Typical uses include validating lot and serial control configuration after a clone or upgrade, reconciling organization parameters across a multi-org deployment, and feeding external systems that need numbering or accounting defaults. A common query to inspect lot uniqueness by organization is:

SELECT organization_id, organization_code, lot_number_uniqueness
  FROM apps.mtl_parameters_all_v
 ORDER BY organization_code;

A wider audit of lot generation and serial settings:

SELECT organization_code, lot_number_uniqueness, lot_number_generation,
       lot_number_zero_padding, lot_number_length,
       serial_number_type, serial_number_generation
  FROM apps.mtl_parameters_all_v;

To correlate parameters with costing accounts:

SELECT organization_code, material_account, cost_of_sales_account,
       negative_inv_receipt_code, stock_locator_control_code
  FROM apps.mtl_parameters_all_v;

Comparisons against MTL_PARAMETERS are valid because the view is a direct projection, though joins to MTL_ORGANIZATIONS or HR_ALL_ORGANIZATION_UNITS, or to the operating unit model through MOAC, are often required to present meaningful organization descriptions alongside these parameters.