I need help with customizing the MIRO transaction in SAP.
Currently in the Payment section, users can only select the Baseline Date for payments. However, my business requirement is to allow users to choose the Invoice Receipt Date instead of the Baseline Date.
I’ve been looking into various customization options but haven’t found a clear solution yet. Has anyone successfully implemented this kind of field modification in MIRO before?
Specifically, I’m wondering:
Are there any available BADIs that could handle this customization?
Is there a BAPI approach that might work for this scenario?
What would be the best technical approach to achieve this functionality?
Any guidance or experience with similar MIRO customizations would be really appreciated. Thanks in advance!
I ran into this same issue about two years ago. We used BADI MRM_PAYMENT_TERMS - it’s perfect for tweaking payment fields in MIRO. You’ll need to extend the screen and handle the date logic in the BADI. Here’s what worked for us: create a custom field on the payment tab that pulls from RBKP-REINDAT (invoice receipt date) instead of the baseline date calc. Then modify the payment terms logic to use that as your reference point. The tricky bit is making sure you don’t break existing payment runs and dunning processes. Test the hell out of it with FAGL_FCV and payment program F110 to make sure everything flows right. Took us about a week including testing, but it’s been rock solid through multiple SAP updates. Way cleaner than screen exits and no transport dependencies either.
Been there with SAP customizations. BADIs and enhancement spots work but they’re a nightmare to maintain and upgrade.
I’d build an automated flow outside SAP’s structure instead. Intercept the MIRO transaction data, modify the date field logic, and push it back seamlessly.
Built something like this for our finance team last year. The workflow grabs invoice data before it hits MIRO, users pick their date field through a simple interface, then everything processes automatically. No core SAP changes.
You get full control over the user experience without touching SAP’s standard functionality. When SAP updates, your customization stays intact.
Takes about a day to set up and you’re done. Way cleaner than BADI implementations that break with patches.
yo, joec! have you checked the enhancement spot FI_INVOICE_PROCESS_UI? I’ve used it for some similar mods in MIRO. there’s also a BADI INVOICE_UPDATE that could be good for the receipt date thing. not entirely sure about the exact stuff, but def worth a look!
MIRO customizations are tricky, but try the config route first before jumping into custom code. Hit up table T001 for company code settings and check payment terms in OBB8. You can often get what you need by tweaking the baseline date calculation through standard config instead of coding.
If that doesn’t cut it, try user exit MV45AFZZ or enhancement MM07MF05 - they’ll give you access to the invoice document flow. I’ve had better luck modifying payment proposal logic through these standard hooks than messing with screen changes. The trick is catching the date calculation before it hits the payment screen, not changing the UI.
This approach made it through three SAP upgrades without any rework, which saved us tons of maintenance headaches later.