TransEditor Groups CSV Format
This type of import enables you to quickly load TransEditor Groups. Each group contains individual TransEditors, which contain Conditions and Actions. It is possible to import “blank” TransEditors (with no Conditions or Actions) if you want to quickly create a number of TransEditors that you can then later modify.
TransEditor Groups are created as Checked Out with a start date of today. Once the group is imported, you need to view the data in Determination to verify the accuracy of the import, create the appropriate start and end dates for the group, and check it in.
TransEditor Group imports are intended to import new groups, not modify existing groups. You cannot, for example, add an editor to a group. You can only import a complete group, then modify it as desired in Determination.
For information about using CSV format files, see Best Practices for Importing Data with CSV Files
To specify a reference list in a TransEditor, you must create the TransEditor on the Conditions tab of TransEditors page. You can include a reference list in the CSV file so that Determination can identify when a reference list referenced.
In Determination, you specify a reference list on the Conditions tab of the TransEditor page. Click the Reference List radio button and then select the reference list you want to use from the drop-down list.
The Operator field automatically switches to EXISTS IN. If you want to exclude the values in the reference list, select NOT EXISTS IN from the drop-down list.
TransEditor Groups File Format
TransEditors consist of IF/AND/OR statements and parent/child relationships, resulting in complex logical statements. Restrictions on logic are imposed on the import file. The following restrictions apply:
- The logic statement IF (A or B) AND (C or D) THEN is not valid TransEditor logic. This statement must be rewritten as: IF (A AND (C OR D)) OR (B AND(C OR D)) THEN.
- You cannot nest OR statements within each other. An (OR) cannot contain a second (OR).
- The logic must be unambiguous. For example, you cannot list a mix of ANDs and ORs with no parentheses, and each open parenthesis must have a matching close parenthesis in the appropriate location.
- If you enter a math expression in the Element field, the upload will not validate the expression. When you view the TransEditor in the UI, you will need to correct any failing expression before you save the data and leave the page.
SDITYPE=TransEditors |
|||
---|---|---|---|
Column Name |
Format |
Req? |
Description |
GroupName |
varchar2(100) |
Y |
Name of the TransEditor group. |
EditorName |
varchar2(100) |
Y |
Name of the TransEditor. |
ParentName |
varchar2(100) |
N |
Name of the editor's parent. If specified, the editor must have been listed earlier in this import file. Can be null if the editor exists at the top level in the group. Note that the ParentName cannot be the same as the EditorName for this line. |
Condition |
varchar2(5) |
Y |
Valid values are IF, AND, OR, and THEN. IF starts a condition. AND and OR are used when there is more than one condition for an editor. |
Open |
varchar2 |
N |
Parentheses. Valid values are zero or more left parentheses: ‘ ( '. Each open parenthesis must have a matching close parenthesis in the file. |
Element |
varchar2(250) |
Y |
Name of an XML element. For example. INVOICE.SHIP_FROM.COUNTRY or a math expression. For information about the limitations, see Using ONESOURCE Indirect Tax Determination TransEditors in Help. |
Operator |
varchar2(15) |
Y |
Valid values are the following:
THEN conditions can only use the equals symbol (=). |
Constant |
varchar2(250) |
Y * |
A constant value.
(*) Use either the Constant or the ValueElement field, but not both. |
ValueElement |
varchar2(250) |
Y * |
An XML element, or a math expression subject to the limitations described in the math section of the Help topic Using ONESOURCE Indirect Tax Determination TransEditors.
(*) Use either the Constant or the ValueElement field, but not both. |
ReferenceList |
varchar2 (250) |
Y * |
Reference list name.
(*) Use only one of the Constant, ValueElement, or ReferenceList fields. |
Close |
varchar2 |
N |
Close parentheses. Each open parenthesis MUST have a matching Close parenthesis in the file. |
Comment |
varchar2(1000) |
N |
A comment about the GroupName. Only the first comment in the group gets imported. |
Example TransEditor Groups File
This file creates a group containing two editors. The first has a single condition and action. The second has multiple conditions and a single action:
-
sdiType=TransEditors
-
GroupName,EditorName,Condition,Open,Element,Operator,Constant,Clo
se,Comment -
OFCGroup,TE1,IF,,INVOICE.SHIP_TO.STATE,=,CT,,Derive Country from
State/Province -
OFCGroup,TE1,THEN,,INVOICE.SHIP_TO.COUNTRY,=,US,,
-
OFCGroup,TE2,IF,(,INVOICE.SHIP_TO.PROVINCE,=,AB,,
-
OFCGroup,TE2,OR,,INVOICE.SHIP_TO.PROVINCE,=,BC,,
-
OFCGroup,TE2,OR,,INVOICE.SHIP_TO.PROVINCE,=,MB,,
-
OFCGroup,TE2,OR,,INVOICE.SHIP_TO.PROVINCE,=,ON,),
-
OFCGroup,TE2,THEN,,INVOICE.SHIP_TO.COUNTRY,=,CDN,,
For more information about formatting a CSV file, see Creating CSV Import Files.
TransEditor Groups Import Prerequisites
This type of import imposes no prerequisites before using the Import/Export Wizard.
TransEditor Groups Import Options
When importingTransEditor groups, the Import/Export Wizard prompts for Company Selection. Select the desired company.
Once the group is imported, you need to view the data in Determination to verify the accuracy of the import, create the appropriate start and end dates for the group, and check the group in before using it.