Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-MI (Application Component) Migration⤷
RE_MI_CL (Package) RE: Migration RE Classic => RE-FX
IMG Activity
| ID | REFXMIV_TIVEXTAXMAP | Specify Tax Code |
| Transaction Code | S_XEN_65000036 | (empty) |
| Created on | 20050726 | |
| Customizing Attributes | REFXV_TIVEXTAXMAP | Assign Tax Code to RE Tax Type and Group |
| Customizing Activity | REFXV_TIVEXTAXMAP | Assign Tax Code to RE Tax Type and Group |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXMIV_TIVEXTAXMAP |
Use
In Classic RE, the FI tax code is entered on the contract. In RE-FX, however, the tax type and tax group are entered on the contract. You can enter the tax code, in addition, as time-dependent data.
In the Propose Conversion Decisions for Customizing step, the system analyzed which tax codes occur in contract conditions in Classic RE. The system entered these tax codes in the table.
For these tax codes, you enter the tax type and tax group that you want to appear on the contract.
It is mandatory that you define a separate tax group for each tax code. Otherwise the contracts cannot be copied properly.
Based on the settings you make here, the system generates all other Customizing settings for taxes (such as, reverse assignment) in the Convert Customizing step, as well as generating the application data in the Convert Dataset step.
The following entries are predefined in the system. You should use these entries if possible.
- Tax Type:
MWST - Output tax
MVST - Input tax - Tax Group:
NONE - No tax
HALF - Half tax rate
FULL - Full tax rate
For example, if you need tax rates for old tax groups, then you have to define these first in the Create Tax Groups IMG activity.
Requirements
Standard settings
Activities
Example
The following tax codes existed in your contracts in Classic RE:
A0 - Output tax 0 %
A5 - Output tax 15 %
A6 - Output tax 16 %
V0 - Input tax 0 %
V1 - Input tax 16 %
From this, the system generates an entry for each of these in the table being processed. Each entry contains the country and the valid-from date of January 1, 1900. The Valid-To Date is blank. Do not change the valid-from and valid-to dates. Assign the following in the Tax Type and Tax Group columns:
A0 - Tax Type: MWST, Tax Group: NONE
A5 - Tax Type: MWST, Tax Group: OLD5
A6 - Tax Type: MWST, Tax Group: FULL
V0 - Tax Type: MVST, Tax Group: NONE
V1 - Tax Type: MVST, Tax Group: FULL
In this case, you now only need to create tax group OLD5 in Customizing. If the tax rate changes later, then you can make this change in the table by assigning the new tax code in the Transformation Table. The contracts still have tax group FULL, but the resulting tax code is then a different one.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
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 |
| V_TIVEXTAXMAP | V - View | SM30 |
History
| Last changed by/on | SAP | 20050726 |
| SAP Release Created in | 600 |
