Nota Fiscal is very peculiar legal requirement in Brazil and it required a thorough understanding to keep this relevant to avoid any business blockage. There is high impact of any wrong setup blocking business from processing invoices. This article explains the impact of upgrade to SAP ECC6 on Financial Accounting setup for Nota Fiscal and will be helpful for quick adoption of current setup to upgraded SAP ECC6 environment.
Below are three main impacts in Financial Accounting:-
(1) Impact on Tax Procedure TAXBRA:-
Tax procedure TAXBRA is application for Brazil which is condition based tax pricing procedure. The access sequences for various tax conditions in TAXBRA have been changed by SAP in standard SAP in ECC6.
E.g. before upgrade to ECC6, the access sequences for condition type for COFINS (BRCO) were as below:-
05 Country / Material / Dynamic Key Field 2 / Dynamic Key Field 3/ Tax Group
50 Country / Company Code/ Dynamic Key Field 2/ Dynamic Key Field 3/ Tax Group
But after upgrade to ECC6, SAP changed the access sequences for condition type for COFINS (BRCO) to below:-
05 Country / Material / Dynamic Key Field 2 / Dynamic Key Field 3/ Tax Group
99 Country
To adapt to new settings for ECC6, the quickest way is to enhance the access sequences to include the one which are now missing in upgraded SAP ECC6.
So in above example, the access sequence 50 should be incorporated into the customization of access sequences BRCO for tax procedure (Transaction OBYZ) resulting in below access sequences:-
05 Country / Material / Dynamic Key Field 2 / Dynamic Key Field 3/ Tax Group
50 Country / Company Code/ Dynamic Key Field 2/ Dynamic Key Field 3/ Tax Group
99 Country
It will ensure that all your existing condition record setup will be picked up as before.
If needed, you can maintain extra condition records for new access sequences introduced by SAP in ECC6, e.g. for access sequence 99 for condition BRCO
Note:
This impact is explained for tax procedure in Finance. However a similar impact will also come in Sales and Distribution (SD) for the pricing procedure part, where access sequences for pricing procedure should also be adopted in the same way as explained above.
(2) Impact on Maintenance of Tax Rate in Transaction J1BTAX:-
After upgrade, SAP has mainly changed the behaviour for below tables as customization tables and thus to be maintained via transport request or by opening the system client.
Description | Table |
Maintain IPI Material-Dependent Exceptions | J_1BTXIP2 |
Maintain ICMS Material-Dependent Exceptions | J_1BTXIC2 |
Maintain ISS Values | J_1BTXISS |
Maintain PIS Values | J_1BTXPIS |
Maintain COFINS Values | J_1BTXCOF |
Maintain Withholding Tax Rates and Assign Official Collection | J_1BTXWITH |
It makes the maintenance of above table difficult in transaction J1BTAX in production environment.
So the definitions of these tables can be changed by enhancing the table definitions in table maintenance or from customization in transaction SOBJ for the relevant view of above tables.
(3) Impact on Decimal Places for COFINS / PIS Tax Rates:-
SAP has also enhanced the option two decimal places to four decimal places for COFINS and PIS tax rates. So a tax rate will 4 decimal places is now possible to be maintained in J1BTAX.
However depending on the tax rate format, you would need below setup:-
- If you still want to continue maintaining the rate with two decimal places:-
- Then apply OSS note 1833440 which avoid any incorrect messaged during tax rates maintenance
- If you want to maintain the rate with four decimal places:-
- Then apply OSS note 1853059 which required additional customizations as attached to OSS note
