This appendix provides the mapping for the XML messages used in the XML Invoices process.
For more information about sending XML messages, that contain Receivables documents, to customers, see: XML Receivables Documents, Oracle Receivables User Guide.
Related Topics
Process Invoice XML Message Map
The XML invoices process uses the Open Applications Group Process Invoice DTD called 171_process_invoice_002.dtd (version 7.2.1).
The following table shows you the mapping between Receivables database columns and the elements of the Process Invoice XML message for the invoice header.
| INVHEADER | Target (XML) | Source |
|---|---|---|
| AMOUNT.DOCUMENT.T.VALUE | AR_XML_INVOICE_V.amount | |
| AMOUNT.DOCUMENT.T.CURRENCY | AR_XML_INVOICE_V.currency_code | |
| DATETIME.DOCUMENT | AR_XML_INVOICE_V.trx_date | |
| DOCUMENTID | AR_XML_INVOICE_V.trx_number | |
| PAYMETHOD | AR_XML_INVOICE_V.payment_method | |
| PARTNER.NAME | AR_XML_INVOICE_V.supplier_name | |
| PARTNER.PARTNERID | AR_XML_INVOICE_V.supplier_code | |
| PARTNER.PARTNRTYPE | Supplier | |
| PARTNER.PARTNERIDX | AR_XML_INVOICE_V.supplier_code | |
| PARTNER.CONTACT.NAME | AR_XML_INVOICE_V.salesrep | |
| PARTNER.CONTACT.EMAIL | AR_XML_INVOICE_V.salesrep_email | |
| DOCUMNTREF.DOCTYPE | AR_XML_INVOICE_V.document_type | |
| DOCUMNTREF.DOCMENTID | AR_XML_INVOICE_V.reference_number | |
| DOCUMNTREF.PARTNRID | AR_XML_INVOICE_V.supplier_code | |
| DOCUMNTREF.PARTNRTYPE | Supplier | |
| one or more | PYMTTERM.AMOUNT.DISCNT.T | AR_XML_PAYMENT_TERMS_V.discount_amount |
| one or more | PYMTTERM.DATETIME.DISCNT | AR_XML_PAYMENT_TERM_V.discount_date |
| one or more | PYMTTERM.DATETIME.DUE | AR_XML_PAYMENT_TERMS_V.due_date |
| one or more | PYMTTERM.DATETIME.PYMTTERM | AR_XML_PAYMENT_TERMS_V.term_start_date_effective |
| one or more | PYMTTERM.DESCRIPTN | AR_XML_PAYMENT_TERMS_V.term_decscription |
| one or more | PYMTERRM.TERMID | AR_XML_PAYMENT_TERMS_V.term_name |
| one or more | PYMTERRM.USERAREA.AMOUNT | AR_XML_PAYMENT_TERMS_V.due_amount |
The following table shows you the mapping between Receivables database columns and the elements of the Process Invoice XML message for the invoice charges.
| INVCHARGE | Target (XML) | Source |
|---|---|---|
| zero or more | AMOUNT.EXTENDED.T | AR_XML_INVOICE_CHARGE_V.charge_amount |
| zero or more | CHARGETYPE | AR_XML_INVOICE_CHARGE_V.line_type |
| zero or more | DESCRIPTION | AR_XML_INVOICE_CHARGE_V.description |
| zero or more | LINENUM | AR_XML_INVOICE_CHARGE_V.line_number |
The following table shows you the mapping between Receivables database columns and the elements of the Process Invoice XML message for the invoice lines.
| INVLINE | Target (XML) | Source |
|---|---|---|
| AMOUNT.EXTENDED.T | AR_XML_INVOICE_LINE_V.line_amount | |
| OPERAMT.UNIT.T | AR_XML_INVOICE_LINE_V.unit_selling_price | |
| QUANTITY.ITEM | AR_XML_INVOICE_LINE_V.quantity | |
| LINENUM | AR_XML_INVOICE_LINE_V.line_number | |
| DESCRIPTN | AR_XML_INVOICE_LINE_V.description | |
| ITEM | AR_XML_INVOICE_LINE_V.item.description | |
| ITEMX | AR_XML_INVOICE_LINE_V.item | |
| UNIT | AR_XML_INVOICE_LINE_V.uom | |
| DOCUMNTREF.DOCTYPE | AR_XML_INVOICE_LINE_V.line_type | |
| DOCUMNTREF.DOCUMENTID | AR_XML_INVOICE_LINE_V.reference_number | |
| DOCUMNTREF.PARTNRID | AR_XML_INVOICE_LINE_V.supplier_code | |
| DOCUMNTREF.PARTNRTYPE | Supplier | |
| DOCUMNTREF.DOCTYPE | PurchaseOrder | |
| DOCUMNTREF.DOCUMENTID | AR_XML_INVOICE_LINE_V.po_number | |
| zero or more | INVCHARGE.AMOUNT.EXTENDED.T | AR_XML_INVOICE_CHARGE_V.charge_amount |
| zero or more | INVCHARGE.CHARGETYPE | AR_XML_INVOICE_CHARGE_V.line_type |
| zero or more | INVCHARGE.DESCRIPTION | AR_XML_INVOICE_CHARGE_V.description |
| zero or more | INVCHARGE.LINENUM | AR_XML_INVOICE_CHARGE_V.line_number |
| zero or more | INVTAX.AMOUNT.TAX.T | AR_XML_INVOICE_TAX_V.tax_amount |
| zero or more | INVTAX.AMOUNT.TAXBASE.T | AR_XML_INVOICE_TAX_V.taxable_amount |
| zero or more | INVTAX.QUANTITY.PERCENT | AR_XML_INVOICE_TAX_V.tax_rate |
| zero or more | INVTAX.DESCRIPTN | AR_XML_INVOICE_TAX_V.description |
| zero or more | INVTAX.LINENUM | AR_XML_INVOICE_TAX_V.line_number |
| zero or more | INVTAX.TAXCODE | AR_XML_INVOICE_TAX_V.tax_code |
The message map for the Confirm_BOD XML message used by the XML Receivables Documents feature is Confirm_BOD (XML - XML, Inbound) and the DTD is 002_confirm_bod_004.dtd.
The Confirm BOD has two control areas. One has the information for the Confirm BOD. The second is an exact copy of the control area from the Process Payment XML message. The second control area provides the context of the Confirm BOD.
The following table shows the mapping of the Confirm BOD XML message.
| CONFIRM | Source (XML) | Value | Target (PLSQL) |
|---|---|---|---|
| STATUSLVL | 00: Success 10: AR Invoice Failure |
AR_CONFIRMATION.initiate_confirmation_process.P_STATUS | |
| DESCRIPTIN | |||
| ORIGREF | AR_CONFIRMATION.initiate_confirmation_process.P_ID. ar_document_transfers.document_transfer_id:ra_customer_trx.customer_trx_id:ra_customer_trx_lines.customer_trx_line_id Passed from Receivables to your customer's Payables system. |
||
| zero or more | CONFIRMMSG.REASONCODE | AR_CONFIRMATION.initiate_confirmation_process.P_REASON_CODE | |
| zero or more | CONFIRMMSG.DESCRIPTN | Invoice InvoiceLine CreditMemo CreditMemo Line DebitMemo DebitMemo Line |
AR_CONFIRMATION.initiate_confirmation_process.P_DESCRIPTION |
This feature has certain limitations. They include the following:
You can only send invoices, debit memos, credit memos, chargebacks, and deposits as XML documents.
To disable the delivery of XML invoice documents to a customer, you must remove the customer's bill-to site from the Trading Partner Setup window in XML Gateway.