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 called “Invoice receipt date” to the payment block? 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 standard MIRO functionality for this requirement?
I ran into the same issue with MIRO invoice receipt date tracking. Here’s what worked for me - use the business config settings in SPRO. You can grab the receipt date through document reference fields in the invoice header without doing heavy customization. Just activate the extra reference fields in vendor invoice config and map them correctly for payment processing. This way you don’t mess with complex table changes but still get what you need. Double-check your vendor field status groups to make sure the new field’s set up right for data entry.
In my experience with MIRO, I recommend utilizing the enhancement spot MM_INVOICE to integrate a custom field for the invoice receipt date. To modify the payment block, consider using the function group MRM1 for the necessary adjustments. Since the RBKP and RSEG tables don’t include this field, you would either need to create a new table or append a structure to accommodate the data. Additionally, incorporating validation logic for this new field is crucial. Thorough testing and proper transport management are essential to ensure the solution operates effectively across different environments.
Try using the MRM_ITEM_SUPPLEMENT BADI - it gives you way better control over payment block fields. I added a custom include to the RBKP table for the invoice receipt date, then modified dynpro 1420 in SAPLMRMH to get the date picker working. The tricky part is making sure data actually saves during MIRO processing. You’ll need to handle field population in your PAI/PBO modules and make sure it plays nice with the standard payment workflow. This way you keep data integrity but still give users the flexibility they need.
Check out BADI MRM_WORKFLOW_AGENTS or MRM_ITEM_DATA_CHECK, which are key depending on your specific requirements. I undertook a similar approach by creating a custom Z-table to store invoice receipt dates linked to document numbers, and enhanced the payment screen using SE80. It’s vital to integrate this into the payment workflow appropriately. Remember that this date must interact with other modules, so consider its impact on postings and reporting. Testing various invoice scenarios is crucial, as this could affect payment terms calculations.
try user exit MRM_INVOICE_PROCESS - this worked when I needed the same thing. You can add custom fields to the payment screen through this enhancement. Just remember to update the screen painter in SE80 to make your field visible. it’s a bit tricky but totally doable without touching the main tables.