SAP ABAP IMG Activity WLF_SOA_SMT_TAX_0001 (BAdI for Mapping of Tax Ship-From and Tax Ship-To Country)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-AB (Application Component) Agency Business (Global Trade)
     ⤷ WZRE_XI_PROXY (Package) Agency Business: SOA proxy implementations
IMG Activity
ID WLF_SOA_SMT_TAX_0001 BAdI for Mapping of Tax Ship-From and Tax Ship-To Country  
Transaction Code S_EBS_44000203   (empty) 
Created on 20101112    
Customizing Attributes WLF_SOA_SMT_TAX_0001   BAdI for Mapping of Tax Ship-From and Tax Ship-To Country 
Customizing Activity WLF_SE_LAND_TAX_ENH   BAdI for Mapping of Tax Ship-From and Tax Ship-To Country 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name WLF_SE_LAND_TAX_ENH    

Use

This Business Add-In (BAdI) is used in the Agency Business (LO-AB) component. It is called when an agency invoice is created using the InvoiceRequest_In service operation or when an InvoiceRequest message is sent out using the service operation InvoiceRequest_Out_V1. You can use this BAdI to determine the tax departure country and the tax destination country on the basis of nearly all parties at header level as well as on the basis of the ShipFromLocation and the ShipToLocation at header level. In the confirmation (service operation InvoiceConfirmation_Out), you can map the tax departure country and the tax destination country to the parties or to the locations. The outbound request process uses the same enhancement as the inbound confirmation process.

Requirements

Standard settings

The BAdI is for single use only, but there is an enhancement implementation with a default implementation of this BAdI available, if software component EA-Retail is active.

Activities

When you call up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already created other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed.

  1. In this dialog box, choose Create.
  2. In the dialog box, enter a name for the BAdI implementation in the Implementation field and then choose Create. The initial screen for creating BAdI implementations appears.
  3. Enter a short text for the implementation in the Short Text for Implementation field on the initial screen.
  4. From the tab index, choose Interface. The Name of Implemented Class field is filled automatically on this tab page because the system assigns a class name using the name of your implementation.
  5. Save your entries, and assign the implementation to a development class.
  6. Position the cursor on the method and double-click to call up method processing.
  7. Enter the code for the implementation between the statements method <Interface Name> ~ <Name of Method> and endmethod.
  8. Save and activate your code. Return to the Edit Implementation screen.
  9. Save the entries on the Change Implementation screen.
    10. Note: It is also possible to create an implementation for a BAdI first and then activate it later. In this case, end your processing at this point.
  10. Choose Activate. The code you stored in the method will now be run through when the application program is executed.

Example

For more information, see the documentation of the BAdI methods:

  • inbound data mapping: MAP_PARTY_LOC_TO_LAND_TAX
  • outbound data mapping: MAP_LAND_TAX_TO_PARTY_LOC

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20101112 
SAP Release Created in 606