SAP ABAP IMG Activity ME_TAX_FROM_ADDRESS (BAdI: Adopt Tax Jurisdiction Code from Delivery Address)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ SRM-EBP (Application Component) Enterprise Buyer
     ⤷ BBP_APPLICATION (Package) Structure Package EBP
       ⤷ ME (Package) Application development R/3 Purchasing
IMG Activity
ID ME_TAX_FROM_ADDRESS BAdI: Adopt Tax Jurisdiction Code from Delivery Address  
Transaction Code S_AL0_96000865   (empty) 
Created on 20020208    
Customizing Attributes ME_TAX_FROM_ADDRESS   BAdI: Adopt Tax Jurisdiction Code from Delivery Address 
Customizing Activity ME_TAX_FROM_ADDRESS   BAdI: Adopt Tax Jurisdiction Code from Delivery Address 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ME_TAX_FROM_ADDRESS    

Use

Application components: MM-PUR-PO-GUI, MM-PUR-GF-TAX

Function group: MEPO

The Business Add-In (BAdI) ME_TAX_FROM_ADDRESS provides you with additional functionality to determine the tax jurisdiction code in purchase orders. At item level, the tax jurisdiction code maintained in the delivery address can be used for tax calculation purposes.

You activate tax handling with tax jurisdiction codes in FI Customizing (transaction OBCO). In the standard system, When an Enjoy purchase order (transaction ME21N) is created, 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 has been maintained there). 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 PO item with the account assignment object, this entry "wins" over the entry in the plant table.

If you implement the BAdI ME_TAX_FROM_ADDRESS, when a PO item is created, these tax jurisdiction codes previously determined by the system will be overwritten with the value from the delivery address. This also applies if no value has been maintained in the delivery address. In this case, the field remains empty. However, you can modi fy this behavior in the code of the implementation (cf. the following description of the example implementation). The checks provided in the system (e.g. whether the combination of tax code and tax jurisdiction code in the system is valid) continue to be run. If you implement the BAdI ME_TAX_FROM_ADDRESS, you must thus ensure that a valid tax jurisdiction code is always maintained in the delivery address. One option is to use an external system for tax calculation purposes here (e.g. Taxware or Vertex). Or you stipulate in the implementation that an empty field is populated with a value from another source.

Manual input of the tax jurisdiction code by the user is taken into account in all cases. If the BAdI is active, however, input is only possible on the "Delivery Address" tab page, not on the "Invoice" tab page.

Requirements

  • You can only use the functionality of the BAdI ME_TAX_FROM_ADDRESS in the "new" purchase order transaction ME21N. In the "old" PO transaction ME21, the code is not utilized.
  • For the country belonging to the plant/company code of the PO item, tax handling with tax jurisdiction codes must have been activated.
  • The system message 06 263 "Tax jurisdiction & of account assignment adopted in item", should be set to ' ' ("no message") in Customizing for Purchasing (transaction OLME -> Environment Data -> Define Attributes of System Messages -> System Messages).

Standard settings

  • In the standard system, BAdI ME_TAX_FROM_ADDRESS is not active (not implemented).
  • The BAdI is not filter-dependent.
  • The BAdI cannot be used multiple times.

Activities

To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation

For more information about this procedure, see the SAP Library under

  • Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.

Example

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

  • The tax jurisdiction code from the delivery address is set.
  • If no value has been maintained there:
    • A warning message is issued
    • The value for the jurisdiction code previously determined by the system is inserted again
    • The cursor jumps to the "Delivery Address" tab page, giving the user the opportunity to correct the tax jurisdiction code manually.

The following data is available to control the system behavior in determining the tax jurisdiction code with the BAdI:

  • Purchasing document header (EKKO),
  • Purchasing document item (EKPO) - old and new status
  • Account assignment data for item (EKKN),
  • Tax jurisdiction code from delivery address
  • Tax jurisdiction code from plant table

Further notes

Documentation for BAdI method GET_TXJCD.

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ME_TAX_FROM_ADDRESS 0 HLA0006041 Purchase Orders 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050718 
SAP Release Created in 470