Wants to design Pricing procedure

Dear Friends,
Can any one guide me which conditions type used for followings and how should take care of taxex
1) Basic Price
2) Less Discount @ 10% (Percentage Or value)
3) Less Additional Discount @ 1% (Percentage Or value)
Sub Total A
4) Add Excise Duty @ 10.30% (Includes ED 10% + 2% Edu Cess + 1% Higher Edu Cess)
Sub Total B
5) Add Packing & Forwarding / Insurance @ 1% (Percentage Or value)
Sub Total C
6) ADD CST/ST/VAT @ 12.5%
Sub Total D
7) Add Freight (Percentage Or value)
8) Grand Total
(All taxex ammount is added to material value)
Regards,
Mahesh

mahesh A wrote:
Dear Friends,
>
> Can any one guide me which conditions type used for followings and how should take care of taxes
>
> 1) Basic Price
> 2) Less Discount @ 10% (Percentage Or value)
> 3) Less Additional Discount @ 1% (Percentage Or value)
>
> Sub Total A
>
> 4) Add Excise Duty @ 10.30% (Includes ED 10% + 2% Edu Cess + 1% Higher Edu Cess)
>
> Sub Total B
>
> 5) Add Packing & Forwarding / Insurance @ 1% (Percentage Or value)
>
> Sub Total C
>
> 6) ADD CST/ST/VAT @ 12.5%
>
> Sub Total D
>
> 7) Add Freight (Percentage Or value)
>
> 8) Grand Total
>
> (All taxex ammount is added to material value)
>
>
> Regards,
>
> Mahesh
Hi Mahesh,
PO pricing and Tax Code maintenance are two separate procdures. For calculation procedure for your PO conditions you have to use a procedure (Either RM0000 or copy of it) and make use of the conditions to calcuate your PO price.
If you have VAT/CST for a calculated amount from the PO, then you have to configure the TaxCodes as per your requirement in FTXP, maintain condition record in FV11 and so on. You can use TAXINN for your TaxCode maintenance.
Before you configure a pricing procedure, make an excel sheet which calculates exactly like your SAP system to help you proceed more clearly and confidently.
Anything pls revert
Shiva

Similar Messages

Want to change Pricing Procedure in the sales order

Hello
I have created a sales order. It has RVVVV9 as pricing procedure. Now I recognise that the pricing procedure in the order is wrong due to incorrect CUSTOMER PRICING PROCEDURE in Customer Master data. Now I changed the CUSTOMER PRICING PROCEDURE in Customer Master data to correct one which will give me the correct pricing procedure(RVVVV8) in the sales order. But I can see that the sales order still has old Pricing Procedure even after updating the cust master data with the correct CUST PRICING PROCEDURE.
I have maintained the pricing procedure determination correctly.
would appreciate your quick response.
//Venkat

Have you checked "Assign document pricing procedures to order types"?
check also ovkk, there is a combination of sales org, distrubtion chanel, division, document pricing procedure and customer pricing procedure. Make sure you have make the right combination.
Regards,
Gunadi

Whta is the standard pricing procedure in CIN INDIA

i want to take a standard pricing procedure ,so what is the standard pricing procedure in CIN INDIA
i want to include the condition like
<b>base price
maximum retailing price
customer discount
material discount
excise duty
VAT
educational cess
additional cess duty</b>
i want to know what should be the customer pricing procedure
and document pricing procedure

hi,
pl use TAXINN. Remaining as usual.
TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
Tax Code: A1
Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A2
Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
Tax Code: A1
Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
Tax Code: A2
Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
Specify the conditions in the sales order that are used for excise rates.
Specify the countervailing duty condition type used for import purchase orders.
Regards,
Rajesh Banka
Reward points if helpful.
Rajesh Banka
Posts: 1,308
Questions: 7
Registered: 11/21/06
Forum points: 1,800
   Re: Taxinn tax procedure settings in SD pricing
Posted: May 6, 2007 11:34 AM    in response to: Sunil Kumar Garg       Reply      E-mail this post
Impact on Pricing Procedure & Condition Record:
Another Important difference between TAXINJ & TAXINN is that in TAXINJ along with formula in Tax Code, you also have to maintain condition record & there are 2 condition types for Basic Excise duty & similarly other excise duties. in one condition you maintain the actual excise duty % & in other you main as 100%, which will be a copy of actual excise duty. But in TAXINN, instead of 2, you require to maintain only one condition type for each excise dity like JEXP for Basic Excise duty & similarly for other excise duties. You require to design pricing procedure accordingly.
source forum thread :
<a href="https://forums.sdn.sap.com/click.jspa?searchID=2814520&messageID=3397693">source thread</a>
thanks.
Sadhu Kishore

Urgent: How to bring the same pricing procedure in reversal order??

Hi,
We have recently implementated CIN at our client location. For the orders present in the system before CIN implementation, when we are creating the reversal orders, system is bringing the new pricing procedure with CIN condition types?
Can we bring the same pricing procedure in the reversal order as in the sales order?
Please advise urgently.
Regards,
Peeyoosh.

