Results for “tp_source_table”

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

Overview

The AR_DOCUMENT_TRANSFERS table, owned by the AR (Receivables) schema, stores information about the transfer of documents to trading partners. It is a transactional log that records outbound document submissions and the corresponding acknowledgements received from external partners, most commonly through Oracle EBS's e-commerce gateway infrastructure. The table forms part of the Receivables module's electronic document exchange capability, tracking which business documents (such as invoices, credit memos, and debit memos) were sent, to whom, and with what outcome.

From a Data Vault modeling perspective, the metadata's foreign-key relationships suggest classifying this object as a link. Two distinct foreign keys reference ECX_DOCLOGS, indicating that AR_DOCUMENT_TRANSFERS sits between a source Receivables entity (identified by SOURCE_ID and SOURCE_TABLE) and the ECX document logging infrastructure. This is a classic transactional-link pattern connecting multiple hubs rather than a descriptive satellite.

Key Information Stored

The surrogate primary key is DOCUMENT_TRANSFER_ID. Two unique indexes define business-key candidates: AR_DOCUMENT_TRANSFERS_U1 on DOCUMENT_TRANSFER_ID, and AR_DOCUMENT_TRANSFERS_U2 on the composite (SOURCE_ID, SOURCE_TABLE), which identifies the originating Receivables document.

The most significant columns include:

• SOURCE_ID / SOURCE_TABLE — identify the originating business document and its source table.
• TP_SOURCE_ID / TP_SOURCE_TABLE — identify the corresponding trading partner document reference.
• DOCUMENT_MSGID — foreign key to ECX_DOCLOGS, linking the outbound message record.
• CONFIRMATION_MSGID — foreign key to ECX_DOCLOGS, linking the partner's acknowledgement or confirmation message.
• STATUS — current state of the transfer (e.g., submitted, confirmed, failed, rejected).
• EVENT_NAME — the business event that triggered the transfer.
• ECX_TRX_TYPE / ECX_TRX_SUBTYPE — the e-commerce transaction classification.
• ECX_PARTY_TYPE — the party role in the exchange.
• EMAIL_ADDRESS — destination address for the document transfer.
• EXCEPTION_TYPE / EXCEPTION_MESSAGE — failure diagnostics when a transfer does not complete successfully.
• REQUEST_ID — concurrent request associated with the transfer.
• LAST_SUBMISSION_DATE — timestamp of the most recent submission attempt.
• APPLICATION_ID / RESPONSIBILITY_ID — context of the concurrent process executing the transfer.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical reporting scenarios include monitoring outbound document delivery status, diagnosing failed partner transmissions, and reconciling Receivables documents against their confirmed acknowledgements. A common query joins AR_DOCUMENT_TRANSFERS to ECX_DOCLOGS on both message IDs to retrieve payload or error detail. For example, a status report by source document might select SOURCE_ID, SOURCE_TABLE, STATUS, and LAST_SUBMISSION_DATE filtered by EVENT_NAME or ECX_TRX_TYPE. Failure analysis queries filter on EXCEPTION_TYPE IS NOT NULL to surface transfers requiring remediation. Trading-partner audit reports group records by EMAIL_ADDRESS or ECX_PARTY_TYPE to measure delivery volumes and success rates over time.

Related Objects

• ECX_DOCLOGS — referenced twice (via DOCUMENT_MSGID and CONFIRMATION_MSGID); the central document log holding XML payloads and processing status.
• AR_DOCUMENT_TRANSFERS_PK — primary key constraint on DOCUMENT_TRANSFER_ID.
• AR_DOCUMENT_TRANSFERS_U1 / U2 — unique indexes establishing the business keys.
• RA_CUSTOMER_TRX_ALL — typical value of SOURCE_TABLE, holding Receivables transactions.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to trace the submitting concurrent program.
• FND_APPLICATION / FND_RESPONSIBILITY — resolve APPLICATION_ID and RESPONSIBILITY_ID context.
• ECX_OUTBOUND_LOGS / ECX_INBOUND_LOGS — related gateway tables providing additional transfer telemetry.