Workflow: invoice blocked due to quantity (BUS2081)

[Former Member]

Hi all

First let me mention that I'm not a developer but a FI/CO consultant and new in this forum as well. So please excuse if this posting is in the wrong forum of if the question is stupid.

We want to optimize the process of invoice verification. Therefore I implemented the Workflow WS20000397 which works great.

But this workflow only deals with price-blocked invoices. What about the quantity-blocked ones?

For this topic I found no information at all, only the Workflow WS00400026, but I'm not shure if this is still to be used with newer releases (4.7, Basis release 620).

But anyway I tried to connect WS00400026 to BUS2081 in the function "event type linkages" with the event BLOCKEDQUANT where I entered WS00400026 as the receiver type.

Now I'm not shure if this Workflow and the procedure is correct because a) I could not find any information about this and b) the "linkage activated" will automatic deactivated when posting an invoice.

Could someone give me some hints how to deal with the quantity blocked invoices and workflow?

Thank you and best regards

Wolfgang

[Former Member · Accepted solution]

Wolfgang,

This may be a bit late, but I have just found this thread. I am looking also looking to tidy up an IV process using Workflow. As you have stated the price variance process is relatively straight forward, but the quantity variance looks to be a bit harder to figure out. The answer will be in BUS2081 somwhere as the event IncomingInvoice.blockedQuant tends to suggest it.

WS00400026 may not work (if you are in a 4.7 environment), as it contains Invoiceitem.CallCreditMemo

which calls the obsolete transaction 'MRHG'. Check SWE2 and may sure that the Event Type Linkage between BSEG_MMIV and BLOCKED_QUANTITY is deactivated. If I find a solution I will definately let you know.

Regards,

Paul...

[Former Member · Accepted solution]

Hi Paul

Thanks for this hint - I'll check it out. It's never too late since I implemented for the moment only the workflow for the price variances without the quantity thing.

When ever you find out something I'll be happy to hear about it.

To all other people here: doesen't any company face the problem with incoming invoices and quantity differences? How do you handle this?

Thanks

Wolfgang

[Former Member · Accepted solution]

P.S.

oh, I forgot: if I can be of use with my two nice little flowcharts (one for the IV, the other for the release), let me know and give me some contact. The charts are done in EXCEL so everybody can use it. Unfortunately they're in German, but since we're talking about flowcharts and not huge text based documents it shouldn't be a problem...

[Former Member]

Wolfgang,

Have managed to get this working, but took considerable amount of time and development effort. The problem with the SAP standard workflow for qty variances is that it is effectively the same as WS200000397 - if you look at workflow task TS91000006 you will see what I mean i.e. the task name is 'At least 1 item blocked for quant reas.?', yet the step name for it is 'Is there at least 1 item blocked for price reasons?'!!!

The main point being here is that it checks on RSEG against SPGRP (price variance check box)instead of SPGRM (qty variance). In order to get this working you will need a developer with reasonably comprehensive ABAP and workflow experience, as a number of custom function modules will need to be generated and coded. Not being a developer I can't really give you any specific detail into what needed to be changed but just a 'heads up' to let you know that it is achievable.

The results are essentially the same from a user perspective (as it uses all the pricing variance functionality). I also tied in a role resolution to it, so that based on the Purchasing Group of the originating PO, the workflow would be routed to the appropriate Buyer(s). The final product delivered to the customer is quite sharp.

[Former Member]

Wolfgang

Wondering if you use the "Mail to Purchasing" functionality as well when you have a price difference?

As well, what is the work effort required to activate WS20000397, as this maybe a better solution for us.

I too am not a developer, rather I do configuration and support for our SAP system.

Regards

Joan Gourlie

[Former Member]

Hi Joan

Good question. First I tend to use this mail function, but then I decided to implement the workflow because

a) I was wondering how this works g and it is kind of sexy

b) I needed already a workflow for the Investment Management and wanted to stick on this technique

c) later we want to scan incoming invoices where we also will need to work with Workflows

d) the WF provides some functions like jumping directly to the invoice and order, delete blocking reasons or change the order

e) the WF could later be modified to cover more or other requirements

Of course the receipant of the Workitem also gets an eMail (via Internet) to let him know about an incoming workitem.

The most time I needed to find out how this works. Now it's just a piece of cake (as long as the SAP-standard WF for this is used without any modifications); would take not more than 15 Minutes to set it up again... no joke. But this depends also on the release you're on.

Of course you have to make a good end user documentation (but you have to anyways for the invoice verification) and about two good flow charts. This together with some trainings really needs the time.

Bye

Wolgang