Search Results transfer_warehouse




Overview

MTL_ADJ_SYNC_WRAPPER_V is an APPS-owned database view within the Oracle Inventory (INV) module, documented in ETRM for Oracle EBS 12.1.1 and 12.2.2 with a VALID status. It functions as a synchronous wrapper — an aggregation and normalization layer — over the adjustment transaction synchronization view, MTL_ADJUSTMENT_TXN_SYNC_V. Its role is to present inventory adjustment and transfer transactions in a flattened, summarized form suitable for downstream reporting, interface extraction, and XML-based integration with external or adjacent systems such as order management, warehouse management, or supply chain execution platforms.

The view does not store data; it is a runtime projection that consolidates transactional detail and rolls up quantities. Because it exposes adjustment and subinventory transfer activity in a single, consistent shape, it is frequently used where a stable, denormalized read model is needed without querying the underlying transaction tables directly.

Underlying Base Objects

The view is defined over the following documented referenced base objects:

  • MTL_ADJUSTMENT_TXN_SYNC_V — the primary source view supplying all transactional columns and measure values.
  • HR_GENERAL (PACKAGE) — an Oracle HR utility package, typically invoked for organizational or security-related resolution.
  • HR_SECURITY (PACKAGE) — provides organization-level security filtering, ensuring that a querying user only sees inventory transactions for organizations they are authorized to access.

The relationship to the base view is aggregate: MTL_ADJ_SYNC_WRAPPER_V groups the rows returned by MTL_ADJUSTMENT_TXN_SYNC_V and applies SUM() to the quantity measures. This makes the wrapper the appropriate layer when summarized, one-row-per-transaction-group output is desired.

Key Columns

The view exposes identity, location, item, and quantity columns. Significant groupings include:

Common Use Cases and Queries

The view is typically queried to report summarized adjustment and transfer activity, and to extract records not yet transmitted for integration. The presence of XML_DOCUMENT_ID and TRANSACTION_EXTRACTED supports extraction-driven workflows.

Listing recent transfer activity by destination subinventory:

  • SELECT transaction_number, transaction_date, item, subinventory, transfer_subinventory, transaction_quantity, transaction_uom FROM mtl_adj_sync_wrapper_v WHERE transfer_subinventory = :p_subinventory AND organization_id = :p_org ORDER BY transaction_date DESC;

Identifying unextracted transactions pending interface:

  • SELECT organization_id, transaction_number, transaction_type, xml_document_id FROM mtl_adj_sync_wrapper_v WHERE transaction_extracted = 'N' ORDER BY creation_date;

Summarizing transfer volumes between subinventories for a period:

  • SELECT subinventory, transfer_subinventory, SUM(transaction_quantity) qty FROM mtl_adj_sync_wrapper_v WHERE transaction_date BETWEEN :p_from AND :p_to GROUP BY subinventory, transfer_subinventory;

Because HR_SECURITY governs organization visibility, results reflect the querying user's authorized inventory organizations.