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

Similar Messages

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.

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

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

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(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 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

About the pricing procedure of purchasing order

Hello friends,
can anyone tell me about the pricing procedure,conditions & texation of Purchase order?
and hoew to maintain all those term in Customisation?

The Basic thing is Condition Technique. In which there are
1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.
A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic
Here the Condition Type is very important like PB00, PBXX,RA01 etc.
In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions. Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.
The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.
The Pricing Schema means the calculations procedure of Condition Type.
Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means
RA01 is based on PB00 like that we have to define in the Pricing Schema
which makes easy to use in real time.
Here PB00 has the Access Sequence - 0002.
But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.
In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.
For the configuration, I may not able to explain properly through here but will give some idea.
Configuration: SPRO - IMG - Material Management - Purchasing - Conditions - Define Price Deternmination Process:
1. Define Access Sequence
2. Define Condition Type
3. Defince Calculation Schema:- Here you have to define the Schema - Define Schema group
1. Define Schema Group vendor
2. Define Pricing Schema group
3. Schema group for Purchase Organisation
4. Assign Schema group to Purchase Organisation - Define Schema determination
1.define calculation schema for Standard purchase organisation
After completion of the Schema Group, we have to assign it to Vendors.
Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.
The Pricing in MM is vast because each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.

Pricing Procedure for diffrent unit of measure for diffrent product

1) Existing Pricing procedure --> Condition type based on Quantity
2) Existing Product --> Sales Unit & Base Unit of Measurement is in NOS ( Numbers )
3) New Product ( Belt ) ---> Pricing of product based on weight
ex :--> Rubber Belt --> 1 belt = 11.50 kg , Price = Rs. 100/ kg
As the production of material will go on weight of Belt will reduce in range of 11.50 to 11 kg . For different batch of production weight will change
every time weight of material will be calculated and price will be charged on basis of net weight ( Kg)
4) New product is assigned to new division ( it will bw sold in new division only )
Question
1) What should be Base Unit / Sales Unit of measurement ?
2) Do we need to create new pricing procedure or existing pricing procedure will work ?
for new product we need to create new condition type for which calculation type will be Net Weight .
3) do we need to do any customization for this ?
Exice people say that if pricing is done in KG (Net weight ) they want to see stock in KG
Management want to see stock in KG & Numbers

May be you can Create a New Unit Of Measure called ZPC. For using ZPC you need to assign Additional Base Unti Of Measure as ZPC in your Material Masters as well.
Use ZPC to create your condition records of pricing and in Sales order you will still have Unit of Measure as PC which the management wants to see..
Similarly you can create Constion records for new product based on Kg.

Pricing procedure not to bill customer but revenue recognition

I'm looking for guidance on how to setup a pricing procedure conditions. First let me explain the situation. What happens is the customer buys say 2000 software licenses on a sales order. The customer is billed and the customer account is debited and a deferred account is credited. Now the customer activates one of the licenses. The pricing from the sales order is copied to a contract. This contract has a start and end date for the license. Now that license can start to be recognized based on the period of the line item contract dates.. The issue we have is that normally for deferred revenue billing takes places. Problem is customer was already billing on the sales order. Somehow the pricing procure has to credit the deferred account that was posted on the sales order and then credit the revenue recognition account that can be used by transaction VF44.
So on the invoice associated with the sales order Invoice from sales order
Dr Customer $1000
Cr 2370 $1000
The account 2370 is the deferred account. This part is fine.
Now we activate 1 of the licenses.
So the pricing procedure has to do the following with no billing to the custo0mer account Invoice from contract
Dr 2370 $120
Cr 2371 $120
This is the problem part. crediting the deferred account 2370 and then posting into the revenue recognition account 2371
Rev Rec – VF44 for Period1
Dr 2371 $10 Cr 4340 $10 Any ideas would be appreciated

Hi
In SD billing documents customer is always debited or credited based on nature of transaction. For posting in two different G/Ls instead of customer account there is only one possible way which I know. In free goods pricing system can post debit and credit entries to different G/Ls and these G/Ls are controlled through account keys which you assign to condition types in pricing procedure.
Do you have any Idea of free goods pricing and its posting? Explore this and give it a try. I am not sure about this because I didn't test this. You can test and see if it helps.
In this for contract item category you have to use free goods pricing which you set in item category settings in VOV7.
Thank$

How to replicate a new pricing procedure from SAP ERP?

Dear Experts,
I have set up a new pricing procedure in the ERP backend and I would like to replicate this to SAP CRM.
A replication using object DNL_CUST_CNDALL has been executed once in the past.
What would be the best way for me to download the new pricing procedure without overwritting any of the existing pricing settings in SAP CRM?
Thanks,
Dan

