SAP ABAP IMG Activity J_1BTAX_GROUPING (Define Tax Groups for Dynamic Exceptions)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-MD-BP (Application Component) Business Partners
     ⤷ FB0C (Package) Financial Accounting customers
IMG Activity
ID J_1BTAX_GROUPING Define Tax Groups for Dynamic Exceptions  
Transaction Code S_ALR_87100866   (empty) 
Created on 19991202    
Customizing Attributes J_1BTAX_GROUPING   Dynamic Exceptions - Grouping 
Customizing Activity J_1BTAX_GROUPING   1 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name J_1BTAX_GROUPING    

Use

In this IMG activity, you define tax groups, which you then use to define dynamic exceptions for Brazilian tax calculation (see Further Notes below). For each tax group, you can specify up to three key fields that are to be used to determine the tax rates for the tax types you activate it for: ICMS, IPI, SubTrib (ST), and/or ISS.

You can choose from the following key fields: material, NCM code, material class/material group, tax code, vendor, customer, industry sector, city code (only in SD), location of service provider, location where service is provided, location of service recipient, company code, plant, and service.

Example

Requirements

If you use condition-based tax calculation for Brazil, then for each tax group that you create or change, you must adjust the access sequences that belong to the conditions that store the tax rates (see the corresponding access sequence activities for SD and MM). You need to include a new step in all those access sequences that conditions use to calculate taxes for the tax types marked as active. Note that we provide a program, J_1B_EXT_ACC_SEQ, that does this for you automatically, which you can access from the Tax Manager's Workplace by choosing Condition Setup -> Migration -> Tax Groups in Access Sequences (refer to the program documentation for details, but be aware that running this report leads to cross-client changes in data). If you change the access sequences manually, the example below illustrates what you need to change.

Suppose you create tax group 50 with two key fields city code and NCM code, calling application General, and marked as active for ICMS only. Then, you need to extend all MM and SD access sequences that are used in the ICMS condtions - by adding step 50. One example from MM is BRIB. You can create step 50 by copying step 5, since they both use the same condition table (the one corresponding to material-dependent exceptions). By copying step 5, you take over the assignment of fields and constant values for the fields - except for the dynamic ones. In the field assignment, you need to assign the city code to dynamic field 1, the NCM code to field 2, and the constant 'X' to field 3. Lastly, assign the constant value '50' to the field Tax group, so that the system can uniquely identify the record during rate determination.

If you do not use condition-based tax calculation, you do not need to adjust the corresponding access sequences. In this case, the system searches through the defined order of key fields of an active group. It uses the first entry it finds in the tax rate tables in order to determine the rate. Assume, for example, that tax group 50 contains the key field NCM code and tax group 51 contains the key field material class. If, during tax the system finds a record for both tax groups, 50 and 51, it takes the lower number, 50.

Standard settings

Tax groups in the number ranges from 0-9 and 91-99 are reserved for SAP; do not delete these groups. If you need to create new tax groups, create them in the range from 10 to 89.

Recommendation

Activities

For each tax group you create, specify:

  • Which key fields are to be used (up to three per tax group)
  • Calling application used to calculate the tax, which indicates where the data is transferred from

    In most cases, we recommend that you choose General, which makes data available from both Sales and Distribution (SD) and Materials Management (MM). If tax rates differ depending on whether the process is a sales or purchasing one, you can also limit the calling application by specifying only SD or MM respectively.

    If you use non-condition-based tax calculation (but we recommend that you switch to condition-based), you can additionally choose the MM applications Inventory Management and Invoice Verification, as well as SD Purchasing.

  • Which tax types the tax group is to be activated for

    Set the corresponding indicators for ICMS, IPI, ISS, and/or ST. Only if the tax group is marked active for a particular tax type does the system consider the rates maintained in the respective tax rate tables during tax calculation. This means that if you deactivate certain tax types for a given tax group, this could, for instance, improve system performance because the system does not take the corresponding tax rates for dynamic exceptions into consideration.

Further notes

You use the tax groups to define dynamic exceptions for the various tax rates in Customizing for Financial Accounting, under Financial Accounting Global Settings -> Tax on Sales/Purchases -> Calculation -> Tax Rates:

When you maintain the dynamic exceptions in these activities, a dialog box appears in which you are prompted to enter the tax group. All the tax groups you create in the current activity are available as possible entries for this field; if you choose F4, you will additionally see which tax types the tax group is activated for.

Business Attributes
ASAP Roadmap ID 201   Make global settings 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
J_1BTAX_GROUPING BR Brazil
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG J_1BTAX_GROUPING 0 HLA0006520 O HLA0006511 O HLA0006500  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
J_1BTXGRUOP S - Table (with text table) SM30  
History
Last changed by/on SAP  20020705 
SAP Release Created in 46C