Search Results iex_xml_request_histories




Overview
Explore in AI Chat

Overview

IEX_XML_REQUEST_HISTORIES is a table owned by the IEX schema within the Oracle EBS Collections (Advanced Collections / IEX) module. It stores the history of XML Publisher (XDO) output requests generated for Collections deliverables such as dunning letters, statements, and correspondence. Each row captures the parameters, status, and rendered document associated with a Collections correspondence request, providing an audit trail of letters produced and delivered.

Based on the FK topology mined from the schema, the table is heuristically classified as standalone, since it holds no foreign key dependencies on parent entities through mandatory linking columns alone but instead references multiple independent business entities. A Data Vault modeling suggestion would treat IEX_XML_REQUEST_HISTORIES as a satellite attached to transaction hubs for customer accounts, delinquencies, and query requests, recording the descriptive and status context of each XML output event.

Key Information Stored

The table contains 41 documented columns. Its surrogate primary key is XML_REQUEST_ID, which uniquely identifies each XML output request row. Business-key candidate unique indexes are documented as SYS_IL0000402263C00004$$, SYS_IL0000402263C00005$$, SYS_IL0000402263C00022$$, SYS_IL0000402263C00038$$, SYS_IL0000402263C00040$$, and SYS_IL0000402263C00041$$, corresponding to functional/LOB index segments rather than meaningful business columns.

Common Use Cases and Queries

Typical uses include auditing correspondence output, monitoring failed XDO requests, and rebuilding/reprinting dunning letters for a specific customer or delinquency.

  • List recent requests for a customer: 
    SELECT r.xml_request_id, r.status, r.document_type, r.creation_date
FROM   iex.iex_xml_request_histories r
WHERE  r.cust_account_id = :cust_account_id
ORDER  BY r.creation_date DESC;
  • Identify failures for follow-up: 
    SELECT xml_request_id, failure_reason, last_update_date
FROM   iex.iex_xml_request_histories
WHERE  status = 'ERROR';
  • Retrieve the rendered HTML document: 
    SELECT html_document
FROM   iex.iex_xml_request_histories
WHERE  xml_request_id = :request_id;

Related Objects

  • IEX_QUERY_TEMP_XREF — joined on QUERY_TEMP_ID; defines the query template template used to build the output.
  • HZ_CUST_ACCOUNTS — joined on CUST_ACCOUNT_ID; provides customer identity and account attributes.
  • IEX_DELINQUENCIES_ALL — joined on DELINQUENCY_ID; supplies the underlying delinquency driving Collections correspondence.
  • FND_XML_REQUESTS / XDO request metadata — the XML Publisher engine tables referenced through REQUEST_ID to trace the underlying concurrent request.
  • IEX_CUSTOMER_OUTPUT / Collections output views — downstream reporting constructs that surface this history in dashboards and delinquency workbench pages.