Hello Dan,
The views in CRM pricing customizing do not allow to change the pricing procedures, condition types and access sequences that have been downloaded from the ERP system. You will see a field in customizing Source System with value A indicating that these were not created originally in CRM and the view does not go to edit mode.
In case a i.e. condition type had been created originally in CRM with the same name as a condition type that exists in the ERP the download of the adapter object will not delete the condition type that was created in CRM.
Therefore it is safe to execute the initial download of the adapter object DNL_CUST_CNDALL without filtering. If you have many pricing procedures in the ERP and you do not want to transfer its customizing to CRM you can create your own adapter object by copying the content of DNL_CUST_CNDALL ( to be on the safe side and keep the original) and then add a filter in your adapter object ,for example in pricing procedures using field KALSM of table T683S, including all the pricing procedures that must be transferred to CRM u2013 those that were transferred in the past and the one that you want to transfer now .However this filter is optional, most SAP customers do not change the standard filters.
The usual options are:
-- Download only DNL_CUST_CNDALL (or a Z object that was created based on DNL_CUST_CNDALL) which contains client dependent and also independent customizing ( i.e access sequences, condition tables). Condition tables may be generated too and it can take longer, maybe up to 45 minutes or so.
-- If you have made changes only to pricing procedure(s) or condition types u2013 client dependent customizing-- it will be enough if you download only DNL_CUST_PRC. As there is no generation of condition tables the download will be faster.
But you must consider that you should not download both adapter objects at the same time ( overlapping times), as part of the content being downloaded is the same and the database will be inconsistent. This can cause errors in pricing, not a severe issue, as it can be solved by a new download of DNL_CUST_CNDALL, but an issue that causes trouble as it is sometimes difficult to determine the root cause of the problem. So if you for whatever reason ( i.e. additional changes in a condition type) download both adapter objects you should always check R3AM1 and download the second object when the download of the first one has finished ( green light in transaction R3AM1)
Best Regards
Luis Rivera

Pricing procedure in me47

Dear sir,
Please advise from where do we get the pricing procedure ,condition types in Me47.since pricing procedure in PO comes from vendor.but if we maintain same vendor in RFQ,it shows different condition types there.
Pls suggest.
Thanks

HI Sweta,
Pricing procedure in RFQ depends on whether you define your RFQ document type in customizing as time dependent or time independent conditions in
OLME ->RFQ/Quotation ->Define Document Types
Here select your document type ->Right scroll -> You will find a column Time-D.C
Case 1> Time D.C is not selected : (i.e time independent conditions )
In this case your pricing procedure for RFQ and PO is same
Case 1> Time D.C is selected : (i.e time dependent condition)
Here your pricing procedure will be selected from your gross price condition i.e from PB00 (or whatever )
Go to M/06 -> Select PB00 ->Details ->under master data -> you will find a field PricingProc (in standard RM0002)
this pricing procedure is used in RFQ
so from your question it seems that you have time dependent condition so you need to check that pricing procedure in M/08
I hope it clarifies

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
base price
maximum retailing price
customer discount
material discount
excise duty
VAT
educational cess
additional cess duty
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

Pricing procedure Doubt

Dear SAP Guru's
I have 4 scenario's like scrap sales, deemed export, domestic sales and jobworks - and i have a customer 300000 - i assigned all the pricing procedures.
but in XD01 we assign customer pricing procedure which is mandatory like 1, A, c etc. but if the same customer i have to do scrap sales, deemed export and jobworks - what do i have to do.
Kindly guide me
regards,
Reshmi

Hi,
As you know we do the pricing procedure determination in OVKK as mentioned below:
Sales Org, + Dis Channel + Division + DPP + CPP + Pricing procedure + Condition type.
DPP - document pricing procedure will change
CPP - customer pricing procedure will not change
Do the following thing:
For all scenarios create different sales document type in VOV8 For eg;
Scrap - ZSCR
Deemed Export - ZDEM
Domestic sales - ZDOM
Jobwork - ZJOB.
Copy all from 'OR' , rename and save them.
Go to OVKI - maintain document pricing procedure. For eg:
3 - Scrap
4 - Deemed export
5 - Domestic sales
6 - Job work
Save them
Go to OVKJ - assign DPP to ales document type.
Here do the following
ZSCR - 3
ZDEM - 4
ZDOM - 5
ZJOB -6
Save the settings.
The customer pricing procedure will be the same for a customer suppose 'A' standard.
Go to OVKK
Here maintain the pricing procedure determination changing the DPP everytime and assign the correct pricing procedure for Scrap, Deemed export, Domestic sales & Job work for respective DPPs 3, 4, 5 & 6. Save the settings.
Now whenever you create the sales order in VA01 using the respective sales document type the system will determine the correct pricing procedure because of OVKJ assignment & OVKK pricing procedure determination.
This will definitely solve your problem.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

Tax Code & Pricing Procedure

Can anyone brief out how the condition types are being picked from tax code as well as pricing procedure...what is the difference??

Dear Mahesh,
The rates for taxes are picked up from TAX code which is clubbing of the condition types from Tax procedure (Taxinj or Taxinn). Now the tax values calculated are carried over to the MM pricing procedure usually with the condition type NAVS. This you can check under the conditions tab in the PO.
All other pricing elements like discounts, freight etc can be handled using the MM pricing procedure conditions and the taxes like excise, VAT, CST, Service tax etc using the tax procedure.
I hope this clarifies.
Regards,
Sid

Pricing Procedure Conditions

Similar Messages

Maybe you are looking for