VAT Transport Sapnote 0000052852

7/22/2019 VAT Transport Sapnote 0000052852

http://slidepdf.com/reader/full/vat-transport-sapnote-0000052852 1/4

04.11.2010 Page 1 of 4

SAP Note 52852 - Transporting tax codes between systems

Note Language: English Version: 39 Validity: Valid Since 29.11.2000

Summary

Symptom

Unable to transport tax codes between systems or to load tax rates in

target system using RFTAXIMP.

Additional key words

FTXP, RFTAXIMP, Tax, 00347

Cause and prerequisites

N/A

SolutionThere have been questions from customers regarding the new 3.0 function for

transporting tax codes between systems. Essentially, the new function is

the creation of tax codes in the target system based on tax codes in the

source system. Note 13528 explains that the tax codes themselves are

contained in transportable tables (T007A and T007S), but that the actual

tax rates appear in condition tables (A003, A053, KONH, KONP) that cannot

be transported due to the number assignment (KONH-KNUMH and KONP-KNUMH are

sequential numbers). The following procedure contains all the details

required to successfully transport the tax codes between systems. Please

pay careful attention to each step.

PROCEDURE:

1. Before transporting the tax rates, the tax codes and, if necessary the

jurisdiction codes (eg. USA, Brazil), must be in the target systems.

These are contained in tables T007A and TTXJ (Transaction OBCP),

respectively.

2. Since program RFTAXIMP in step 7 below will submit Transaction FTXP

internally in batch input mode, we recommend that you first check that

nobody else is blocking FTXP at the time RFTAXIMP is running. You can

check this using Transaction SM12, table name RSTABLE, enqueue key

T007A* or T007S* or T030K* while RFTAXIMP is running.

3. In your source system, export the tax codes you want to transport to

the target system as follows:

a) Run Transaction FTXP (Maintain Tax Code).

b) Enter the COUNTRY you want to work with -> Press ENTER.

If the country does not have jurisdiction codes, screen 101 will be

displayed with the country entered. Otherwise, screen 102 will be

displayed with the country entered and a validity date. In both

cases, all other fields are blank.

c) Execute Tax code -> Transport -> Export.

d) Create a new transport request and note its number.



04.11.2010 Page 2 of 4


e) Select the check box in front of each tax code you want to

transport.

f) Save your entries.

Note that the jurisdiction structures are not copied during the export

they are in table TTXJ and must be copied separately.

4. In your source system, search table T007V for the number of the

tranport request generated in step 3d to ensure that the marked tax

codes have been loaded.

If you don't find the corresponding entries in table T007V, refer to

Note 99173.

In some cases, not all selected tax codes are included in table T007V.

In such a case, heed Note 136363.

5. Release the transport request created in step 3d using Transaction

SE10 and transport the tax codes and tax rates into your target systemusing program r3trans.

6. In your target system, search table T007V for the number of the

tranport request generated in step 3d to ensure that the tax rates

have been transported.

Any value in that table relating to P30 or S11 originated from the

Walldorf development systems and should be disregarded.

7. In your target system, run program RFTAXIMP with the correct transport

number. (To do that, you should use Transaction SE38 if you are using

a release lower than 4.0A. Otherwise, you can also start RFTAXIMP from

Transaction FTXP -> Tax code -> Transport -> Import. For more details,

refer to Note 95088.)

To ensure that the correct transport number is being used, view table

T007V using Transaction SE17. You can also verify that the right

country has been used. The person running RFTAXIMP must have authority

to run batch programs. If you have problem at this step, refer to

Notes 38466 and 98483.

8. The success of the transporting process can be verified using

Transaction FTXA or reviewing tables A003 (without jurisdictions),

A053 (with jurisdictions), KONH and KONP using Transaction SE17.

OTHER ISSUES:

o The systems environment must be set usually to changeable (table

T000) or Transaction SCC4 (activate the 'Changes w/o automatic

recording' field) since customizing tables are being transported.

To check the status of your system, use report RDDIT097 which is

accessible only by a DDIC user, or use Transaction SCC4.

If you wish to prevent changes being made to the system, refer to

Note 110970. If Note 110970 has not been implemented, and the

system status is "non-modifiable", the tax codes cannot be

imported, and the system issues error message 00347 "Field

KONP-KBETR (1)2 is not an input field".

o When the tax codes are imported, the percentage rates are only



04.11.2010 Page 3 of 4


added or overwritten in the target system, but not deactivated.

For example Tax code XY, Country DE.

Source system | Target system | After the transport

AccKy Tax percent. | AccKy Tax percent. | AccKy Tax percent.

| |

MWS 15,000 | MWS 10,000 | MWS 10,000

VST 10,000 | VST | VST 10,000

VST | VST 20,000 | VST 20,000

NVV 1,000 | NVV | NVV 1,000

VST | VST | VST

ESA | ESA | ESA

ESE | ESE | ESE

This missing function is provided by Note 126597.

o The user must have authorization that allow update in Transaction

FTXP (SAP_ALL).

o If you want to import the tax codes using the same effective dates

as in the source system, you will need to make the following change

in program LF82VF00. This is also covered in Note 45461. Once

installed, the effective date of the source system will always be

passed to the target ystem.

Activate (remove the *) the line which reads:

PERFORM BDC_FIELD USING 'RF82T-DATAM' I-T007V-DATAM.

All of the above steps should enable you to successfully transport tax

codes between systems. If it does not, call Customer Support.

Header Data

Release Status: Released for Customer

Released on: 28.11.2000 23:00:00

Master Language: German

Priority: Recommendations/additional info

Category: Consulting

Primary Component: FI-GL-GL-F Value Added Tax (VAT)

Secondary Components:

FI Financial Accounting

The Note is release-independent

Related Notes



04.11.2010 Page 4 of 4


Number Short Text

1149815 FTXP Transport tax code with jurisdiction code: Date missing

1009266 Tax code transport - message F4794

711008 Norway: Legal change as of 01.03.2004

616045 FI/LO Enhancements for Russia

332049 Import of tax codes is incorrect

136363 Transport of tax codes. MWSKZ is missing in T007V

126597 Transport of tax codes (deactivation of lines)

110970 Transport of tax code/system has status ?not changeable?

99173 FTXP: Table T007V is not supplied with data

98483 RFTAXIMP: Import of old transport requests

95088 Error when importing tax codes

Documents

VAT Transport Sapnote 0000052852