Search Results ece_tp_loc_code

Overview

ECE_MVSTO_HEADERS_V is a private, active view owned by the APPS schema in Oracle E-Business Suite, defined within the e-Commerce Gateway (EC) product. It extracts header-level information for the outbound Movement Statistics (INTRASTAT) transaction, which supports regulatory reporting of goods movements across borders within the European Union. The view carries the display name "Movement Statistics Header View" and the business entity category INV_MOVEM, reflecting its ownership under the Inventory (INV) functional scope.

The view consolidates transaction profile data, trading partner definitions, and movement statistics attributes into a single denormalized row suitable for flat-file extraction and EDI generation. Because it is marked private, it is intended for internal use by the e-Commerce Gateway extraction programs rather than as a general-purpose reporting interface, though it remains queryable in practice.

Underlying Base Objects

ETRM documentation identifies the referenced base objects as ECE_MTL_MOV_STAT_V (a view), ECE_TP_DETAILS and ECE_TP_HEADERS (synonyms over the trading partner setup tables), and the supporting packages and views FND_GLOBAL, HR_GENERAL, HR_LEGAL_ENTITIES, HR_LOCATIONS, HR_ORGANIZATION_UNITS, and HR_SECURITY.

The join conditions link a trading partner header (ETPH) to its detail line (ETPD) and to the movement statistics view (EMMSV), with the legal entity resolved through HR organization views and HR_SECURITY enforcing access control. FND_GLOBAL supplies session context, including the operating unit implicitly used for data restriction. The view text is essentially a SELECT joining these sources and projecting a fixed literal ('EDI') for the communication method and 'MVSTO' as the trading partner document identifier.

Key Columns

• TRANSLATOR_CODE — sourced from ETPD.TRANSLATOR_CODE, the trading partner detail attribute that drives the user's search. It identifies the translator (mapping/format definition) applied when generating the outbound INTRASTAT file, and is therefore central to output format selection.
• TP_DOCUMENT_ID / TP_DOCUMENT_TYPE / DOCUMENT_STANDARD — identify the transaction document ('MVSTO') and the EDI standard in use.
• TP_LOCATION_CODE_EXT, TP_DESCRIPTION, TP_REFERENCE_EXT1, TP_REFERENCE_EXT2 — trading partner location and header reference data.
• PERIOD_NAME, EDI_TRANSACTION_REFERENCE, EDI_TRANSACTION_DATE — reporting period and prior EDI transaction identifiers from ECE_MTL_MOV_STAT_V.
• MOVEMENT_TYPE, STAT_TYPE, USAGE_TYPE, MOVEMENT_STATUS, ZONE_CODE — INTRASTAT classification attributes determining how the movement is reported.
• REPORT_REFERENCE, REPORT_DATE — source document reference for the movement.
• LEGAL_ENTITY — the HR organization ID of the reporting legal entity, resolved via HR_GENERAL and related HR views.
• ATTRIBUTE1–ATTRIBUTE15 (TPH_ and TPD_ prefixed) — descriptor flexfield segments from the trading partner header and detail records.

Common Use Cases and Queries

The primary use case is the outbound Movement Statistics INTRASTAT extraction. Developers investigating translational behavior typically query by translator code to confirm which partners are configured with a given format. For example:

SELECT translator_code, tp_document_type, tp_description, legal_entity
FROM apps.ece_mvsto_headers_v
WHERE translator_code = :p_translator_code;

To inspect movement classifications for a reporting period:

SELECT period_name, movement_type, stat_type, usage_type, movement_status
FROM apps.ece_mvsto_headers_v
WHERE period_name = :p_period;

Because the view executes HR_SECURITY and FND_GLOBAL logic, results are filtered by the session's operating unit and security profile. Queries run from PL/SQL or concurrent programs should therefore be executed under an initialized applications session to avoid empty results.