Scale type D for group conditions

Hi all,
I am creating a new group condition and am trying to make it scale type D - graduated-to-interval scale. However because this is a group condition, SAP is giving me an error (Scale type 'D' cannot be used for group condition 'X').
What is the best solution to this?
I would like to give discounts based on:
Sales quantity:
1-100 = 15% off
101-200 = 25%
201-300 = 35%
301-400 = 45%

Hello
This is b'coz your condition type with active Group condition Indicator. That means, here the system calculates the basis for the scale value from more than one item in the document.
So, the scale D maintain in Scale basis for those condition type, does not go with it and throws an Error.
Thus, if you want to scale functionality for condition type with group condition indicators use GrpCond.routine to maintain routine.
Routine number for creating group key identifies a routine that calculates the basis for the scale value when a group condition occurs in pricing.
For instance.
Check routine 3-Mat.Pricing Group. This is an example of a structure of group key formula. A structure of group key formula can be used to influence the basis the system uses when reading the scale of a group condition. The formula is assigned to a group condition type in customizing.
Formula '3' adds up the quantities / values of all of the line items in the sales document that have the same material pricing group (field KONDM) as the current sales document line item.
A company defines a particular discount (condition type Z001) with scales based on weight. When a sales order line item is priced that is eligible for the Z001 discount, the user would like the system to read the scale with not just the weight of the current line item, but the combined weight of all items in the sales document that have the same material pricing group as the current line item. To accomplish this, the user defines condition type Z001 as a group condition and assigns structure of group key formula '3' to it in customizing.
I hope this assist you.
Thanks & Regards
JP

Similar Messages

Use of Scale Type D

Hello Gurus,
I wanted to use scale type D for one of my scenario
The details are given below
I want to divide the share of revenue betwen my client and his JV partner.
I created a condition type ZBAS - for basic rate * quantity. This condition type is statistical
this total amount will be distributed between client and his JV partner
For claint share I have condition type ZCI1 -60%
For JV Partner Share I have condition type ZCI2 - 40%
My Scenarios is when my rate is 10,000
then ZCI1 - 60%
ZCI2 -40%
When Rate is 15,000
ThenZCI
upto 10,000 - 60%
from 10,000 -15000 - 55%
ZCI2
upto 10,000 - 40%
from 10,000 -15000 - 45%
I tried to use the scale type but I am not getting correct values. System is not determining the 60% for value upto 10,000
Appreciate your inputs
Thanks
Narayan

