Scale type in condition type

Hi,
What is the importance of scale type in condition type.Actuly I want to know that how we use scale type in condition record.Please explain this with example.
Regards
Prabudh

Hi,
can u do a small search in this forum, todad morning also there was one posting regarding the same.
Scales
A scale in a condition record where prices, discounts, or surcharges are defined for different customer order quantities or values.
This scale is used by the system to determine the price, discount, or surcharge for a given quantity or value.
This is defined in the each condition type
spro--> img>sd->basic functions> pricing>pricing control->define cond type--->select any one condtion type eg: PR00--> come down u will find scales views.
scales basis:
depending upon the scales basis the prices are determined according.
example:
A company want to give discount based quantity scale ie, if customer buy 10 pcs the prices would be 100/ unit & if he purchase more than 20 the prices would be 80/unit.
So in scale basis u have to select quantity scale. & the prices aganist teh qunatity will be defined in condition record maintanenace (tcode:VK11). The other sclaes basis available are
B Value scale
C Quantity scale
D Gross weight scale
E Net weight scale
F Volume scale
G Scale based on a formula
L Point scale
M Time period scale - Month
N Time period scale - Years
O Time period scale - Days
P Time period scale - Week
R Distance
S Number of shipping units
T reserved (IS-OIL, time prices
X reserved (IS-OIL, day prices)
scale formula:
here there small routine is predefined to determined of scales
hope this helps u
regards,
Arun prasad

Similar Messages

Output Type vs Condition type

Hi all,
What is Output type and Condition type?
What are the similarity and diffrences between them?
Regards,
Amit

Output type and Condition type have no similarity.
Output type is used to determine the mode of communication; Print-out, Telex, Fax, External Send, Simple mail etc for an application.
An application can have various output types; for example V1 will have output types for Order, Quotation etc.
Further; the output type defines the Processing Routines and Forms which will be executed when the user choses the same from a transaction.
Example if the user while processing a PO; selects an output type and the medium say Print Output; the application will execute the processing routines and forms corresponding to the output type used.
Condition Type is related to pricing in SD; for example; price, discount, rebate, tax; all are different condition types.
To add; for an SD document the condition type will invariably come in to picture at an earlier stage than output type !! (ofcourse)
Hope it helps.
Edited by: Neeraj Batra on Nov 13, 2008 11:53 AM

Scale Types in condition types customization?

Dear ALL,
In spro in "define condition types" in MM we have to assign the type of Scale whether FROM ,TO, NOT USED, INTERVAL etc.. to PBDD, AMO2 etc. Between Scale types i.e. FROM (BASE) Scale and TO Scale what are the differences? What is the concept behind these types of scales?
Thanks

From to TO Scale means
If your price with vendor is like , If you buy
up to 1000 quantity you get at $ 1.00 a PC
> 1000 you get at $ 0.95
> 2000 you get at $0.85 like wise you can define the scale...while PO creation based on the quantity system will pull the price.
Rewards the points for helpful answer

Scale basis in condition type?

Hi
I want to know the exact functionality of Scale basis in a condition type.
Basically what does scale basis, scale formulae, check value ,scale type etc mean?
Explanation with an example would be highly appreciated.
Also we do maintain scale basis at condition record level, then whats the difference between the two?
Thanks

Hi ! Christino,
Q) functionality of Scale basis in a condition type?
A) The entry made here decides whether the condition value calculated is on the base of per quantity(say per pc or per no.) or per weight(say per Kg or per pound) or per volume(say per litre or per ml or per cm^3)
Q) What does scale formulae, check value ,scale type etc mean?
A) Scale Formulae - is a setting(ABAP/4 code you write) to make condition value to be calculated any other than those mentioned in the above answer.
->Check value field once set helps in deciding whether the scales you mentions have to be in a ascending or descending in scales rate
(ex.for Material A 1pc to 50pc price is $100
                         51pc to 200pc price is $99
                        201pc to 500pc price is $98, is an example of ascending scale rate. descending is opposite)
