Search Results ece_mvsto_headers_x




Overview
Explore in AI Chat

Overview

ECE_MVSTO_HEADERS_X is the extension (attribute) table for ECE_MVSTO_HEADERS in the Oracle e-Commerce Gateway (EC) module. It resides in the EC schema and holds custom, customer-defined attributes that are attached to the parent MVSTO header record without modifying the seeded, Oracle-owned base table. In Oracle EBS 12.1.1 and 12.2.2 this pattern is the standard mechanism for extending EDI transaction data: the base table stores the standard inbound/outbound structure, while the corresponding "_X" table stores the DFF (Descriptive Flexfield) or custom columns populated at transaction processing time. The object is documented as VALID in ETRM 12.2.2 with two physical columns.

From a Data Vault modeling perspective, the heuristic classification mined from the FK structure is standalone. Because the table carries only an identifier and a security reference and no downstream dependents, it is best treated as an optional satellite of the parent header — a suggestion for warehouse design rather than a constraint imposed by EBS. Its sole foreign key points to FND_SECURITY_GROUPS, indicating that row-level access to the extension data is governed by Oracle Application Object Library security profiles rather than by transactional business keys.

Key Information Stored

The documented physical schema is deliberately narrow, containing only two columns:

  • TRANSACTION_RECORD_ID — the join key that ties each extension row to its parent record in ECE_MVSTO_HEADERS. In the EBS extension-table convention this identifier is the primary key of the "_X" table and simultaneously the foreign key to the base header's transaction record identifier, giving a strict one-to-one (or one-to-zero-or-one) relationship between the parent header and its extension.
  • SECURITY_GROUP_ID — the security grouping column used by Oracle Application Object Library to isolate data by responsibility and security profile. This is the only documented foreign key, referencing FND_SECURITY_GROUPS.

In a standard 12.1.1 / 12.2.2 environment the table typically contains the DFF context and attribute columns underlying the flexfield segments (for example ATTRIBUTE_CATEGORY and the ATTRIBUTE1 through ATTRIBUTE15 set). Such columns are added during implementation by the Flexfield definition and therefore are not part of the baseline ETRM metadata. Implementers should confirm the actual column list in their instance with the data dictionary rather than assuming the seeded set.

Common Use Cases and Queries

The extension table is consulted whenever inbound or outbound MVSTO (Material/Stock Transfer Order) EDI data must be reported or validated together with site-specific attributes. Typical scenarios include: validating that custom attributes were populated before an outbound purchase order or ship notice interface, extracting user-defined fields for operational reporting, and troubleshooting flexfield values that did not appear on the transmitted document.

  • Retrieving custom attributes for a specific header:
    SELECT x.transaction_record_id, x.attribute_category, x.attribute1, x.attribute2
    FROM ece_mvsto_headers_x x
    WHERE x.transaction_record_id = :p_record_id;
  • Joining extension data to the parent header:
    SELECT h.transaction_record_id, h.*, x.*
    FROM ece_mvsto_headers h, ece_mvsto_headers_x x
    WHERE h.transaction_record_id = x.transaction_record_id;
  • Security-filtered extraction honoring the security profile:
    SELECT x.* FROM ece_mvsto_headers_x x
    WHERE x.security_group_id = :p_security_group_id;

Because the table is a one-to-one extension, LEFT OUTER JOINs from the base header are appropriate when the existence of a custom attribute row is itself business-meaningful.

Related Objects

  • ECE_MVSTO_HEADERS — parent header table; joined on TRANSACTION_RECORD_ID.
  • FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key; controls which responsibilities may view the extension row.
  • ECE_MVSTO_LINES / ECE_MVSTO_LINES_X — line-level base and extension tables that carry the same design pattern for the detail level.
  • ECE_MVSTO_HEADERS_X dependent flexfield definitions, stored in FND_DESCRIPTIVE_FLEXS and FND_FLEX_VALUES via the Application Developer responsibility.
  • EC_PROCESS_RULES / EC_GRP_* — e-Commerce Gateway configuration tables that drive which MVSTO transactions are processed and therefore which extension rows are created.
  • EC_TP_HEADERS or EC_TRADING_PARTNERS — trading partner definitions that supply the routing context for the parent transaction records.