HI
check the below links
[Re: Scale type D|Scale type D for group conditions;
[Re: Pricing scales|Pricing scales;
Regards,
Prasanna

Group Condition types & routines - pricing

Do we have to code the group condtion routines all the time? If I just have the group condition box checked without any routine coded, I am seeing that SAP is grouping all the items in the sales order using the same access. Please let me know. Thanks.

Hi,
This depends on your requirement. If you have defined the condition at the material pricing group level, then no need. The routine is used only if you want the condition to be read differently for each item (with the scale base value being total of all the items).
You can find some help in the below link:
http://help.sap.com/saphelp_erp2005/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm
There are some helpful SAP Notes if you need further clarifications:
39034     Group condition routine
854978     Function of cumulated scale base values (in SD)
109708     Scale processing for group conditions
Hope this helps.
Regards
Nikhilesh

Group condition with varying keys

Hi every one,
How to declear group condition with varying keys.
gajanan

Hi Rudrag,
What Karan has mentioned is absolutely correct.
To simpify it,
Suppose you have two materials M1 and M2 for which you want to give customer/material specific discount.
Create one material pricing group (e.g, 01) in customising, assign the Material Pricing group 01 to both the material in their respective material master in Sales org 2 view.
In V/06, open the condition type K005, activate the "Group condition" check box and assign "Routine 3" in the "Gorup condition routine" check box by selecting the value from the drop down.
Now create condition record for Condition type K005 in t.code VK11 for the two materials for one specific customer.
For example, for cudtomer C1 and Material M1, discount is Rs.10 per Piece(PC).
Go to scale and specify in the scale that if 10 Pieces then discount is Rs.15 per piece.
Similarly, for Custome C2 and Material M2 maintain a condition record for discount is Rs.20 per piece.
Go to scale and maintain and specify that, if 10 pieces order then discount will be Rs.25 per piece.
Now create a Sales order for the Customer C1 with the two material M1 and M2 with quantity 4 pieces and 6 pieces respectively.
System will add up the quantities of both the material as 4+6=10 pieces.
Even though, there respective order quantities are 4 pieces and 6 pieces , but still both the item will avail the discount for 10pieces level beacuse of the group condition settings.
But, the rate of the discount will taken from there individual condition record.
That means, M1 will get discount of Rs.15 per piece. So for 4 pieces discount will be Rs.60.
Similarly, M2 will get discount of Rs.25 per piece. So for 6 pieces discount will be Rs.150.
If there is no setting for group condition then, M1 would have got discount of Rs.40 and M2 would have got discount of Rs.90.
I hope this is clear.
Regards
Pradyumna

Get Delivery date(EKET-EINDT) in MM Pricing routine(group condition)

Hi All,
I have created an MM pricing routine RV65A092 in VOFM. So when creating PO(ME21n), this routine will trigger..
Now the problem is I need EKET-EINDT for grouping condition. It was mentioned to call program SAPLMEPO and get EKET data.
Please help me how to get delivery date in that routine which is filled in Item level during PO creation
Thanks
Ram

Hi Ram,
For SD you have the SAP Note 531835 - Using field PSTYV in the condition access. For MM is simmilar, although you must use the enahncements. Instead use the userexits that note says, use the enhancement LMEKO001 (EXIT_SAPLMEKO_001) to populate fields ZZ in KOMK and LMEKO002 to populate KOMP.
I hope this helps you
Regards
Eduardo

MWST-group condition rounding difference between invoice and credit memo

Hi Experts,
I have an issue with MWST rounding issue.
Before jumping into the actual problem these are the prerequisites
SAP Version: ECC6.0
Condition type: MWST, with group condition tick enabled!
US Scenario (No Implication of CIN)
Scenario: - From Billing document  to Credit memo invoice.
When a invoice is referenced to the credit memo, there is a difference in the rounding value.
E.g.: Invoice tax value: 387.34 when completely referenced to credit memo become;s 387.31.
Please throw some light on it!

Hi,
Check Note 315792 - Group conditions of the same amount on item and related notes.
Perhaps Note 80183 - Rounding will help you too.
Regards,
Eduardo

How to set required for group of condition type in the same condition class

Hello,
we have a group of condition type with the same condition class B, the last one have been set, and all of others will be inactive.
but we don't set any required for all the condition types in pricing control, so if user don't set any of them, the sales order or billing is still saved. that is a risk.How can i fix it? Thanks.
Sophie

Hello,
incompletion log is not available in invoices.
You have different options:
- activate a validation in FI when the Billing document is released into accounting, so that te release into accounting is not allowed if the invoice amount is zero;
- define a subtotal in the pricing procedure as sum of the pricing conditions of your group, then develop a custom routine to be assigned in the formula "CalType" (field T683S-KOFRM) where an error should be raised if the amount of the subtotal is zero (use as an example formula 48);
Best regards,
Andrea

Shipment Cost: Group Condition Type calculated on a special weight...

Here is the scenario: A shipment (truck) combines multiple deliveries, grouped on a stage when same destination (happens often).
A condition per LB is to be calculated on the cumulated weight per destination (per stage) BUT not simply on the gross weight, but on the heavier of 2 special weights: the business here uses a special formula according to the packaging, and it gives 2 weights (stored in Z fields of LIKP), an actual weight and a cubic weight.
The purpose is to identify for each delivery the heavier weight and to use cumulated the weight across the deliveries to the same destination to calculate the per CWT cost.
This is my first issue: the condition type is defined at Delivery calculation base, Calculation Type Multi-dimensional, and as a group condition). How do I define to use the cumulated of each delivery heavier weight ? In the Scale for condition type view, I used the scale basis D Gross Weight (which is not right..), there is also a field for a Scale Base Value formula, I wondered if that is what I should use..
My 2d issue: once the cost is calculated, I have to re-distribute it on the deliveries as per the proportion of their heavier weight compared to the total weight used for the calculationShould that be an alternate Condition Base Value formula in the pricing procedure (where xkwert would be.the heavier weight.would that be then a new Z field to be filled in by the user exit determing the heavier value) ??
Thanks a lot, it is a tough one, I know...who is the best ever shipment cost pricing consultant ? !

Hi Guys
Unfortunately I do not think that you will get an answer now. Either your question is not simple or we do not know.
So in the interest of keeping the Forum tidy and easier to surf through could you please close your thread and either try one of the other forums or try another post. I do not think that most people will bother to look this far back anymore.
Sorry I cannot help as I would if I could.
Regards
Frenchy.

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

Group Condition at Header on Scale basis

Hi,
I want to know, how system assign the corresponding condition amount of header to individual item .
in our system
e.g in our system we have condition ZD22 for packainf and forwading charges as fixed amount and scale is qty
i have add Rs 300 at header and in my PO there are 3 item having qty,   100 ,100 and 2500   after adding condition amount at header as 300   when i checked the on individual item i found for first two item it 75.89 each and for third item the amount is 148.22
I want to know how system divides the header amount to individual item if scale is qty.
regards,
zafar

Hi
Kindly note this scenario
Condition value XXXX    180
Marked as Header + Group Condition
PO
Item 1       qty   1           Price 300
Item 2       qty   1           Price 100
Item 3       qty   1           Price 50
Ratio = Based on value =Qty*Value
300:100:50   = 6:2:1
Therefore XXXX distributed to items as   120 , 40,20

Selecting the best Price for a condition type but only for some customers

Hi All,
I have this situation where we have condition type ZPPR (COPY OF PR00) with 5-6 Condtion tables.
in Access sequence for ZPPR, we have Exclusion Indicator set for all the conditiona tables so if first price is found, it doesn't search for others.
Now I have a requirement that we should search for all the condition records and choose the lowest price. But this should happen for only a certain type of customers and not for everybody.
Spefically we have:
1. Contract Price
2. Plant/Material price
Normally, if contract price is found, it doesn't look for Plant/Mat price but we want to offer our customers(some of them) an option where they could choose the lower of the two price. We set both the prices every day based on some inputs.
Regards,
Luke
Edited by: Lukesh Singla on Dec 21, 2011 8:49 PM

Hi Luke,
We have multiple option for this implementation:
Option 1: If possible based on access sequence. Not sure if this is suitable considering you mentioned that ZPPR has 5-6 access sequence.
1) Store Contract price in condition type ZPPR and store Plant / Material Price in new condition type say, ZPPX.
2) Have separate pricing procedure and determine them based on customer type. In first pricing process XXXX01, configure Condition exclusion with the setting that ZPPX should be deactivated if ZPPR is present, condition exclusion procedure D (exclusive) . In second pricing procedure XXXX02, configure condition exclusion with the setting that compare ZPPX and ZPPR and activate best condition type for the customer by using condition exclusion procedure C (Best condition between two exclusion groups ).
Option 2:
1) Copy ZPPR and its access sequence to a new condition type and access sequence say ZPPX without checking exclusion indicator in the access sequence. In the condition type control for condition type ZPPX >> Master data section >> Reference Condition type = ZPPR so that master data records need not be duplicated.
2a) Assign the current procedure to the set of customers which should get the first price. Create a new procedure with condition type ZPPX instead of ZPPR keeping other parameters similar and assign the new procedure to other set of customers who should get the best price.
OR
2b) if 2a is difficult in terms of future maintenance, add condition type ZPPX in the same procedure and create 2 new pricing requirement validating the customer segments and assign them to respective condition type in procedure ZPPR and ZPPX.
3) Maintain condition exclusion for condition type ZPPX with B ( Best condition within Condition type).
Hopefully it helps. Let me know if you need any other help in implementation of the solution.
Regards,
Naveen Aggarwal

