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

Similar Messages

Output determination with base pricing condition types

Hi folks,
got a question regarding the Output determination..
In the outptut type i.e order confirmation and change order confirmation, it is showing the the base price condition type i.e PR00.
But the client wants it to pick up the condition type material discount k004...
is it possible ? because what my understanding was that the output types typically picks the base condition type PR00.
but the client wants it to pick up this K004..
can anyone say how to do this....
thanx in advance,
sourav
I

In the Pricing procedure configuration there is a column Print, where for each condition you may specify if and how the condition should be printed. There is good documentation (F1) available on this field. Clear this field on PR00 and set to 'a' (or any other applicable value) for K004. This change will affect all the documents that are using the same pricing procedure though.
Otherwise either the output processing program or the form (both names may be found in the Output configuration) will have to be changed or, if the standard ones are being used, those will have to be copied as the custom (Z...) objects and then modified accordingly.

Scale base value condition pricing

Hello I am creating a pricing condition ZPC1 that will only be applied to about half the items on the sales order but will be Scaled base need to be on the total number of items ordered weather the condition is applied to that item or not .
For example
The scale will be
0 -500       $1 per case
501 - 100 .50 per case
item 1    500 case order    will have pricing condition ZPC1
item 2    500 case order    will NOT have pricing condition ZPC1
I want the Scale price to be $.50 per case on item 1 not $1 per case.
The condition type is set up as
Scale basis C Quantity scale
Thanks James

Dear James
Go to V/06, Selct your condtion type ZPC1, open controls.
In Scales Change Check value from Descending to Ascending, save.
Now go to vk11 and maintain the condition record,
enter line item , select, click on scale, put your range and amount.
Save it, Either overwrite previous one or go to vk12, delete previous entry and then go ahead with the steps mentioned above.
Regards
Pavan

Determination of Base price condition type depending on Item Category

Dear All,
The requirement I have is as stated below:
There are two materials A and B that are individually sellable materials. But during a specific time period the company decides to give a scheme where in Material B is given as free when a particular quantity of material A is purchased. Irrespective of the scheme, material B can also be individually purchased during the scheme period.
Now in the former scenario where material B goes free with material A in the same order, the base price of material B should not go to revenue G/L but to a different G/L called Scheme G/L. To counter this scheme G/l there is another counter G/L into which 100% discount on base price to material B goes.
In the latter case, if material B is sold individually, then the base price should go to Revenue G/L and not scheme G/L and the 100% discount is not applicable.
Can you please guide me on how to configure this.
The approach I have taken is as follows:
The condition types for base price are ZBPR and ZBP1(reference condition type of ZBPR)
Item Categories to be considered: ZTAN and ZTNN (for material B going as free during the scheme)
The requirement is such that, whenever the item category for a particular material is ZTAN, the condition type to be picked must be ZBPR while the condition type ZBP1 must be deactivated.
Similarly, if the item category for the line item is ZTNN, then the condition type to be picked must be ZBP1 and the condition type ZBPR must be deactivated

Dear All,
I have fulfilled this by doing rev acct determination in vkoa using item category and moving it up the order. Also I used a requirement in v/08 for 100% discount on free material.
This has resolved my issue and i am now closing this thread.
Thanks and Regards,
Rohan
Edited by: Lakshmipathi on Apr 2, 2011 10:53 AM
Since you have arrived at a solution, please change the status of the thread to "Answered"

Base amount condition type

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

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

Discount calculating sum of Active & Inactive Base Price condition type

Hi,
For condition type ZBPO-Base Price maintained condition record with two key combinations, In sales order Conditions Price determined for ZBPO condition type with Inactive and Active. But Discount condition type ZDCO calculating 15% discount on sum of the Inactive & Active of ZBPO amount.
Requirement is Discount should be calculate Active ZBPO condition type only. Without deleting inactive condition type in Sales Order Conditions, what are the configurations need to do.
For Ref: Please check the below screen short.
Regards,
Parviz.

Dear Lakshmipathi,
Thanks for replay, Please check the below screens as you asked.
Inactive:
Active:
In Analisys I kept mouse curse on the condition types I'm not get any message on that (Dont know the reason why your asking that). Clicked on condition type and sent with access details.
Inactive:
Active:
Regards,
Parviz.

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.

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

Two scales in one condition table?

Hi,
I have a requirement to implement the condition technique for a Table that looks like a "Matrix" and has two scales (one horizontal, the other one vertical) that determine a fixed amount.
As far as I see I can only implement one scale into each Condition Table, how can this be done?
Thanks,
Doro

Hi,
thanks a lot for your answer. In my case the once scale is a quantity (number of participants) and the other scale is a dollar amount (Net revenue).
Based on the level achived in both categories, I end up with a fixed dollar amount that needs to be multiplied by the number of participants.
As the scales should be configurable, I would like to have them as a condition table itself and not hard coded somewhere.
I was thinking along the lines of creating 3 condition tables. First one to determine the "Scale Level" for the Participants, store that values somewhere (suggestions?), the second one determining the "Scale Level" for the Net Revenue, again store that amount somewhere and then last but not least, creating another condition table that contains both scale levels and determines the fixed amount.
Could that work? And how could I move the fields between the different condion types? I also seem to have a problem ending up with some sort of "Scale level" as it is not a quantity or amount....
You proposed: "Your best bet would be to have the sale basis decided by formula (Option G) and then you need to code and place the formula in the next field - Scale Formula in Condition type config (v/06). "
Which field do I have to fill in that Scale Formula for that to work?
Your help is greatly appreciated!
Doro

Pricing limits for condition type PR00

