Pricing Procedure condition tax apply on Subtotal

Hello Guru's,
I have an issue, while applying taxes on custom Pricing Procedure, The Scenario is to apply TAX on a sub total, It contains costFreightMiscellaneous expenses + --- XXXX etc,. , I have to collect 10% on the subtotal amount. Is there anyway in SAP to find 10% Tax on subtotal amount.will anyone guide me?. If it needs user exit will you guide me the procedure. It will be of great help.
Full points for the solution.

Hi PV
You can go for Alt calc type ,there we can write, the requirement what we need and that has to be put in the subtotal table
Reward if useful
Regards
Srianth

Similar Messages

MM Pricing procedure VS Tax procedure

Hi Gurus,
I have checked many thread here , but still can not find the answer.
Tax calculation procedure basically calculate the tax amount based on condition recaord maintained
(dor tis corresponding Condition type).
But we also can maintain Condition record for the condition type NAVS (pricing procedure) that bring tax amout into the pricing procedure of PO).
My question is why do we have to maintain Tax procedure as well as pricing procedure (regarding tax of course ).
Cheers Guys
Julien

HI
Basically why we have taxing procedure is that its always country specific that means it can be any vendor selling any material but he has to follow some government regualations whcih is what will be given in the taxing procedure that sholuld be the same for all customers it will be different if the customer is foreign.
the pricing procedure is where we carry out pricing that is customer specific here we can have different prices for different customers depending on what he buys and ETC.
hope this clarifies .
Regards
Vignesh

Pricing procedure(Condition technique)

Hi All
Can someone provide me all the configuration steps in pricing procedure in MM...

Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
Highlight it and double click the Control icon in the LHS screen.
We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
The detail description of each column is given below.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
System copies description of condition type from its description (V/06).
From and To:
1.From: This can be used as a base to the condition type for calculating further value.
1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
This is commonly used for condition types
SKTO - Cash Discount
VPRS - Cost (Moving average price/Standard Price).
Print:
The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex.,
For all Price condition types like PR00 etc. we assign ERL - Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
or
Hi,
Pricing Procedure in MM
The steps are:
SPRO->MM->Purchasing->Conditions->Define Price dertermination process
1. Define Condition Table:
2.Define Acces Sequence,
3.Define Condition Type,
4.Define Claculatin Schema,
5.Assign Calulation Schema,Acces Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organisation,
8.Assign Schema Group Of Vendor to Purchasing Organisation,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organisation and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
Edited by: MANI ROOPA SD/MM on Apr 17, 2008 8:44 AM

Pricing procedure and Tax Procedure.

Hi,
Can any body suggest, how to bring tax values in Condition, in Pricing procedure of MM. Now as per my settings Tax is coming under tax head and MM pricing prodcedure is coming separately, I need ,
Thanks & Regards
Sudhansu

Hi,
Did all you taxes in tax procedure in %!
No access sequence required for your requirement. Create a condition type as ZTFT & maintain
Cond. Class: D
Calculat.type: B
Cond.category: N
Keep BLANK access sequence filed & make it as item condition and then add this condition type in pricing procedure with logic just before calculation of TOTAL price.
Now do create PO with all taxes and now you can see all tax amounts in condition type ZTFT in PO Condition TAB( which flow from tax procedure to MM pricing procedure with a condition type ZTFT)
Regards,
Biju K

Pricing Procedure Condition Type EK02

Dear, Gurus
I have an MTO scenario. All is working I mean from the production order the cost is coming to my sales order in condition type EK02. But that is making all other condition types as inactive.
current pricing schema
Pr00 Price it is manual.
Other Z condition types which are also manual.
Then EK02.
Gross Sales
K005
K007
Net Sales
MWST
ZSED Sales excise duty
Value after Tax
VPRS
also, at the top the net value does not change at all it stays constant and seems to pick up the EK02 price.
I want all other condition types to be manual but active even if EK02 price is picked up from Production Order.
How can I set it up to make them all green as active?