-> Scale type is setting the validity of the scale (say the scale rate starts from a particular point of quantity or value)
Q)Also we do maintain scale basis at condition record level, then whats the difference between the two?
A) at the condition record level it just a reflection of what scale basis you have set in customizing of Condition type.
Hope this helps. Do provide your feedback.
Regards,
PATHIK
Message was edited by:
        Pathik Pandya

Creation of new movement type and condition type

Hi experts,
I am going to create a new movement type and the new condition type. Please suggest me how to create and implement it.
Thanks
Harmandeep

Please check these answered links:
Create a new movement type
Create Movement Type Error
When we need to create a new movement type?
can we a create a condition type for PO
Create new condition type with respective GL acc. for PO
Re: Condition type

What type of condition types i have to take if i am chossing TAXINN procedu

hi,
sap gurus,
good evening to all,
which condition types i have to take if i am chossing TAXINN procedure for different taxes at different
tax slabs in different situations and different states.
for example:
some times i have to consider sales tax
some times i have to consider excise tax
some times i have to consider cess
somes times i have to consider addational tax on taxable value like in gujarat.
some times i have to consider cess on VAT like in kerala.
some times i have to consider Central Sales Tax.
plz help me on this
thanx in advance
regards,
balaji.t
09990019711,
timmampalliattherateofgmaildotcom.

Take all the tax types applicable.
For VAT and sales taxes maintian them in tax determination.
For excise tax types, there are four pricing procedures in SD and TAXINN procedure in FInance which lists down all the taxes. If he higher edn cess in not maintianed then maintian it.
Please refere to SD,MM and the relevant building blocks such as sales from factories, depots, stock transfer etc. They are all available at the www.help.sap.com in the building block library.
regds
Jude

Calc type of condition type

Hi,
if one of my pricing conditon type has calculation type ," net weight", then for calculation of total condition value, where will the total weight be picked up:- from the material master per unit weight or from the alternative unit of measure tabs of the material master. i.e.
regards
sachin

Hi
It takes the values from the document itself.
Thanks,
Ravi

