Prevent pricing errors in sales order

[Former Member]

Hi,

While creating a new condition price with VK11 it can happen that pricing data is wrongly typed in. For example a wrong pricing unit is entered. Instead of a pricing unit of per 1000 pieces the user enters per 1 piece. This can have a big impact in the order value, and adds time to correct it especially it invoiced with the wrong value.

Has anyone developed a solution to avoid these type of condition price errors? For example, like a pop up message appear in order creation upon saving it, notifiying the fact that the price is wrong.

Thanks

[Lakshmipathi · Accepted solution]

I dont think, anybody has developed some control for this since these are all user discipline.  If you want to have any such control, first of all, you need to identify for which material codes, pricing unit differs.  Next, based on certain criteria, may be material group, you can group these material codes and record the same in a zee table with the allowed pricing unit.  Finally, with the help of USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ), you can validate the pricing unit.

G. Lakshmipathi

[Former Member · Accepted solution]

Thanks for your reply G Lakshmipathi.

Proper user training to stop this type of behavior was my first response back to the business. But not accepted as a closed case. We have around, give or take, 100 backoffice sales people around Europe entering in new prices. The most common mistake is entering a price per 1 piece. Our standard is a price per 1000 pieces. Very often there is a large turnover of new staff in this area and knowledge transfer for creating prices correctly is not executed well or at all.

Thanks for the idea of a variable table and the mentioned userexit. It does make sense to validate this while creating the condition records than catching it later in the sales order.

[former_member182378]

Tony

Additional comment: A condition type which is D (Not possible to process manually) for field Manual entries, in V/06.

Even if you incorporate the logic of getting a pop up in the sales order, apart from deleting that particular line item and then changing in VK12. And then creating the line item again, in the sales order.

There is no way to correct, the scenario you have given, in the sales order itself!

[Former Member]

Thanks for the input TW.

Proper user training to stop this type of behavior was my first response back to the business. But not accepted as a closed case. We have around, give or take, 100 backoffice sales people around Europe entering in new prices. The most common mistake is entering a price per 1 piece. Our standard is a price per 1000 pieces. Very often there is a large turnover of new staff in this area and knowledge transfer for creating prices correctly is not executed well or at all.

It does make sense to validate this while creating the condition records than catching it later in the sales order.

[former_member182378]

Tony,

According to your example / scenario, the error is done while maintaining the condition records, so if you need to incorporate validation (in the system), it should be done while saving condition records. And not while creating the sales order.

http://scn.sap.com/thread/126925

As already suggested by G Lakshmipathi, entering data in SAP whether master data or transactional data should be done correctly by users; this is a matter of user discipline.

If a company starts with investment in enhancement to validate master data, where would one stop...

[moazzam_ali]

Hi Tony

MR Lakshami has given you the tight answer. You have to go for this valiation at sale order level with suggested process. Moreover I would like to add in Lakshami's post that what if you validate the condition record before creating sale order.

Why don't you use Pricing Release statuses and create a status with block status. User A maintain condition records and these are not applicable on sale order until a 2nd user B checkd all condition record and release them. It will be check on first level which is already available in standard and SAP has given solution for this in Pricing condition's Statuses. IF you want to validate it at second level then go for above process which is already explained very well by Mr. Lakshami.

Thank$

[Former Member]

Hi,

This is a master data issue. so no where you can put any logic to check this in standard SAP.

You need to do enhancement based on your requirement like material or  material group, or Minimum order value, etc etc..

Regards

Pitabash