usage of price group KONDA

[former_member182378]

Hello,

Please comment on the below usage of price group KONDA by a client

KNVV-KONDA is blank, while creating sales order with this customer, the user is manually inputting KONDA at item level. They input this because they want to classify that the material is relevant for discount and some discount is also populating in that line item. (pricing condition record maintained with some fields and price group)

Price group KONDA is meant for the customer and not for material. This way of using KONDA at item level for item level discount does not seem the “right” usage of KONDA. What is your opinion?

TW

[jignesh_mehta3 · Accepted solution]

Hello TW,

Price Group (KNVV - KONDA) is generally used to bring together a particular group of Customers.

In one of my assignments, the client had a scenario where Public Hospitals that buy under a Government Tender get a special price for Materials specificed by Government authorities.

For his purpose we have created a new Price Group - Hospitals with Tender and assigned the same to respective Customers. Now in in Pricing Procedure we have a Tender Discount condition and the Access Sequence used is Price Group/Material.

This ensure that Tender Discount is available only to Customer who belong to particular Price group.

Hope this helps.

Thanks,

Jignesh Mehta

[jobis · Accepted solution]

Hi TW,

Is KONDA in sales doc coming from the partner SP or any other..?  If its not from SP, then it could be of use at item level.

Otherwise, it could be just used as a field for determining a different value for any condition for different items, as is the case in your OP.

Thanks

Jobi

[former_member182378 · Accepted solution]

Thanks members for your posts!

For this client, in several markets price group is used in connection with material, at item level in sales order. Some markets (sales organizations) have enhancement, in these the price group is populated automatically and for the rest it is manually entered. The price group value depends upon the product and the product hierarchy.

As observed at the start, KNVV-KONDA is blank.

Business does not want to go ahead with any changes, because it is working fine. There are other empty fields, at line item level, in case they want to use, at a later stage.

Thread is closed.

TW

[moazzam_ali]

Hi TW

Yes you are right. This is not the right way to use this field. This field is for customer grouping not for materials. If this client needs to group customers in future they are going to need this field.

For materials there are other fields that they can use like material pricing group KONDM.

Did you ask the client that what is the reason they are using this field instead of KONDM and who asked them to follow this practice?

Thank$

[former_member182378]

Thanks MoazzaM, Jignesh!

But then why has SAP given KONDA at item level also?

(With required configuration, VOV7, activate Business items) user can input different KONDA per line item in the order.

TW

[moazzam_ali]

Hi TW

If we see the fields in header and item we can see that customer based fields are there in both screens where as material based fields are only there in item level. There could be following reasons for this.

Customer is same for all items but material could be different for each item.

If we create sale order and afterwards change groups in customer/material master data it doesn't change in sale order automatically. We have to do it manually.

If we are using some field for pricing and we are not sure about its group at the time of master data creation we can add here manually.

These are some scenarios which comes in my mind and there could be many others. SAP delivers many fields that are editable in standard and we make them output only with variants in sale order for instance pricing date or payment terms. These material or customer fields could also be greyed out based on scenario or customer's requirement.

Thank$