Dear Peeyoosh
I am unable to understand from your comments
"For the orders present in the system before CIN implementation, when we are creating the reversal orders"
Please let me know how do you reverse a sale order. To my knowledge, we can reverse delivery and billing but not sale order. Either we can close the sale order by assigning some reason for rejection or delete the sale order.
This being the case, please let me know why you are reversing and how you are reversing. If you want the same pricing procedure for both normal sales and returns, then maintain the same pricing procedure for both document types.
thanks
G. Lakshmipathi

Pricing Procedure (Debit Memo)

I have a pricing procedure at oder level let suppose ABC, I made delivery and billing all is well till that.
Than if delivered quantiy is less than the target quantity client will suppose to create a debit memo sort of penality to the customer, reference to that invoice quantity confirmation source is POD.
My debit memo pricing procedure is different from ABC, mean a PROO and MWST is appear on that not other charges or condition type.
I have assign the procedure at debit memo sales document type but what happen when in VA01 give the reference of invoice and copy the item the whole same (ABC) pricing is came up on the order (Debit Memo Request) which is not required I want the actual procedure will call.
If after this i directly go to the billing document after approval of this document my actual pricing procedure is there, but a different condition type is present in the 2nd pricing procedure that will not come, so I manually press the "Carry out new pricing" so that condition type than will appear..
Hope my gurus understand the problem. I want that actual pricing procedure is available at order if not that all the condition type will appear at the time of billing. I cant set the carry out new pricing setting in the copying control because if i done this the whole condition type of order will aappear at billing as well.
if have any query please feel free to ask.
Regards,

Dear W,
I have a pricing procedure ABC having following condition types
1. PR00
2. ZSED
3. ZWEH
4. MWST
sales to order above procedure work and i got the accounting documents and invoice.
My 2nd pricing procedure is XYZ for Debit Memo and assign on document type, have th efollowing steps.
1. PR00
2. MWST
3. ZHE1
4. ZHE2
when i create debit memo with reference to invoice at debit memo (Sales document type) the pricing procedure ABC is come automatically, and when I go to billing the actual pricing procedure is come, plus i have to press maullay carry out new pricing button, other wise the common condition type is came at billing, if in copying control if i by default maintain the carry ou tnew price system duplicate the condition types.
Hope you will now understand my issue and give any value added feedback for the resolution of hte issue.
Regards,

Different pricing procedure in delivery

Dear All,
In STO scenario we are sending material from mfg plant to Depots, Sales area defined for STO 1001,20,PP where till now we have used only one pricing procedure in Delivery(NL) & Billing (F8), but due to business requirement we want maintain different pricing procedure for different divisions (02,03,04,05). But due to sales are are same we are not able to determine different pricing procedure in delivery. Plz advice how I can achieve this.
regards,
sps.

Hi S P Shukla,
First of all pricing procedures are determined on the following basis or you can say determination rule
Sales Area + Customer Pricing Procedure + Document Pricing Procedure=Pricing Procedure
here document pricing procedure is for the sales document type here you can use delivery document type procedure,which is an indicator i believe is in the document type configuration.
Revert if helpful
Mohit Singh

Wrong Pricing Procedure getting picked up in Value Contract

While creating Value Contract, when we maintain conditions, the condition type which we want to maintain are missing.
During a year, PO is made a for a value of around 15 crores. So we need to make contract which will pick up the same pricing procedure which is picked up for all those PO's. The pricing procedure was specially created for these PO's.
Now while we create contract it should pick up that same pricing procedure which it picks up in the PO.
The vendor, material & Purchase Org is same in our contract as it is there in the PO.
So I feel when we create a contract it should pick the same pricing procedure as it does for PO's, but our contract picks some other pricing procedure.
what is the configuration to be done specially for Value contract.
Regards,
Karthik

Hi,
The pricing procedure is determined differenetly for contract & PO .
For PO, pricing procedure is determined by the Vendor Schema Group and Purchase Org Schema Group.
But in case of Contract the pricing procedure is based on condition supplements of condition type PB00.
Condition type PB00 is considered as master condition type in case of Pricing procedure of contract.
In std SAP contract system picks up RM0001or RM1001 because these pricing procedures are maintained in the Condition Supplements of PB00.
If you want to have pricing procedure other than RM0001 or RM1001 then you need to maintain that pricing procedure in the Condition Supplement of condition type PB00.
Regards

New pricing procedure for invoice correction

Hi ALL,
We want a new pricing procedure during invoice correction request.
Scenario:When we execute a sales order ,create a delivery & create a billing docuemnt with z@1111 a pricicng procedure.
Now we want to create an invoice coreection with different pricicng procedure Z@0002.
can any one help!!!
Regards,Rajneesh

Maintain a new Document Pricing Procedure in Invoice correction request. This will help in determining new pricing procedure based on assignment in T.Code: OVKK.
Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

How to design a Pricing Procedure with both MWST and MWSI in it ?

Hi there.
My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
I know that One pricing procedure can only be assigned to 1 Document Type. So,
Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
regards
Poo

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful.

I want to keep two price in one pricing procedure can it be possibl;e

