Skip to Content
0

PO block but allow invoices & retention payments

Jan 04, 2017 at 07:42 PM

31

avatar image
Former Member

Hey everyone

I have a question specific to blocking POs, which I do using MK05...

I use SAP for subcontractors we use and need to block and unblock their accounts as required - where they are not authorised for works anymore but may have been, and did do works for us in the past. As I use them for sub-contractors rather than materials order (which is done separately), I need to block the whole account (under the particular plant / company code; this part, I can do) So I don't need to block specific parts of the account, it's just a specific type of block I need.

So, say, where a sub-contractor's account is blocked under MK05 for a purchasing block, the problem is that if there either invoices outstanding or retention payments to be released, the purchasing block instates a block so that no payments whatsoever can be released (unless the block is lifted). So, where they aren't allowed to work for us in the future, but need to be paid for works in the past, is there a function that allows me to do stop a PO from being raised for future works whilst releasing payments for those already done?

I would have thought that by leaving a posting block active on the system, it would leave the option available but it doesn't (TC: XK05) as posting invoices etc are technically posting, but this may be a lack of knowledge on my part as I don't have any involvement in the posting of such documents and may be using the terminology wrong....

I would have also thought then, that by restricting the code under:

Block for quality reasons - Block function and then specifying "01" - which states "Block purchase order" that it would limit it to my requirements but this also seems to be falling short.

Do let me know if it just my lack of SAP naigation (which is highely likely) that is causing this or if there is indeed capacity for this at all

Many thanks

Ellie

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

0 Answers