Condition type before CST/VAT calculation

Dear Friends ,
Is it possible to create a condition type which will get added only after excise duty calculation but before CST calculation.
If its possible kindly tell me how to go about it.
Regards,
DGN

Hi,
you will have to add an additional condition type in TAXINN procedure as "Freight Before Vat" , mantain it as statistical as it is only for calculation. and mantain FV11 for the same.
Further The same freight amount will also have to be entered in the PO pricing Procedure for Inventorization , payment etc.
first you have to make a tax condition type , make 2 , one as Value adn other percentage based. assign it to your tax procedure in steps which are before subtotaos: "Total excsie duty +cess" and "base for sales tax" , make sure to change the "to" part of base for sales tax .also make sure to tick these new conditions as statistical .Mantain FV11 for the Freight conditions.
The above config will only help you in calculating Correct Vat , this has nothing to do with PO pricing procedure. Freight will have to be entered in PO Pricing procedure normally as well.
Regards,
Vikas

Similar Messages

Quantity based condition type for excise duty calculation in tax procedure

Hi,
If any one has worked on the issue of excise duty calculation on Quantity of items purchased Quantity based condition type.
[<b>For a formula based calculation procedure TAXAU]</b>
Example : If quantity purchased = 10 units
Duty to be calculated @ Rs.3 per unit
Duty on the 10 units = Rs.30
Other than SAP Note 816835 any help is appreciable.
Thanks a lot,
Uma
Message was edited by: Uma

I could not find this condition type/Tcode in our client system.
Even we are on 4.6c.
Thanks,
Message was edited by: Uma

How are US tax condition types XR1 to XR6 calculated

i searched few forums to understand the ways of US taxes getting claculated particularly on condition types XR1 to XR6, is the value available in SAP system or is the percentage value maintained in the taxware or vertex system?
if in SAP where is this maintained, i could see the same input & output tax codes assigned in OBCL settings for many states in US, so i am not able to relate this in FTXP, as different states provide different calculation.
if it is maintained through external system, is there way we can check the values or see in the screen?, how is this link of checking the external system enabled, is it through 301 cal type & its associated function module,
will there be a chance to change this value from the user end or do we need to seek Taxware or Vertex assistance here.
sorry on too many questions.
just got confused with the way it works
Regards
Ilango

Hi Ilango,
Check my responses to your respective questions:
i searched few forums to understand the ways of US taxes getting claculated particularly on condition types XR1 to XR6, is the value available in SAP system or is the percentage value maintained in the taxware or vertex system?
In SAP, only Condition Type XR1 to XR6 are only condition which is responsible for computation of tax in US & Canada. Where, even condition types UTXD & UTXE are equally essential to this. These condition types used for external tax calculation.
if in SAP where is this maintained, i could see the same input & output tax codes assigned in OBCL settings for many states in US, so i am not able to relate this in FTXP, as different states provide different calculation.
Well, I don't think there much from SD side to explorer here. As Tax procedure hardly have any role to play in SD business process for tax rate determination. But, that is very significant from GL Account determination for respective Tax Transaction in SD.
Refer my posts on
Tax code and SAP SD - ERP Operations - SCN Wiki
Plant-wise Different Tax General Ledger Accounts - ERP Operations - SCN Wiki
Whereas, configuration for Non-Taxable transaction as maintained in TCode OBCL, generally comes in picture when Tax Jurisdiction is not maintained in respective Ship-to master. Based on that configuration system will determine Tax Jurisdiction for those Ship-to.
% are maintained in FV11, not in FTXP.
if it is maintained through external system, is there way we can check the values or see in the screen?, how is this link of checking the external system enabled, is it through 301 cal type & its associated function module,
301 is not the only Routine associated. As like UTXD & UTXE there respective routines 500(collect tax input - export to IVP) & 501(get tax output data - import from IVP) are equally important with others 301 to 306(Set tax values and percentage into condition structure and fill tax base amount based on FM GET_TAX_RESULTS_FOR_301_306)
Refer SCN Wiki Tax jurisdiction - ERP SD - SCN Wiki
will there be a chance to change this value from the user end or do we need to seek Taxware or Vertex assistance here.
Hope you are aware, these tax IVPs are tool that is used to calculate taxes for the US tax rules.Yes, you might need to ask respective Tax IVP.
In Taxware, it provides the tax jurisdictions codes for master data addresses in SAP. Based on combination of both tax jurisdictions, the Taxware product code and dates, Taxware returns rates and amounts of tax and which jurisdictions get the tax.
Hope that helps you. If you still have any specific question, do revert back.
Thanks, JP

Condition type for CST

All SAP Gurus,
Which condition type to be used for CST?
(for example as we use JMOP for excise duty).
Regards,

hi
check
JIPC Sales tax inv.
JIPS Sales tax setoff
u can get the list in http://help.sap.com/bp_bblibrary/600/html/J05_EN_IN.htm
hope it help
regards
kunal

