SAP ABAP IMG Activity TTEC_DT (Define Tax Event Determination)
Hierarchy
☛ SAP_AP (Software Component) SAP Application Platform
   ⤷ AP-TTE (Application Component) Transaction Tax Engine
     ⤷ AP_TTE_CONFIG_C (Package) Transaction Tax Engine ( Configuration )
IMG Activity
ID TTEC_DT Define Tax Event Determination  
Transaction Code S_A4C_68000101   (empty) 
Created on 20020806    
Customizing Attributes TTEC_DT   Maintain Decision Tree 
Customizing Activity TTEC_DT   Maintain Decision Tree 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name TTEC_DT    

Use

Rules for tax event determination are defined in this activity with the use of a decision tree.

A decision tree is a set of logically connected statements, that is test questions. Test questions are either Value Comparison or Parameter Comparison Tests. These test questions are evaluated to determine whether they are true or false, and this process leads to one of the following outcomes:

  • An additional Value Comparison or Parameter Comparison Test such as Is this a sale?
  • A Result, such as Domestic Acquistion.
  • An Error Condition, such as No Tax Event Can Be Determined, when insufficient information is available to determine a result.

SAP supplies decision trees for the following countries

Country (ISO Code)   

  • CA
  • CH
  • DE   
  • EU   
  • JP
  • UK
  • US   

If possible, use the decision tree that corresponds to your business process as a template. Make sure that you make your own copy of this tree and save it under a different name. In this way, you retain the tree contained in the standard as a template and avoid the risk of any modifications that may affect tax event determination. Furthermore in the event of legal changes an updated version of this tree will be supplied. Repeat this progess so that you always have a proper, clean template on which to base your own trees.

Requirements

To configure the decision tree type to your requirements, you must select or create a field catalog variant in the IMG activity:

Define Decision Tree Variant Fields.

Standard settings

The decision tree type for tax event determination is derived from the field catalog, ttevc_dt_adm. This field catalog is included in the standard delivery and is not modifiable.

Deletion

The following options are available:

Decision Tree -> Set as Deleted

Decision tree still appears in the table ttec_dt but cannot be copied. The version of the deleted tree has been retained for auditing purposes.

Decision Tree -> Delete from Database

Decision tree is completely removed from the database.

When you are developing a decision tree and have several historic versions that are no longer needed, you can delete them as described.

  1. Choose Tree Directory.
  2. Select the relevant decision tree.
  3. Choose Decision Tree -> Delete Historic Versions

This will delete all versions of the decision except the latest one, regardless of its Release status.
Note
Do not use this function on productive trees.

Activities

Copying a Decision Tree

SAP supplies

To copy a decision tree that has been created for one country/tax community to another country/tax community:

  1. Choose Execute.
    2. You branch to the screen Maintain Decision Tree.
  2. Choose the decision tree that you want to copy.
  3. Choose Utilities -> Extras.
  4. Choose Copy Decision Tree to Other Country.
  5. Enter data as required.

Creating a Decision Tree

  1. Choose Execute.
    2. You branch to the screen Maintain Decision Tree.
  2. Enter a Tree ID and Description.
  3. Assign a field catalog variant. This is a prerequisite.
  4. Enter the Valid-From Date.
    5. Note

A decision tree must be released before it is available for tax event determination, even if the Valid-From Date is in the past. See the final step.

  1. Enter Decision Tree Origin.
    2. This is optional but recommended as it allows entry of the person or department responsible for the decison tree, which is useful if questions arise.
  2. Choose Create.
    3. In the tabstrip Targets, the Target Parameters, Tax Event, Tax To Role, and Tax From Role appear. The Target Parameter Context containsTax Event and Taxable Country. Target parameters are parameters that can be inserted as Results. Additional ones can be defined as required. See Additional Information for more details.
    In the tabstrip Notes, the user can enter information that may be useful for knowledge transfer.

