Skip to Content
0

Delete inactive pricing conditions in Billing

Apr 12, 2017 at 10:32 AM

135

avatar image

Hello,

We have implemented the functionality of pricing condition exclusion. It is all working fine, however, we have a requirement from user that they do not want to see the inactive pricing condition in the billing document. In-short if a condition is inactive, it should be removed/deleted from the billing document- conditions tab.

Please suggest how this can be achieved. Manually the user will not do it as there are lot many billing documents created per day & there is an element of error.

Thanks for your answers.

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

3 Answers

Shanthi Kumar Juluru Apr 12, 2017 at 11:36 AM
0

It can be achieved only with little coding in billing user exist. You can delete inactive condition types from XKOMV internal table in the billing user exit.

Share
10 |10000 characters needed characters left characters exceeded
G Lakshmipathi
Apr 12, 2017 at 11:38 AM
0

You need to add this logic in a pricing routine or pricing user exit. But I am not sure, how far, that would be successful as ideally, both the condition types should be there in the table.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks for your answer. What would be the need to keep both the conditions as inactive conditions are of no significance.

Thanks for your answer. Apologies if the answer is naive.

0
G Lakshmipathi
Apr 12, 2017 at 03:40 PM
0
What would be the need to keep both the conditions as inactive conditions

As I already pointed out, even the condition types are inactive, the corresponding values should be posted in SD tables and I dont think, removing from the table is a Best Practice. On various SAP OSS notes (I am not sure on the note reference), SAP have very clearly mentioned that if your business process is running with some pricing exit and if there is a change in coding, you should be very very careful. So taking into consideration this point, you need to do a thorough and negative testing in development once code change is done.

Share
10 |10000 characters needed characters left characters exceeded