Creating a Price record for a specific Sales Order

[Former Member]

Dear Gurus,

Greetings. My requirement is that we need to give a special price for a single Sales Order for the combination of Sold to Party / Material / Quantity.

That means this price should be used only once in the Sales Order and cannot be repeated in any other order for the same combination also.

The issue is if I make the PR00 as manual and enter the price in Conditions, then there is a chance that the user can go to Edit mode and change the price and with the no. of transactions being done per day it is next to impossible to track this aspect.

So I need the price condition type in non edit mode.

Then the only way to populate the condition value is to flow from the condition record with the condition type as 'B: Automatic entry has priority' or 'D: Not possible to process manually', then the users cannot change the value any time.

The difficulty I am facing is if I have to maintain a Condition record for only one Sales Order, my access sequence should be Sold to Party / Material / Sales Document (VBELN). System is allowing me to create a Table but not allowing me to initialise the field values when I create an Access Sequence saying 'Select a document field for VBELN'. In the Field Catalogue at the bottom of the screen, VBELN is not available either under KOMK or KOMP. What to do noiw?

Tried searching in the forum but gurus are saying add the field value from the Field Catalogue which as I said is absent.

How do I give a Sales Order specific price which should not be editable later on.

Thanks in advance.

Regards.

Venkat - Hyd

[Former Member]

Hi

You cant use the filed VBELN in the pricing calculation(condition table) since you can't input the sales order no to create the condition record. The sales order number is created internally by the system if your order number range is internal.

You can use what Mr.Krishna has suggested to achieve your requirement.

Regards

Rajkumar K

[Former Member]

Hi,

In view of your requirement SAP has given the following :

You can specify the maximum number of orders in a condition record. For example, you offer your customers a special discount on a new product. You want the discount to count for the introductory order and for one refill order. The system keeps track of the number of orders the customer places and, after the maximum number is reached, automatically deactivates the condition record. After deactivation the condition type no longer appears on the pricing screen in the order. In addition, the system automatically stores statistical data for condition records where a maximum number of orders is specified.

Specifying the Maximum Number of Orders

You can specify the maximum number of orders (up to a maximum of three) in the condition record. The condition update indicator must be maintained in Customizing for Sales for the corresponding condition types.

To specify the maximum number of orders:

Choose Logistics ® Sales and Distribution ® Master data.

You reach the Sales Master Data screen.

Choose Conditions and select the condition record you want to work with.

Within the condition record, choose Additional sales data.

Enter the maximum number in the Maximum number of orders field.

Choose Back to return to the overview screen of the condition record or save your work.

Now for your condition type with the key combination u can do above and u will get it.

Regards

Krishna

[Former Member]

Hi Krishna

Where is the max. no. of orders field in that additional data view in vk11.

rgds

Rheya

[Former Member]

Hi,

In your condition type - V/07 u need to tick condition update and then in VK11 u will find that field

Regards

Krishna

[Former Member]

May be it is my mistake that I could not convey my requirement correctly. Let me try again.

More like a Quotation and then a Sales Order. If I make a Quotation with a manual PR00 price and refer it to create a Sales Order, then the price in the sales order is in edit mode, then some one can go to VA01 or VA02 and change it, which I want to avoid. I need the condition value in non edit mode in the sales order, edit mode in Quotation (since I need to enter the special price). Price will be or should be used only for one ocassion.

My scenario is not a Quotation & Sales Order, I am only using this to explain that I need to give a special price in the sales order only once and then it should not be possible to use that price to create another sales order. In the change mode VA02 or display mode VA03, it should be in non edit mode.

Next time I will need to give another special price to some other customer again only for one sales order.

Since if I make a condition type manual in v/06, then in Quotation I can enter the price but in sales order it will be in edit mode, allowing some one to edit it which i want to avoid (it is not possible to check if anyone is changing the prices, since there will be around 300 to 400 transactions happeing per day).

How to do it?

Regards.

Venkat - Hyd

[Jelena]

I think the easiest solution for this would be just to have a manual conditions, something like a "price override". You can limit authorization for that condition to only small group of users.

All changes in the orders are tracked, so you'll see who changed the condition. Make sure the users are trained properly.

[Former Member]

Thanks Jelena for your valuable solution. I will definitely try out this suggestion. I think this will solve my issue.

On the other hand, as I said before, I cannot use a Manual condition type since it will be in edit mode for ever giving a chance for that value to be edited wrongfully. Again as i said before it is not physically possible to check to find if such prices are being changed due to the volumes involved.

So, I want to use a method where there is no chance of editing the condition value at any time by using a condition record, which flows into the sales order and that condition type can be set to non edit mode in V/06.

In the mean while, any other suggestions.

Regards.

Venkat - Hyd

Closing the thread since no more inputs for long. Thanks everyone. 24.11.2009

Edited by: yajee venkat on Nov 24, 2009 9:23 PM