ONESOURCE
INDIRECT TAX
INTEGRATION FOR
SAP
CONFIGURATION GUIDE FOR SPECIAL
FUNCTIONS
PRODUCT VERSION 6.4.3.0
Document Version 1
ii
© 2017 Thomson Reuters/ONESOURCE. All Rights Reserved. Proprietary and confidential information of Thomson Reuters.
Disclosure, use, or reproduction without the written authorization of Thomson Reuters is prohibited. In compliance with the license
agreements for the Open Source Libraries leveraged by Thomson Reuters, our customers can obtain copies of these libraries by
contacting Technical Support at https://tax.thomsonreuters.com/support/onesource/indirect-tax/
The software documented within is Patent Pending in the United States.
iii
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
DOCUMENT HISTORY
Version Number Version Date Summary
v1
July 21, 2017
First version of this guide for ONESOURCE
Indirect Tax Integration for SAP 6.4.3.0
iv
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Table of Contents
Introduction .......................................................................................................................... 7
Welcome to ONESOURCE Indirect Tax Integration for SAP .............................................................. 7
Who Should Read This Guide? ......................................................................................................... 7
Prerequisites ..................................................................................................................................... 8
Resources ......................................................................................................................................... 9
Support Protocol ............................................................................................................................. 10
Style Conventions ........................................................................................................................... 10
Special SAP Functions ...................................................................................................... 11
Cash Discount Configuration ........................................................................................................... 11
Cash Discounts Taken/Received At Payment ............................................................................ 11
Cash Discounts On Legacy Documents .................................................................................... 15
Deferred Taxes Configuration .......................................................................................................... 18
General Ledger Accounts .......................................................................................................... 18
Deferred Tax Rules ................................................................................................................... 22
Adjustments to Posting Keys ..................................................................................................... 23
Setup of Tax Codes .................................................................................................................. 24
Finance Control Table ............................................................................................................... 25
Determine Condition Type for Taxes ......................................................................................... 26
Route Configuration .................................................................................................................. 27
Determination Set Up ................................................................................................................ 28
Plants Abroad.................................................................................................................................. 32
Price Procedure Setup .............................................................................................................. 32
Billing Type Assignment in Interface .......................................................................................... 36
Triangulation Configuration with Determination When Using SAP Integrations ................................. 36
Evaluated Receipt Settlements in A/P.............................................................................................. 38
Service Entry Sheets in A/P ............................................................................................................. 39
Down Payments Processing ............................................................................................................ 39
Brazil Enablement ............................................................................................................. 39
Configuration Within FI Module ........................................................................................................ 41
Creating New Brazil Condition Types for FI ............................................................................... 41
Creating the Tax Procedure ...................................................................................................... 43
Defining Tax Codes for Sales and Purchases ............................................................................ 46
Jurisdiction Code Settings ......................................................................................................... 47
Adding the Required Tax Regions ............................................................................................. 47
Configuration Within SD Module ...................................................................................................... 48
Creating New Brazil Condition Types for SD.............................................................................. 48
Creating the Pricing Procedure.................................................................................................. 50
Assigning the New Pricing Procedure to Sales Transactions ..................................................... 51
Define Tax Determination Rules ................................................................................................ 52
Define Tax Relevance of Customer Master Records.................................................................. 52
Define Tax Relevance of Material Master Records .................................................................... 52
Configuration Within MM Purchasing Module................................................................................... 52
Creating New Condition Types .................................................................................................. 52
Creating a Calculation Schema ................................................................................................. 54
Assigning the New Calculation Schema to Purchase Transactions ............................................ 55
SAP Master Data Setup .................................................................................................................. 56
v
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Assign Tax Indicator in the Material Master Sales Organization View ........................................ 56
Maintain Default Values for Tax Codes ...................................................................................... 56
Maintain Commodity Code ........................................................................................................ 56
Assign Tax Indicator in the Customer Master............................................................................. 56
Maintain Condition Type ZITD to Determine Tax Code .............................................................. 57
ONESOURCE Table Configurations ................................................................................................ 57
Maintain Determine Condition Types for Taxes Table ................................................................ 57
Brazil Registration Number Requirements and Other Field Mappings ........................................ 61
Class /IDT/BRAZIL_MATERIAL_USAGE .................................................................................. 62
Class /IDT/BRAZIL_FED_REG_NUMBER ................................................................................ 62
Commodity Code Map in Field Mapping Table .......................................................................... 62
Configuring the System to Support Nota Fiscal ................................................................................ 62
J1BTAX Settings ....................................................................................................................... 62
Other Configuration Settings (SPRO) ........................................................................................ 67
New Brazil Route /IDT/ROUTE_GROUP_DELIVERY ................................................................ 69
New Brazil Auto Journey /IDT/JOURNEY_BRAZIL_SD_ADJUST .............................................. 69
Dynamic CST Determination for MM ......................................................................................... 70
CST Determination for SD ......................................................................................................... 70
Tax Jurisdiction Codes for Brazil Nota Fiscal ............................................................................. 71
Optional Field Mappings for Inbound STO Process ................................................................... 74
India Enablement............................................................................................................... 75
India GST SAP OSS Notes ............................................................................................................. 76
2448045 and 2073062- GST India: Taxes Should Be <Line Item Wise> .................................... 77
Configuration Within FI Module ........................................................................................................ 78
Setup of India Business places.................................................................................................. 78
Vendor Account Groups and Number Range ............................................................................. 78
India Tax Procedure .................................................................................................................. 78
Defining Tax Codes for Sales and Purchases ............................................................................ 80
Correction of Tax Rate for ZITF and Other Fee Based Calculations ........................................... 80
Defining New Account Assignment Keys ................................................................................... 80
Setting up a Blank Account Key ................................................................................................ 81
Defining Tax Accounts .............................................................................................................. 81
Assigning Tax Codes for Non-Taxable Transactions.................................................................. 81
Configuration Within SD Module ...................................................................................................... 82
Creating India SD Condition Types............................................................................................ 82
India Pricing Procedures ........................................................................................................... 82
Assigning India Pricing Procedures to Sales Transaction........................................................... 84
Define Tax Determination Rules ................................................................................................ 84
Define Tax Relevance of Customer Master Records.................................................................. 84
Define Tax Relevance of Material Master Records .................................................................... 84
Configuration Within MM Module ..................................................................................................... 85
New Partner Functions To Add To Table ................................................................................... 85
Creating New Condition Types .................................................................................................. 86
India Calculation Schemas To Be Added ................................................................................... 86
Assigning the New Calculation Schemas to the India Purchase Transaction .............................. 87
SAP Master Data Setup .................................................................................................................. 88
Assign Data to Vendor Master ................................................................................................... 88
Assign Tax Indicator in the Material Master Sales Organization View ........................................ 90
Maintain Default Values for Tax Codes ...................................................................................... 90
Maintain Commodity Code ........................................................................................................ 90
Assign Tax Indicator in the Customer Master............................................................................. 90
vi
Assign Data to Customer Master ............................................................................................... 90
Maintain Condition Type ZITD to Determine Tax Code .............................................................. 91
ONESOURCE Table Configurations ................................................................................................ 91
Customer Address Source Table Configuration ............................................................................... 92
SAP Table Mapping Requirement for GST ...................................................................................... 92
New India STO Transaction J_1IG_INV ........................................................................................... 93
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
INTRODUCTION
WELCOME TO ONESOURCE INDIRECT TAX
INTEGRATION FOR SAP
Corporations using SAP as their Enterprise Resource Planning (ERP) system can simplify their worldwide
Indirect Tax requirements by implementing ONESOURCE Indirect Tax Suite. The suite includes
Determination, Integration for SAP, Reporting, and Compliance. The benefits provided by ONESOURCE
Indirect Tax Suite are:
• Fast, accurate sales, use, consumer’s use tax, and VAT results.
• Monthly tax rate and rules updates for over 175 countries.
• Integrated tax calculation with SAP minimizing user decisions and tax errors.
• Removal of the need to change SAP tax codes each time a rate/rule changes, eliminating
business interruptions, and running out of tax codes in SAP.
• Complete audit database from which you can generate both standard and custom reports as well
as returns.
ONESOURCE Indirect Tax Integration for SAP 6 is a totally new interface designed, built, and maintained
by Thomson Reuters. It’s a new global tax integration solution designed from the ground up with
integration pointing into SAP ECC and Hana application modules as desired. It consists of a data
collector, tax interface, and return process of tax results to the calling application with G/L integration in
support of downstream SAP processes such as standard VAT reports and returns processing. It makes
use of the SOAP (Simple Object Access Protocol) provided by SAP to communicate with ONESOURCE
Indirect Tax Determination. The new Integration enables worldwide tax calculations, including VAT, US
Sales and Use Tax, and other country-specific taxation.
The interface is entirely built within the SAP Development Workbench, including a user menu for all
interface related configurations, setups, and reports. The interface has a new field mapping solution
allowing a Tax Business Analyst to map SAP data to Determination and vice versa via a customization
table, eliminating most of the user-exit coding of the past. Tax calculation logs can be accessed via a
transaction with a search function from within SAP greatly simplifying tax setup, analysis, and
troubleshooting.
WHO SHOULD READ THIS GUIDE?
If you are responsible for overseeing setting up ONESOURCE Indirect Tax Integration for SAP, you will
need to coordinate help from the following people:
• SAP Business Systems Analyst
• SAP Configuration Consultant
• SAP Technical Resource (ABAP Programmer)
• SAP Security Contact
• Tax Professional
Make this guide available to each of these contributors to ensure you have a successful installation.
8 Introduction
Prerequisites
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
PREREQUISITES
For a seamless and successful deployment of Integration for SAP we highly recommend that you follow
this sequence of documents:
• User Guide
• Installation and Programmers Guide
• Configuration Guides
When working on Integration for SAP you must have a deep knowledge of the SAP tax features, covering
all aspects of FI, MM, and SD and have spent significant time either as an expert configurator or
consultant in these areas. Because the setup of tax integration with ONESOURCE Indirect Tax also
includes technical work in the ABAP Workbench, such as data dictionary changes and ABAP coding, you
must be able to understand and interpret these changes as well. We recommend that you assemble a
team to implement this product because it requires both functional and technical input. Your team should
include someone who thoroughly understands business requirements and processes, as well as
someone who can implement the required software changes.
Please take the following into account before setting up the Integration for SAP:
• This guide assumes a fresh install of the Integration for SAP. Customers who are upgrading from
a prior 5.x version of Integration should contact Thomson Reuters Indirect Tax.
• Minimum SAP system version must be ECC 6.0, EHP 5. Please see tested platforms by
Thomson Reuters in Platform Information section. With Integration for SAP version 6.4.3.0 the
system has also been tested for portability to Hana platform and was tested with a Hana 1511
environment.
• Minimum Determination version must be at 5.5 or greater due to the use of the Tax Code
Qualifier function.
• It is assumed that the persons who install, configure, and use the tax interface in SAP have some
basic understanding of the overall ONESOURCE Indirect Tax Suite of products and how they
interact with each other.
Introduction 9
Resources
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
RESOURCES
Resource Description
Customer Support Look for answers in the Knowledge Base, or to open a support ticket.
User Guide This is an overview of the architecture, basic business processes and
touch points as they relate to Sales and Use tax, as well as VAT
scenarios in FI, SD, and MM. The target audiences are the Business
Systems Analysts, Consultants, and Tax Professionals who setup
the tax processes in SAP.
Installation and
Programmers Guide
This guide instructs on how to install the Integration for SAP. The
target audience is the Basis person that will process the application of
the transports to the SAP system and the ABAP programmers that
will perform the required include statements within the user exits and
other coding blocks. There is also discussion in this manual for the
ABAP programmer regarding customization logic and how custom
additions to the programs should be added to the system if needed in
the future.
This guide describes the supported combinations of operating
systems, databases, and application servers/web containers.
This guide lists the end-of-life dates for ONESOURCE Indirect Tax
Integrations for SAP.
Consult this guide to see which combinations of software we test with
Integrations.
Configuration Guide SAP
tables
This guide instructs how to configure and setup SAP tables and
processes to enable tax calculations to meet your unique
requirements.
Configuration Guide
ONESOURCE tables
This guide instructs how to configure and setup our ONESOURCE
Indirect Tax tables and processes to enable tax calculations to meet
your unique requirements.
Configuration Guide for
Special Functions
This guide instructs how to configure and setup SAP and Integration
tables and processes to enable tax calculations to meet your unique
requirements for special functions within SAP such as Plants Abroad,
Cash Discounts, Deferred Taxes, Service Entry Sheets, etc.
10 Introduction
Support Protocol
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
SUPPORT PROTOCOL
The ONESOURCE Indirect Tax Integration for SAP is built, maintained, and owned by Thomson Reuters
Tax & Accounting Indirect Tax. The business unit has a dedicated group of SAP Business Systems
Analysts, ABAP Programmers, and Quality Assurance people who have built this product. We follow SAP
best practices, development standards, and strive to minimize the impact this solution will have on your
SAP environment. With any 3
rd
party Add-On in SAP, the vendor providing the solution is responsible for
support of that Add-On. In the case of an issue with the ONESOURCE Indirect Tax Integration for SAP
please follow these simple steps to open a support ticket with Thomson Reuters:
1. Identify the potential issue and gather all necessary facts (log files, scenarios, configurations,
screen prints).
2. Provide steps to reproduce the scenario leading to the issue.
3. Provide system environment information such as your SAP Version, EHP and SP level, as well as
the Integration version.
4. Open a support ticket with Indirect Tax at
https://tax.thomsonreuters.com/support/onesource/indirect-tax/
.
STYLE CONVENTIONS
Style conventions provide a guide as to how to interpret information.
Bold text indicates most user interface elements, such as:
•
Data you are expected to enter, such as in a text field
•
Pages, buttons, tabs, and field names
•
Dialog boxes, drop-down lists, selections within lists, and check box titles
•
Windows
•
Menu items
Italic text indicates the following:
• File and folder names
• Software programming terminology and executable files
• Document titles
CAPITALIZED text indicates keyboard commands, such as ENTER, or database components.
Courier text indicates command-line input/output.
<brackets> indicate user entry. For example, <host> indicates you should replace the text and angle
brackets with your server name.
Book titles are shown in italics and sections within a book are in quotation marks, such as “Tips and
Tricks” in the ONESOURCE Indirect Tax User Guide.
Indicates suggestions or additional, detailed information.
Special SAP Functions 11
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Indicates important text that should be carefully reviewed before proceeding.
SPECIAL SAP FUNCTIONS
CASH DISCOUNT CONFIGURATION
CASH DISCOUNTS TAKEN/RECEIVED AT PAYMENT
It is imperative that you make sure that your pricing procedures include the STKV and STKO conditions
on either side of the tax calculation conditions for ONESOURCE otherwise the system will not work
properly for this feature. Please refer back to the above sections of this guide on set up of the SD pricing
procedure and the MM calculation schema and make sure that these conditions are present for all
referenced pricing. The STKV condition is used as shown for countries that calculate cash discounts net
basis, and the STKO is used for countries like Germany that use the gross calculation method with a VAT
adjustment at time of payment. This is required along with the additional configuration discussed below.
This is not an “out of the box” set of conditions that are provided by SAP and must be added on the MM
side. You will find them as standard on the SD standard pricing procedure.
There are two simple configuration flags that need to be set at both the company code and country level
in order for the cash discounts feature to function as needed based on country tax requirements. We will
12 Special SAP Functions
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
demonstrate this for two countries and note that the requirements will need to be set for each country
based on the tax policy of the country. It is usually required that you set these flags at the company code
level unless you have plants abroad turned on in your system. With plants abroad the flags must also be
set at the country master data level so that it will work based on reporting country in plants abroad
configuration.
Transaction code: SPRO navigate to > SAP NetWeaver > General Settings > Set countries >
Define Countries in mySAP Systems
Select the GB country and the DE country and note the settings for the Net Discount Base and the Net
Tax Base fields on the screen. For GB both fields should be checked and for DE both fields should be
unchecked. See examples below.
Special SAP Functions 13
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
In Great Britain, the base amount for the sales tax results from the invoiced amount minus the agreed
cash discount, for example. In this case, the base amount for the tax calculation is net.
In Germany, for the possible deduction of cash discount, first tax is also paid when the document is
posted. Then, a tax adjustment is made during the payment settlement. In this case, the base amount for
the cash discount calculation is gross, that is, it includes sales tax.
For more information on the cash discounts setup and explanation see SAP Note 300253 - Postings tax
base and cash discount base gross/net.
Transaction SPRO navigate to > Financial Accounting > Financial Accounting Global Settings >
Company code > Enter Global Parameters
14 Special SAP Functions
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Select and display the company codes for GB and DE countries and note the settings for the fields as
shown below. For GB both fields should be checked and for DE both fields should be unchecked. See
examples below.
Special SAP Functions 15
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Remember to set these flags for all countries and all company codes based on the required tax policy on
cash discounts for that country.
CASH DISCOUNTS ON LEGACY DOCUMENTS
If you are installing this version of Integration as an upgrade to your current SAP environment then you
will likely have documents in your open A/R or open A/P that have not been paid and contain a cash
discount calculation. At time of payment these transactions will have used a tax code assignment logic
that does not match the rules of assignment under this Integration. This will cause a conflict with our new
logic and likely not process the tax adjustment on the recognized cash discount either by way of a wrong
amount or hard error. Legacy documents will require special handling in one of several ways depending
on the prior logic that was used to create them in your legacy system.
Keep in mind this is a temporary process only required until your open A/R and open A/P has passed the
oldest applicable cash discount date logic…. Normally this will be an issue only the first month on the new
system:
a. If you have O1 and I1 tax codes on documents from Integration 5.X due to an upgrade.
b. If you converted to SAP and loaded from scratch your old open A/R and using a dummy
or exempt tax code for the load allowing the tax on the order to remain netted in one
amount.
c. If you are upgrading from native SAP calculations using same tax codes as you will use
under this Integration.
d. If you are upgrading from native SAP calculations and using different tax codes in order
to segregate legacy procedures from the tax codes used under this Integration.
Recommended solutions to each of these possible scenarios are discussed below.
Option A: With Integration 5.x the O1 and I1 tax codes used on orders had a “one-to-many” relationship
with the various tax rates for standard, reduced rate taxes, etc. For this scenario we recommend the Cash
16 Special SAP Functions
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Discount Table mapping of the “one-to-many” driver codes of 01 I1, XX, YY to a Determination tax code
of “LEGACY” and have a custom rule created for LEGACY that is set up within your tax rules. An
additional TCQ will also need to be set up using one of the conditions as the Determination Tax Code of
“LEGACY” that will drive the ERP_TAX_Code assignment back to O1-MWS for a Seller role and I1_VST
for a buyer role. Screen print examples of the Cash discount table, customer rule, and TCQ set up are
shown below:
Transaction SM30 on table /IDT/D_CASH_DISC to set up the Cash Discount Table configuration for
legacy tax codes
This is the custom rule you would need to set up to get the table to drive to this rule in Determination.
You would also need a TCQ set up in Determination based on the Determination Tax Code of “LEGACY”
as shown below:
Special SAP Functions 17
Cash Discount Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Remember that if you have set the fallback tax code in the cash discount table you will need Tax Code
Qualifiers for XX and YY as well.
Option B: If this is a new SAP system you loaded your initial open A/R balances from a legacy system
you might have used a tax exempt code on them because they already had tax included on the invoice
balances. In this situation you don’t have the tax amount or rate data to do step “A” above. You will have
to avoid use of the cash discount function on these invoices and manually calculate a miscellaneous
18 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
difference charge to the Cash Discount account that can be taxed using an override tax code that is
manually entered on the line. This would be done as follows:
• Remove the cash discount amount from the invoice lines prior to selecting them from the open
items list in F-28.
• Use an additional line at the bottom of the screen with a posting key and the account number for
cash discounts taken.
• On the next screen enter the cash discount amount, an override tax code, check the calculate tax
button, and enter a cost center if required by your account set up.
• Rate changes may be an issue due to date driven logic in our integration rates.
Option C: If you are converting from native SAP your documents may have the same tax codes as you
are now using with this integration. In that case the process would work for the cash discount the same
as if creating the original invoice under our integration. Follow all steps as noted above for the
configuration of the cash discounts table, the Determination custom rules, and the Cash Discount Tax
Code Qualifiers.
Option D: If you are converting from native SAP and the tax codes were assigned to different tax codes,
then you will have to load the cash discount table configuration, Determination custom tax rules, and then
TCQ’s for both old and new tax code logic. Or if you do not want to clutter your TCQ list with so many
lines then you could elect to use option B and use the misc. difference calc. instead.
DEFERRED TAXES CONFIGURATION
Deferred Tax Configuration involves special configuration to SAP FI module, Integration, and several
areas of Determination such as rules, and tax code qualifiers. We have added this to the guide as a
special chapter at this point after discussions on both SAP standard configurations and special
configuration within Integrations and Determination.
The deferred tax process within the Integration has been designed to work with the F.38 RFUMSV25
program to transfer documents that have cleared the payment process from the deferred tax liability
account to the target tax account. For assistance to the user we have identified all of the required
configuration for deferred tax within the FI module of SAP as well as what is required within the
Integration tables and Determination rules, mapping, and tax code qualifiers. At this time we have not fully
tested the newer RFUMSV50 transfer program and recommend that you contact our Professional
Services group if you need assistance with the newer program.
GENERAL LEDGER ACCOUNTS
You must set up tax liability accounts for deferred tax and the target tax code accounts. See example as
the following. Your account assignment numbers may be different:
175013 Output tax deferred std. rate
175014 Output tax std. rate (target)
154013 Input tax deferred std. rate
154014 Input tax std. rate (target)
It is critical for proper running of the deferred tax transfer program RFUMSV25 that the deferred tax
accounts be set up with open item management and line item display switched on otherwise the program
will not run correctly. This requirement is not however required for the target accounts.
Special SAP Functions 19
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
The deferred accounts must also avoid using the “*” for the tax category field and should use either “<” or
“>”. See example screen shots below for one of the deferred and target accounts.
Deferred Output Standard Rate Account:
20 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Deferred Input Standard Rate Account:
Special SAP Functions 21
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Target Output Standard Rate Account:
Target Input Standard Rate Account:
Status of Open Item Management is optional on the target accounts.
22 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
DEFERRED TAX RULES
To be able to run the Deferred Tax Transfer program, make the settings in Customizing for:
Transaction: SPRO navigate to > Financial Accounting (FI) under General Ledger Accounting >
Business Transactions > Closing > Report > Sales/Purchases Tax Returns > Deferred Taxes.
Hana Transaction: SPRO navigate to > Financial Accounting > General Ledger Accounting >
Periodic Processing > Report >Sales and purchase tax returns >deferred taxes > Define Deferred
Tax Rules
You must set up a deferred tax rule as shown below and then assign it to the given company codes.
Special SAP Functions 23
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
ADJUSTMENTS TO POSTING KEYS
Adjustments to the posting keys are required in order for the RFUMSV25 program to work correctly. To
fix the issue, the posting keys of 40 and 50 must not have the payment transaction checkbox checked. If it
is checked the program will throw an error and not pick up the data correctly. If this occurs you will get the
following error when running the program:
Now to solve this above issue, go to OB41: Select Posting Key 50
24 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Payment transaction check box needs to be unchecked
SETUP OF TAX CODES
Set up of deferred tax codes and target tax codes:
Transaction: SPRO navigate to > financial accounting > financial accounting global settings > tax
on sales purchasing > calculation > define tax codes for sales and purchasing. (FTXP)
Set up the standard rate tax code for both input and output tax as well as deferred tax codes for input and
output tax. On the deferred tax codes you must also set up the properties with the target tax code field
populated with the desired final tax code as shown below:
Special SAP Functions 25
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
In our example for Mexico we have:
• A1 set as standard rate output (the target tax code)
• A5 set as deferred output tax SR
• V1 set as standard rate input (the target tax code)
• V5 set as deferred input SR
A5 and V5 would have the target tax codes of A1 and V1 set in the properties tab.
FINANCE CONTROL TABLE
Use transaction /N/IDT/FI_CONTROL_V and make sure that table /IDT/D_FI_CONTRL_V has the last
line as shown in the screen print below. This should be present in the standard view of this table as part
of your transport. If not present then add to the customer view of the table using transaction
/N/IDT_FI_CONTROL.
26 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
DETERMINE CONDITION TYPE FOR TAXES
/IDT/DETER_COND_TYPE
This table will have new routes for Deferred Tax added to the list. You must make sure that you have
added the required condition types to this table per your prior condition type setup. Make sure the last
column is populated for these new route entries as shown in our example below.
Special SAP Functions 27
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
ROUTE CONFIGURATION
With the transport for deferred tax this table was modified to include a new route. You must make sure
that you have all of the correct AltCTy values populated in this table after the transport. The new route is
/IDT/ROUTE_NON_GROUP_DOC_DT and the last two columns should be populated with the correct
AltCTy value and AltCBV value.
28 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
DETERMINATION SET UP
You will need to set up custom rules in determination in order to drive your tax calculation to a deferred
tax scenario. This will be different depending on your tax policy requirements for the country that you are
setting up. In some countries like Mexico all initial sales are run through the deferred tax scenario and
you may elect to drive the deferral based on the country code. For others it might only apply to services
and so a product code would be used to drive deferred.
For the purpose of our example we have chosen a simple assignment based on a single product number.
This will require us to set up a custom rule, a product mapping, and a trans-editor that will work together
to create this deferred map in Determination.
Rules
Set up of customer rule for a product name:
In the below example we have set up rule 1004 as defining a product name of “Firearms and Ammunition”
as a deferred tax product for company code 6000. Your set up here will be different based on your tax
procedure for your given country scenario. This is just an example.
Special SAP Functions 29
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Within Determination, go to Menu > Tax Data > Authorities > Basic Rates and Rules.
Within this custom rule you must populate the tax treatment field with the value “Deferred Invoice” from
the drop down list. This will populate the DI code into the XML of the request data to Determination with
the code that will late be used to assign the A5 or V5 tax code by way of the Tax Code Qualifier set up in
Determination.
Mapping
Set up of product name mapping to product code:
Next step is to set a product mapping for the product name to the product code. In this case the product
name of “Firearms and ammunition” is mapped to the product code s-1020. See screen shot below.
Menu: Company data > product mappings. Reminder: this is just an example of the process.
30 Special SAP Functions
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Set up of Trans Editor to convert part number to product code
In this step you need to create a Trans Editor to populate the LINE.PRODUCT_CODE with the
LINE.PART_NUMBER. This is the third step that is needed to map in Determination the part number to
the product code,
Menu: Logic Settings > Trans Editors
Tax Code Qualifiers
Set up of Tax Code Qualifier for Deferred Tax:
Menu: Logic Settings >Tax Code Qualifier
You will need to add a deferred tax code mapping to the TCQ set up in your Determination so that the V5
Input deferred tax account is correctly mapped. This will need to be in a sort order that puts it above the
standard rated V1 tax code in the order sequence.
Conditions are shown below:
Special SAP Functions 31
Deferred Taxes Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Note that the TAX.TAX_TREATMENT element is set to “DI” in this set of conditions in order to drive to
the deferred tax code.
The A5 tax code will also need to have a TCQ set up as noted below:
Conditions for the A5 tax code shown below:
32 Special SAP Functions
Plants Abroad
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Note that in this configuration set up we have not addressed the use of a Tax Code
Qualifier for the target tax code using the TAX.TAX_TREATMENT of DP. This is
because we are using the normal standard tax rate code of A1 to also contain the target
tax calculation for deferred tax. If you decide to use a different and separate tax code for
the target deferred tax then you will need to make a copy of the standard A1 TCQ and
add the TAX.TAX_TREATMENT condition of DP to it to get it to drive to your desired
target tax code and account key combination.
Hana system note: If you run f.38 RFUMSV25 program and encounter an issue using
the dynamic selection screen option you could receive a short dump. We have found a
note that recommends adding a parameter to your logon profile in order to avoid this
error. Go to System/user profile/own data and add to your parameters tab
FAGL_GET_GLTO_OLD with a value of X to your list to avoid this issue.
PLANTS ABROAD
Plants Abroad configuration is standard in SAP and involves several steps. Here we are identifying the
required steps that you will need to modify in addition to the standard SAP configuration requirements for
plants abroad in order to get it functioning with our new condition types and pricing procedure logic.
Reminder that you will need to identify any countries where you DO NOT want to use
plants abroad and turn off the feature after you do the activation step for plants abroad
(See SAP documentation on Plants Abroad Configuration). OSS note 850566 notes this
process with transaction OBY6 selecting the country you want to turn off, then
Environment / Additional data. Put an “X” in the field “Plants Abroad Not Required”
PRICE PROCEDURE SETUP
Transaction Code: V/08. Select procedure RVWIA1, then Control.
Special SAP Functions 33
Plants Abroad
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This is the standard RVWIA1 pricing procedure as provided by SAP for Plants Abroad. Copy it and save it
to a new pricing procedure as ZVWIA1 as this will be modified to be used with Integration for SAP.
The screen shot above is the updated version of ZVWIA1 pricing procedure that needs to be in place.
Modify your saved version from the prior step so that it now appears as you see here.
Define Pricing Procedure Determination.
34 Special SAP Functions
Plants Abroad
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
You will need to set up the pricing procedure determination based on the sales org for the area that will
use this new pricing procedure for plants abroad. Example is below. Make sure you assign for both sales
orgs on both sides ( both buyer side and seller side of the transaction).
Special SAP Functions 35
Plants Abroad
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This screen should already be configured for plants abroad as part of SAP standard.
Note that the plants abroad billing type WIA should already be set to DoPr of “B” per standard SAP setup.
36 Special SAP Functions
Triangulation Configuration with Determination When Using SAP Integrations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
BILLING TYPE ASSIGNMENT IN INTERFACE
For Integration to know which documents are of type plants abroad and apply the special journey defined
for this process, an additional setup needs to be done in the Integration configuration. There is a menu
item available in the User Menu for this. See other table configuration of this guide for Plants Abroad
Table
Transaction Code: /N/IDT/PLANTS_ABROAD
TRIANGULATION CONFIGURATION WITH
DETERMINATION WHEN USING SAP INTEGRATIONS
Triangulation simplification, or simply triangulation, is a special regime in the EU that applies to qualifying
chain transactions. In triangulation, all countries in the transaction are different EU member states,
registered in their own country. In any given Triangulations scenarios, there are three parties involved,
SELLER, BUYER and MIDDLE MAN. Due to the nature of the transaction and the available data within
SAP to provide to determination system to properly assess the tax liability in the triangulation scenario,
we use seller role rather than Middle man role.
Following are the Steps to Configure the Triangulation using Seller role.
Configuration:
COMPANY_ROLE=S (Sales Transaction)
Please remove the trans-editor that sets the Company role to M in determination, if you have one.
1) In order to trigger the triangulation evaluation for a transaction TRANSACTION_TYPE should be set
to T1. There are multiple ways to achieve this:
a) Use Trans Editor in Determination:
Special SAP Functions 37
Triangulation Configuration with Determination When Using SAP Integrations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
b) We can set the TRANSACTION_TYPE to T1 based on the EU Triangulation flag (VBAK-
XEGDR) on the sales orders or Billing document.
c) To do so one could populate a USER_ATTRIBUTE based on the EU triangulation flag. Use
the custom field mapping configuration with in Global Next to map the field. Then use a
38 Special SAP Functions
Evaluated Receipt Settlements in A/P
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Trans Editor in Determination to switch the TRANSACTION_TYPE to T1 based on if the
USER_ATTRIBUTE = X.
d) Using a user-exit based field mapping to set the TRANSACTION_TYPE to T1 based on
unique custom logic.
Sample Transaction
Following is an example of the needed minimal data requirements to make a triangulation work based on
a sample between NL, FR, and DE:
1. Address element details.
SELLER_PRIMARY.COUNTRY=NL (represents the intermediate seller’s country
(Ex.Company code/Sales org))
SHIP_FROM.COUNTRY=FR (represents the country of origin (Ex. Plant))
SHIP_TO.COUNTRY=DE (represents the destination country (Ex. Ship to Customer))
2. Following are registration requirements for the above example case:
REGISTRATIONS.SELLER_ROLE=NL123456789B12 (the seller’s registration. Note that it
is currently a requirement of the tax engine that the seller be registered in the seller primary
country.
REGISTRATIONS.BUYER_ROLE=DE123456789 (the buyer’s registration in the ship to
country; this is a tax engine requirement as well).
Invoice Messaging:
This setup will lead to the following invoice message based on return data from Determination:
EUS1CT01: No VAT liability since Triangulation Simplification applies under Arts. 141 and 197 of EC
Directive 2006/112. Customer to account for Intra-Community Acquisition, reverse charge.
EVALUATED RECEIPT SETTLEMENTS IN A/P
For the ERS invoice process to work with our integration there are no additional configuration steps
required other than the required SAP configuration to set up the ERS process. We recommend that you
refer to SAP configuration guides on the subject for all needed set up of the Vendor master, log number
ranges, output options, etc.
For reference we have listed some of the various steps required for set up per the SAP guides, however
your configuration may be different due to your desired output method for vendor notification.
• The indicators for evaluated receipt settlement must be activated within the desired
vendor master record. (XK02)
• A confirmation is expected for the purchase order
• GR-IR indicators and ERS indicators should be activated in the PO
• Tax code must be activated in the PO
• Maintain number range for the accounting documents. (OMR2)
• Maintain number range for the logistics documents. (OMRJ)
• Assign number range to the RD and RS Transaction codes
• Maintain message types
• Maintain conditions for message determination
Brazil Enablement 39
Service Entry Sheets in A/P
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
• Assign forms and programs
Note that our set up and testing of the ERS process integrated with a Determination tax
calculation assumes that all entries are utilizing the Determination tax calculation based
on the tax codes assigned on the originating purchase order using the configured
calculation schema for purchasing.
SERVICE ENTRY SHEETS IN A/P
For the Service Entry Sheets (SES) process to work with our integration there are no additional
configuration steps required other than the required SAP configuration to set up the External Services
Management (MM-SRV) process. We recommend that you refer to SAP configuration guides on the
subject for all needed set up of the Service Master for planned services, output options, etc.
For reference we have listed some of the various steps required for set up per the SAP guides, however
your configuration may be different due to your desired output method for vendor notification.
• The PO should be created with any Account Assignment Category and Item Category of D -
Service
• In the Item Details
Invoice tab-
S. –Based IV indicator is activated in the PO
• Tax code must be activated in the PO
• Maintain message types
• Set up optional configuration to have taxes calculate at the service line level for any country
rather than at the PO line item level. (SPRO
IMG
Materials Management
External
Services Management
Taxes at Individual Service Level)
DOWN PAYMENTS PROCESSING
For Down Payments processing there are no additional configuration or processing steps required other
than those outlined by SAP standard configuration and processing guidelines. Please refer to SAP help
information on configurations and processing transactions.
BRAZIL ENABLEMENT
NOTE: In this release the Brazil functions that we have added are available to be
utilized within a production system at this time.
The Brazil tax calculation logic is notably complex with many calculations and configuration requirements.
It is a challenge to implement even by the most experienced, and requires a lot of adjustments and
configurations that are specific to your company requirements, customers, products, business models,
and reporting needs. Therefore it should be understood that the current ONESOURCE Indirect Tax
support for Brazil should be looked at as a beginning Brazil Enablement or initial platform with which to
aid in your successful implementation of Brazil VAT logic rather than a be-all end-to-end solution. In
addition to what we offer here, you will need to partner closely with your ONESOURCE Indirect Tax
40 Brazil Enablement
Down Payments Processing
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Professional Services representative or other Brazil tax experts to identify and complete all company
specific requirements necessary for your successful Brazil implementation.
We recommend that you review and use extensively the SAP library documentation for Brazil country
configuration and review all of their Brazil specific tables and various configuration options for both native
tax calculation and Nota Fiscal activation and mapping. Most all of the standard Brazil tables for CFOP
code, Nota Fiscal mapping, Tax laws, etc. all still apply while using our enablement with ONESOURCE
Indirect Tax for SAP Integration. Exception to this is where native SAP Brazil tables use actual tax rates
tied to the tax code in SAP as well as the jurisdiction code activation. Our processes rely on our
Determination tax engine and tax content in order to store and use all current and historical tax rates
within the calculation. Taxes are calculated using non-jurisdictional that utilized the full address rather
than the assigned jurisdiction code. The Jurisdiction code is however populated and used within the
system to map to the correct field in the Nota Fiscal document but does not influence the tax calculation.
There is really no way to identify a complete list of all the tables you will need to populate for Brazil
because it is entirely dependent on your specific business activities within the country, how you are
registered, your specific taxing requirements, products, customers, vendors, etc.
We have a few areas where we have added our own configuration table settings for applying our
Integration process. Some SAP configuration tables may not apply as they are used for a totally internal
tax calculation verses the use of an external tax calculation engine such as ONESOURCE Indirect Tax for
SAP. Our documentation below is not intended to be a “be-all-end-all” configuration roadmap for Brazil
configuration, but instead will address the additional steps that are needed beyond standard SAP setup
requirements.
SPECIAL NOTE ON TAX JURISDICTION CODES: For correct population of the
various Nota Fiscal forms for all transactions in Brazil, the tax jurisdiction code is used
to represent the two digit tax region code followed by a space and then the 7 digit
applicable IBGE municipal code. This feature is prevalent and imbedded within SAP’s
standard logic. Our design takes full advantage of this feature for the population of the
Nota Fiscal but does not utilize the tax jurisdiction code for tax calculation purposes.
Our intention is to avoid any harm to the native SAP processes and calculation logic for
Brazil. Our exception to this is that we do not tie actual rates to the tax codes and
codes do not need to be change when authority rates change. All of our Determination
tax call logic depends on the correct address including full postal codes in order to
establish taxability for the transaction. Users should not confuse the two uses of the
jurisdiction code between our 6.x logic which uses full address, and our 5.x Integration
logic which was based on tax jurisdiction code assignment to the tax calculation. Our
new Brazil enablement is a totally different calculation method and does not turn on the
jurisdictional method for tax calculations in Brazil. This is intentionally a separate
approach for our Integration and Determination products moving forward.
This next section outlines the configuration steps required to get a simple Brazil scenario working from
AP and AR. Brazil taxation is very complex and the steps shown here only cover the most basic concepts.
Brazil Enablement 41
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CONFIGURATION WITHIN FI MODULE
CREATING NEW BRAZIL CONDITION TYPES FOR FI
Here you are creating new condition types for tax calculations to the FI side. Later you will have to do a
similar process for the same codes on the SD side. Do not confuse the two as they are different. To
process for the FI module:
1. From IMG (SPRO), navigate to Financial Accounting > Financial Accounting Global Settings
> Tax on Sales/Purchases > Basic Settings > Check Calculation Procedure
2. Select Define Condition Types from the pop-up window and click Choose.
3. Create a new condition type by copying the existing ZITR changing the description as needed.
Make sure the fields show the same as the screen shot below and then save the new Brazil
condition types. See list below for an example of the condition types that will be required.
42 Brazil Enablement
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
With the change to dynamic assignment of the condition types and tax authorities, the
number of conditions types was dramatically reduced. However additional condition
types will be needed for Brazil in order to tie a separate condition type to each tax type
so that native SAP configuration can be used to map all required fields for correct Nota
Fiscal utilization. Because of the mapping to the Nota Fiscal documents we do not use
the dynamic assignment of condition type ZITR and ZITF for Brazil like we do for other
countries. Instead condition types must be created for each need and mapped
according to your specific Brazil tax requirements. Our list below is a starting point
however you will likely need additional conditions types depending on your specific tax
calculation needs. Consult with your Professional Services representative on the
possible need for additional condition types to meet your tax requirements. Our list
below is only a beginning sample.
Brazil Enablement 43
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This is a recommended list for starters as an example. Your list of required condition types may be
different due to your specific tax calculation requirements.
CREATING THE TAX PROCEDURE
The tax procedure used for Brazil is very similar to other tax procedures used for other countries.
The following steps show how to do this for Brazil.
1) From IMG (SPRO), navigate to Financial Accounting > Financial Accounting Global
Settings > Tax on Sales/Purchases > Basic Settings > Check Calculation Procedure.
2) Select Check Calculation Procedure and click.
3) Select Define Procedures from the pop-up window and click Choose.
4) Select New Entries.
5) Enter ZTAXBR and define it as IDT Tax Procedure Brazil.
6) Save the new template.
7) Highlight the newly created procedure (in this example, ZTPBR1) and double-click Control in
the left-hand navigation window.
44 Brazil Enablement
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
8) Perform the following actions on this page:
o Insert new Step 100 CTyp BASB
o Insert new Step 106 for the Call to IDT with condition formula 990.
o Insert new Step 121, CTyp ZBPI, assign CAL Type formula 991.
o Insert new Step 130, CTyp ZBCO, assign CAL Type formula 991.
o Insert new Step 140, CTyp ZBIC, assign CAL Type formula 991.
o Insert new Step 144, CTyp ZBID, assign CAL Type formula 991.
o Insert new Step 148, CTyp ZBIE, assign CAL Type formula 991.
o Insert new Step 150, CTyp ZBIP, assign CAL Type formula 991.
o Insert new Step 160, CTyp ZBIS, assign CAL Type formula 991.
It should now look like the following:
Brazil Enablement 45
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Your Tax Procedure may require additional lines for additional condition types based on your specific tax
calculation requirements for Brazil. The screenshot shown above is intended as an example. Your final
tax procedure will be different.
Note also the Tax Law lines on this tax procedure as they may be required depending on your
configuration. BLIC and BLIP are statistical conditions that are provided by SAP as part of their country
offering for Brazil and may be needed within your tax procedure depending on how you are referencing
the native calculation for Brazil taxes. You may have these named differently in your system.
In tandem with this changes will need to be made to the following table to enable this to work
Transaction: J1BTAX / Condition Set Up / Nota-Fiscal Mapping / Tax Laws MM
Enter the tax procedure you just created in prior step.
46 Brazil Enablement
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Note that in the above example the table entry for ICMS is the statistical tax law condition rather than the
condition type you created previously.
DEFINING TAX CODES FOR SALES AND PURCHASES
Defining the tax codes for the system is no different than the configuration instructions as noted in the
Configuration Guide SAP tables
documentation. See same section heading as in this document. You will
however need to look at your tax code assignment differently with Brazil because the number of tax codes
that you need, will be greater. For Brazil we do not use the dynamically created conditions of ZITR and
ZITF and you will need tax codes that can be mapped as a one-to-one relationship with your tax
conditions and tax authorities. This is required in order for your mapping to work correctly for the Nota
Fiscal processes. For example we have included a table list below for the tax codes you will need to
Brazil Enablement 47
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
consider. This list below is not all-inclusive and you will likely need more tax code assignments based on
your specific tax and reporting requirements.
JURISDICTION CODE SETTINGS
With ONESOURCE Indirect Tax Integration for SAP version 6.x we are no longer using jurisdiction codes
for determining the tax authorities but instead use the appropriate buyer and seller addresses as mapped
in our Integration. Jurisdiction code settings will not be applicable for Brazil taxes however the jurisdiction
code will be needed for population on the Nota Fiscal.
ADDING THE REQUIRED TAX REGIONS
SAP defines tax regions which are used is several modules. The jurisdiction code returned from
Determination when creating a P.O. is validated with the entries in the Tax Regions table.
1. Navigate to Transaction: J1BTAX > Entities > Tax Regions > New Entries. After clicking on
Entities you will have to enter the country code “BR” for Brazil.
Make sure you have your required list of tax regions as shown below.
48 Brazil Enablement
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CONFIGURATION WITHIN SD MODULE
CREATING NEW BRAZIL CONDITION TYPES FOR SD
Here you are creating new condition types for tax calculations to the SD side. Just like the prior process
for FI, you will have to create the same list of conditions as described above.
1. Navigate to Transaction: VOK0 > Condition type > Condition types >Definition.
Create a new condition type by copying the existing ZITR changing the description as needed. Make
sure the fields show the same as the screen shot below and then save the new Brazil condition types.
See list below for an example of the condition types that will be required.
Brazil Enablement 49
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
With the change to dynamic assignment of the condition types and tax authorities, the
number of conditions types was dramatically reduced. However additional condition
types will be needed for Brazil in order to tie a separate condition type to each tax type
so that native SAP configuration can be used to map all required fields for correct Nota
Fiscal utilization. Our list below is a starting point however you will likely need additional
conditions types depending on your specific tax calculation needs. Consult with your
Professional Services representative on the possible need for additional condition types
to meet your tax requirements.
50 Brazil Enablement
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This is a recommended list for starters as an example. Your list of required condition types may be
different due to your specific tax calculation requirements.
CREATING THE PRICING PROCEDURE
Within the pricing procedure, the tax call to the external system is enabled by a set of condition types and
the condition value formulas 992, 993 and 994. (See Installation and Programmers Guide
as your
condition base formula numbers may be different) The condition base formulas are created as part of the
initial install. The steps below describe the process of creating your price procedure.
1. From IMG (SPRO), navigate to Sales and Distribution > Basic Functions > Pricing >
Pricing Control > Define and Assign Pricing Procedures.
Follow all processes as outlined in the Configuration Guide SAP Tables
. Review the example below that
we have created for pricing procedure ZPPBR1. Your pricing procedure will likely be different from our
example based on any additional condition types you may have had to create that are specific to your
implementation and tax requirements.
See our example below:
Brazil Enablement 51
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Notice that unlike our pricing procedure for EU countries Brazil is not using the ZITR and ZITF conditions
used for dynamic processing, but instead the conditions that were set up based on a one to one mapping
to the specific taxing authority/tax types are used.
ASSIGNING THE NEW PRICING PROCEDURE TO SALES
TRANSACTIONS
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
52 Brazil Enablement
Configuration Within MM Purchasing Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
DEFINE TAX DETERMINATION RULES
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
DEFINE TAX RELEVANCE OF CUSTOMER MASTER
RECORDS
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
DEFINE TAX RELEVANCE OF MATERIAL MASTER
RECORDS
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
CONFIGURATION WITHIN MM PURCHASING MODULE
CREATING NEW CONDITION TYPES
The standard SAP condition type MWST is set up to derive tax based on SAP tax tables. To enable
external tax calculation using the Integration, you will need to create the same list of condition types in
MM that you completed for FI and SD modules:
You may also want to make sure the two condition types SKTO and SKTV for cash discounts are
available in the table for use on the calculation schema.
1. From IMG (SPRO), navigate to Materials Management > Purchasing > Conditions >
Define Price Determination Process > Define Condition Types
Brazil Enablement 53
Configuration Within MM Purchasing Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
1. On the pop-up window select Define Condition Types.
2. On the main page navigate to Condition Type MWST and select the record.
3. Select Copy from the navigation bar, and then update the page to match the values shown in
the following example.
54 Brazil Enablement
Configuration Within MM Purchasing Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CREATING A CALCULATION SCHEMA
You must make configurations in the calculation schema to enable the tax calls. Calculation schemas in
pricing for MM are used in our new Integration in order to take advantage of document level calculation of
tax as is needed for max tax scenarios. See the User Guide
for more discussion on this topic.
Within the calculation schema, the tax call to the external system is enabled by a set of condition types
and the condition value formulas 992, 993 and 994 therefore each calculation schema used for external
calls needs to be configured in a similar way. The steps below describe the process.
1. From IMG (SPRO), navigate to Materials Management > Purchasing > Conditions >
Define Price Determination Process > Define Calculation Schema.
Brazil Enablement 55
Configuration Within MM Purchasing Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
We recommend that you copy one of the SAP country calculation schema templates
and make your changes to that copy.
ASSIGNING THE NEW CALCULATION SCHEMA TO
PURCHASE TRANSACTIONS
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
56 Brazil Enablement
SAP Master Data Setup
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
SAP MASTER DATA SETUP
ASSIGN TAX INDICATOR IN THE MATERIAL MASTER SALES
ORGANIZATION VIEW
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
MAINTAIN DEFAULT VALUES FOR TAX CODES
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
MAINTAIN COMMODITY CODE
Transaction Code: MM02. Access the Foreign trade import page:
If a NCM Code is maintained in the Control Code on the Foreign trade import page, the Integration
provides this code to the Determination for a tax decision. This code can be set when setting up a
material.
ASSIGN TAX INDICATOR IN THE CUSTOMER MASTER
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
Brazil Enablement 57
ONESOURCE Table Configurations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
MAINTAIN CONDITION TYPE ZITD TO DETERMINE TAX
CODE
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
ONESOURCE TABLE CONFIGURATIONS
MAINTAIN DETERMINE CONDITION TYPES FOR TAXES
TABLE
Transaction Code: /N/IDT/DETER_COND_TYPE
New Authority Type Column
As of release 6.3.0.0 a new column was also added to the table in order to tie the condition type to a
specific tax authority in SAP. This was due to logic needed to support the use of multiple condition types
being returned to SAP for direct linkage to tax authorities used for complex scenarios for Brazil. With the
new Brazil logic now applicable with this release, the mapping is critical for being able to drive needed
results to the various Nota Fiscal forms. This table is shipped blank and you will need to add your needed
mappings to this table based on the condition types you created in the prior steps. See example below
For each route name you will need a line in the table for each of the condition types you created for your
Brazil tax procedure, pricing procedure, etc. The new Authority field needs to be populated with the
58 Brazil Enablement
ONESOURCE Table Configurations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
matching authority name. You will likely need to use the Country Group column to limit these mappings
based on the standard country group of “BR” that is in the standard view of the Country Group Table.
In addition to this example you can refer to the table below that we have provided. This is an example as
yours may be different due to your condition types created and authorities assigned to them.
Sort
Order Route Name
Cntry
Grp CoCd NatureOfTx
ERP
Tax
Cd Authority Ctyp Description
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_SALES
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_SALES
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_SALES
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_SALES
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_SALES
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_AR BR * Percentage * IPI ZBIP IPI
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Percentage
*
IPI
ZBIP
IPI
Brazil Enablement 59
ONESOURCE Table Configurations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Percentage
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_BILLING_GEN
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_BILLING_PA
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_PURCHASING
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_PURCHASING BR * Exempt * ISS ZBIS ISS
/IDT/ROUTE_GROUP_SALES
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_GROUP_SALES
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_SALES
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_SALES
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_SALES
BR
*
Exempt
*
ISS
ZBIS
ISS
60 Brazil Enablement
ONESOURCE Table Configurations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_AP
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_AR
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_FI
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_DT
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_DP
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_FB5
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Exempt
*
PIS
ZBPI
PIS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_NON_GROUP_DOC_LIV
BR
*
Exempt
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_DELIVERY BR * Percentage * PIS ZBPI PIS
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Percentage
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Percentage
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Percentage
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Percentage
*
ISS
ZBIS
ISS
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Exempt
*
PIS
ZBPI
PIS
Brazil Enablement 61
ONESOURCE Table Configurations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Exempt
*
COF
ZBCO
COFINS
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Exempt
*
ICMS
ZBIC
ICMS
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Exempt
*
IPI
ZBIP
IPI
/IDT/ROUTE_GROUP_DELIVERY
BR
*
Exempt
*
ISS
ZBIS
ISS
BRAZIL REGISTRATION NUMBER REQUIREMENTS AND
OTHER FIELD MAPPINGS
Tax registration numbers mappings have been included in the standard view of the field mappings table
using the Business Place that is assigned to the Brazil company code. Table J_1BBRANCH was added
to the field mapping table for this purpose and standard mappings entered as a convenience to the
system user. You may have additional mappings that you require for your specific tax situation.
62 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CLASS /IDT/BRAZIL_MATERIAL_USAGE
This class is used within the field mapping table for Brazil mapping of the IS_BUSINESS_SUPPLY field
within the item request journey. Logic within this class looks at the material usage field within SD or MM
documents to determine if the IS_BUSINESS_SUPPLY field should be set to either “True” or “False”.
• If j_1bmatuse = “0” (mc_resale) then IS_BUSINESS_SUPPLY = False
• If j_1bmatuse = “1” (mc_industrialization) then IS_BUSINESS_SUPPLY =
False
• If j_1bmatuse = “2” (mc_consumption) then IS_BUSINESS_SUPPLY = True
• If j_1bmatuse = “3” (mc_ asset) then IS_BUSINESS_SUPPLY = True
CLASS /IDT/BRAZIL_FED_REG_NUMBER
This class is used within the field mapping table for Brazil mapping of the Federal Registration number for
the Buyer or Seller within the Header and Item request journeys. Logic within this class creates a
required federal registration number that is a concatenation of the Company Registration Number, the
Business Place, and the CGC number.
COMMODITY CODE MAP IN FIELD MAPPING TABLE
You will see in the standard view of the field mapping screen shots above that the Commodity Code has
also been added to the Item Request Journey as a mapping of field EKPO-J_1BNBM (Control Code).
For Brazil to work with ML81N (Service Entry Sheets), the tax codes should be set to SERVICES. We
need this step too.
Transaction – J1BTAX -> Tax Calculation -> Tax Codes MM – All the MM tax code line should be
checked with Service check box including the driver.
CONFIGURING THE SYSTEM TO SUPPORT NOTA
FISCAL
As stated at the beginning of this chapter, we recommend that your review and use extensively the SAP
library documentation for Brazil country configuration and review all of their Brazil specific tables and
various configuration options for both native tax calculation and Nota Fiscal activation and mapping. The
setting that we draw your attention to in the below noted section is not all inclusive of what is needed but
we wanted to specifically direct you to these tables as part of your task. Without these settings your
documents will not correctly populate required fields within the Nota Fiscal documents.
J1BTAX SETTINGS
Transaction: J1BTAX
Brazil Enablement 63
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
1. Within the J1BTAX menu you will need to go to: Condition Setup > Nota-Fiscal Mapping >
The three screens that follow will need to be configured for Tax values for MM and SD as well as
the tax laws for MM.
64 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Tax Values MM (example only…your condition types may be different)
Tax Values SD (example only… your condition types may be different)
Tax Laws MM (example only… your condition types may be different)
2. Within the J1BTAX menu you will need to go to: Nota Fiscal > Invoice Verification > NF-
relevant PO Conditions
Brazil Enablement 65
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
(example only… your condition types may be different)
3. Within the J1BTAX menu you will need to go to: Nota Fiscal > Inventory Management > IM
Posting Strings
66 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
(example only… your condition types may be different)
4. Within the J1BTAX menu you will need to go to: Condition Setup > Tax Types
Brazil Enablement 67
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
(example only… your condition types may be different)
OTHER CONFIGURATION SETTINGS (SPRO)
Transaction: SPRO > Financial Accounting (NEW) > Financial Accounting Global Settings (NEW) >
Tax on Sales and Purchases > Basic Settings > Brazil > Condition Based Tax Calculation >
Specify Cal. Procedures for Condition-Based Tax Calculation
68 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Application V (example only… your Pricing Procedure name may be different)
Brazil Enablement 69
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Application TX (example only… your Tax Procedure name may be different)
NEW BRAZIL ROUTE /IDT/ROUTE_GROUP_DELIVERY
This Route handles the complexity of calculating tax unique to delivery transactions. This was added to
support Brazil STO process for Nota Fiscal based on the delivery document.
NEW BRAZIL AUTO JOURNEY
/IDT/JOURNEY_BRAZIL_SD_ADJUST
This Journey adjusts the Brazil SD document and process when use to set the application area from TX
to V. This was done to allow the system to utilize the standard Nota Fiscal mapping logic in SD for
Brazil.
70 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
DYNAMIC CST DETERMINATION FOR MM
As part of the 6.4.0.0 release for the Brazil enablement, we needed to implement a solution to
accommodate dynamic laws exceptions for the Nota Fiscal on LIV Invoices. Default laws come in via
configuration that is done for the dynamic exception. The default laws utilize standard condition
technique for condition types that exist on the tax procedure.
The dynamic exception uses the ship-from and ship-to tax regions using vendor for ship-from and plant
for ship-to from the master data to lookup the associated tax region in the Brazil tax region table
(J_1BTREGV) and then uses that as the ship-from and ship-to information (along with other associated
data) to lookup in the exception table (J_1BTXIC3) to see if a valid record exists for processing.
Given our new approach for jurisdiction codes the master data will be able to have jurisdiction codes on it,
however the system will not be turned on as jurisdictional for Global Next. The jurisdiction code now
contained on the master data is used for the dynamic exception check.
ICMS tax rates are based on the combination of ship-from and ship-to state. For each combination of
ship-from and ship-to location we can enter the tax rate for ICMS and freight. ICMS text can be
maintained against the tax code for MM IN Brazil Tax Manager's Work Place (This would be treated as
the default tax law) and is expected to be populated in the Nota Fiscal document that gets created for LIV.
An exception is configured in the system (ICMS exceptions are configured in the system and are available
in J_1BTXIC3 based on the tax group configuration. SAP determines the exception during the processing
of standard function module1 _1B_PROCESS_TKOMV. This gets overwritten with the default one as
soon as the Nota Fiscal type is entered during the NF creation.
According to the new design we are dynamically getting the Condition table, access sequence and
generated field list from tables T685, T682I and T682Z respectively.
MM CST is determined from the condition record and then passed on to the Nota Fiscal document when
that gets generated in the LIV process.
All tax groups created needs to be migrated to the corresponding access sequence for the condition type.
CST DETERMINATION FOR SD
For Dynamic CST determination for SD the SAP system uses a function module to establish the CST.
Our include into this function provides the tax region code that is needed for the ship-to state and ship-
from state based on the standard addresses.
Include /IDT/SD_REGION_BR_JURD_CODE – This include program is required to be added at the start
of the function module J_1B_READ_DYNAMIC_TABLE. See Installation and Programmers Guide
for
instructions.
This has code to populate the tax region for customers (STATE_TO) and Plants (STATE_FROM) if
required to Read Dynamic Tax Exception table on SD side for tax code jurisdictions.
For Customer the country and region is obtained from the Customer address and the tax region is derived
by using the table J_1BTREGX. This tax region is then passed on to SAP as (STATE_TO) part of the
standard logic to function module J_1B_READ_DYNAMIC_TABLE.
Brazil Enablement 71
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
For Plant the country and region is obtained from the Plant address and the tax region is derived by using
the table J_1BTREGX. This tax region is then passed on to SAP as (STATE_FROM) part of the standard
logic to function module J_1B_READ_DYNAMIC_TABLE.
TAX JURISDICTION CODES FOR BRAZIL NOTA FISCAL
For our Global Next Integration 6.4 solution we are trying to follow SAP standard logic and table usage in
order to establish the required tax jurisdiction code for the Nota Fiscal. Doing so will allow the customer
to properly use SAP provided logic for the correct mapping of the Nota Fiscal Tax Jurisdiction code on the
NFe, and will also allow the customer to support proper mapping for the four free trade zones located in
Brazil.
New Table /IDT/D_TXJCD_DEF is part of this transport and this table will hold the Tax Jurisdiction Code
Definition for Brazil. A sample entry on this can be seen from the screenshot below. This table can be
maintained with the transaction code /IDT/D_TXJCD_DEF. Due to the internal checks that SAP
maintains with the standard table TTXD, we created the new table to avoid the jurisdictional calculation
requirement. See view of table /IDT/D_TXJCD_DEF shown below.
Transaction code: SE16 table /IDT/D_TXJCD_DEF
Tax Jurisdiction Code for Brazil is determined from the address and the address will need the Country,
Region and Correct Postal code to be filled in. The SAP table J_1BTREG_CITY will be used to get the
Tax Jurisdiction Code value from the address data and it needs to be populated with the valid list of
codes.
Four hooks are required within the programs in order to activate our logic for jurisdiction code data within
the master records. We have included this information within the Installation and Programmers Guide
.
In addition to the new table and the hooks, the following three SAP tables are also required to be
populated for jurisdiction code logic. See menu screenshot below and menu path:
Menu path: SPRO / Financial Accounting / Financial Accounting Global Settings / Tax on Sales and
Purchasing / Basic Settings / Brazil / Define Brazilian Tax Regions and assign to Geographic
Regions.
72 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
All regions must be populated in the table and special tax regions assigned and populated for use with the
four tax free zones within Brazil.
Menu path: SPRO / Financial Accounting / Financial Accounting Global Settings / Tax on Sales and
Purchasing / Basic Settings / Brazil / Define Tax Jurisdiction Codes
Brazil Enablement 73
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This table will need to be populated for around 5,500 municipalities in Brazil and include the formatted
jurisdiction code for each municipality and free trade zone. Users can obtain a list of these from the
Brazilian Government. We recommend you consult with our Professional Services Team as they may
have files available to download. The jurisdiction code as required for the Nota Fiscal is in two parts. The
first part is 3 digits and comprises the two digit abbreviation for the state followed with a space. The
second part is the government assigned municipal code which is 7 digits.
Menu path: SPRO / Financial Accounting / Financial Accounting Global Settings / Tax on Sales and
Purchasing / Basic Settings / Brazil / Assign Postal Codes to Tax Jurisdiction Codes
This SAP table will need to be populated with approx. 5,500 entries representing the postal code ranges
for each of the municipalities within Brazil including the four free trade zones. See screenshot of the
table below:
.
74 Brazil Enablement
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This is another large table entry step that must be completed so that Integration can establish the correct
tax jurisdiction code based on the postal codes maintained within all master data addresses for Customer,
Vendor, Cost Center, etc. This list of postal codes may be obtained from the Brazilian Government. We
also recommend that you consult with our Professional Services Team as they may have download files
available. This table will likely change more frequently as postal codes are added/maintained for the
country.
Before entries can be populated in this table the prior jurisdiction code table must first be populated as
entry to this table does a verification check against the prior table.
OPTIONAL FIELD MAPPINGS FOR INBOUND STO PROCESS
Two new journeys were established for Brazil processing of goods movement and are used when the
user wishes to establish Nota Fiscal documentation on the inbound goods movement transaction. These
two new journeys are noted below.
India Enablement 75
Configuring the System to Support Nota Fiscal
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
• /IDT/JOURNEY_HEADER_REQ_BR_GM
• /IDT/JOURNEY_ITEM_REQ_BR_GM
For each of these two journey to work and populate the correct data for the scenario there are several
field mappings that must be maintained. We have now included them in the standard view of the field
mapping table. Below is a screenshot of these mappings for your reference.
INDIA ENABLEMENT
This section of the guide will walk you through important configuration and set up that we have found to
be needed for the new India GST regime changes that at this point are scheduled to be active as of
September, 2017. Because of the timing of this release we anticipate an additional patch release that will
likely be required prior to India GST going live in a production environment. Our ONESOURCE India
enablement closely follows SAP processes that they are developing for India GST and requires usage of
the tax procedure TAXINN with all of the related tax and condition types that are used for the old tax
regime prior to GST. We do not recommend trying to use the 5.X integration versions for India GST and
also do not recommend using any other tax procedure other than TAXINN as SAP documentation
requires it. SAP downstream processes, reporting, and compliance requirements may be affected if you
do not follow their requirements, causing you untold customizations and adaptations in order to meet
country requirements.
Some of TAXINN taxes and related conditions are still applicable for product commodity codes that are
currently not included in the new GST tax regime. Users will need to calculate tax for these products as
they have in the past and in addition, add the new GST functionality for the products that the government
deems as converted to GST.
76 India Enablement
India GST SAP OSS Notes
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Rather than use separate condition types for the three new GST tax authorities (CGST, SGST, and
IGST), we have elected to take advantage of our dynamically generated tax condition ZITR as it is used
for most all other countries. If the India government reporting requirements change after our release date
and the ZITR condition conflicts with the new reporting requirements, the standard SAP recommended
conditions for CGST,SGST, and IGST per their new configuration requirements could be substituted and
adjusted into ours.
As a pre-requisite, SAP OSS note number 1175384 must be reviewed and your systems
upgraded to the appropriate support pack level per this Note. You must do this prior to importing the
other India GST OSS notes listed below AND the pre-requisite update to Determination 5.9.0.0.
As a pre-requisite, Determination 5.9.0.0 which supports India GST logic and has supported
content is required to install prior to installing Integration for SAP 6.4.2.0.
INDIA GST SAP OSS NOTES
At this time the India Enablement is based on a set of Draft SAP OSS notes that were published at the
time of this release and some of them afterwards. Finalization of the India GST tax laws and SAP’s
solution for India GST is still in process. Because of this you will need to install all of the OSS notes
manually as part of your installation and configuration tasks prior to development and processing of your
India GST solution. Number of notes to install may vary depending on what EHP level you are on.
SAP may publish additional OSS notes prior to their final release. You may need to address any
additional notes by comparing the most current list to the list that you have already installed. Additional
notes will require your extra attention, testing and adaptation to this release. We anticipate a patch
release that we may need to complete once the final SAP solution for India GST is final. It should
address additional notes and adjustments.
Please make sure that the following OSS note and their list of sub OSS notes and prerequisites have
been added to your system prior to our 6.4.2.0 release installation transports.
OSS note 2421394 is the master list OSS note for India GST in ECC version of SAP.
OSS note 2435968 is the master list OSS note for India GST in Hana versions of SAP.
Make sure you fully review this OSS note for your SAP version and plan accordingly as the list of
supporting notes included in this note is large and additional prerequisites may also be noted and
required depending on your version level.
As of 3/8/2017 we have seen an issue in the OSS note code for 2378678 for ECC that is not
correct and is not allowing the GST partner field to display on the screen. It is however in the database
table. Customers may need to address this for display of the field on screen on FB60, FB65, and MIRO if
SAP has not provided a fix by the time of our 6.4.2.0 release.
India Enablement 77
India GST SAP OSS Notes
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
OSS note 2293375 refers to CRM billing through BAPI_ACC_DOCUMENT_POST. This BAPI is
not used by the Global Next Integration. A system user may not need to apply this OSS note unless they
have customizations applied.
If you were testing the MIRO transaction with our prior 6.4.2.0 release for India GST
you would have noticed that the HSN field was made available within the GL tab of
the MIRO transaction. After 6.4.2.0 release SAP applied two OSS notes 2419215
(ECC) and 2434513 (Hana) that now remove the HSN field from the GL tab of the
transaction. This is a change to the SAP logic as they assume the field is not needed
for a GL account addition to the MIRO invoice.
2448045 AND 2073062- GST INDIA: TAXES SHOULD BE
<LINE ITEM WISE>
Note: Please refer to SAP service market place to get the latest version of these two notes and
implement this if applicable.
Issue: We have seen that Gross Amount is not getting correctly passed to Determination with Integration
for SAP for Country India when there are multiple lines in the document from MIRO and FB* transactions.
Analysis: This issue is happening as the line item wise tax is activated for India. SAP has changed the
code for line item wise calculation logic for India.
Resolution: Line by line taxation is not required for India and can be turned off using the function module
J_1I7_USEREXIT_CHECK_PROG. This OSS notes allows turning off line by line tax call by making sure
that FIXTX_ITEM is not set as 'X' in the user-exit J_1I7_USEREXIT_CHECK_PROG. This is applicable
only if India GST is enabled in the system.
Suggested User-exit Change
Check the input company code and get the country for that from the T001 table. If the country is India and
GST is turned on then check for the value in variable FIXTX_ITEM for the program and/or transaction
code to turn off the line by line tax call for India.
Per SAP program documentation:
• “To skip item level tax calculation for FI transactions (FB60, F-48, FB01, F-02...) N2073062.”
• “Set the variable FIXTX_ITEM as 'X' by idenfifying ONLY these FI cases (e.g., you may use SY-
CPROG or SY-TCODE to identify these cases, as it suits you).”
• “FIXTX_ITEM = 'X' based on your logic.”
Reference OSS note: 2073062 - Line item wise tax calculation not required for certain FI transactions
like F-02, FB60, FB01, F-48 for Indian company codes. This OSS note is referenced in Integration for
SAP 6.4.2.0 Install guide User-exit J_1I7_USEREXIT_CHECK_PROG is mentioned here too for the same
issue. Manual changes listed as per OSS notes add the required changes to function module
J_1I7_USEREXIT_CHECK_PROG for making this work.
78 India Enablement
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CONFIGURATION WITHIN FI MODULE
SETUP OF INDIA BUSINESS PLACES
India set up requires the use of Business Places for each established reporting entity and contains the
registration numbers for India companies. Follow all standard SAP Library configuration steps for each
business place for each of your GST registration numbers. You will have to create these business
places tying them to respective company codes, shipping points, sales orgs, plants, etc. per standard
SAP configuration.
VENDOR ACCOUNT GROUPS AND NUMBER RANGE
SAP Configuration for India recommends set up of Vendor Account Groups for separating Domestic
Vendors and Import Vendors. Please follow SAP configuration instructions per SAP Library.
Vendor number range for both TDOM and TIMP
Number range assignment: yours may be different according to your needs.
INDIA TAX PROCEDURE
We recommend that you use the SAP provided tax procedure TAXINN and make a copy of it to ZTXINN
as we show here. SAP documentation on the conversion to GST requires that you move to the conditions
technique version of the tax procedure TAXINN from the old formula based tax procedure TAXINJ. If you
have not converted to the new procedure you must do so at this time.
India Enablement 79
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Transaction: SPRO >Financial Accounting >Financial Accounting Global Settings >Tax on Sales
and Purchases >Basic Settings >Check Calculation Procedure.
1. Go to page 9 of the Configuration Guide SAP Tables
and follow all steps for “Creating New
Condition Types for Global Tax” if you have not already created the conditions for ZITR and
ZITF.
2. Follow page 13 instructions to create a copy of tax procedure for India GST. Once in the list
of procedures locate the tax procedure TAXINN and copy it to a new procedure before
adding the ONESOURCE conditions at the bottom of the procedure. See highlight box in the
example below for adding the ONESOURCE tax conditions to the bottom of the procedure.
Note that this screen print is a modified version of the TAXINN pricing procedure. We
recommend that you use the SAP provided version (or your current version) and add the
ZITR and ZITF conditions at the bottom rather than copying these print screens verbatim.
You may need to modify the procedure based on your specific taxation needs for the
calculation of the prior tax regime tax authorities that are still in use for GST excluded
products.
Current publications for India GST state that there are some products that are
excluded from the new GST calculation and will continue to use the old taxation
rules. Thus the pricing procedures for FI, SD, and MM calculations will be a mix of
old and new tax calculations. The ONESOURCE Integration and Determination
systems are creating new releases specific to India GST in order to meet the added
GST regime requirements. Calculation and related configuration for product not yet
moving to the new tax regime must follow prior configuration and processes and
additional features and functions relating to non GST product taxation are not
addressed in this release.
80 India Enablement
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Rather than use separate condition types for the three new GST tax authorities (CGST, SGST, and
IGST), we have elected to take advantage of our dynamically generated tax condition ZITR as it is used
for most all other countries. If the India government reporting requirements change after our release date
and the ZITR condition conflicts with the new reporting requirements, the standard SAP recommended
conditions for CGST, SGST, and IGST per their new configuration requirements could be substituted in
place of ours. However this would require additional configuration requirements within our tables. Contact
our Professional Services group if you wish to use this approach.
3. Follow page 16 through page 18 instructions on how to assign the new tax procedure to the
India company code(s), and change message control.
DEFINING TAX CODES FOR SALES AND PURCHASES
Continue in the Configuration Guide SAP Tables page 18 and create all of your required tax codes for the
India tax regime for GST. This should include the driver tax codes of I1 and O1 as well as the final tax
codes that you will need for your reporting requirements.
CORRECTION OF TAX RATE FOR ZITF AND OTHER FEE
BASED CALCULATIONS
Bottom of page 23 of the Configuration Guide SAP Tables notes procedure for correction of the tax rate
for ZITF if you have any fee based calculation.
DEFINING NEW ACCOUNT ASSIGNMENT KEYS
Bottom of page 24 of the Configuration Guide SAP Tables notes procedure for account assignment keys.
India Enablement 81
Configuration Within FI Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
SETTING UP A BLANK ACCOUNT KEY
Bottom of page 27 of the Configuration Guide SAP Tables notes creation of a blank account key.
DEFINING TAX ACCOUNTS
Bottom of page 28 of the Configuration Guide SAP Tables notes recommendation for set up of tax
accounts.
New field for India tax account assignment requires separate entry by business place
and the OSS notes added this field to the table. In order to access this view of the
table you will need to use a different transaction code and program in order to see the
new view that includes the Business place. This will likely change following the final
release of the India GST product from SAP.
Normally this is done through SPRO menu but for now must be done via sm30 as it is a different table for
India that will have access to this table in the release for India.
Transaction Code: SM30
Name: J_1IT030K_V
In addition to maintaining J_1ITO30K_V table, customers also have to maintain OB40
entries with a generic GL account but the Tax Code and Account Key should match.
ASSIGNING TAX CODES FOR NON-TAXABLE
TRANSACTIONS
Bottom of page 33 of the Configuration Guide SAP Tables notes Assigning Tax Codes for Non-Taxable
Transaction.
82 India Enablement
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CONFIGURATION WITHIN SD MODULE
CREATING INDIA SD CONDITION TYPES
You will need to follow the instructions as noted beginning on page 38 of the Configuration Guide SAP
Tables for the creation of SD condition types ZITD, ZITE, ZITR, and ZITF. You will be adding these
conditions to the current pricing procedures for SD. You may also need to add the SKTO and SKTV
conditions for cash discounts.
Condition Type Conditions and Categories
Condition
Type
Text
Condition Category
Calculation Type
ZITD
IDT Collect Data
D
A – Percentage
ZITE
IDT Call Determin.
D
A – Percentage
ZITF
Return IDT Fee Value
D
B – Fixed amount
ZITR
Return IDT Tax Value
D
A – Percentage
SKTO
Cash Discount
E
A – Percentage
SKTV
Cash Discount
E
A – Percentage
INDIA PRICING PROCEDURES
SAP native procedures identify several SD pricing procedures that it may use for the native tax
calculation. ONESOURCE Indirect Tax uses these same pricing procedures and inserts our call condition
types at the end of the procedure for ZITD, ZITE, ZITR, and ZITF processes. You may likely use a
separate pricing procedure for Factory Sales, Export, and Stock Transport processes.
Sample pricing procedures are shown here below with the added conditions needed for the Integration.
You copies will likely be different, taken either from the SAP configuration instructions or from the new
GST SAP configuration instructions. In either case add the four conditions that you created in the prior
steps for all the various pricing procedures that you use. Exports are exempt from GST so may likely
have a different pricing procedure. Any call on Export scenario should bring back tax of IGST exempt
status (ZE) which would then follow with an entry in the audit database that can be used for compliance
reporting.
You can do this procedure by referencing page 45-48 on the Configuration Guide SAP Tables
. Use the
standard pricing procedure(s) as offered from SAP or your prior procedure, and add the four conditions as
shown.
Example of Factory Pricing Procedure:
India Enablement 83
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Example of Stock Transport Order Pricing Procedure:
Example of Export Pricing Procedure:
84 India Enablement
Configuration Within SD Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
ASSIGNING INDIA PRICING PROCEDURES TO SALES
TRANSACTION
Based on your setup of SD document types, pricing procedures, products, etc. you will need to assign the
various pricing procedures to your sales transactions. See page 49-50 of the
Configuration Guide SAP
Tables for examples on how to assign the procedure to your sales documents.
DEFINE TAX DETERMINATION RULES
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
DEFINE TAX RELEVANCE OF CUSTOMER MASTER
RECORDS
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
DEFINE TAX RELEVANCE OF MATERIAL MASTER
RECORDS
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
India Enablement 85
Configuration Within MM Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
CONFIGURATION WITHIN MM MODULE
NEW PARTNER FUNCTIONS TO ADD TO TABLE
Because of the new field for the GST Partner that has been added to both the SD, MM and FI process we
see the need to also create partner roles for GST Partner and allow for custom mappings of the new
partner function to the XML request data for transferring this updated address to the Determination
request. Please follow the below steps to add this to the partner roles table and in the next step complete
the new address mapping to the customer address mapping tables.
Transaction: : SPRO -> Materials Management -> Purchasing -> Partner Determination -> Partner
Roles -> Define Partner Roles
1. From the diagram above you will see that you need to create new entries for ZG - GST
Partner with a KU for Customer side and ZP - GST Partner with a LI for the Vendor side. We
have used the first letter of Z as SAP has reserved this set of partner codes and being in the
customer area or namespace and will not write over them if they add new partner roles to the
table. You will get a warning message if you attempt to enter any custom codes other than
“Z”. Save your work as a new entry. If your system already uses these codes then you will
need to adjust and use different codes for the two GST Partner assignments and also adjust
your next two steps.
2. Next step is to assign the new partners to the India vendor groups
Transaction SPRO -> Materials Management -> Purchasing -> Partner Determination -> Partner
Roles -> Define Permissible Partner Roles per Account Groups
86 India Enablement
Configuration Within MM Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Per this screen shot add these four new entries to the table. Your partner code could be different if they
were already assigned.
CREATING NEW CONDITION TYPES
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
Condition Type Conditions and Categories
Condition Type
Text
Condition Category
Calculation Type
ZITD
IDT Collect Data
D
A – Percentage
ZITE
IDT Call Determin.
D
A – Percentage
ZITF
Return IDT Fee Value
D
B – Fixed amount
ZITR
Return IDT Tax Value
D
A – Percentage
SKTO
Cash Discount
E
A – Percentage
SKTV
Cash Discount
E
A – Percentage
INDIA CALCULATION SCHEMAS TO BE ADDED
Per recent documentation and notes on India GST we have identified two possible calculation schema
that you may need to add to your system for purchase of import goods, and purchase of domestic goods.
We have included below examples of both of the calculation schema however yours may be different
according to your tax needs. What is important is that the same condition types that were created in the
prior step must be added to your calculation schema for India GST so that calls will be made to
Determination. See copy below and follow the like instructions from the
Configuration Guide SAP
Tables.
Example of Purchase of Import Goods Calculation Schema
India Enablement 87
Configuration Within MM Module
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Example of Purchase of Domestic Goods Calculation Schema
ASSIGNING THE NEW CALCULATION SCHEMAS TO THE
INDIA PURCHASE TRANSACTION
In the prior configuration step Vendor Account Groups and Number Range you created two new groups
for Vendor master data. One was created for domestic vendors (TDOM) and one for import vendors
(TIMP). Likewise in this step you will need to create calculation schema assignments based on these two
vendor types.
Transaction: SPRO -> Materials Management ->Purchasing -> Conditions -> Define Price
Determination Process -> Define Schema Group
In this step you need to assign two schema group codes to the table for Domestic and Import vendors.
88 India Enablement
SAP Master Data Setup
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Transaction: SPRO -> Materials Management -> Purchasing -> Conditions -> Define Price
Determination Process -> Define Schema Determination -> Determine Calculation Schema for
Standard Purchase Orders
In this step you need to assign the two schema group codes that you created in the prior step to the
pricing procedures created above.
You will need to use the new schema group codes when you set up your vendor master data in the next
step so that vendors are assigned to the appropriate pricing procedure.
Transaction: SPRO -> Materials Management -> Purchasing -> Conditions -> Define Price
Determination Process -> Define Schema Determination -> Determine Schema for Stock Transport
Orders
Here you will need to assign the pricing procedure for domestic vendors to the UB document type and
supplying plant for Stock Transport purchase orders.
SAP MASTER DATA SETUP
ASSIGN DATA TO VENDOR MASTER
In setting up your vendor masters using the new vendor group TDOM and TIMP you will need to also
assign the Vendor Schema Group code to the purchase data view in the vendor master records.
India Enablement 89
SAP Master Data Setup
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
Transaction: XK02
For vendors created as TDOM you would assign on this view the Z1 code designating it a domestic
vendor that used the calculation schema created for domestic sales.
For vendors created as TIMP you would assign on this view the Z2 code designating it an import vendor
that used the calculation schema create for import purchases.
Within the Vendor Master Control tab you will also need to record the GST tax registration number in the
Tax3 field for India.
Within the Vendor Master for India vendors there is a CIN tab at the top that is used to store other
important data for India taxes. You will need to utilize this tab to add needed registration numbers for the
old tax regime authorities if applicable and also make note of the new GST data tab within CIN details and
assign the correct code for the GST Ven. Class. field.
90 India Enablement
SAP Master Data Setup
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
ASSIGN TAX INDICATOR IN THE MATERIAL MASTER SALES
ORGANIZATION VIEW
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
MAINTAIN DEFAULT VALUES FOR TAX CODES
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
MAINTAIN COMMODITY CODE
Transaction Code: MM02. Access the Foreign trade import page
ASSIGN TAX INDICATOR IN THE CUSTOMER MASTER
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
ASSIGN DATA TO CUSTOMER MASTER
Within the Customer Master Control tab you will also need to record the GST tax registration number in
the Tax Number 3 field for India.
India Enablement 91
ONESOURCE Table Configurations
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
For India Customers there is also a CIN tab that contains registration number data for the old tax regime
information if needed. Go to CIN details tab to fill in required information there as needed.
MAINTAIN CONDITION TYPE ZITD TO DETERMINE TAX
CODE
This is the very same process as is documented in the Configuration Guide SAP Tables. Please refer to
the other guide and process as required.
ONESOURCE TABLE CONFIGURATIONS
The following is a list of the India specific field mappings that you must add to the custom view of the field
mapping table as of this release for India GST registrations, and commodity codes. Because of the way
the SAP code has been released in draft mode we cannot populate these as standard mappings at this
time and require users to enter them manually. At a later point in time these may be made standard
mappings once our customers are all on the higher release level that is required. There will most likely be
other fields that you will want to add for your specific tax requirements. See
Configuration Guide
ONESOURCE tables for more information on the field mapping instructions.
92 India Enablement
Customer Address Source Table Configuration
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
The following is a list of the India specific address mappings that you must add to the custom view of the
field mapping table as of this release for India Business Place and partner function addresses. Because
of the way the SAP code has been released in draft mode we cannot populate these as standard
mappings at this time and require users to enter them manually. At a later point in time these may be
made standard mappings once our customers are all on the higher release level that is required. There
will most likely be other addresses that you will want to add for your specific tax requirements. See
ONESOURCE Table Configurations Guide for more information on the address mapping instructions.
CUSTOMER ADDRESS SOURCE TABLE
CONFIGURATION
New address source for GST Partner has been coded and part of the India Code Transport but because
of the nature of the India Enablement project this needs to be manually mapped to the customer view of
the address source table. Please review the screenshot below and add the GST partner line to your
table.
Currently the address source for Place of Supply for SES function has not been added and will be added
in a patch release 6.4.3.1
SAP TABLE MAPPING REQUIREMENT FOR GST
Transaction code: SM30 to the Table J_1IEXCDEFN
India Enablement 93
New India STO Transaction J_1IG_INV
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
This list of entries needs to be added to the table in SAP for requirements on the India GST process. Your
procedure names may be different.
NEW INDIA STO TRANSACTION J_1IG_INV
New transaction code was created by SAP for use in India where there are two plants in same region and
a STO is required to produce both and outbound invoice on the sending plant as well as an inbound
invoice on the receiving plant.
We have addressed this with a special and separate optional configuration transport that must be applied
with installation of the Integration system as of release 6.4.3.0. Your programmer must also add two
hooks or include statements as noted below. This new transaction uses the calculation call from the
outbound delivery invoice to then save the information in a temporary table to later be used in the creation
of the inbound invoice. There is no second call in transaction code J_1IG_INV so the tax call data must
be temporarily saved and referenced for the inbound invoice. An additional journey, route and mappings
are also utilized in this scenario.
The steps in this scenario include:
1. Transaction ME21n for creation of the STO purchase order
2. VL10B – create delivery in background
3. VL02N – post goods issue
4. VF01 – invoice on outbound delivery
5. MIGO – receipt of goods in inbound plant
6. J_1IG_INV – invoice for inbound plant
A new journey called /IDT/JOURNEY_INDIA_STO_INB is created for doing the second tax call for the
Buyer side. This tax call is available in the log for the calculation call but we will not be sending this
information to the Audit. The second call is deleted after the required details are stored in the custom
table.
See below screen shot of Data in table /IDT/D_INDIA_STO.
94 India Enablement
New India STO Transaction J_1IG_INV
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
GST inbound Invoice is then created by executing transaction code 'J_1IG_INV'.
SAP uses the program J_1IG_INB_INV_STO for this. This program calls function module
J_1IG_INB_INV_CREATE and that in turn calls the BAPI BAPI_ACC_DOCUMENT_POST to post the
inbound invoice (Accounting document). We use the taxes calculated and stored in the table
/IDT/D_INDIA_STO for this document. This is added just before the BAPI call within a BADI provided by
SAP.
SAP has provided the BADI BADI_J_1IG_STO that allows us to change the tax values before the BAPI
posting. An implementation needs to be created for this BADI. Method CHANGE_BEFORE_POST can be
used for this. Tax codes and Account keys stored in the custom table will be used to populate the tax
values for the BAPI posting.
Hook 1 – Include /IDT/INDIA_GST_STO_BADI needs to be added in the method
CHANGE_BEFORE_POST as shown in the screen shot below.
Then the BAPI BAPI_ACC_DOCUMENT_POST gets called immediately after this. We need to create an
implicit enhancement as BAPI does a validation for Account Key.
Hook 2- The include program /IDT/INDIA_GST_STO_SKIP_ACCKEY needs to be added at the start of
the function module FI_TAX_GET_TAX_ACC_BY_KSCHL to skip this validation. This is required only for
India GST STO.
India Enablement 95
New India STO Transaction J_1IG_INV
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
The document that gets created will be send to Audit using the existing journey
/IDT/JOURNEY_AUDIT_SAVE_FRM_GL
New Route /IDT/ROUTE_NON_GROUP_DOC_INSTO - Route for India GST STO Inbound Invoice is
created for this purpose. This is added to switch on route configuration.
Go to /IDT/ROUTE_CONFIG - Route Configuration and insert this line to the table.
This new route is then added to the Auto Journey Configuration table too.
Go to /IDT/AUTO_JOURNEYS - Automatically Processed Journeys table and insert these lines to the
table using your specific company code(s) on the line or lines.
Address Mapping Configuration is maintained for this route so that the Audit Update happens correctly.
See list below and add these mappings to the Address Mapping table as custom views.
96 India Enablement
New India STO Transaction J_1IG_INV
ONESOURCE INDIRECT TAX INTEGRATION FOR SAP VERSION 6.4.3.0
CONFIGURATION GUIDE FOR SPECIAL FUNCTION V1
As the Inbound Invoice document creates a FI accounting document (Type RE) we will need to maintain
the FI configuration table with a new FI process entry. (/IDT/FI_PROC_INDIA_IB_STO).
Go to /IDT/FI_CONTROL - FI Process Control Configuration table and add this line as below.
User system must install optional transport to the system and follow the instruction in the Installation
Guide for transports and include statements that must be added for the hooks into the programs. See
Installation and Programmers guide on Optional India section for further details on the transport and
includes that are required.
