Search Results transfer_warehouse

Overview

APPS.MTL_ADJ_SYNC_WRAPPER_V is an Oracle E-Business Suite inventory view that serves as a consolidated, aggregated wrapper over the adjustment transaction synchronization data set. Its primary role is to present inventory adjustment and transfer transactions in a flattened, reporting-ready form suitable for downstream integration, reconciliation, and interface processing. The view is defined in the APPS schema and is documented in the ETRM repository for both EBS 12.1.1 and 12.2.2.

Unlike a base transactional table, the wrapper view reduces transactional granularity by grouping records on transaction header attributes while summing quantity columns. This design allows consumers—such as inventory interfaces, synchronization programs, and reporting tools—to retrieve a single aggregated line per transaction and item context rather than iterating over multiple underlying detail rows.

Because the view exposes both transfer and adjustment attributes, it is frequently referenced when users investigate warehouse movement activity. The presence of the TRANSFER_WAREHOUSE column makes it directly relevant to searches involving "transfer_warehouse," which is one of the transfer-specific columns surfaced by the view.

Underlying Base Objects

Per the ETRM metadata, MTL_ADJ_SYNC_WRAPPER_V is defined over a single view, MTL_ADJUSTMENT_TXN_SYNC_V, and depends on two packages: HR_GENERAL and HR_SECURITY. The dependency on HR_SECURITY is significant because it means row-level security and organization access rules governed by the HR security model may filter the data returned by the view, depending on the responsibility and security profile of the querying user.

MTL_ADJUSTMENT_TXN_SYNC_V supplies all of the columns that the wrapper consumes, including transaction identifiers, item and locator attributes, and the quantity and unit-of-measure fields. The wrapper does not add columns of its own; instead it applies grouping and aggregation to the underlying view's result set. Consequently, any change to the definition or filtering logic of MTL_ADJUSTMENT_TXN_SYNC_V propagates directly to the wrapper.

Key Columns

• TRANSACTION_NUMBER, TRANSACTION_DATE, TRANSACTION_TYPE, TRANSACTION_TYPE_ID — identify the adjustment transaction, its effective date, and its classification.
• ORGANIZATION_ID, WAREHOUSE — the inventory organization and subject warehouse for the transaction.
• INVENTORY_ITEM_ID, ITEM, ITEM_DESCRIPTION, REVISION — the item and revision affected by the adjustment.
• SUBINVENTORY, LOCATOR — the source subinventory and locator within the organization.
• TRANSFER_WAREHOUSE, TRANSFER_SUBINVENTORY, TRANSFER_LOCATOR — the destination warehouse, subinventory, and locator for transfer transactions. These columns are central to transfer-related investigations.
• LPN, TRANSFER_LPN, CONTENT_LPN — license plate numbers for the source, destination, and contained items.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, SECONDARY_QUANTITY — aggregated quantities (SUM) at the transaction, primary, and secondary UOM levels.
• TRANSACTION_UOM, PRIMARY_UOM, SECONDARY_UOM — the corresponding units of measure.
• TRANSACTION_SOURCE, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_ACTION_ID — source and action context for the transaction.
• CREATION_DATE, TRANSACTION_EXTRACTED, XML_DOCUMENT_ID — audit, extraction, and interface grouping attributes.

Common Use Cases and Queries

Typical uses include reconciling inventory adjustments, verifying transfer movements between warehouses, and feeding downstream synchronization or XML-based interface processes. The following query returns aggregated transfer activity for a given destination warehouse:

SELECT organization_id,
       warehouse,
       transfer_warehouse,
       item,
       transaction_type,
       SUM(transaction_quantity) AS total_qty,
       transaction_uom
FROM   apps.mtl_adj_sync_wrapper_v
WHERE  transfer_warehouse = 'M1'
AND    transaction_date >= TRUNC(SYSDATE) - 7
GROUP  BY organization_id, warehouse, transfer_warehouse,
          item, transaction_type, transaction_uom;

To identify adjustments not yet extracted for interface processing:

SELECT transaction_number, transaction_date, warehouse,
       item, transaction_type, xml_document_id
FROM   apps.mtl_adj_sync_wrapper_v
WHERE  transaction_extracted = 'N'
ORDER  BY transaction_date, transaction_number;

Because aggregation is already applied within the view, additional grouping is only necessary when rolling up across transaction numbers. Query performance is influenced by the underlying MTL_ADJUSTMENT_TXN_SYNC_V definition and by the HR_SECURITY organization filters applied at runtime.