Skip to Content

Bad performance in J1BTAX migration for NF-e Brazil


on Jan. 11th we moved the actual NF-e package into production without having run the complete J1BTAX exceptions Tax Groups to conditions migration.

Why did we do this? When running the migration we faced huge runtime issues for the sum of 590.000 relevant table entries in J_1BTXIC3.

At last, we had a processing time of 2,2 seconds per entry in our production systems which is terrible. So for the Moment, our Brazil sales org. is working via a workaround.

May I ask the community for their experience with the different possibilities for the migration provided by SAP?

What was your runtime? Which sequence did you follow for migration (e.g. run the consistency check etc.)..

Which problems popped up?

Thanks for any response!

best regards


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 27, 2016 at 09:32 AM

    This query is not related to sales and hence moved from SAP ERP SD Billing to Security

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2016 at 01:02 PM

    Hello Benjamin,

    J1BTAX migration works in the following manner for ICMS exemptions:

    For each line on J_1BTXIC3 the system can create up to 5 lines on table A382, from each line created on table A382 one line will be created on table KONH and from each line on KONH one line will be created on KONP.

    When you have many records on the ICMS Exemptions it is normal to have a huge process time on the report. To help with that, it is possible to run in background the program: J_1B_GEN_TAX_COND_BACK

    In this program you will need to specify the name of your table (J_1BTXIC3 on your example I suppose), and the name of the Tax Group, which can vary from 10 to 89.

    I hope I have helped with this.


    Daniel Zambrini

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.