Check dupciate condition type in PO pricing calculation schema

Dear Gurus,
In my PO priciing schema I maintain all the condition type manual.
I want to control the duplicacy while enter the same condition type.
Is there any solution to check the duplicacy.
Thanks in advance
With regards
Soumen

Dear Gurus,
In my PO priciing schema I maintain all the condition type manual.
I want to control the duplicacy while enter the same condition type.
Is there any solution to check the duplicacy.
Thanks in advance
With regards
Soumen

Excise,cst,vat calculation

Hi!,
Can any one send me the material regarding procedure /rules/regulations of our government for excise,cenvat availament, sales taxes,cst,vat in different scenarios...
I am new to taxes...
[email protected] or [email protected]
thanks in advance.
full points will be given,
ramesh B.
Edited by: Ramesh Balivada on Feb 12, 2008 7:20 AM

Dear Ramesh,
The rule for excise,cenvat availament, sales taxes,cst,vat vary from company to company, product to product within the same company. These inputs are correctly available from the client & we require to map the same accordingly. Incase of CST, it is 4% against 'C' form when product / material crosses the state boundary, but without 'C' form the LST / VAT will be applicable.
Regards,
Rajesh Banka

Condition Records For Tax Condition types for SAP 4.7

Dear Experts,
What is the procedure to maintain condition records for tax condition types like CST , VAT and Service Tax. We are not using CIN. In MM01 and XD02 tax classifications i have maintained UTXJ condition Type and also maintained the above mention tax condition types.. But when i create condition records for UTXJ in VK11 the sysytem is asking for Tax code. In FTXP when i defined Tax code A1 for Tax ProcedureTAXIN1 where i maintained all the Tax condition types there.But i am unable to save the Tax % in FTXP.When i try to save the tax code it is not saving.
Is there any other procedure to maintain Tax condition types for SAP4.7.
My Pricing procedure that i maintained in V/08 is Z00001.
Regards
Jyoti

Hi Jyoti
Since you are not using CIN, you can do the follwing for tax conditions
Check the assignment of the TAx procedure to country
once u do this , you will be able to maintin the vendor and customer records for MWST type for taxes
then create condition records for MWSt with access sequence MWST in condiution type or design one suited to your needs
alternatevely in the current procedure you can change access sequence for condition type UTXJ form the current one to MWST and then maintain condition records
hope this helps
thanks
Akasha

Tax not calculated in MIRO for the condition type JVCD

Hi,
We made some new different tax code and attached with JVCD , its calculating in PO but in MIRO calculation part not done but for other condition type ,JVRD,JVRN system calculating well...
Please tell me some way why not system calculating in case of JVCD and JVCN for capital case..
Thanks in Advance,
Dharmveer

Hi,
We totally agreed with you and already we checked our configuration part is OK.Actually we want to map some process where we captured excise in GR but no need to take credit i.e. to post the excise in J1IEX,so we do not have to post our cenvat/modvat entry in MIRO but we need to calculate VAT whether it is deductible or non deductible.So far this thing is concerned,we made separate tax code which we use at time of MIRO posting and in configuration we did not attached the tax code in logitics-basic excise -assign to company code. Because once we attached here , system asking to make to pass furst RG part2 entry then it allows to post MIRO entry which we do not want .So please understand this scenario is different and we got the success for JVRN/JVRD for VAT but getting issue in case of capital VAT where system does not calculate tax for JVCN/JVCD .....where we want to process MIRO without posting J1IEX..
Please thing and analyse ..give some helping response..
Thanks,
Dharmveer

MASS CHANGE OG CONDITION RECORD CST CONDITION TYPE

Dear SD experts,
Could anyone plzz suggest me how to change the condition type for CST from 3% to 2% .
There rae some 2500 records how to change it.
I had taken the key combination as
Country/Plant Region/Region.TAXC11Cust/tax mat
RegardsJAYANTH

Hi Manu;
At any given point in time you can have only one valid condition record with a validity period.
1. Create a condition record with validity from today to 12/31/2007
2. Create a condition record with validity from 01/01/2008 to ....
You issue would be solved.
Regards.

Condition type NAVS calculation

When i create PO's :
Condition type NAVS is been calculated as 0 for some PO's and for other PO's it gives value X.
Can somebody help where does the calculation takes place for this Condition type,
i tried searching for the existing routines for this condition type(m/08) bur there are no routines implemented for this.
Somebody please help me...
Regards,
Vnk.

Hi
I don't think it is basis related. Please ask in appropriate forum.
Regards,
Rajan

Cash discount in taxinn before cst

Dear Gurus, My client wants cash discount in taxinn. scenario is as follows
cash discount in betwen Cst and Excise duties as follows
Basic                                             =100
Excise such as BED and Hsess      =8.24
Total +Exc.Duties                             =108.24
Cash Discount                                    =2.24
Total for cst                                    =106
4%CST                                            =4.24
Tot PO                                            =110.24
For that in taxinn one condition is maintained before cst and calculation is ok as per invoice.
Problem is when we do MIRO , system shows amount difference.
Why this happening?
Any solution

