46C Payment blocking and LIV (Logistics Invoice Verification)

[Kjetil Kilhavn]

By changing the block code which is "Not changeable" from A to R problem 2
is solved. So now only problem 1 remains. Any suggestions as to what would
be the best approach? I can think of two different ones myself, but maybe
someone out there has a better one.
 
1) Function module creating BSEG CREATED event
A function module can be registered to be triggered by the BUS2081 posted
event (direct entry in SWE2)
This function would check whether the invoice was blocked, and raise an
event for BSEG.CREATED if it was
 
2) Create an own workflow for payment blocked BUS2081 documents
I would still need a function module to find out if the document was
blocked, but it could then probably be a check function for the event
linkage. This would perhaps make it easier to handle them different from
the blocked BSEG documents if that becomes an issue (currently they are
treated exactly the same way, and it is always the BSEG document that is
displayed).
 
Let the flow of good ideas start!
--
Kjetil Kilhavn
 
 
 
 
 
                    Kjetil
                    Kilhavn              To:     sap-wug at listserv.mit.edu
                                         cc:
                    11.06.2002           Subject:     46C Payment blocking and Logistics invoice verification
                    09:04
 
 
 
 
 
I was about to send a long message when I remembered to check the archive
first (very useful), so you won't have to read an even longer sad story :-)
Since then I have come further, and for FI invoices our Statoil-specific
solution is now probably going to be OK. However, LIV has been a problem
for many a developer it seems - and now it is my turn.
 
It is a requirement here that all invoices that are without reference to
purchase orders and which exceeds certain amounts (depends on company code)
should be blocked for payment until they have been approved by a person
responsible for the cost object they are assigned to.
 
My problem is that registration of invoices is performed both via FI (FB60)
and MM (MIRO) - the latter of which is the problem. As mentioned the FI
invoices are now probably going to be OK. Setting up (through the
Customizing / Implementation Guide (SPRO)) a payment block for LIV
documents was not to difficult either. There are two problems remaining.
 
1) No event for amount blocks
When registering an invoice in MIRO which ends up as blocked due to the
amount limit there is no event.
There are two events defined on BUS2081 - and they are for price and
quantity differences. There is no separate event for amount blocks. When a
LIV document is blocked due to price differences the corresponding event is
triggered.
 
2) The payment block code in the FI document is not the same as for an FI
invoice blocked automatically
While the FI documents get payment block code A (which has been set as Not
changeable), the follow-on document to a LIV invoice gets payment block
code R (Invoice Verification). I can't find a reference to this code in
customizing, and this means the block can be released manually (since only
one code can be Not changeable).
 
Does anyone have any experience with payment blocking due to amounts?
 
I suspect an object extension is what I have to do - we already have a
ZBUS2081, so I will just continue enhancing that.
The plan (unless someone has a solution which avoids extending the object)
is to define an event for amount blocks, a use the ReleaseSingle method to
release the block when approval has taken place and have a second step in
the workflow which releases the block on the corresponding FI document.
--
Kjetil Kilhavn
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.