On the left area of the screen, two nodes appear:
The decision tree "branch" that contains the Decision Tree Field Description.
The initial decision tree node for maintaining either a Parameter or Value Comparison Test.

  1. Right mouseclick the initial decision tree node to insert a value comparison test or parameter comparison test, as required. See Additional Information for more details.
  2. Maintain Value, Parameter Comparison Tests, Results or Errors, as required.
  3. Choose Save.
  4. Choose Decision Tree -> Release to release the decision tree. Only a released decision tree can be used for tax event determination.
  5. Choose Decision Tree -> Check to validate settings. The results of this validation are displayed in the column Status, and details are in the tabstrip Messages.

Follow-On Activities

Choose:

Validate Customizing Settings
and
Simulate Tax Determination and Tax Calculation
to test Customizing settings.
For Customizing update, choose Immediate Customizing Refresh.

Additional Information

Before creating a decision tree, it is important to differentiate between a value comparison test and a parameter comparison test:

Function: Insert Value Comparison Test

Value comparison tests are used to evaluate test questions when a static test is required. In static tests, the value of one parameter is compared to the value of one or several parameters that are explicitly listed.

The following fields are used for testing the value comparison test:

  • Test Parameter: parameter that is being tested
  • Test Parameter Context: uniquely identifies the test field
  • Parameter Value
  • Comparison Value: value against which the test parameter context is tested

    Example

    The following question is evaluated using a Value Comparison Test:

    Concern liable for tax?

  • Test Parameter:
    • Business Partner Taxability (Data Element: TTET_Partner_taxability_typ)
  • Test Parameter Context
    • Country Role (Data Element: TTET_Country_Role)
    Parameter Value ST (Ship-To)
    Partner Role (Data Element: TTET_Partner_Role)
    Parameter Value ST (Ship-To)
  • Comparison Values
    • 100 (Company)

    In common language, this question Concern liable for tax? can be stated as follows:

    If the test parameter Business Partner Taxabiliy with the context fields Country Role with the Value ST and the Partner Role with the value ST has the value 100 (company) then the statement Concern liable for tax is true.

Function: Insert Parameter Comparison Test

Parameter comparison tests are used to evaluate test questions when a dynamic test is required. In dynamic tests, the value of one parameter is compared to the value of one other parameter.

The following parameters are used for testing the parameter comparison test:

  • Test Parameter: parameter that is being tested.
  • Test Parameter Context: uniquely identifies the test parameter.
  • Test Parameter Value: value of the test parameter context.
  • Comparison Parameter: parameter against which the test parameter context is tested.
  • Comparison Parameter Context Field: uniquely identifies the comparison parameter against which the test parameter context is being tested.
  • Comparison Parameter Value: uniquely identifies the value of the comparison parameter against which the test parameter value is being tested.

    Example

    The following question is evaluated using a Parameter Comparison Test:

    Domestic Delivery?

  • Test Parameter:
    • Country (Data Element: TTET_Country)
  • Test Parameter Context
    • Partner Role (Data Element: TTET_Partner_Role)
    Parameter Value OA (Order Acceptance)
  • Comparison Parameter
    • Country (Data Element: TTET_Country)
  • Comparison Parameter Context Parameter
    • Partner Role (Data Element: TTET_Partner_Role)
    Field Value ST (Ship-To)

    In common language, this question Domestic Delivery? can be stated as follows:

    If the test parameter Country with the context parameter Partner Role with the parameter value OA is the same as the comparison parameter Country with the context parameter Partner Role with the parameter value ST then the statement Domestic Delivery? is true.

Function: Insert Result

Tax events that are determined are entered as results. The result comprises:

  • Result Parameter Context: uniquely identifies the result field.
  • Result Parameter Values

    Example

    For the tax event: Swiss Import Tax, the result would appear as follows:

  • Result Parameter Context
    • Taxable Country
    Parameter Value CH (Switzerland)
  • Result Parameter Values
Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG TTEC_DT 0 AEC0000481 Transaction Tax Engine 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
TTEC_DT T - Individual transaction object TTEC_DT  
History
Last changed by/on SAP  20021202 
SAP Release Created in 400