Hi,
I have got a scenario at hand, where i have to assign tolarence limits to all the conditions types in the pricing procedure. i have maintained limits in Transaction OVB2 except Base price condition type i.e. PR00. the problem i am facing is, we have got some where around 1,500 material and 3,200 customers and the price variation between the material is large(3000-150000). The main purpose of maintaining limits is to reduce the risk when entered manually. Please do consider the general business implications while replying.
eg: new pricing procedures, condition records for base price etc makes a hafty job, so can you please suggest me any other means to have a tolerence limit to condition type PR00(PR00 is used as base price for all pricing procedures).
Thank you, Have a nice day at work.
with regards
RVS Prasad

Hi venkata siva
As you are having around 1500 materials in your business . That means you need to maintain condition records for all these materials. While maintaining condition records only , in VK11 for PR00 condition type , maintain upper limit and lower limit in additional data . Then there should not be an problem
Another way of maintaining pricing at upper limit and lower limit is in OVB2.
Regards
Srinath

Adding the tax condition type after customer pays

Hi,
I have a strange situation.
The customer has payed the invoice amount and evrything is cleared and the complete Order to Cash cycle is complete.
Now my client wants to charge the customer with the tax amount (implemented later) on the invoice that is already been cleared.And that amount should as usual go to the tax G/L account. There are not many Condiiton types but just the base price condition type and tax condition type.
I have maintained a necessary condition record for MWST.
SAP transaction wise I am thinking to create a normal sales order of the invoice amount (Base + Tax condition type) and then complete the order to cash cycle.And once it is completed I would create a debit memo request and subsequent debit memo for the base price which would be adjusted later.
This will solve my basic purpose of Tax amount goin to the tax account.
This is only for few SO in the production
Please let me know in case anyone has a better idea.

Hi ronaldo
You create a sales order with document type L2 ( debit process) . so you create the sales order with reference to billing . Now manually you enter the tax condition type (MWST) at the sales order level and then do billing.Make sure that in the tax condition type details you have maintained the option C "Manual entries are possible" .So that you can enter the the tax condition type manually at the sales order level.
So some additional taxes are being charged to the payer.So he will be paying some extra taxes as he has already paid for the billing document that has been passed to FI
Regards
Srinath

CONDITION TYPE PR00 TO SALES AREA + DOC PP + CUST PP

Hi ,
While defining pricing procedure we only assing condition type pr00 to the procudure ? why is that so ? Since we have many condition types .?

Jerry Jerry,
Condition type PR00 is the base condition price. The whole price calculation is based upon the condition record entered for the condition type PR00. In actuality we assign all the other condition types but all these would turn out to be useless until we enter the base price condition type PR00 in the pricing procedure.
For example if in a pricing procedure we have entered conditions like K007 and KF00 and have not entered the base price condition type PR00 the values of K007 and KF00 will be shown as 0 as for these discounts there is no basis of calculation i.e. no base price.
Hope this answers your question.
Reward points if helpful.
Nagesh Murthy.

Create New Tax code and condition types

hi experts,
i want to create new tax code V10 and new condition types ZWKT and ZSTX under V10.
i have a requirement that is create service general Purchase Order with following tax conditions
1. Work Tax 4% on 70% of Bill Amount.
2. Service Tax 12.36% on 33% of Bill Amount.
while creating PO when user select ZWKT and ZSTX, system should calculate 4%( on 70%) and 12.36% (on 33%) and place the tax amount on relevant fields automatically.
( i tryed with tcode:FTXP and created tax code(country key: IN, procedure: TAXINN and taxtype: V input tax) but problem with assigning condition types and calculation procedure)
please help me in this issue (step by step).
Thanks.
srinu.

Hi,
Here you have to create two dummy condition type for Base Value. One for Service Tax and other one for Work Tax.
Then create two condition type for Work Tax & Service Tax.
Ex : Work Order Base Value condition type is "A"
Service Tax Base Value condition Type is "B"
Work Order Tax condition Type is "C"
Service Tax condition type is "D"
In Pricing procedure just add all the above condition type as below
Both Base Value condition type will be calculated from System Base Value & in FV11 maintain the Base Value percentage against the Tax Code & Condition Type as per ur req (70% for Work Tax & 33% for Ser Tax)
Work Order Tax & Ser Tax will be calculated from respective Base Value. In FV11 just maintain the tax %.
Sangram

Is there any specific Transaction for defining Scale Basis.

Hi All,
Is there any specific Transaction for defining Scale Basis? What is the Table name for the Scales?
Thanks & Regards,
Fedor.

Hi,
You can maintain scale basis in condition record T.Code"VK11", and table in which scales are stored is "KONM"
balu

OVKK--Condition Type?

Hello All,
When you define the determination of pricing procedure in txn OVKK, there is a field 'Condition Type'. What is this used for..?
The F1 says:
Proposed condition type for fast entry
The condition type that the system automatically proposes in the double-line entry screen during sales order processing.
Now, what exactly does this mean?
Someone, plz explain...
Rgds,
Rags.

Hello Rags,
In OVKK the condition type which you specify is displayed in the sales order at the line item level in the "CnTy" field & the adjacent field "amount" shows its condition record. This will be shown per piece.
Say your sales executive needs to inform the customer about the base price (condition type PR00) of the item for that particular sales order, then he/she does not need to check at the item level pricing. He/she can directly check at the line item level & tell the price. If the condiiton type is not maintained in OVKK, then the respective fields will be blank in the sales order.
With best regards,
Allabaqsh G. Patil.

Scale basis in condition type?

Similar Messages

Maybe you are looking for