Can a scales-based condition be defined as group condition?

We have a scales-based condition, applying to certain items. A formula has been created, which basically loops through all items equipped with this condition, calculating the value based on the accumulated quantity of all items up to the one currently calculated. The condition rebate is then applied if the "max" value hasn't been exceeded.
The formula itself works fine as long as the condition is not defined as a group condition. If it is set as such, the condition value is overwritten due to the sum quantity of all items exceeding the scale maximum... the client insists on the condition being a group condition, whereas I think this destroys the purpose (calculate rebate for items up to the last one before max is reached). Any suggestions?

Create a hidden item lets say P1_MYITEM and set its default value to *2*
Just amend the IR SQL query to add a where clause like below
//remember the default value of item is 2 and this will evaluate to false and return no data initially
where 1 = :P1_MYITEMBefore setting your filters and refreshing the report just set the value of the item P1_MYITEM to *1* (make sure you set the item's value into session state using Page Items to Submit property)
So ideally the dummy where clause will now evaluate to true and the data will be shown

Table for Rebate Condition Types( Condition Records)

Hello All,
I need the table and the FM name which stores the values of the Key Combination of the Rebate Condition Type maintained in a Rebate Agreement.
If not, at least, give me the name of the FM which stores the values of the key combination maintained in condition records for pricing.
Regards,
Raghu.

I'll give an example,what am looking for..:
I've a Condition Type: ZBAX for ex. it has a key combination: Sales OrgCustomerMaterial.
I maintain condition records as:
For CU70/21100043/3456 the value of the condition record is say 100 euro.
My question is where will I get the values CU70/21100043/3456 ?
FYI..in T685 the defintion of the Condition Type is stored. in SAP, no T-table is meant to store condition record values.
KONA contains data on Rebate Agreements i.e. RA no, Rebate Recepient etc..
I know that KONP stores the accrual %, scale base, scale values etc..
but, I want to know where are the values for the key stored? Or, the FM that would fetch me these details?
I hope am clear..
Regards,
Raghu.

Assign Shipment Cost Condition Types to Origin Groups

Hi all!
I need to assign condition types from shipment cost document (tr VI01) to origin groups. In customizing we have possibility to assign purchase document condition types to origin groups, but i cannot choose conditions types from shipment document there. Please, help, Is there any customizing whehe i can do it?

Hi,
Generate table which include field Transportation planning point(or any other which is common) by T_03
Assign this table in access sequence by T_07
Then in condition type detail under tab changes which can be done option MANUAL ENTRIES - set blank (No limitations ) by T_06
Then maintain condition record in TK11 for all conditions
Here don't put any prices for condition just save
Now When you create shipment cost document all condition will come automatically,then user will put only price and save.
Kapil

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

Scale type D for group conditions

Similar Messages

Maybe you are looking for