I’m working with the MIRO transaction and need to customize the payment section. Currently users can only select the baseline date, but I want to give them the option to choose the invoice receipt date instead.
Is it possible to add a custom field for “Invoice Receipt Date” in the payment block of MIRO? I’m looking for any available enhancement options like BADIs or BAPIs that would allow this modification.
Has anyone successfully implemented something similar? What would be the best approach to extend the MIRO interface with this additional date field? Any guidance on the technical implementation would be really helpful.
I’ve done similar customizations in MIRO and found enhancement spot MRM_LOGISTICS_INVOICE works better than the payment terms BADI mentioned above. Check out the MRM_HEADER_CHECK implementation - that’s where you’ll add your custom field logic. The tricky part? Making sure the field actually saves to the database. You’ll probably need to extend table RBKP with a custom field using an append structure. I’d start with a custom screen variant to test the UI changes before tackling the backend logic. Don’t forget proper field validation - invoice receipt dates have specific business rules to follow.
hey! for adding that invoice receipt date field, you can use BADI MRM_PAYMENT_TERMS. also, dont forget to update the screen painter for the new field. it worked fine for me, but just be cautious about data persistence issues!
Just modify the PBO/PAI modules directly in the MIRO screen. The field’s already there in RBKP-BLDAT - it’s just hidden. Quick screen painter change in SE80 and you’re done. Invoice receipt date shows up right away. Way easier than messing with BADI implementations.
Been there, done that. MIRO customizations suck because you’re stuck with legacy SAP code that wasn’t built for flexibility.
Yeah, those approaches work, but you’re looking at months of dev, testing, and maintenance nightmares. Every SAP update might break your custom code.
I hit this same problem last year. Instead of diving into SAP customization hell, I built workflow automation that handles it outside the system. It grabs invoice data before MIRO sees it, lets users pick their date fields through a simple web interface, then pushes everything to SAP with dates already mapped correctly.
Took me 2 days vs the 3 months our SAP team quoted for the custom BADI route. Zero risk of breaking during upgrades.
The automation does data validation, business rules, and sends notifications when invoices need attention. Users actually like it because the interface isn’t from 1995.
Skip the headache and automate around the limitation instead of wrestling with ancient SAP frameworks.
I did this same thing about six months ago. Used enhancement framework instead of the old SMOD approach. You’ll want enhancement spot MRM_INVOICE_POSTING - gives you way better control over payment section fields. Pro tip: use implicit enhancement points in include MRM_PAYMENT_F01. You can add your custom field logic without messing with core SAP code. Adding the field is easy - the real pain is document splitting logic afterwards. Invoice receipt dates mess with how SAP calculates payment terms, and that screws up FI document creation. Had to customize payment proposal programs too since they ignored the new date field for vendor payment runs. Testing was a nightmare - took way longer than development because every payment scenario acted different with the custom date. Double-check your existing payment terms configuration before you go live or you’ll hate yourself later.
Those technical approaches work, but I’d start with a screen exit using transaction SMOD to check for existing user exits in MIRO payment processing. Look at enhancement MRMH0001 first - it’s got several function exits that might save you from building custom BADIs. I’ve done invoice date modifications before. Adding the field isn’t the hard part - it’s making sure it plays nice with SAP’s payment run logic and dunning procedures. Your invoice receipt date will mess with aging calculations and cash flow reporting, so test how downstream processes handle the custom field. Before you build anything custom, check configuration table T052 for additional date categories. SAP often has the functionality already built in - just buried in standard config and not shown on the default screen. Pull up the field catalog for MIRO and see what’s available but hidden.