Search Results tp_document_type




Overview

APPS.ECE_MVSTO_HEADERS_V is a denormalized Oracle E-Business Suite view exposed in the ECE (E-Commerce Gateway) schema. It consolidates EDI trading partner configuration with material movement statistics, producing a single row per movement transaction suitable for outbound MVSTO (Material Movement Statistics) EDI document generation and reconciliation reporting. The view is part of the standard outbound EDI infrastructure delivered with EBS 12.1.1 and 12.2.2, and is typically invoked by the ECE transaction processor or by custom concurrent programs that extract movement data destined for a value-added network.

The view standardizes the communication method (hard-coded to 'EDI'), the trading partner document identifier (hard-coded to 'MVSTO'), and the transaction date (SYSDATE at runtime), while the remaining columns are sources from trading partner definitions, location cross-references, legal entity data, and the underlying movement statistics view. It is read-only; no DML is supported against the view.

Underlying Base Objects

The view is defined over the following documented objects:

The view therefore joins trading partner configuration to inventory movement facts, and enriches the result with HR organization and location reference data.

Key Columns

Common Use Cases and Queries

Typical uses include troubleshooting why an MVSTO document is not generated, confirming the document type or test flag applied to a partner, and building reconciliation reports that pair movement statistics with trading partner configuration.

Identify the document types and standards configured for a given trading partner:

SELECT tp_document_type, document_standard, translator_code, tp_test_flag
FROM   apps.ece_mvsto_headers_v
WHERE  tp_location_code_ext = :p_location_code;

List recent movement statistics destined for outbound EDI, enriched with customer and legal entity names:

SELECT period_name, movement_type, movement_status, edi_transaction_reference,
       edi_transaction_date, customer_name, legal_entity_name
FROM   apps.ece_mvsto_headers_v
WHERE  edi_transaction_date >= TRUNC(SYSDATE) - 30
ORDER  BY edi_transaction_date DESC;

Validate test versus production routing before submitting the ECE outbound program:

SELECT tp_description, tp_test_flag, tp_reference_ext1, tp_reference_ext2
FROM   apps.ece_mvsto_headers_v
WHERE  tp_test_flag = 'Y';

Because HR_SECURITY is applied through the underlying HR views, results are automatically limited to the organizations and legal entities accessible to the session user, which makes the view safe for use in self-service and multi-organization reporting without additional filtering.