BUS2081 - Incoming invoice blocked due to QUANTITY (Rel. 4.6c )

MacPherson, Graeme (AU - Melbourne) gmacpherson at dc.com
Thu Jan 31 22:22:08 EST 2002


Hi Torsten
 
I implemented this workflow scenario on 46B and we had 2 different processes
(& hence two different workflows) for invoices blocked due to quantity and
invoices blocked due to price. The quantity block workflow notified the
buyer of the block who would then chase up the requester of the goods to
enter a goods receipt (if appropriate).
 
Once the requester posted a goods receipt, the quantity block was cleared
when MRBR is executed which also clears the work item.
 
I would suggest that your workflow is not designed to delete quantity blocks
and that you should possibly alter your process instead. In the case of a
price block, it may be appropriate to delete a price block through workflow
but this is not the case for quantity blocks.
 
Also, from a technical point of view, there are 3 tables which you would
have to delete/modify: RBKP_BLOCKED, RSEG and BSEG. The standard transaction
MRBR takes care of all this and raises the necessary events to drive the
workflow.
 
Cheers
 
Graeme MacPherson
Senior Consultant
Deloitte Consulting, Melbourne
Ph: +613 8615 7000
Mob: 0414 473 554
 
-----Original Message-----
From: Torsten Schnorpfeil [mailto:torsten at processflow.de]
Sent: Friday, 1 February 2002 2:40 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: BUS2081 - Incoming invoice blocked due to QUANTITY (Rel. 4.6c)
 
Hi Flowers,
 
I'm currently working on a workflow for processing incoming invoices
blocked due to quantity. The object 'BUS2081' provides a method to check
if the price block can be deleted when there are no price variancies
anymore. Such a method doesn't exist for quantity (unfortunatly)! And
you can't just simply delete the blocking flag on the table RSEG b/c the
variances still exist. So I need a consistent way to solve that (e.g.
Function module, etc.)! Did somebody solved this already? if so, how?
Any suggestions highly appreciated!
 
 
So long, let it flow...
 
Torsten
 


More information about the SAP-WUG mailing list