Batch Level Input XML Elements
The following elements are found in the <INDATA>
The <INDATA> element is defined as <INDATA version="X">, where X indicates the current compatibility version.
|
Element Name |
Type |
Req? |
Description |
|---|---|---|---|
|
<CALLING_SYSTEM_NUMBER> |
varchar2(100) |
No |
A pass-through element that contains a descriptor of the calling system sending the transaction. ONESOURCE Indirect Tax Determination supports two audit keys to enable the lookup of audit records. The two combinations are as follows: HOST_SYSTEM or MERCHANT_ID Configuration parameters can modify which keys are used and in which order. |
|
<COMPANY_ID> |
number |
No |
The internal Determination ID of the merchant. |
|
<COMPANY_NAME> |
varchar2(100) |
Yes* |
The name of the company running the transaction. ONESOURCE Indirect Tax Determination uses this element to apply the correct company-specific settings for the transaction. (*) Returned if EXTERNAL_COMPANY_ID is not populated. |
|
<COMPANY_ROLE> |
varchar2(20) |
Yes |
The role the company plays in a given transaction: Buyer (B), Middleman (M), or Seller (S). Each role results in different transaction tax and reporting requirements. |
|
<EXTERNAL_COMPANY_ID> |
varchar2(100) |
Yes* |
The unique identifier used by your business application to indicate which company to use in Determination. This identifier also distinguishes between different calling applications that may be used by your company. This element may be passed at the batch level or with each invoice, and is passed through to the Determination output and the audit tables. (*) Required if COMPANY_NAME is not populated. |
|
<HOST_REQUEST_INFO> |
structural |
No |
Contains pass-through elements used to identify the originating request from the ERP source. |
|
<HOST_REQUEST_ID> |
varchar2(100) |
No |
A pass-through element used to identify the document with the originating request from the ERP source. |
|
<HOST_REQUEST_LOG_ENTRY_ID> |
varchar2(100) |
No |
A pass-through element used to identify the originating request from the ERP source in log files. |
|
<HOST_SYSTEM> |
varchar2(100) |
No |
The name of the ERP instance sending the transaction. Determination supports two audit keys to enable the lookup of audit records. The two combinations are as follows: HOST_SYSTEM or MERCHANT_ID Configuration parameters can modify which keys are used and in which order. |
|
<PASSWORD> |
varchar2(16) |
Yes* |
Database user password used to validate the transaction submitter. (*) Required if the CALC_AUTHENTICATION_REQUIRED Configuration parameter is set to Y and a custom authentication scheme has not been implemented. If authentication is enabled, the password is subject to expiration. You can turn off expiration using the option Password Never Expires in the user setup. See |
|
<SCENARIO_ID> |
number(10) |
No |
This is an internal ID generated by Determination for Workbench scenarios. |
|
<SCENARIO_NAME> |
varchar2(100) |
No |
This is the name of the Determination Workbench scenario. |
|
<USERNAME> |
varchar2(60) |
Yes* |
Database user name used to validate transaction submitter. (*) Required if the CALC_AUTHENTICATION_REQUIRED Configuration parameter is set to Y and a custom authentication scheme has not been implemented. |
|
<XML_GROUP_NAME> |
varchar2(30) |
No |
The XML Group you want to use for the transaction. XML Groups determine those elements that Determination passes back to the calling application. If the XML group specified here is invalid (owned by the wrong company) for an invoice contained in the current XML transaction, the XML group specified for the company on that invoice is used instead. |
|
<XML_GROUP_OWNER> |
varchar2(100) |
No |
The company name associated with the XML group being used. This must be an ancestor of the submitting company or the company itself. Do not use slashes or characters in company names. |
|
<INVOICE> |
structural |
Yes |
The INVOICE and /INVOICE elements are structural. They serve as the container for an individual invoice. Each batch can contain multiple invoices. |