Previously all my condition types were manual entry so all were green.
Pr00   manual
Zman manual
Zsat   manual
Zetc   manual
Also, in PR00 class is B=Prices       Calc Type = C for qty
All the ZMan, etc is A=discount/Surcharge   calc type=B fixed amount.
To be scenario all I added was condition type EK02 in pricing procedure and by standard it is in class B=prices     calc type=C for qty, and cond cat=costing
When production cost transfer to EK02 lets say example 500. All those previous cond are yellow inactive. and then net price equals 500!
In terms of my terminology and basic understanding you can only have one cond type function as price in class B=prices.
So either the EK02 or the Pr00 needs to have cond type B for Price. If I make the Pr00 a discount/Surcharge nothing changes in respect to updating the price in sales order. Lets say even if its all corrected and I have lets say EK02 function as price the Zman and Z condition types are under discount surcharge, that at least should not be inactive?
Please help
thanks

Pricing Procedure vs Tax Procedure

Dear all,
The scenario is as follows
My company purchase material from a trading company which imports the materials from other countries.
In PO we have maintained import pricing procedure so that we can take the duties paid by trading company during import.
We pay duties to the trading company.
Taxes are also involved in this.
I have created a pricing procedure for this seperate where there is a line with 'condition value' = total of
[ Net price of materialCustoms dutyCVD+ECS on CVD + SEC ECS on CVD + AED]
Now we all know tax should be calculated on this total amount.
In normal case the Net price will come as the base price for tax calculation which is here wrong.
I want this total amount to be the base amount for tax calculation in tax procedure.
What i need to assign in the pricing procedure against this 'total' so that it is taken as base amount for tax calculation
How to do this?
sapmmlearner