You can try this workaround....
Create a condition type and assign it to purchasing schema and to this condition type use the subtotal for eg D, E etc in which you pass this value to some variable and in Taxinn procedure you can write routine in CalType which it will copy value from this variable and assign to this condition type.
With this you can enter the percentage in purchasing schema and this will flow in taxxin procedure.

Reg.Condition types required

Dear All
The below condition types are not in our Development system.
Where to get it. JMOP,JEC1,JVCS and JVRD
JMOP - Excise Duty
JEC1 - Cess
JVCS - CST
JVRD - VAT
Please help.
Thanks
Rajakumar

Yes,Every condition type doing different different calculations.
Therefore which condition type should be selected for CESS and ECESS. when I look for JEC1 and JSEP for CESS and ECESS. There is not available in condition type.
Please advise
Thanks
Rajakumar

Problem in VAT Calculation @ the time of MIRO

Dear All,
We are using the Tax Procedure TAXINN.
When we create a LIV document with ref to a PO using the transaction MIRO & when I check the calculate tax button, the tax amount which is displayed in the Basic data is more than the amount which is displayed in the taxes tab.
For Ex:
Created a PO with the following details.
Total Qty in PO - 10
Base Price - 1000/qty.
BED - 14% - 1400.00
ECS - 2% - 28.00
VAT - 4% - (4% on 11428) - 457.12
So my total Tax = 1885.12 (Including Excise & VAT).
Now when I create a MIRO document the tax amount which gets calculated when I check the Calculate button is 1885.12 (Same as above) in the Taxes tab of MIRO.
But the tax amount which is displayed in the Basic data tab is 1,942.24
Also when I simulated the MIRO entrys the VAT amount which was simulated was - 514.24 & not 457.12 as in PO.
Can anyone please advice on the reason for this mismatch in VAT calculation during the time of MIRO?
Is there any specific settings for VAT in TAXINN ??
Note :
The Excise & VAT are calculated correctly during the time of PO creation. Also I havent maintained any additional VAT condition types for my VAT in the tax procedure.
Awaiting helpful replies.
Regards,
Edited by: SAP FC on Dec 5, 2008 3:44 PM

Hi All,
Please note that when I removed the VAT condition type JVRD from the Classify condition types settings in IMG then the VAT amount which is calculated in the Basic data tab of MIRO is equal to the actual Tax amount as in PO (Excise + VAT ), but the amount which is displayed in the tax tab of MIRO is less.
Now if I maintain the Classify condition types settings in IMG for my VAT condtn type JVRD then the VAT amount which is calculated in basic data is more than both the PO as well as tax tab in MIRO.
Please note as you all have suggested I tried this after creating a new material & with the newly maintained condition records in FV11.
But still the issue persists..
If anyone have any idea. plz revert.
Regards,
Edited by: SAP FC on Dec 9, 2008 10:23 AM

Base amount condition type

please tell me how does system picks the value of base amount for the condition type BASB in tax calculation procedure.
as per my understadning system should pick this value automatically and should calulate differnt taxes on that
as atthe tim eof miro i am making use of some tax code but system is not picking the base amount for the tax code

hi,
these steps are following
1. define condition type t.code OBYZ
2. Define accounting keys        OBCN
3. define calculation procedure OBYZ
4. Assign tax procedure to country OBBG
5. Define tax codes                    FTXP
6. define tax accounts                OB40
tax calculation mention customer/vendor , PO, MIGO, MIRO,
sales order, billing documents,
before posting Assign to tax procedure to country.
calculation procedure example
under control data
steps     counter            condition type     from   to     A.keys
10            0                      BASB             -           -       -
100          0                       vs01               10                vs1
110          0                       vs02               100     110     vs2
same level
base acondition 10

AZWR condition type

Hi,
I would really appreciate it if someone could shed some light on the AZWR condition type. I have the following queries -
1) When the condition type AZWR is included in a pricing procedure, which account key should be assigned to it ?
2) Should AZWR be included in the pricing procedure that is determined for the downpayment request document (FAZ) ?
3) When AZWR is included the pricing procedure which is determined for the subsequent billing documents, what should be the sequence of the condition types in this pricing procedure including AZWR?
4) What role does AZWR play during the downpayment posting and clearing cycles (Tcodes - F-29 and F-39) ?
I would be most grateful if the above could be illustrated with examples.
Sri.

Hiya
Its a down payment condition type and to set it the following Customizing settings have to be made:
Settings for the billing plan To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) For the `received down payments and `down payment requests from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) For posting key 19, set the sales order as an optional field
Maintain the field status definition (transaction OB14) For field status variant 0001, field status group G031, set the
sales order as an optional field
Assign the company code to the field status variants (transaction OBC5)
Regards

Condition type before CST/VAT calculation

Similar Messages

Maybe you are looking for