Invoice DTD elements that Oracle supports are presented in this section. These tables also show how the data elements map to columns in the Payables Open Interface tables.
The AP_INVOICE_INBOUND message map is used to populate the Payables Open Interface tables with invoice records based on data in a PROCESS_INVOICE_002 XML message. The following sections present details associated with that message map.
Note: Most data values are seeded.
XML Gateway Details:
| Parameter | Value |
|---|---|
| Message Map Name: | AP_INVOICE_INBOUND |
| Direction: | Inbound |
| (Internal) Transaction Type: | AP |
| (Internal) Transaction Subtype: | INI |
| External Transaction Type: | PROCESS |
| External Transaction Subtype: | INVOICE |
| DTD Directory: | ap/xml/oag721 |
| Map Directory: | ap/patch/115/xml/US |
| Message Maps XGM File Name: | apxmlinb.xgm |
Workflow Business Event System Details:
| Parameter | Value |
|---|---|
| Event Name initiated by the Message Map after the transaction is processed: | oracle.apps.ap.inv.invoice.recv |
| Event Subscription Name initiated by the Application after the transaction is processed: | no subscription in this version |
General Message Map Details:
| Parameter | Value |
|---|---|
| The Open Interface or API is initiated for the transaction by the Message Map: | No |
| Name of the Application Open Interface associated with validation of the entire transaction: | Payables Open Interface |
| Are levels expanded and/or collapsed in the Message Map: | Yes |
Target Detail Open Interface Tables:
| Table |
|---|
| AP_INVOICES_INTERFACE |
| AP_INVOICE_LINES_INTERFACE |
The following tables show values that default when the Payables Open Interface is populated.
Defaulted Columns:
| Defaulted Columns | Default Value, and Condition (if any) |
|---|---|
| AP_INVOICES_INTERFACE.INVOICE_ID | Assigned next sequence value |
| AP_INVOICES_INTERFACE.GROUP_ID | Assigned variable value from the XML Gateway Internal Control Number. |
| AP_INVOICES_INTERFACE.SOURCE | XML GATEWAY |
| AP_INVOICE_LINES_INTERFACE.INVOICE_ID | Assigned from corresponding header row |
| AP_INVOICE_LINES_INTERFACE.INVOICE_LINE_ID | Assigned next sequential value |
The following tables show values that are derived when the Payables Open Interface is populated. Note that import later derives some invoice values such as the accounts for Freight and Miscellaneous distributions. For details on values that import derives or defaults, refer to the Payables Open Interface Table Descriptions, Oracle Payables Reference Guide.
Derived Columns:
| Derived Columns | Default Value, and Condition (if any) |
|---|---|
| AP_INVOICES_INTERFACE.PAYMENT_METHOD | Derived from supplier site. |
| AP_INVOICES_INTERFACE.VENDOR_SITE_ID | The supplier (VENDOR_ID) and the operating unit (ORG_ID) are derived from the PARTY_SITE_ID in the XML envelope. |
| AP_INVOICES_INTERFACE.INVOICE_TYPE_LOOKUP_CODE | If the invoice amount is zero or positive then the value is STANDARD. If the invoice amount is negative then the value is CREDIT. |
| AP_INVOICE_LINES_INTERFACE.LINE_TYPE_LOOKUP_CODE | For INVLINE elements, LINE_TYPE_LOOKUP_CODE is "ITEM". For INVTAX.AMOUNT.TAX.T elements, the line type value is TAX. If INVCHARGE.CHARGETYPE is "Freight" then the line type value is FREIGHT. If INVCHARGE.CHARGETYPE is anything other than "Freight" then the line type value is MISCELLANEOUS. Note that the CHARGETYPE is not case sensitive. |
| AP_INVOICE_LINES_INTERFACE.TAXABLE_FLAG | Thisvalue is set to Y in two scenarios: -If the taxable flag is set to Y at the header then this value is set to Y for all Item lines. -This value is derived for Item lines only, and is based whether INVTAX is within INVLINE. The value is set to Y when tax should be prorated to the item. |
| AP_INVOICE_LINES_INTERFACE.LINE_NUMBER |
XSLTs are not provided in the Oracle transactions. You may add them to your own or modified Message Maps by invoking the Execute Procedure to Perform XSLT Transaction in the Message Map.
XML Style sheets must be stored in the directory that is defined in the Profile Option, if they are used.
The AP_INVOICE_INBOUND message map collapses the dataarea and the PROCESS_INVOICE and INVHEADER elements into AP_INVOICES_INTERFACE.
We do not use any data in the user areas.
The following table contains information about Invoice Header (INVHEADER) DTD elements and how they map to open interface tables.
For a text description of the following table, see: Text Description of the Invoice Header Table.
| Field/Data Type | Description/Comment | Payables Open Interface Table column (inbound) |
|---|---|---|
| AMOUNT.DOCUMENT.T -VALUE -CURRENCY | Qualifier needs to be "DOCUMENT" to be mapped. | AP_INVOICES_INTERFACE.INVOICE_AMOUNT AP_INVOICES_INTERFACE.INVOICE_CURRENCY_CODE |
| DATETIME.DOCUMENT | Qualifier needs to be "DOCUMENT" to be mapped. | AP_INVOICES_INTERFACE.INVOICE_DATE |
| DOCUMENTID | AP_INVOICES_INTERFACE.INVOICE_NUM | |
| DESCRIPTN | AP_INVOICES_INTERFACE.DESCRIPTION | |
| PARTNER.CONTACT.EMAIL | PARTNERTYPE needs to be "Supplier" to be mapped. If null, the email address will be derived from the trading partner setup. | AP_INVOICES_INTERFACE.VENDOR_EMAIL_ADDRESS |
The following table contains information about Invoice Charge (INVCHARGE) DTD elements and how they map to open interface tables.
For a text description of the following table, see: Text Description of the Invoice Charge Table.
| Field/Data Type | Description/Comment | Payables Open Interface Table (inbound) |
|---|---|---|
| AMOUNT.EXTENDED.T | Qualifier needs to be "EXTENDED" to be mapped. | AP_INVOICE_LINES_INTERFACE.AMOUNT |
| INVCHARGE.CHARGETYPE | If INVCHARGE.CHARGETYPE is "Freight" then the line type value is FREIGHT. If INVCHARGE.CHARGETYPE is anything other than "Freight" then the line type value is MISCELLANEOUS. Note that the CHARGETYPE is not case sensitive. | AP_INVOICE_LINES_INTERFACE.LINE_TYPE_LOOKUP_CODE |
| INVCHARGE.DESCRIPTN | AP_INVOICE_LINES_INTERFACE.DESCRIPTION |
The following table contains information about Invoice Line (INVLINE) DTD elements and how they map to open interface tables.
For a text description of the following table, see: Text Description of the Invoice Line Table.
| Field/Data Type | Description/Comment | Payables Open Interface Table (inbound) |
|---|---|---|
| AMOUNT.EXTENDED.T | Qualifier needs to be "EXTENDED" to be mapped. This is price x quantity. It does not include tax, freight or miscellaneous charges. | AP_INVOICE_LINES_INTERFACE.AMOUNT |
| OPERAMT.UNIT.T | Qualifier needs to be "UNIT" to be mapped. | AP_INVOICE_LINES_INTERFACE.UNIT_PRICE |
| QUANTITY.ITEM | Qualifier needs to be "ITEM" to be mapped. | AP_INVOICE_LINES_INTERFACE.QUANTITY_INVOICED |
| DESCRIPTN | AP_INVOICE_LINES_INTERFACE.ITEM_DESCRIPTION | |
| ITEMX | Currently used to identify PO line. | AP_INVOICE_LINES_INTERFACE.VENDOR_ITEM_NUM |
| UNIT | Code conversion needs to be consistent with trading partner. | AP_INVOICE_LINES_INTERFACE.PO_UNIT_OF_MEASURE |
| DOCUMNTREF.DOCTYPE | Not mapped, but for a purchase order, the DOCTYPE must be "PurchaseOrder". | |
| DOCUMNTREF.DOCUMENTID | Currently used to identify PO number. | AP_INVOICE_LINES_INTERFACE.PO_NUMBER |
| DOCUMNTREF.LINENUM | AP_INVOICE_LINES_INTERFACE.PO_LINE_NUMBER | |
| DOCUMNTREF.SCHLINENUM | AP_INVOICE_LINES_INTERFACE.PO_SHIPMENT_NUM |
The following table contains information about Invoice Tax (INVTAX) DTD elements and how they map to open interface tables.
For a text description of the following table, see: Text Description of the Invoice Tax Table.
| Field/Data Type | Description/Comment | Payables Open Interface Table (inbound) |
|---|---|---|
| AMOUNT.TAX.T | Qualifier needs to be "TAX" to be mapped. Always use TAX.T to submit tax information. Do not use TAX.TAX. | AP_INVOICE_LINES_INTERFACE.AP_INVOICE_LINES_INTERFACE.AMOUNT |