I’m working on a project in S/4HANA and I need some help with MIRO and withholding taxes. Right now when we do MIRO for a vendor all the withholding taxes set up for that vendor show up. But we want to show only the taxes that match the specific PO type we’re working with.
For example if a vendor has EH taxes 01, 04, 06, and 07 but we’re working with a PO type that only uses 01 and 04, we want to display just those. I tried using BAdIs MRM_WT_SPLIT_UPDATE and MRM_HEADER_CHECK but they didn’t work. Can anyone offer any advice on how to achieve this? Thanks a lot!
hey pete, i’ve dealt with similar issues before. have u considered using a custom enhancement to filter the withholding taxes based on PO type? u could create a user exit in the MIRO transaction that checks the PO type and only displays relevant taxes. might be worth exploring if the BAdIs didn’t work out for ya
I’ve faced this challenge in a recent S/4HANA implementation. One approach that worked for us was implementing a custom function module that gets called during the MIRO process. We linked it to the PO type and configured it to filter the withholding tax options accordingly.
To set this up, we created a Z-table to map PO types to allowed withholding tax codes. Then, we developed a function module that reads this table and filters the tax options. We integrated this into the MIRO process using an enhancement spot.
It required some development effort, but it gave us precise control over which taxes appear for each PO type. The business users were quite happy with the streamlined process. Just ensure you thoroughly test across different scenarios to avoid any unintended consequences in your withholding tax calculations.
yo pete, have u tried using a custom enhancement? i had a similar issue and created a user exit in MIRO. it checks the PO type and filters the taxes. u could set up a custom table to map PO types to allowed tax codes, then use that in ur enhancement. might take some work but it cud solve ur problem
I’ve grappled with this exact issue in a recent S/4HANA project. What worked for us was implementing a custom exit in transaction CMOD. We created an enhancement at the point where MIRO retrieves the withholding tax codes. In this exit, we added logic to check the PO type and filter the tax codes accordingly.
To make it flexible, we set up a custom table (let’s call it ZWTAX_PO_MAP) to store the mapping between PO types and allowed withholding tax codes. The exit reads this table and applies the filter.
It took some trial and error to get it right, especially handling different scenarios like POs with multiple items. But once we ironed out the kinks, it worked like a charm. The users were thrilled with the streamlined process.
Just a heads up - make sure to thoroughly test across various PO types and tax scenarios. And don’t forget to update your custom table whenever there are changes to PO types or tax codes.
In my experience, tackling this issue requires a combination of configuration and custom development. One effective approach is to leverage the condition technique in SAP by creating a custom condition type for withholding taxes and linking it to the PO type. You then set up a determination procedure to filter the applicable taxes during MIRO processing. This involves defining a new condition type in SPRO, establishing a custom table to store PO type and tax code relationships, implementing a pricing procedure with the new condition type, and modifying the standard MIRO pricing procedure to incorporate your custom step. This method provides flexibility without relying on extensive coding and integrates well with standard SAP processes, although some trial and error during setup and testing may be required.