Results for “transaction_record_id”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ECE_MVSTO_DETAILS_X is a database table owned by the EC schema within the Oracle E-Business Suite e-Commerce Gateway module. It serves as the extension ("_X") counterpart to the base table ECE_MVSTO_DETAILS, holding the customer-defined descriptive flexfield (DFF) and attribute columns that extend the standard transaction detail structure. In Oracle EBS 12.1.1 and 12.2.2, the e-Commerce Gateway processes inbound and outbound EDI transactions — including the movement of sales orders, purchases, invoices, and shipments — and the MVSTO (Move Order / Miscellaneous Shipment Transaction Object) detail records provide the transactional line-level data that flows through this interface. The extension table preserves the seeded application columns while allowing implementers to attach additional attributes without modifying the base schema.

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as standalone. This suggests that ECE_MVSTO_DETAILS_X functions less as a dependent satellite and more as an independent attribute holder, which is consistent with its narrow two-column structure. Modelers may treat it as an extension attribute set that would typically be sourced alongside a hub or link representing the parent transaction record, rather than as a full satellite with its own driving business key.

Key Information Stored

The documented physical schema for this table in ETRM 12.2.2 is intentionally minimal, comprising only two columns. The most significant documented columns are:

  • TRANSACTION_RECORD_ID — The primary surrogate identifier for the detail extension row. This value corresponds to the parent record in ECE_MVSTO_DETAILS, enabling the extension attributes to be linked back to the core transactional detail. It functions as the principal join key between the extension table and its base table.
  • SECURITY_GROUP_ID — A foreign key referencing FND_SECURITY_GROUPS. This column enforces Oracle EBS multi-org / security-group data partitioning, ensuring that the extension row is visible only to users authorized for the owning security group, consistent with the security architecture applied across e-Commerce Gateway tables.

The surrogate key in this table is TRANSACTION_RECORD_ID, which acts as the correlation point to the base table. Because the metadata documents only two columns, there is no independent unique business-key index beyond this identifier; the business key is inherited from the parent ECE_MVSTO_DETAILS record. Any additional DFF segments (typically numbered ATTRIBUTE columns) are stored physically but are not enumerated in the documented schema excerpt and should be confirmed against the live data dictionary.

Common Use Cases and Queries

Typical scenarios involve reporting on extended EDI transaction details, auditing security-group isolation, and reconciling staging records with their extension attributes. A representative query joins the extension table to its base and to the security group setup:

  • Identifying all extension rows for a given transaction record:
    SELECT x.transaction_record_id, x.security_group_id FROM ec.ece_mvsto_details_x x WHERE x.transaction_record_id = :record_id;
  • Auditing security-group coverage:
    SELECT x.transaction_record_id, g.security_group_name FROM ec.ece_mvsto_details_x x, fnd_security_groups g WHERE x.security_group_id = g.security_group_id;
  • Detecting orphaned extensions that have no surviving base detail:
    SELECT x.transaction_record_id FROM ec.ece_mvsto_details_x x WHERE NOT EXISTS (SELECT 1 FROM ec.ece_mvsto_details d WHERE d.transaction_record_id = x.transaction_record_id);

These patterns support data-quality reconciliation, migration validation, and access-control reviews common in e-Commerce Gateway implementations.

Related Objects

The principal relationships documented and implied by the metadata are:

  • ECE_MVSTO_DETAILS — the base table this object extends; joined on TRANSACTION_RECORD_ID.
  • FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key; provides security-group definition.
  • ECE_MVSTO_HEADERS and ECE_MVSTO_HEADERS_X — the header-level parent and its extension, providing transaction context above the detail line.
  • FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — DFF metadata that describes any flexfield segments physically present in the extension.
  • ECX_* interface tables — the e-Commerce Gateway staging and processing tables that feed and consume MVSTO transaction data.

Together these objects form the transaction-record hierarchy for MVSTO processing, with ECE_MVSTO_DETAILS_X supplying the implementation-specific attributes layered over the seeded detail model.