Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

Transactions

TransEditor components

TransEditor typically has 4 components:
  • Name
  • Hierarchy
  • Conditions
  • Actions

Name

Each TransEditor must have a name. The name you enter for a TransEditor should be unique and descriptive.

Hierarchy

During transaction processing, Determination evaluates transaction data against TransEditors according to this list. (The 1st TransEditors in the list's read and applied before the 2nd TransEditor in the list's read and applied).
TransEditors can be connected to one another with AND and OR operators. Connecting a TransEditor with AND establishes a parent-child relationship. In this relationship, the parent TransEditor's at a greater level than the child TransEditor. During transaction processing, the parent TransEditor must evaluate to true before any child TransEditors get evaluated.
In the
EDITORS
 list, a parent TransEditor is identified with a plus or minus icon, and each child TransEditor's hierarchically listed beneath the parent TransEditor.
TransEditors connected with OR establish an alternative. For example, you may want to evaluate the ship-to address based on the city or the ZIP Code. With OR, either TransEditor must evaluate to true before further evaluation or action's taken. For child TransEditors that are connected with OR, the parent TransEditor must evaluate to true before the child TransEditors are evaluated.
You can nest connected TransEditors to create deeper levels (for example, you can create an AND+AND+AND scenario). You can also mix AND and OR connectors for TransEditors (for example, you can create an AND+(OR+OR) scenario).

Conditions

Conditions test whether transaction data meets certain criteria. Conditions are sometimes referred to as if clauses because, if the conditions specified in the TransEditor match the transaction data then the actions specified in the TransEditor are taken on the transaction. If the conditions don't match, no action's taken. Typically, TransEditors include conditions and actions. You can, however, have TransEditors that have:
  • No conditions but 1 or more actions. This indicates that the actions are always performed. For example, you may want a TransEditor to set the line level ship-from location to Warehouse 1. In this scenario, the TransEditor has no conditions and only 1 action.
  • 1 or more conditions but no actions. This is common in AND scenarios. For example, you may want a TransEditor to evaluate the customer number and the line level ship-to state before further address evaluation occurs. In this scenario, the TransEditor has 2 conditions: 1 to evaluate the customer number and 1 to evaluate the line level ship-to state.
You can also connect conditions to other conditions with AND and OR. Connecting conditions with AND establishes a parent-child relationship, and connecting conditions with OR establishes an alternative. On the TransEditors page, child conditions have a number depth of the parent condition. For example, Condition 1 is the parent. Condition 1-1 is the 1st child condition and Condition 1-2 is the 2nd child condition.
During processing, a parent condition must evaluate to true before the child condition's evaluated. Conditions connected by OR evaluate to true if either condition evaluates to true.
Like TransEditors, you can nest conditions to deeper levels, and you can mix AND and OR connectors for conditions.

Actions

Actions (or results or outcomes) set the value for an XML element when the conditions of a TransEditor evaluate to true.
The value can be:
  • A constant. For example, an action can set the line level CUSTOMER_NUMBER to 123.
  • The value for another element. For example, an action can set the line level IS_EXEMPT.ALL to true.
  • The value of an element after it's modified by a math expression. For example, an action can set the line level GROSS_AMOUT to GROSS_AMOUNT+USER_ELEMENT.ATTRIBUTE1.

Reorder actions in the TransEditor

The
Reorder
 feature lets you reorganize actions within the TransEditor interface. You can access this feature when multiple actions are present.
  1. Go to the TransEditor interface.
  2. Select
    Reorder
     to open the
    New Location
     window.
  3. Select the new location for the action from the dropdown list.
    Reorder
     now becomes active. If no new location is selected, an error message states "Action is required."
  4. Select
    confirm
     and process the reorder request. A success message "Actions reordered successfully" appears when you are done.

This article applies to:

  • Product: ONESOURCE Determination, ONESOURCE Indirect Tax