Search Results default_from_subinventory_code

Overview

MTL_MOVE_ORDER_HEADERS_V is an Oracle E-Business Suite Inventory (INV) view that exposes move order header information for reporting and integration purposes. Move orders are internal inventory documents used to request and authorize the transfer of material between subinventories, between organizations, or to and from accounts. The header record stores the descriptive and controlling attributes of a move order, including its number, transaction type, organization, default source and destination subinventories, header status, and approval status. This view allows external reports, concurrent programs, and integration interfaces to retrieve header-level move order data without directly querying the base transaction table.

Within the Oracle EBS 12.1.1 and 12.2.2 releases, this view is documented as "Retrofitted," reflecting that it was re-created or re-pointed as part of the multi-org and table restructuring changes introduced across these releases. It is a reporting-oriented object rather than a transactional entry point; inserts and updates against move orders are performed against the underlying MTL_MOVE_ORDER_HEADERS table or through the Move Order APIs and Forms.

Underlying Base Objects

The view text identifies the principal base object as MTL_MOVE_ORDER_HEADERS, aliased MMOH, which supplies the majority of the exposed columns. It also joins MTL_TRANSACTION_TYPES (MTT) on TRANSACTION_TYPE_ID to resolve the transaction type name and action, and joins the MFG_LOOKUPS table twice (aliased MFG1 and MFG2) to translate status codes into meaningful values. Specifically, MFG1 is joined on the MTL_MO_HEADER_APPROVAL_STATUS lookup type and MFG2 on the MTL_MO_HEADER_STATUS lookup type.

Because the view performs these joins internally, consumers receive decoded values such as TRANSACTION_TYPE_NAME and the resolved approval and header status meanings without having to repeat the lookup logic. The documented metadata does not list any additional referenced base objects beyond these, so the view should be treated as a header-level projection of MTL_MOVE_ORDER_HEADERS enriched with transaction type and lookup descriptions.

Key Columns

• MOVE_ORDER_HEADER_ID – Primary identifier of the move order header; the join key to move order lines.
• MOVE_ORDER_NUMBER – User-facing move order number.
• TRANSACTION_TYPE_ID / TRANSACTION_TYPE_NAME / TRANSACTION_ACTION_ID – The inventory transaction type driving the move order and its resolved name and action.
• ORGANIZATION_ID – Owning inventory organization of the move order.
• DESCRIPTION – Free-text description of the move order.
• DEFAULT_DATE_REQUIRED – Default required date for the movement.
• DEFAULT_FROM_SUBINVENTORY_CODE / DEFAULT_TO_SUBINVENTORY_CODE – Default source and destination subinventories.
• DEFAULT_TO_ACCOUNT_ID – Default destination account for account transfers.
• HEADER_STATUS / STATUS_DATE – Current header status and the date it was set.
• HEADER_APPROVAL_STATUS / APPROVAL_DATE – Approval state of the header and approval date.
• ATTRIBUTE1 through ATTRIBUTE15 / ATTRIBUTE_CATEGORY – Descriptive flexfield columns.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE for concurrency and audit tracking.

Common Use Cases and Queries

Typical usage includes move order status reporting, approval monitoring, and extract feeds for warehouse or integration systems. The following query lists unapproved move orders in a given organization:

SELECT move_order_number, transaction_type_name,
       header_status, header_approval_status, creation_date
FROM   mtl_move_order_headers_v
WHERE  organization_id = :org_id
AND    header_approval_status <> 'APPROVED';

Because the view resolves the approval and header status lookups, results can be filtered or displayed directly using the decoded meanings. For line-level detail, join MOVE_ORDER_HEADER_ID to MTL_MOVE_ORDER_LINES. As with all reporting views, restrict queries by ORGANIZATION_ID and date ranges to maintain performance on high-volume installations.