MM-PUR default scales for condition types for service (ME31K

Hi,
We have faced the following problem:
The business case was, to have default scales for certain condition types for a service for a purchasing contract.
We didn't find it in SAP, so we wrote an OSS. SAP answered that it's not possible now, nor in the future.
So we decided to look around in SAP, and found out that it was half possible.
I've abused the exit USEREXIT_XKOMV_BEWERTEN_INIT of program RV61AFZB.
In this exit I provide the internal table staffel for program SAPMV13A with the correct information (via ASSIGN ('(SAPMV13A)STAFFEL[]') to <staffel>.)
In this way, if a user adds a service, this exit will get reached and the scales are filled. If the user then clicks on conditions and then double clicks the condition type with the scales, all the default scales are shown to the user. If you then click on save, the next screen is the service screen, if you then click on save again, all the date is stored in the database. (bit of a work around, but this works)
However, I can't figure out how to save the scales data, when you only add a service and then push the save button without viewing the conditions. Quite logically actually because I'm skipping two whole screens with pbo and pai modules, in these modules internal converting takes place.
Has anyone encountered this problem before and how did you solve it then ?
Alternatively what is the SAP standard way to add pricing condition scales on condition types of a service of a purchasing contract? As you know there is no BAPI yet to change/create a purchasing contract.
I was thinking, to add the scales by updating the tables directly via ABAP, I know that's not a clean way to do it, although it isn't too risky.
Kind regards, Rob Dielemans

Dear Rob,
Is this solution properly working for you?
I think my problem is similar: purchasing outline agreement (contract) refuses to apply relevant scale prices in the item line. Always uses the first price - without considering order quantity depencies.
Regards,
Tamás
Edited by: Tamas Szabo on Mar 31, 2009 3:50 PM

Condition Type for commissions across sales orders

Hi,
I have a requirement for which I need inputs:
We have sales employee who will get commissions based on the total sales they make. The relevant sales employee will be brought into SAP as a business partner (specific account group and hence partner function).
A tiered commission would be set up for each of the sales employee, for e.g. 1 to 10,000 , commission is 2 %, 10,000 to 30,000 commission is 3 % and above that is 5 %. The commission applicable should be determined at the time of sales order creation. The commission applied to an order should be determined based on all the sales orders for the sales employee and not that specific sales order. For e.g. if the sales employee has already got one sales order of worth 6000 and he gets another order of worth 9000, then as per the example, he is entitled to 2 % for 4000 of the order (his total sales now reacheds 10,000 and he moves now into the next bracket) and is entitled to 3% for 5000 of the order value. Also in case any order gets cancelled then the cumulative sales value for the sales employee should take care of the cancelled order.
I have a condition type where by I maintain the scale and the corresponding commision rates for the sales employee. I have ticked the condition update setting so as to cumulate the order value. I have the following questions:-
1. How do I ensure that the rate applicable for the specific order takes into consideration the past sales orders for the sales employee and not only that sales order.
2. How do I determine the condition record based on parter function (partner funtion for the sales employee)? I did bring in the partner role in the pricing communication structure but that does not work.
3. How should I take care that the cancellation or sales order takes out that value from the cumulative value for the condition record. As of now it does not.
A quick response would be highly appreciated.

Hi Kastubha,
Thanks for your reply. I am trying now to use rebates for this functionality. However I have few questions and I am unable to progress beyond a point:
Let's say that for a sales employee i set the rebate agreement. The sales employee's commission is as follows:
1 - 10,000 (1 %)
10, 000 - 30,000 (3%)
30,000 and above (5%)
The calculation type for condition type is percentage, scale type is graduated to interval scale.
I am trying to use scale in rebate agreement to set up the commission structure for the sales employee. However, there is only accrual rate that I can enter. There is no place to enter the accrual rates as per the scale.
Because of this, what is happening that the rebate record determined is the accrual rate and not what is as per the scale. Also I need the condition record to keep track of total sales for the employee so that it knows what commission rate to apply based on how much the sales employee has achieved.
Am waiting for you inputs.
Best Regards,
Sunil

Condition type for discount on quantity basis

hi all
in pricing procedure of MM, i want to make a discount on quantity basis.
for ex- 100q- 2% discount.
which condition type i have to maintan
thankx
susanta

Hi,
Here your requirement is Discount is in percentage but scale basis is quantity.
So use Condition Type RA01 (Discount % on Gross) or Copy of it, in Calculation Schema (M/08)
Note: - Keep Scale basis as ''C" Quantity scale for the Discount Condition Type
Now in ME11 (Purchase Info Record) OR MEK1 (Condition Record), maintain scales for this condition type ss for 100 Qty, 2.00% Discount.

Creation of new condition type: MWST

Hi, Everyone.
I would like to ask for some help regarding this issue: Creation of new condition type: MWST with the following details:
1. For the country French Polynesia, Create a new VAT condition of 10%.
2. Create a new one called : Class : Z u2013 Designation : France : TOM corresponding to 10 % of VAT to be invoiced
and then associate this new VAT code u201CZu201D to the applicant Nr 221860
If you could provide me a step by step process on how to resolve this, it would be very much appreciated. Thank you so much.

Hello
What type of condition type you want.
It is always advisable to create a new conditon type copying a standard condition type.
For gross price condition types select PB00/PBXX
For freight charges, Copy FRA1/FRB1
Regards

Currency conversion issue for condition type

Hello,
I am creating two invoice document.
1. Customs Invoice (ZCDS)
2. Inter company invoice.(IVA)
both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
ZCDS
IVA
Regards,
Jagjeet

Hi Jagjeet,
For IVA invoice type -(For condition type- YUMU)
Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
For ZCDS Invoice Type -(For condition type- YUMU)
Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
To solve your problem write code in User exit - userexit_pricing_copy to change konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
Regards,
Vikas Mulay.

Shipment cost :Cond. type FS00 - condition record exists (removed manualy)

hey all ,
my requirement is to charge for every container (packing material) in the shipment .
i coped condition FS00 (container) and called it Z100 .
the condition is defined with following parameters :
cond.class : B - prices
calc.type : S -number of shipping units
calc base : C -handling units
the condition opens in a pricing procedure under item category ZK01 which is defined the shipment header as cost relevant.
AND the problem :
when i opens the shipment cost document the condition doesn't appears .
in the analysis i get this message :
" condition record exists ( removed manually ) "
when i add the condition manually and double click on him there is a field that
specify that the condition is inactive because : " inactive due to calculation basis (shipping)
after checking the relevant notes :
i don't have a requirement in the procedure or the access to this condition .
i didnt delete is manually
so the above isn't the reasons that the condition isn't showing .
other condition types ( old condition types ) is active in this procedure ( new procedure )
does any body have an idea ?
Best Regards
ASA

hey RP ,
no exclusion and no formulas in this pricing procedure ?
any other ideas ?
i post this in an other forum and got this :
Hi,
There should not be two or more conditions with the condition class B in the
same pricing procedure.If there are two coditionswith the condition class B
in the same pricing procedure then it will invalidate all other conditions
in the pricing procedure.Check if any other condition(other than Z100) has
the same condition class. If yes use some other condition class for it.
Regards
Avinash Gyale
is it make any sense ?

Service tax condition types in Pricing Procedure in SD(Taxinn)

I need one more advice on Service tax.
I am configuring order type for services.In that in pricing I have to add the service tax conditions type for service tax & cess on that.We do not have any standard condition type in our pricing procedure for services.
Is there any standard SAP doc. to configure service tax condition types in pricing procedure or I have to copy from JLST & JLSR(surcharge).What about the account keys I will used for these condition types.
If you have any doc. related to this issue please send it to me....or suggest me what to do.
Please remeber I am using TaxINN tax procedure.
Please help me
Thanks & Regards
Sunil Garg

PROCEDURE: Initial Steps
Create two new Tax conditions: JSE4, JES4. Steps for creation of Tax Condition is illustrated below
Create new condition types
SAP Standard IMG -> Financial Accounting -> Financial Accounting Global Settings -> Tax on Sales/Purchases -> Basic Settings -> Check Calculation Procedure. (Transaction OBYZ)
Select Define Condition Types
Select Condition Type JIN1 and Click on Copy as (F6) and give the Condition type as JSE4 and the Name as Service Tax.
Select Condition Type JIN5 and Click on Copy as (F6) and give the Condition type as JES4 and the Name as ECS on Service Tax.
Outcome: The two tax conditions, one for Service Tax and the second for Education Cess on Service Tax have now been created.
1. Create a new tax posting key VS9 and VS0.
The path for this is:
SPRO  Financial Accounting  Financial Accounting Global Settings  Tax on Sales/Purchases  Basic Settings  Check and Change Settings for Tax Processing
Select the Processing Key MW1 and Click on Copy as (F6) and give the Key as VS9 and Name as India Service Tax.
Select the Processing Key MW1 and Click on Copy as (F6) and give the Key as VS0 and Name as ECS on Service Tax.
Note: If there are multiple service tax registration numbers, you need to have separate account posting to different GL accounts based on service registration number. This can be done provided a separate tax code is maintained for each service registration number.
To achieve this you need to define a set of 2 separate G/L accounts for service tax and Education CESS on service tax respectively, for every service registration number.
In such a case, please activate multiple accounts posting per tax code as follows:
Defining the GL accounts for the Service tax and ECS on Service Tax:
SPRO  Financial Accounting  Financial Accounting Global Settings  Tax on Sales/Purchases  Posting -> Define Tax accounts
Go to Details of the Transaction VS9 (Service Tax GL account) and enter the Chart of accounts
Select the Tax Code Check Box if you want to have Tax Code Specific GL accounts or Blank when the common GL accounts
Regards,
Rajesh Banka
Reward points if helpful.

Can we attach requirement for manual condition type

Hi,
Pricing question....
ZOTH is the manual condition type
(The condition type configuration: - Manually editable, no access sequence attached )
(Pricing procedure : - No alternative calculation type attached)
Can I attach a requirement to ZOTH in the pricing procedure?
Laxman

hi,
we can very well have requirements for manual conditions also. Like we have standard requirement "2" Item with pricing and this is assigned to PN00 ( Net price ) condition which is a manual condition.
you can check in RVAA01 pricing proc. also
regards
sadhu kishore

Scale type in condition type

Similar Messages

Maybe you are looking for