Ansicht
Dokumentation

MM_PUR_S4_PO_MOD_TAX - BAdI: Modify Tax Jurisdiction Code of Purchase Order Item

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Purchasing (MM-PUR-PO) component.

You can use this BAdI to determine the tax jurisdiction code in purchase orders and use it, for example, on item level for tax calculation purposes if the tax jurisdiction code is maintained in the delivery address.

In the standard, the system takes the following sources into account for the jurisdiction code: reference documents (RFQ, contract), plant table, manual user input, account assignment object (if a tax jurisdiction code is maintained here). In the process, the system overwrites the previous value in this list in each case. If, for example, you have maintained a tax jurisdiction code for a purchase order item with the account assignment object, this entry wins over the entry in the plant table.

If you implement the BAdI MM_PUR_S4_PO_MODIFY_TAXJURCODE and a purchase order is created, the tax jurisdiction codes previously determined by the system will be overwritten with the value provided from the BAdI implementation. The checks provided in the system (for example, whether the combination of tax code and tax jurisdiction code in the system is valid) continue to be run. If you implement this BAdI you must ensure that a valid tax jurisdiction code is returned. In addition to returning the tax jurisdiction code of the delivery address, another option is to use an external system for tax calculation purposes here. Manual input of the tax jurisdiction code by the user is taken into account in all cases.

This BAdI is primarily intended to be used in the Custom Logic app.

In SAP S/4HANA (on-premise), in SE18/19, you have the more powerful BAdI Tax jurisdiction code taken from address (ME_TAX_FROM_ADDRESS) at your disposal.

In the standard system the BAdI MM_PUR_S4_PO_MODIFY_TAXJURCODE is not active (not implemented).

The BAdI is not filter-dependent

The following information applies if this BAdI is used in key user extensibility:
The BAdI cannot be used multiple times

Note
With this BAdI you can use the optional importing parameter:
PURCHASEORDERITEM_OLD.
This parameter contains the item data of the previous roundtrip, for example, the data before the last change was done.

If you implement the BAdI MM_PUR_S4_PO_MODIFY_TAXJURCODE the following data is available to control the system behavior in determining the tax jurisdiction code:

• Purchasing document header (PURCHASEORDER)

• Purchasing document item (PURCHASEORDERITEM/PURCHASEORDERITEM_OLD) - old and new status

• Account assignment data for the item (PURORDERACCTASSIGNMT_TABLE)

• Tax jurisdiction code from plant table (TAXJURISDICTION_PLANT)

• Tax jurisdiction code from delivery address (TAXJURISDICTION_DEL_ADDRESS )

In the example implementation supplied for BAdI MM_PUR_S4_PO_MODIFY_TAXJURCODE the following system behavior is defined:

• The tax jurisdiction code from the delivery address is set.

• If no value is maintained in the delivery address: the value for the jurisdiction code previously determined by the system is inserted again.

For the country/region belonging to the plant/company code of the purchase order item, tax handling with tax jurisdiction codes must be activated.

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 3853 Date: 20240606 Time: 214219     sap01-206 ( 82 ms )