Hello,
As per your said scenario:
My company purchase material from a trading company which imports the materials from other countries.
In PO we have maintained import pricing procedure so that we can take the duties paid by trading company during import.
We pay duties to the trading company.
Taxes are also involved in this.
I have created a pricing procedure for this seperate where there is a line with 'condition value' = total of
Net price of materialCustoms dutyCVD+ECS on CVD + SEC ECS on CVD + AED
Now we all know tax should be calculated on this total amount.
In normal case the Net price will come as the base price for tax calculation which is here wrong.
I want this total amount to be the base amount for tax calculation in tax procedure.
What i need to assign in the pricing procedure against this 'total' so that it is taken as base amount for tax calculation
My question is if your company and your vendor /supplier (Is a trading company from where you are procuring the materials) are geographically located at the same place (such is within country in same place or within country at different places, etc)
means, then you should not worry about the Import duty. Because for you, when you procure the goods it should be treated as Inland/Domestic procurement (by the by your vendor, who is trading company procures materials from Abroad, that is his risk or his duty to pay the Customs duty or Importation clearing charges, etc since he is procuring from outside the country through Import procurement process, so don't worry for that).
Hence when you order the material through standard PO to your vendor (that is trading company), then Logically it must be Domestic pricing procedure (there is no involvement of import duties, importation, etc), that means system will pickup the Pricing procedure - Domestic - which consists of Gross price, and all other suitable pricing elements which are in currently used in your company (for the vendor) and part from the tax condition elements such as Basic excise duty (BED), SED, AED, Cess, etc... these are not part of the Pricing proceudre, but relevent to the Tax procedure. So which can be arranged in a sequential order for the Tax procedure - TAXINN - which is currently in use from any industry - for calculating the tax amount for the item that you procure from the supplier or vendor. And thats how you (your company) will pay the Duty or tax amount agains the goods that are procured from external source.
Please note: the tax caluclation is always based on the Base amount, not on anything else, that is based on the total ordered amount through the PO. And the tax amount is always interm calculated by adopting the suitable tax code in the PO (in item details), provided you have to maintain all these tax condition elements in a Condition records through FV11 t.code. then once the tax code (i.e., Input tax - which is tax on purchases) is adopted for the PO, system will pick all the valid condition records and sum the total tax amount in the PO.
Maintainaing of condition records is required, because the tax procedure which is a Condition based tax calculation procedure. hence you have to maintian the condition records as you said. Then it will calculate correctly.
Hope it clarifies,
Regards,
Sapsrin

Help needed-Regarding pricing procedure and tax inn configuration

Hello Friends
I have a new scenario in sap mm-
i have to do teh customizing in 2 days please guide me up.
my company SAY :A is in india imports material from parent company B in america.
This A company some times gets material from local vendors in mumbai. where VAT and CST comes into place.
we are using use tax INN configuration for this.
ther are Customs duty, there is no excise duty as everything is just imported., edu cess, CVD,and freight charges etc.
can you please decribe me in detail the pricing procedure required for my company A which is in india.
and the customization of TAXINN.
any information will be really helpfulbecause i am struck on creating condition types.
Help me SAP GURUS>>Please..u wil be my life saver..

Hi Aravind,
For domestic purchase Vat & CST are applicable. If it is intra state VAT is used & if it is interstate CST is used. These condition types have to be manitained in the TAX procedure.
JVRD - I/P VAT
JVCS- I/P CST.
we have maintained condition records for both these condition types along with the tax code in FV11. In the case of import purchase, you need to maintain seperate pricing procedure for import which will include ,
JCDB - BASIC CUSTOMS DUTY
JCV1-CVD
JECV-EDU CESS
J1CV- SEC EDU CESS
JEDB- IMPORT CESS
JADC- ADDITIONAL CUSTOM DUTY.
All these conditions will be available in PO item level & you need to maintain % for these conditions. Hope it helps.

Priceing procedure - condition type - number of units

Hi, I have a condition type in my pricing procedure. When I display item conditions for an item in a sales document I can see that my condition applies to 1000 units of measure. How do I change my condition so that the calculated amount applies to only 1 unit of measure?
Thanks

Hi Marko
Go to VK12 and change the UoM . Change the UoM and maintain the base unit of measure (ex:pc) that you have maintained in MMR . Provided you have not maintained Sales unit of Measure.
Also check wheather you have maintained any alternative UoM or not and that alternative UoM has been maintained in VK12 or not
Also check in V/06 in that condition type details wheather any UoM has been maintained or not. If it has been maintained then make the UoM feild blank by removing the UoM that has been maintained in V/06 and then check
Regards
Srinath

Pricing procedure for tax

hi all, i need some help.
in PO, i used my customized pricing procedure which is ZRBAPO.
the pricing procedure contain standard price , discount , and freight
ex :
price (PBXX) = 100 USD
disc (ZDIC) = 10 USD
freight (ZFRI) = 20 USD
total = 110 USD
standard system use 110 as base amount for tax (tax proc TAXID cond type BASB), but i only want determined base amount only from basic price and discount, which is the value is 90 USD not 110 USD.
how we achieve that req?
what's the relationship between pric proc ZRBAPO and TAXID?
Thanks
Best Regard,
Hendry

Hi Hendry,
In your customized Pricing procedure ZRBAPO, I suppose the tax condtion type used is "NAVS", pl check what is the "From reference step" that you have defined, it might be the step agaist the Total value of 110 USD,
Now you make a change in the pricing procedure, make a sub total after price and discount and use that step to calculate the tax condition, this should resolve your issue.
Regards
Merwyn

MM Pricing procedure - Condition type post to different GL account in MAP

Hi All,
We have a requirement for posting intercompany Stock transfer between Company A and B, and the transfer price will be Moving Average Price (say $ 100) + Mark up (say 25% i.e., 25) of supplying plant.
Created a new PO pricing procedure, and created a new Accrual condition type ZMRK for markup and made it statistical posting. Also in the pricing procedure the Condition type we assigned an Account key ZM1 and Accrual Key ZMA. we tried posting the Goods receipts in the receiving Company B, and it is posting the following entry :
Invetory A/C DR 125 (note: Account key ZM1 was not considered for debit account for markup)
GR/IR A/C CR 100
Markup Accrual A/C CR 25
REQUIREMENT: Our requirement is that the Mark-UP condition should not hit Inventory Account and should be debited to I/C Mark Up account (assigned to Account key ZM1) and entry should be as below:
Inventory A/C DR 100
Markup A/C DR 25
GR/IR A/C CR 125 (accrual is not required, if we can include the markup into GR/IR account)
OR
Inventory A/C DR 100
Markup A/C DR 25
GR/IR A/C CR 100
Markup Accrual A/C CR 25
NOTE: The Material is maintained as Moving Average Price and we dont want to add the Mark Up cost into the MAP of the receiving plant.
Please check and let me know if there is a way to do a condition type in PO pricing procedure to solve the issue of not hitting the inventory posting for condition record or any other way to handle this requirement.
Thanks in advance,
Surya

Hey surya,
I am also facing the same issue. Can you pls let me know whether you achieved this using any standard configuration.

Scaling in case of Pricing Procedure Condition Types

Hi,
I want to maintain Scaling in Condition Types of the Pricing procedure. Please guide me to maintain it.
Thanks & Regards
Saeed Arif

Hi,
If you have maintained Purchasing Info Record: In ME12 transaction go to Conditions tab. Select the Condition Type 'PB00' and click the Scales icon (F2) on top of the screen. Here, maintain the Scales.
First decide the Scale Type, Scale Basis and Validity periods for which you want to maintain the Scales. Save your changes and you can see the effect on Price, while creating the PO for the quantity mentioned as per the Scales.
Regards,
Narayana.
Edited by: Narayana Ghanta on Oct 13, 2008 3:43 PM

Pricing Procedure Conditions

Hello All,
I am new procing procedure, just studing now, i got the basic things how system searching for it. but one thing i want to know.
The condition types i added in Purchase info record, these condition types also found it in calcuation schema(i copied std one)
So can any one please tell me conditions maintained in Info record and also where we can maintain in PO also. How it works.. please tell me..

hi
the conditions u have maintained in inforecord is only for values for perticular condition
u can change them in condition tab of purchase order also u can add other conditions which u have not included in inforecord
refer following link
GR Printout
http://help.sap.com/saphelp_di46c2/helpdata/EN/dd/5616a5545a11d1a7020000e829fd11/frameset.htm
regards
kunal
award if helpful

Relation between Tax procedure and Pricing procedure

Dear All,
I would like to get more clarity on Tax procedure, Pricing procedure.
a) Why do we have Tax procedure and assigned to Country?
b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module? We are even creating lot of pricing procedure for Sales in SD module.
Regards
Manivannan R

