tax functionality

[Former Member]

hello experts,

i have searched the forum but not able to find any suitable answer,

i want to understand the process of tax determination in sales documents(w/o cin).

like i m trying to configure but no success.

this is what i am doing.

1.first maintain tax classification in customer and material masters

2.configure tax c.types and assign to pricing procedure.

3.create condition records for tax c.types

4.here is an error as i enter tax code. the error is as follows(Tax ID SD cannot be checked (there are several/no tax records)

-.how the system picks the value from the tax calculation procedure for example:taxinn or taxinj

here we maintain the tax code foreg : v6

my question is that how systems uses this tax code and how to do that

please help me

as this is the third times that i am posting the issue

but replies yet

thanks

mohit

[Former Member]

not answered

[huseyin_catalbas]

If you are using the tax code on a system different than where it is originally defined then it is probably because the transport of the tax code was not done properly. The transpor of tax codes requires manual post processing as explained in the corresponding IMG documentation given below.

-

---

Important note on transporting tax codes -> F1

Message no. F4 794

Diagnosis

Transporting tax codes requires manual postprocessing. This postprocessing is also necessary if tax codes have to be transported from one client to another within the system.

Procedure

When tax codes are transported, only the tax rates of the tax codes are transported.

The transport of tax codes between systems or clients is carried out in two steps:

1. step:

Export of tax codes from the source system or source client

2. step:

Import of tax codes into the target system or target client

Export

1. In Customizing for Financial Accounting Global Settings in the source system or client, select Tax on Sales/Purchases -> Calculation -> Define Tax Codes for Sales and Purchases.

2. Select Tax code -> Transport -> Export.

3. Assign the export to the corresponding transport order, and note the order number.

4. Select and save the tax codes to be transported.

5. Make sure that the tax codes selected are marked with the transport number in table T007V.

To check the table, from the R/3 initial screen, select Tools -> ABAP Workbench -> Overview -> Data Browser.

Enter the table name. The tax codes are in field MWSKZ and the tax jurisdiction codes are in fields TXJCD.

6. Carry out the transport into the target system.

To do this, from the R/3 initial screen, select Tools -> ABAP Workbench -> Overview -> Workbench Organizer -> Environment -> Customizing Organizer.

Import

1. Make sure that the tax codes to be transported are selected in table T007V in the target system or target client.

2. In Customizing for Financial Accounting Global Setting in the source system or client, select Tax on Sales/Purchases -> Calculation -> Define Tax Codes for Sales and Purchases.

3. Create the tax codes that do not already exist in the target system.

Create them complete, but without tax percentage rates.

If you set internal systems in company codes in the USA or Canada, the corresponding tax jurisdiction codes should also exist. You can make the settings for these in Customizing for Financial Accounting Global Settings under Tax on Sales/Purchases -> Basic Settings -> Define Tax Jurisdiction Codes.

4. Select Tax code -> Transport -> Import.

5. Check the proposed values for the transport order and country.

6. Carry out the import.

Notes for the transport of tax accounts

When you transport tax codes between different systems or clients, no tax accounts are transported.

Adjust the tax accounts in the source and target system (or source and target client) manually.

[claudia_neudeck]

Dear Mohit,

it seems to be that you get the message ID VK 242.

"Message VK242 is just an information message which doesn't affect the

pricing or tax

functionality directly. So in my opinion there isn't any need to

bypass this message. As I found out VK242 has been implemented to

support an end user in maintaining condition records and to avoid

inconsistencies between SD and FI tax customizing. This works perfectly

fine for all standard tax scenarios where the tax code is linked to

a FI tax rate directly. In case of internal or external tax

jurisdicition this logic works a little bit coarser because it's not

possible to check the whole SD and FI customizing in detail based at

that time given information. Hence the system just can 'sensitize' the

user that he should thoroughly customize his tax scenario."

For taxes please have a look into the notes 112609 and 400766, which explain the

tax rules.

Hope that the information are helpful.

regards

Claudia

[Former Member]

hello mam,

first of all thanks for ur reply

actually system is not copying the c.type value in the order after showing the message

thanks

mohit

[Former Member]

Hi Mohit,

The tax code which you are entering is it present in tcode FTXP , in the correct procedure , under OUTPUT TAX?

Also ensure correct GL account is assigned to the tax code

[Former Member]

thanks Mr.Trotsky for ur prompt reply

as mentioned in my thread refering to that,

i have maintained taxinn and tax code a1 i.e. standard

there are many c.types in this code for which do i have to maintain g/l,contuining on this how does the system get the c.type for this code for ex:- there r many c.types in this code how system uses which .c.types,when we assign this tax code in our tax condition record

thanks

mohit