Search Results ece_attachment_details




Overview
Explore in AI Chat

Overview

ECE_ATTACHMENT_DETAILS is a temporary staging table owned by the EC schema within the Oracle e-Commerce Gateway (EC) module. Its documented purpose is to hold temporary detail data used during the extraction of attachments. In Oracle EBS 12.1.1 and 12.2.2, the e-Commerce Gateway processes inbound and outbound transactions across multiple interface formats; when an outbound transaction requires attachments to be transmitted alongside the transaction data, the extraction process requires a transient working area to hold the attachment segments before they are assembled, formatted, and written to the output file. ECE_ATTACHMENT_DETAILS serves exactly this role. Records in the table are populated and consumed by concurrent programs that drive the extraction, with the RUN_ID column tying each row to a specific extraction run.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. The absence of parent-child relationships within the EC data model, combined with the low-granularity, run-scoped nature of its contents, means it does not naturally act as a hub, link, or satellite. It is best understood as a transient staging structure rather than a persistent business entity. Because its content is fully expendable once the extraction completes, the table should not be treated as a durable source of record for any downstream analytical model.

Key Information Stored

The documented physical schema comprises 23 columns. The most operationally significant are:

Note the distinction: TRANSACTION_RECORD_ID is the surrogate value backed by a unique index, whereas ATTACHED_DOCUMENT_ID is a foreign-key reference supplying the business linkage to the source attachment.

Common Use Cases and Queries

The table is primarily queried during troubleshooting of e-Commerce Gateway attachment extraction. A support analyst might inspect the working set for a failed extraction run:

SELECT ATT_SEQ_NUM, ENTITY_NAME, NAME, PK1_VALUE,
       SEGMENT_NUMBER, CONTINUE_FLAG, ATTACHED_DOCUMENT_ID
FROM   EC.ECE_ATTACHMENT_DETAILS
WHERE  RUN_ID = :run_id
ORDER BY ATT_SEQ_NUM, SEGMENT_NUMBER;

To reconstruct attachment content for a given document, the ATTACHMENT_SEGMENT column is concatenated in sequence order. Joining to FND_ATTACHED_DOCUMENTS via ATTACHED_DOCUMENT_ID confirms the originating attachment metadata. Because rows are transient, any temporary diagnostic extraction must be captured before the extraction program clears its working set.

Related Objects

  • FND_ATTACHED_DOCUMENTS — The only documented foreign-key target; joined on ECE_ATTACHMENT_DETAILS.ATTACHED_DOCUMENT_ID = FND_ATTACHED_DOCUMENTS.ATTACHED_DOCUMENT_ID.
  • ECE_ATTACHMENTS — Related gateway attachment control data.
  • ECE_INTERFACE_HEADERS / ECE_INTERFACE_LINES — Interface staging tables for outbound transaction data.
  • FND_DOCUMENTS — Underlying document definitions referenced through FND_ATTACHED_DOCUMENTS.
  • FND_LOBS — Stores the actual attachment content where held as large objects.
  • ECX_* concurrent programs — The extraction programs that populate and consume this table.

Together these objects form the attachment extraction pathway within the e-Commerce Gateway, with ECE_ATTACHMENT_DETAILS acting as the transient detail layer.