Search Results send_date

Overview

IGF.IGF_SL_COD_DOC_DTLS is a transaction data table within the Oracle E-Business Suite IGF (Global Intercompany) schema. It stores the XML documents exchanged between Oracle EBS and the COD (Country of Distribution / centralized data exchange) system as part of the intercompany balancing and distribution processing flow. Each row represents a single document — either outbound or inbound — together with its lifecycle dates, current processing status, and the full XML payloads themselves. The table lives in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is owned by the IGF schema but exposed to APPS through the standard synonym IGF_SL_COD_DOC_DTLS.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. It has no foreign key relationships to other database objects and is not referenced by any dependent structures. In practice this means it functions as an independent operational ledger of COD document traffic rather than a satellite attached to a parent hub or link. The DOCUMENT_ID_TXT column acts as both the surrogate primary key and the sole business-key candidate, being the single column in the unique index IGF_SL_COD_DOC_DTLS_PK.

Key Information Stored

The table contains 17 documented columns. The most operationally significant are:

• DOCUMENT_ID_TXT (VARCHAR2, 30) — Identifier for the document; primary key via IGF_SL_COD_DOC_DTLS_PK.
• OUTBOUND_DOC (CLOB) — The XML document sent to the COD system.
• INBOUND_DOC (CLOB) — The XML document received from the COD system.
• SEND_DATE (DATE) — Timestamp when the document was transmitted to COD.
• ACK_DATE (DATE) — Acknowledgement date returned by COD. This is the column most frequently queried by users searching for document confirmation timing.
• DOC_STATUS (VARCHAR2, 30) — Current processing status of the document in its lifecycle.
• DOC_TYPE (VARCHAR2, 30) — Document classification; documented values include DL, PELL, and COD.
• FULL_RESP_CODE (VARCHAR2, 30) — The complete response code returned by the COD system, used for error diagnosis and reconciliation.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY — Standard Who columns providing audit lineage.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent manager context identifying which EBS request and program generated or last modified the row.

Two LOB storage segments, SYS_IL0000402622C00002$$ and SYS_IL0000402622C00003$$, back the OUTBOUND_DOC and INBOUND_DOC CLOB columns respectively, both residing in APPS_TS_TX_DATA.

Common Use Cases and Queries

Applications and support teams use this table to trace the transmission history of intercompany and distribution documents, confirm receipt by COD, and troubleshoot integration failures. Because ACK_DATE is the acknowledgement timestamp, it is central to any reconciliation report that measures turnaround between SEND_DATE and confirmation.

• Confirm whether a given document was acknowledged: SELECT DOCUMENT_ID_TXT, SEND_DATE, ACK_DATE FROM IGF.IGF_SL_COD_DOC_DTLS WHERE DOCUMENT_ID_TXT = :doc_id;
• Identify documents sent but never acknowledged: SELECT DOCUMENT_ID_TXT, SEND_DATE FROM IGF.IGF_SL_COD_DOC_DTLS WHERE ACK_DATE IS NULL AND DOC_TYPE = 'COD';
• Report on response codes for failure analysis: SELECT FULL_RESP_CODE, DOC_STATUS, COUNT(*) FROM IGF.IGF_SL_COD_DOC_DTLS GROUP BY FULL_RESP_CODE, DOC_STATUS;
• Audit who or what last touched a document: SELECT DOCUMENT_ID_TXT, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID FROM IGF.IGF_SL_COD_DOC_DTLS;
• Measure COD acknowledgement latency: SELECT DOCUMENT_ID_TXT, (ACK_DATE - SEND_DATE) AS days_to_ack FROM IGF.IGF_SL_COD_DOC_DTLS WHERE ACK_DATE IS NOT NULL;

Related Objects

The documented dependency metadata classifies IGF_SL_COD_DOC_DTLS as standalone. It does not reference any other database object, and the only referencing entity documented is the APPS synonym IGF_SL_COD_DOC_DTLS, which exposes the table to the APPS schema for concurrent programs and forms. Consequently, there are no FK-to-PK join columns to report — the DOCUMENT_ID_TXT primary key is not carried as a foreign key into any child table. Related objects of interest therefore remain the APPS synonym, the COD integration interfaces and concurrent programs that write rows via the PROGRAM_ID and REQUEST_ID columns, and the COD/DL/PELL document generation logic in the IGF module. Queries into surrounding intercompany tables are typically matched on the DOCUMENT_ID_TXT value at the application layer rather than through database-enforced joins.