UMS1, UMS2, and UMS3 Tree Types You create a format tree of the tree type UMS* to be able to generate an advance return for tax on sales and purchases. The three tree types differ in how the data is summarized:
UMS1: No summarization; data is output per line item
UMS2: Summarization per tax code and/or transaction key
UMS3: Summarization based on how you have customized the output
All three tree types can be used to generate a DME file as either a flat file or an XML file; this is defined in the format tree. Below are further details about creating UMS* format trees and which program(s) you need to run to generate the corresponding output file.
You run the Advance Return for Tax on Sales and Purchases program; from the
SAP Easy Access
menu, choose
(or via Transaction SA38, program RFUMSV00). To create a file using an UMS1 format tree, choose the
Posting Parameters
button, then set the
Create DME File
indicator, specify which format tree the system is to use, and enter a name for the file that is to be created. Run the program, and the system generates a file.
To select and prepare the required tax data, you first run the Advance Return for Tax on Sales and Purchases program (RFUMSV00), but do not set the
Create DME File
indicator as above; instead, you must specify a program run date and an identification under
Posting Parameters
. Then, to generate the file (flat or XML), you run the DME File for Summarized Advance Tax Return program (RFUVXX00). Follow the same menu path as above, and choose
DME File with Summarized Tax Data
. To retrieve the data prepared by the prerequisite program, you need to enter the same program run date and identification. Refer to the program documentation for further details.
Because UMS2 and UMS3 offer summarized tax data, the format trees are constructed a bit differently, as described below.
UMS2
The UMS2 tree type enables you to summarize per tax code or transaction key. When you create an UMS2 format tree, the
source field inventory
consists of ABAP system fields and application-specific fields. The application fields (under
For UMS2
) include company code data, tax office data, and others, such as:
Transaction key (KTOSL)
Tax base amount (HWBAS)
Tax amount (HWSTE)
Tax on sales/purchases code (MWSKZ)
Assume, for example, that you work with tax codes A1 and A2, and you need to report postings of EUR 500 and EUR 200 for A1, and EUR 300 for A2. This example describes how to summarize the A1 postings as EUR 700 and A2 as EUR 300; if you do not summarize by tax code, the output of the tax amount will simply list EUR 1000.
To summarize the output as EUR 700 for A1, create a node
Tax Amount A1
, specify the source as structure RFUMS2_TAX_ITEM and field HWSTE, and assign a
condition
as follows:
Arg 1-1 |
Arg 1-2 |
Type |
Operator |
Arg 2-1 |
Arg 2-2 |
Type |
Operator |
|---|---|---|---|---|---|---|---|
RFUMS2_TAX_ITEM |
MWSKZ |
2 |
= |
’A1’ |
1 |
This condition instructs the format tree to take the tax amount value (EUR 1000) in field HWSTE and list that portion of it with tax code A1 in this field (EUR 700).
You then create another node,
Tax Amount A2
, with the same source structure and field; define the same condition, but with Arg 2-1 ‘A2’. In this case, the condition instructs the format tree to list that portion of the tax amount value which was posted with tax code A2.
You repeat this step for as many tax codes as you need to summarize by.
UMS3
The UMS3 tree type differs from UMS2 in that it offers you 99 base amount fields (BAS01-BAS99) and 99 tax amount fields (STE01-STE99), whereas UMS2 only offers one field each for the tax base amount (HWBAS) and tax amount (HWSTE). The advantage of UMS3 is that you do not need to create conditions to summarize by each of the tax codes. Instead, you define the summarization in Customizing and then map these values directly to the UMS3 format tree.
You configure the relevant settings in Customizing for
Financial Accounting
, under
Using the sample amounts above, assume you have to report postings of EUR 500 and EUR 200 for A1 and EUR 300 for A2. The sum of all A1 postings must be reported in field 6 on the tax form, and the sum of all A1 and A2 postings must be reported in field 10. In the
Group Tax Balances
activity, you specify the following:
Tax Code |
Description |
Transaction Key |
Group No. |
|---|---|---|---|
A1 |
16% output tax |
MWS |
6 |
A1 |
16% output tax |
MWS |
10 |
A2 |
20% output tax |
MWS |
10 |
Then, in your UMS3 format tree, you map the group numbers from the Customizing activity to the corresponding source fields. So, in our example, you create two nodes for each of the group numbers and assign the source fields BAS06 and BAS10, both from structure RFUMS3_TAX_ITEM.
Based on these Customizing settings and mapping to an UMS3 format tree, the output will be EUR 700 in field 6 and EUR 1000 in field 10.