SD Billing - Pricing error in Billing item

[Devonwtxus]

Dear Experts

Does anyone know of a way; config or abap to prevent a delivery item to go to billing if the new billing item results in a pricing error during VF01/VF04?

Background; we have a couple of very rare scenarios where the pricing is fine on the sales order but by the time the order gets through delivery processing to billing...along with some errors on the users part...well the re-pricing at billing time does not come up with a price.

The price is basically a copy of PR00. And R/3 does issue a message V1 801, and stops the item from posting to accounting due to the error.

But it's still causing issues for Finance/Sales, and difficult to manage.

Really hoping there's a way to prevent the item from going to billing. So the delivery item can just sit in the system until the pricing issue is addressed and then go to billing in the next run.

Even better would be if it showed up in the billing error log so we could track them.

I've dug through copy control, vofm, and config in the billing area. But seems like the item has to go to billing so it can be re-priced in order to determine if there's a valid price or not. Which then leaves us with the item - unless there might be a way to use userexit_fill_vbrk_vbrp to prevent the item from saving with the billing document.

But wondering if I've missed something in config for an easier approach?

Any ideas would really be appreciated.

Best Regards,

Devon

[Former Member · Accepted solution]

Devon,

My suggestion is why don't you relook in the customer requirements and do the needed configuration. And check with authorizations provided for Delivery(Vl01N) and billing(VF01) should be different. Similarly the persons who are to release to accounting using VF02 should be maintained seperately.

You can have a posting block deactivated so that automatic flowing of values to G/L account can be stopped.

Maintain two pricing process one at the sales order level and another at Billing Level.(if price changes) Discipline the end users from commiting the errors

Regards

Sathya

[Devonwtxus · Accepted solution]

Hi Sathya,

Thank you for the reply.

We'll definitely take another couple walkthrough's on the configuration. Really, really hoping that we missed something here. Although the solution has been in production now 6 years.

Definitely agreee that the authorizations are important to meet the segregation of duties, and they've been very diligent in this area to meet their SOx and other regulatory requirements. One of the challenges in this issue has been that most the system updates are automated by batch jobs and many from interfaces to internal and external systems. Rarely does a user handle a document. Which has made it difficult to see where this originated. Luckily this has only occured a couple times in last several years.

But when it does occur, it's after the fact that we find out and is not fun to deal with.

I like your suggestion on disciplining the users. Part of this research is to see if we can determine what if any changes we can make on the users end without making significant changes to the business process.

Hoping to get some more time in the next few days and dig in to this a little more. My original thoughts were that R/3 must give you some way to exclude these items in copy control, config, billing due list, or even userexit. Which would be a nice quick win.

But haven't found anything so far.

Best Regards,

Devon

[Devonwtxus]

Closing this one. It has been open a while.

It doesn't occur very often, so this is being handled through a manual procedure.

The only time that the issue becomes significant is around month-end/year-end when all posting errors must be corrected.

[claudia_neudeck]

last reaction was before 2 month

[Former Member]

Hello,

Since the requirement is to have a control or check after the billing document is created and then repriced, the most logical way would be to use the exit "userexit_fill_vbrk_vbrp"

in this a check can be put for the message mentioned or else the code for checking the value as required, if the check fails then the item to be deleted.

hope this helps

Thanks

akasha