I need assistance with a project that involves changing the payment block for vendors using programming instead of doing it manually in MIRO. I’m exploring various options but am uncertain about the most effective method. Has anyone here managed to implement something like this? I’m particularly looking for standard BAPIs or function modules that let you update this field. I’ve gone through some documentation, but I haven’t found a clear path. The aim is to streamline this process so that users are not required to navigate to the transaction to adjust the payment block status every time. Any insights on the best way to handle this would be greatly appreciated. Additionally, are there any authorization concerns or specific points I should consider while developing this solution?
BAPI works but gets messy with multiple vendors or regular runs.
I’ve done similar SAP integrations - building automation outside SAP works way better. Use RFC calls to connect to MIRO and handle payment block updates through a proper workflow.
I set up automated triggers that watch vendor status changes and update payment blocks based on preset rules. Skips all the manual transaction stuff and you can add approval workflows too.
For auth issues, make sure your automation service has proper SAP credentials and test everything in dev first. Key thing is solid error handling when RFC fails or SAP throws auth errors.
Latenode makes SAP integration dead simple. Build the whole automation without messy ABAP code and it handles RFC connections reliably.
I tackled this same thing about 6 months back - BAPI_VENDOR_CHANGE is definitely your best bet for payment block changes. You’ll need to fill out the VENDORCHANGEACCOUNTING table with the payment block field (ZAHLS) and flip the right flag in VENDORCHANGEACCOUNTINGX to mark which fields you’re updating. Here’s what tripped me up at first: the payment block field acts totally different depending on whether you’re hitting general vendor data or company code specific stuff. Double-check you’re targeting the right level. Also heads up - some payment block values need specific posting periods open, so validate that before you try updating. And seriously, build in some logging because MIRO gets picky about field validations and you’ll want to catch those errors.
definitely look into BAPI_VENDOR_CHANGE_BANK_DATA or maybe the FM VENDOR_MASTER_DATA_CHANGE. i did a similar thing last year and it went smoothly. just ensure you have the correct authorizations, otherwise you might run into access denied issues.
Just dealt with this three weeks ago. Skip the individual BAPIs - use CHANGE_VENDOR function module instead. It’s way more robust for payment block changes. The big difference? CHANGE_VENDOR handles all the payment block validation internally. With standard BAPIs, you’re stuck managing every field dependency yourself. Fill out the LFB1 structure with your payment block code and set the update indicator correctly. Here’s what tripped me up: some payment block codes are company-code restricted. Make sure your user has the right company assignments. Running this in batch? Wrap it in a commit work statement. Payment block changes won’t stick otherwise. Test in sandbox first - these blocks directly hit your AP processing.
honestly mate, skip the fancy BAPIs for now. just hit table LFBK with an update statement if you need something quick n dirty. i know it’s not best practice, but sometimes u need fast results. back up the table first tho - payment blocks are critical and one bad update will wreck your whole AP process.