Hi
Tax
During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
Tax codes are the link between pricing procedure and tax calculation procedure.
Pricing
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
Example
Example of a Pricing Procedure
If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
Pricing Procedures in the R/3 System
The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
Creating and Maintaining Pricing Procedures
You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
To reach the pricing procedure screen from SD Customizing:
1. Choose Basic Functions
2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

Link b/w Pricing Procedure & Tax procedure.

Hi all,
What is the link between Pricing Procedure & Tax Proceduere. In Tax Procedure how the Base ammount is picked from Pricing Procedure.

Hi,
Tax codes are the link between Pricing procedure & Tax procedure.
While creating Tax code (T-code FV11) we use condition types for VAT, BED, AED and others. Against these condition types we maintain percentage of taxes / duties.
THese tax codes are used in PO at invoice tab.
regards,
Anand

Pricing error: Mandatory condition Taxes via TTE (0TTE) is missing

Hello All,
For Complaint in CRM change in default item category gives the captioned error. The error is there for all Sales Organisations.
Any suggestion how this error can be removed.
Thanks & Regards,
DP

Hi PePe,
Thanks for the response. Yes in the pricing procedure condition 0TTE is mandatory. We use this pricing procedure in some other transactions where tax is calculated.
When we add an item (let say item 160) the defaulted item category does not result in any error , but when we change it to a different item category which is not price relevant this error pops up for item 110. Moreover this error disappears with some dummy change or with an Update price on Conditions tab.
We in fact tried to trace the TTE for different instances and it fails with an error "TTE processing terminated" which eventually results with error "Pricing error: Mandatory condition Taxes via TTE (0TTE) is missing" on the order.
Any suggestions what all needs to be checked and how this error can be diffused?
Regards,
DP

Pricing Procedure condition tax apply on Subtotal

Similar Messages

Maybe you are looking for