Skip to Content

Change existing SD Pricing Procedure - help

Nov 01, 2017 at 02:55 PM


avatar image
Former Member


I am hoping to get some advice on an issue that we are facing. We have an existing SD pricing procedure which is outdated and requires many changes with new condition types and new account keys (new GL account assignment). From reading OSS Note 388112, it appears that I cannot change the existing pricing procedure and would need to copy the existing procedure and make changes to a new pricing procedure. All new sales orders would then follow the new pricing procedure. Existing sales orders would then have to be closed and then recreated to follow the new pricing procedure.

The problem is that due to the nature of our business, sales orders can remain open over a long period of time (over a year) and to close and recreate the sales order would be difficult due to the volume and also the integration with PS and MM.

I am looking at potentially phasing the changes so that we keep the existing sales orders and all new sales orders would follow the new pricing procedure. I am wondering if anyone else has had this issue and can provide advice/feedback on what approach they used?

In addition, does anyone know if I can change the existing automatic GL account assignment in the existing pricing procedure without negatively impacting the existing pricing procedure? In some cases I would use the existing account key and just point to another GL account. However, in other cases, I would need to create a new account key to attach to the existing pricing procedure. If anyone could provide advice and feedback it would be greatly appreciated!

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Veselina Peykova
Nov 01, 2017 at 04:05 PM

The note does not mention anything about recreating the existing sales orders.

It suggests creating a new procedure and assigning it in OVKK, which will be used for new documents and to complete the existing documents with the old procedure in the way you do now.

Did you try the scenario in a sandbox?

Create a few documents, process them to different phases, then assign the new pricing procedure in OVKK, create a few new documents, process them end-to-end, then process all documents that you created before switching to the new procedure.

Show 5 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Thank you for taking the time to reply to my question. I really appreciate it.

You are correct that the note does not mention recreating the existing sales orders. I must have read that in another forum posting.

I pondered recreating the existing sales orders into new ones because I thought that it would be confusing to have different pricing procedures because the closing process would be different for the new vs old/existing sales orders. This is further complicated by the fact that sales orders can remain open over long periods of time (over a year). Therefore there would be many existing sales orders for quite some time.

A number of the changes to the pricing procedure requested are related to GL account assignment. If I changed just the account key (pointing to a different GL account assignment) assigned to the existing pricing procedure, would that negatively impact the existing pricing procedure?

In other words I would keep the existing pricing procedure structure but change only the account key (and therefore the GL account assigned). Please see below screenshots:

Would this be ok? Or would it be technically considered changing the existing pricing procedure?

Any advice would be greatly appreciated!


vmtwe.png (15.0 kB)
16opq.png (111.8 kB)

Very few users (except power users) look at pricing procedure ID, most look at the pricing results, account determination screen and accounting postings.

I see no reason why the business will be confused by pricing procedure ID changes, but as you are going to change a lot of things - prepare good documentation, handle workshops with the key users, write what's new document and make sure this is distributed to end users.

I have done this pricing procedure switch a few times already and had not problem with users grasping the concept about different pricing procedures - new vs. old when they are given sufficient time to practice in the QA system.

As to your question about account determination changes - why don't you test this as well?

It does not take long to prepare examples and test and you will be then sure that you have not missed something important.

I ask the business to provide VKOA in templates - Sales together with FICO department, which means that the key users are well aware what postings are expected with the newly created documents.

Former Member

Thanks Veselina for your input and advice. We've never changed a pricing procedure here before so I was concerned that the users may be confused with the closing process for the new vs existing sales orders. In addition, the fact that we will have these existing sales orders open for quite some time would further complicate matters as this transition period of new vs existing sales orders will be over the period of at least a year - if not more.

With our current pricing procedure in our existing sales orders, the accounting staff must make a number of post-closing journal entries in order to ensure that the final closing journal entries are correct. It is very time consuming and cumbersome which is why I had hoped that I could change the account keys /gl account assignments first on the existing pricing procedure and then add the new conditions and new account keys in the new pricing procedure.

This would be somewhat of a two step process so that we can reduce the existing journal entries on existing sales orders and then plan ahead to reduce even more journal entries with the new pricing procedure in place.

I will definitely prepare lots of examples and testing. It is good to hear that you've done this pricing procedure switch many times without any issues with users grasping the concept of new vs old. I guess I'm a bit nervous about forging into unknown territory. You are correct in that most of the accounting staff review the closing entries very carefully so they would know which final adjusting entries they would need to make in the new vs existing sales orders.

Thanks again for your help!


It is completely normal to be concerned - from your explanation I understand that this is not a minor change.

If the processes differ significantly between the old and the new concept - explain to the users that documents created before date xx.xx.xxxx need to be treated according to the procedure described in document A and for orders created after this date they need to follow the procedures described in document B. Also, make users aware of the consequences when they create order with reference. If you are still concerned that this can be difficult and confusing for some users - build them a simple report where they can see the pricing procedure when they list open sales documents. It does not have to be fancy, just a query will suffice.

I have never modified settings for account keys for tax that are currently used in a live system, but it does not seem a good idea. If this is what you intend to do, please speak with your FICO colleagues first.

As to any VKOA changes - it is best to discuss with the billing and accounting/controlling department when it is the best time to introduce these into the productive environment.

Former Member

Yes, I am re-thinking the change in account keys. I don't think that I will make this change after all. I think that the transition will be much cleaner if there are no changes to the existing pricing procedure and sales orders. The closing process would be status quo for existing sales orders. Then, as you've mentioned, all new sales orders created after a specific date would follow the new process.

I really do appreciate your advice and thoughts as it really helps to get ideas from someone who has already been through this process :) Thank you once again!