i ve two price in my pricing procedure
wen i m giving the price of second one first one is comming inactive
so how to configure and shuting out this problem
please help me GURUs
with hope
subrat

like this
basic price @36.11 for 300unit is 10833
MRP @117 for 300units 35100
MRP price after [email protected]% 23341.50
Total basic price 10833
assesable price after abatement 23341.50
assesable value 10833
excise duty on MRP after abatement@16% 3735
CESS on excise duty @2% 75
CESS duty for secandary higher education@1% 37
total net sales 14680
sales tax [email protected]% 1835
total value 16515

Want to updated sales pricing procedure through quotation

Hello Friends,
In general scenario: we update any condition type in vk11 tcode and tht is reflected in quotation pricing.
my requirement : while creating quotation if the user changes any price for any condition tht should automatically get updated in pricing procedure for tht particular condition type.
pls suggest how it is possible??
Regards,
Sunny

Hi Sunny,
you can write exit in VA21 to update the sales pricing .
Thanks & Regards,
Devalla T Kumar

Rebate fixed amount condition in the pricing procedure

Hi SD Gurus,
i'm using rebate fixed amount conditions (Lum sum).
The situation from a business point o f view is the following: i pay the customer 1000$ once he made something.
This kind of condition is not relevant for accruals since they have to be built manually (manual accrual). As a consequence i'm note sure if this condition shoul be put in the pricing procedure used for invoices. In the other and for sure this condition should be inserted in the pricing procedure for manual accrual/credit note.
What is your point of view!!
Thanks
C

if you are going to use Rebate, then there is no need to add condition type in standard pricing procedure, if you have designed your pricing procedure, include condition types for rebates as in standard pricing procedure.
This condition type is linked to Rebate type.
I think you first try the scenario in IDES and then do the same settings as per yoru requirement.
If you want step-by-step procedure for rebates will help you
Please refere the thread
rebate documentation
Regards
Jitesh

Subtraction in the pricing procedure.

Hello Friends,
I have requirement as follows:
I have two steps in the pricing procedure. One has a condition type and the other does not. Now my requirement is to subtract the condition price of step 1 from the condition price of step 2 and display it as the condition price for step 3 which has no condition type.
I have been suggested to create a new routine in vofm and assign that in the pricing procedure.
Is there any otherv way of doing this?
If not, how we design the code to get the values from the structure KOMV for the field KWERT for different steps to calculate and update in the rpicing procedure?
Can u please guide me.

and display it as the condition price for step 3 which has no condition type
In SD, unless you have a condition type, you cannot show it as a pricing since it has an impact in FI via Account Key and G/L Account assignments. Please explain more about the Business Process and how you want to capture. Dont go for VOFM and all when the process can be configured via standard.
G. Lakshmipathi

Required information on Subtotals in Pricing Procedures

Hi All,
I want more information on Subtotals assignment in pricing procedure,
I am designing a new pricing procedure and I have assigned all necessaty condition types , requiremtns, Account keys etc but I am not getting a proper total. For that I need sub total assignment
My pricing procedure is as below
Cond A---- 100$
Mat Value ===   Same a Cond A value                        what will be Subtotal ?
Cond B------ 20$
Cond C         30$
Cond D         10$
Value Add == Cond BCD                                         what will be subtotal ?
List Prise= Mat Value + Value add                              what will be subtotal ?
Cond E------ 10$
Discount                                                                      What will be subtotal?
Cond F------ 10$
Tax                                                                             what will be subtotal?
All conditon will be totla value
Total -
say 200$                                          what will be subtotal ?
Regards,

I hope you are aware of:
Subtotal is
u2022 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/vendor discount or the cost of a material) are stored.
u2022 If the same fields are used to store different condition amounts, the system totals the individual amounts.
u2022 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.
For Gross Price, it can be 1or 9.
For Net Value, it can be 2/3.
For Total, it can be A.
For Statistical value, it can be C
For Cash Discount, it can be D.
For Freight, it can be 4.
For rebate, it can be 7.
For Cost or internal price, it can be B.
For Tax refer JFACT-IN:Factory sale with formula, std pricing procedure.
Thanks & Regards
JP
Thanks & Regards
JP

Problem in pricing procedure of scheduling agreement

Dear All,
I am creating a scheduling agreement, when i am giving condition type at item level a message occur "Condition type XXXX is not in procedure A M ZB1002" Message no. VK045.
I am not able to understand from where this pricing procedure is picking. But in Define Schema Determination the pricing procedure is different, it is ZBLOSR.
The same case is happening in info record while maintaining condition type, the same pricing procedure ZB1002 is picking up by default. I want to change the pricing procedure.
Please help.....

hi..
have u maintained the combination of schema group for vendor schema group, purchasing org and pricing procedure...
and assign this vendor schema group to vendor master...
From this combination system getch the pricing procedure for particular vendor...
go to spro..MM ..Purchasing..Condition...Define Price Determination Process..Define Schema Group..
check these settings...
Hope it works..
Thanks..

Wants to design Pricing procedure

Similar Messages

Maybe you are looking for