I need to update the payment block field through automated programming instead of manual entry. Can this be done using any available BAPIs, function modules, or custom ABAP code?
I’m working on a project where we need to set payment blocks automatically based on certain business conditions. The manual process in MIRO works fine, but we want to streamline this through programming.
Has anyone successfully implemented this functionality? What would be the best approach to achieve this programmatically? I’ve looked into some standard SAP functions but haven’t found a clear solution yet.
Any guidance on the right function modules or BAPIs to use would be really helpful. Also, if there are any specific authorization requirements or considerations I should be aware of, please let me know.
You can also use function module CHANGE_DOCUMENT_FB03 with BAPI_INCOMINGINVOICE_CHANGE for complex scenarios. FB02 transaction works great through BDC recordings when you’re handling multiple fields at once. Just make sure your workflow’s set up right - payment blocks usually trigger approval processes. When I did this last year, we had to modify the document change tables (CDHDR/CDPOS) to track everything properly. Check your system’s customizations first though. Some companies have custom validation exits in user exit MRMH0001 that’ll mess with programmatic changes. The payment block field (ZLSPR) validation runs at both header and line item levels depending on how you’ve got it configured.
I had the same issue a few months back. BAPI_INCOMINGINVOICE_CHANGE works great for this - you can modify payment blocks on vendor invoices after they’re posted in MIRO. Just populate the PAYMENTBLOCK field in the INVOICEHEADERDATA structure with whatever block code you need. Make sure your authorization objects are set up right first (F_BKPF_BED and M_RECH_WRK). Don’t forget to commit explicitly with BAPI_TRANSACTION_COMMIT after it runs successfully. One heads up - you’ll need the original document details as input, so grab the invoice document number and company code first. Your payment block codes need to match what’s in your SPRO config too.