Skip to Content

Synchronize Payroll Tax Data

Not even the upgrade to TaxFactory 10 has confounded as many customers as, apparently, the requirement to use the new Payroll Tax Data Sync tool. The tool has been available to customers since March 2014, and its use will become mandatory as of April 2015 when SAP will stop publishing transport files containing regulatory update (TUB) data. In the year since its first release it has undergone a number of revisions and updates via Support Pack and Note.

One of the complicating factors for some customers can be the use of custom tax data in the SAP tables. Likewise, maintaining tax data for multiple states or differing tax authorities, or reciprocal tax situations where employees live in one state but work in another, can make the situation much more complex. Addressing these complications is beyond the scope of this blog, unfortunately. Instead, the focus here will be correct operation of the basic Sync tool functionality, as this must be working first before such more advanced topics may be addressed.

Synchronize Payroll Tax Data

The Old Way

The old method of keeping tax data synchronized between TaxFactory and SAP was a two-step process:

  1. Download Regulatory Bulletins from BSI and apply them, one at a time in an incremental fashion, to your TaxFactory database via the maintenance update tool in the TaxFactory client.
  2. Download the most recent TUB (Tax Update Bulletin) transports (matching the highest level Regulatory Bulletin applied) from the SAP Service Marketplace and import them to your ECC system via STMS (or the TP command-line tool, if you’re really old-fashioned).
    1. TUBs could be applied either incrementally or cumulatively, depending upon your needs. Generally, if your tax tables did not contain custom data, you would use the cumulative transports.
    2. TUBs would become available from SAP usually one or two days after the matching Regulatory Bulletin was released by BSI.

There were several complications associated with this method, not least of which was potential confusion about which TUB transports to apply and which client to apply them to, as well as the delay between availability of the BSI Regulatory Bulletin and the SAP TUB.

A Streamlined Process

The new method eliminates the need to download TUBs from SAP and apply them as transports. Instead, you download and apply Regulatory Bulletins to your TaxFactory database the same as before, then you run a tool in your SAP system to synchronize the changed tax data from TaxFactory into the appropriate SAP tables. This eliminates the delay in availability of TUBs, it eliminates the extra downloads and imports, it potentially places control in the hands of payroll experts instead of Basis, and on the surface seems logical and simpler than the old process.

When it works properly, it is indeed simpler. The key is ensuring your system is ready for the tool, and understanding the process.

System Preparations

BSI TaxFactory

The main requirement on the TaxFactory system is that you have TaxFactory 10.0 properly installed, configured, and working in concert with your SAP Payroll system. See BSI TaxFactory 10 Installation/Upgrade for SQL Server for details about installing or upgrading to TaxFactory 10.

However, I also recommend that you apply the most recent Cyclic update to your TaxFactory system. For more details, see BSI TaxFactory 10 Cyclic Update.

Otherwise, the main requirement is to apply the Regulatory Bulletins that you wish to synchronize. We’ll go into this in more detail below.


On your SAP Payroll system there is a minimum required Support Pack level and then a number of SAP Notes which must be applied. Additionally, there is a minimum TUB level that must have been applied the “old” way first.

HR Support Pack

The Sync tool was initially delivered with Note 1975742 (BSI: Synchronize Payroll Tax Data). The changes from this Note cannot be applied via SNOTE, however, but instead must be applied via HR Support Pack (HRSP). Therefore, the minimum required HRSP for the Sync tool is:

  • SAP_HRCUS 6.00:  A6 (e.g. 106)
  • SAP_HRCUS 6.04:  72
  • SAP_HRCUS 6.08:  01

As the minimum required HRSP to support Tax Reporter for Year-End 2014 was higher than this, the chances are good that you have already met this requirement.

SAP Notes

On top of the HRSP, there are a number of Notes to correct or improve the functionality of the tool, and new Notes are being released fairly frequently at this time. Many of the most commonly reported issues with the tool are corrected by one or more of these Notes, so it’s very important to apply them. The required Notes are detailed in Note 1975742 (previously mentioned) and Note 2082725 (BSI: Synchronize Payroll Tax Data – FAQ), but there are additional newer Notes not yet updated in the FAQ. The most up-to-date list is maintained on SCN at Synchronization Tool notes and updates – TaxFactory 10. That discussion thread is also a good place to post questions or issues with the tool.

Depending upon your Support Pack level, of course, many of the Notes may already be in your system. Here is the list of Notes and the HRSP in which they were delivered (numbers given for SAP_HRCUS 6.00 (ERP 6.00 – EhP3), 6.04 (EhP4-7), and 6.08 (EhP8)), as of the date of this blog:

It is important to apply all of the Notes listed above, even if the Note title implies that it may not be applicable to you. For instance, you may not wish to hide the transport pushbuttons and therefore feel you do not need Note 2064814. However, this Note also includes critical corrections, and so must be applied for correct functioning of the tool.

Bear in mind that a Note may be updated later, thus causing it to be included in a more recent Support Pack. Also, new Notes for this tool are released frequently.

UPDATE 23 April 2015:

I have added two Notes to the list above (in bold), 2155723 and 2160075 (released just today).

Note 2127736 Special Instructions

UPDATE: Previously this Note required special handling, as detailed below. However, as of 13 March 2015 it has been re-released, and a new prerequisite Note (2141706) created. Applying the prerequisite in advance prevents the activation errors that required the special handling.


Like several others, this Note involves both automatic corrections (that can be applied with SNOTE) and manual “post-implementation” corrections. You will likely encounter activation errors in SNOTE, as follows:



You can safely ignore this error and “activate anyway,” as you will be creating this data type in the post-implementation manual phase, as described in the Note. You cannot create it in advance, as the automatic correction introduces a report to be run which then creates the new data types. After you run the report, all will be well (and you can confirm by checking the objects in your transport request afterwards).

Minimum TUB

Before running the sync tool for the first time, you also must bring your SAP system up to a minimum of TUB 019 the “old-fashioned” way (download TUB transports from SAP and import them via STMS). This has proven to be a source of confusion for a number of users who thought their systems were at or above TUB 019, yet they still got the error “The system does not have the required TUB installed” when attempting the tool. The confusion has occurred frequently enough that there is a KnowledgeBase Note (2139409) explaining the issue and the correct procedure.

In a nutshell, the key point is that TUBs have both client-independent and client-dependent components. The client-dependent components must be applied to your working client, however some of them have a table class that prevents direct import to any client other than 000. As a result, a number of customers have been applying TUB updates to client 000 in their systems, but never cascading the changes to their working clients. This results in an inconsistent TUB status in the working client, and this is what the Sync tool reads. Thus, the error message is correct.

The correct, or best, procedure to follow to ensure the TUB is correctly applied to your working client depends on whether you have customized any of the entries in the affected tables. If you have not customized the tables, then you can safely import the common and cumulative transports of the TUB directly to your working client.

Wait — didn’t I just say that these transports contain tables that can only be imported to client 000? Yes, that’s true. However, in STMS there is an override option you can set, Ignore Non-Permitted Table Class. You can find this option on the Options tab of the import dialog (for importing single requests only — you cannot choose this in Import All).

So, in this circumstance, you will select your working client for all five of the typical transports involved in a TUB, but choose this advanced option for the two cumulative transports containing tables T5UTA, T5UTB, T5UTD, T5UTR, T5UTW, and T5UTZ.

If you have customized any table entries, then there is no change for the “Common Tax Data Update” transports, and you must choose between Cumulative or Incremental Tax Data Updates, and import the latter only into client 000. Afterwards, you must use transaction SM31 to compare the table entries between client 000 and your working client, identify the newly created entries in client 000, and adjust your working client to copy those entries over. This procedure is explained in detail in Notes 2139409 (The system does not have the required TUB installed) and 1532493 (TUB: Applying transport files from TUBs). More information is also found in Note 1910128 (TUB: Finding and applying TUBs for TaxFactory 10.0).

Apply Regulatory Bulletins to TaxFactory

Ok, the prep work is done, it’s time to sync some data. But, first there needs to be some data to sync.

Logon to and select Product Maintenance. Choose productBSI TaxFactory, then under Maintenance select Regulatory Bulletins. Choose BSI TaxFactory 10.0 Regulatory Bulletins and then select the download link for each and every Regulatory Bulletin that is newer than what you currently have installed in TaxFactory (for example, if your system is currently at bulletin level 42, you will download bulletins 43 through 49 (or higher if available)).

While on this page, also click on the title of each bulletin. This will open a new browser window with the cover page for the bulletin. Scroll through the cover page and make a note of all of the Effective Dates in the section for BSI TaxFactory Engine (you are not concerned here with ReciprocalTax, WageAssessor, etc). You don’t need to separately record each tax authority, just each unique effective date for federal, state, or local tax changes. For example:

Here you see two tax authority changes (Arkansas and Hawaii, but they both have the same effective date, so you only need record it once. In our example of applying bulletins 42 through 49, we find that almost all of the changes have an effective date of 1/1/2015. One state change (for Oregon) has an effective date of 4/1/2015, and a number of changes have an effective date of “immediately.” What we are concerned with here are all the unique dates found in the range of bulletins. In our example, there are only two: 1/1/2015 and 4/1/2015. We’ll come back to the “immediate” changes in a bit.

Logon to your TaxFactory client as user TF10, connect to your working Data Set (if necessary), and jump to System Tools. Under Maintenance Tools you can confirm the current bulletin level, then click Manual Update.

Browse to the first of your downloaded Regulatory Bulletins and click Process.

When the import is done, look through the Maintenance Output for any errors, and check the end of the Update Output for something similar to the following:

Check the Summary to see that the most recent number has incremented, and then repeat the process with the next bulletin, until you have imported them all. Note that occasionally a bulletin’s update output is larger than the client tool seems capable of displaying, in which case the View Update Output link may not show as far as the end of the report. In this case, if the maintenance output shows only success messages, you should be good to go.

When all the bulletins are imported, click Exit and confirm on the prior screen that the bulletin number has incremented appropriately.

Synchronize Bulletin Data to SAP

Run the Tool in DEV

Logon to your customizing and development client in your development system and execute transaction:


First confirm it is properly connecting to your TaxFactory system and reading the bulletin level there. You can do this by pressing Display Version in the Regulatory Bulletin Information section, near the bottom of the screen.

The first time you run the tool in DEV, you will only see data for the BSI Client. After you’ve run it in productive mode at least once, you will also see the local SAP bulletin level. Note, however, that the local SAP data will only be accurate in your DEV system, unless you manually sync the data in each system. If you create transports for the sync’d data out of DEV, however, then the QAS and PRD systems will not display their bulletin levels.

Effective Dates and Test Run

Leave Test Run selected (the default) in both Synchronize Cross-Client Data and Synchronize Client-Specific Data for the first execution. In Effective Dates, enter the dates you recorded from the bulletin cover pages on separate lines, using the same date as Start Date and End Date on each line. You can also enter the dates as a range, using the earliest date as Start Date and the latest date as End Date, but this will cause the tool to run for each date in between, even though there are no updates for any of those specific dates. This could increase the runtime quite a bit.

What about the changes with effective date “Immediately?” You do not need to worry about these. As they don’t have an effective date, the tool will always find them and synchronize them if necessary.

The first time you run the tool productively (or any test runs before that first productive run) the tool does a few special tasks which are not then repeated after:

  • The tool moves entries from table BTXTAXC to table T5UTZC (approximately 4,900 table entries). BTXTAXC is obsolete. Once this migration is made, it will not be repeated, and future updates will occur in T5UTZC.
  • The tool attempts to recreate all the tax areas in your system. If they already exist, nothing is changed and a warning message is logged. In future runs, only new tax areas are created, so the number of warnings will drop significantly.
  • The tool creates tax authority mappings (SAP<->BSI) in the TaxFactory data set. Most of these should already exist if you applied the initial tax mapping file to your TaxFactory system when you first installed (this file is supplied by SAP, not BSI: see BSI TaxFactory 10 Installation for SQL Server – Part 3), however unless you have been manually keeping these mappings up-to-date, there may be some missing. Future runs of the tool will update the TaxFactory database with new tax authority mappings, but shouldn’t need to update so many of them.

Press Execute ().

When it is finished, you will see a results screen in which you can see exactly what the tool did (or would do if not in test mode):

Productive Run

With a successful test, it’s time for the real thing. Depending on how the test went, you may decide here to split the run up into smaller parts, or just go for it. Select Productive Run for both Cross-Client Data and Client-Specific Data. Do not select Process Tax Authority Mappings Only. Adjust your effective dates, if needed. Enter a description, such as “TUBs 043-049.” Click Execute.

You will get a popup confirmation stating This action will update the selected Payroll Tax Data. Are you sure? Click Yes.

This first run may take a while, though it may possibly run faster than the test.

When it is complete, you should see all the same warning messages in the log as during the test run, but also one informational (green) message: All entries have been successfully saved to the database. If you have this message, and no errors or terminations, then likely everything has worked fine. You can also drill down into the various tables listed in the results to see what changes were made — these should match the descriptions from the bulletin cover pages. If in doubt, check the tables directly with SE16 to see that the entries are there.

In the TaxFactory client, on the home screen, you should see There are 0 unmapped authorities. You may also see a large number of messages in the message viewer, as if there had been a pay run.

Back out from the results to the selection screen. Click on Display Version again, and now you should see your Regulatory Bulletin version displayed for SAP data as well as BSI data.

Create Transports

Having synchronized the changes in your development system, you can create transports with the relevant table entries to migrate them to your QAS and PRD systems. You will create a workbench transport for the cross-client data and a customizing transport for the client-specific data. These are cumulative transports which will capture all of the non-custom data in these tables.

At the top of the selection screen, click on Cross-client:

Create a workbench transport as you normally would. Then repeat the process for Client-specific and a customizing transport.

The cross-client transport saves all entries from tables BTXAUTH, BTXFORM, and T5UTX. The client-specific transport saves all entries from tables T5UTD, T5UTZ, and T5UTZC, and all SAP-generated entries from tables T5UTA, T5UTB, T5UTR, and T5UTW. That means that if you have custom entries in that last set of tables, they will not be captured in the transport.

Transport Issue with Table T5UTD

UPDATE: On 3/17/2015 SAP released Note 2128332 which should address this issue. I have not yet had the opportunity to test the Note myself, but will update the blog when I have. If the Note works as intended, then the client-specific transport should be usable as designed, and the problem with table T5UTD should not occur.

PREVIOUS WORKAROUND: At the time of writing this blog, several customers (including myself) reported an issue with table T5UTD not updating correctly via the client-specific transport. For now, the workaround and suggested practice is to use the cross-client transport, but not the client-specific transport. This means that after importing the cross-client transport in your QAS or PRD system, you will then need to open the system for client-dependent changes via SCC4, then run the Sync tool for client-specific data only. Afterwards, close the system to changes again.


Once you are satisfied with everything in your DEV system, release the transports (the various Notes you applied, and the workbench and customizing regulatory updates).

Apply the changes to your QAS TaxFactory system the same as you did for DEV: Cyclic bulletin (if applied in DEV), and Regulatory Bulletins.

In your SAP QAS system, import the transports you released from DEV into your working client (the Notes and workbench updates are client-independent, so choice of client is irrelevant). If you examine the logs for the transports, you will be able to confirm updates to the appropriate tables.

NOTE: If you applied Note 2128332 before creating the transports, then all should work correctly (see Transport Issue with Table T5UTD above). If you did not, the transport for client-specific data may not correctly update table T5UTD for some customers. Therefore, I recommend not importing this transport (or don’t even create it in the first place) without applying the Note.

Now here things get a little sticky. The transports you just imported included all the regulatory update data needed in your SAP system. However, you may still need to process tax authority mappings on your TaxFactory system. You can determine this from the home page of your TaxFactory client (when connected to the working Data Set), in the System Summary:

If you see a number other than 0 for unmapped authorities, then you need to process tax authority mappings. The Sync tool has a facility for managing this, but it requires that your SAP client be opened for client-specific changes, even though you are not changing anything on the SAP system. This is because, currently, the option to process tax authority mappings only works if Productive Run is selected for Synchronize Client-Specific Data, and Productive Run is only available if the client is open for configuration/customizing changes.

Start transaction SCC4, click on the Display -> Change button () to put the view in Change mode, and double-click your working client. In the section for Changes and Transports for Client-Specific Objects select the radio button for Changes without automatic recording.

Note you do not need to enable Cross-Client Object Changes, only client-specific changes. Save this change and go into transaction HRPAYUS_SYNC_TAX_DT again. Set Synchronize Cross-Client Data to Do Not Run (and note that Productive Run is greyed out). Set Synchronize Client-Specific Data to Productive Run and select the checkbox for Process Tax Authority Mappings Only. Set an Effective Date (any date should do) and an appropriate comment.

NOTE: If you are not using the client-specific transport, then leave Process Tax Authority Mappings Only unchecked, and instead do a full sync of client-specific data. This will also update the tax authority mappings at the same time.

Execute, and confirm in the warning dialog. The runtime should be fairly quick. When it’s done, in the results you should see a number of lines equal to the number of unmapped authorities with the message System creates mapping between tax authorities…

Return to your TaxFactory client, refresh the home screen, and note that the number of unmapped authorities has now dropped to zero. Return to transaction SCC4 and set the client change option back to the previous setting (most likely No changes allowed).

When ready, repeat this process in PRD.

Checking the Results

You can confirm that your transports properly set the appropriate entries in your SAP system by executing the Sync tool with Test Run set for both cross-client and client-specific data and the same effective dates as used in DEV. Drilling down in the results should show grey lights and the message No changes have been detected for table… for each table, and a green light and the general message No missing tax authority mappings found.

Handling Custom Data in SAP Tables

The procedure above is oriented for customers who do not customize the tax data in any of the SAP tables. These customers previously would have always used cumulative TUB transports instead of incrementals, and would have imported all the TUB data directly into their working clients.

However, some customers have custom data which they need to maintain and do not wish to overwrite. How should this be handled if this is your situation?

Previously, you would have imported TUBs into client 000 instead of your working client, and then used the compare function in SM31 to identify and copy entries, table by table, that exist in client 000 but not your working client.

The procedure with the Sync tool is very similar. In this circumstance, you will execute the Sync tool for client-specific changes in client 000 instead of your working client, and then once again use SM31 to compare and adjust entries to your working client.

NOTE: Recently SAP has stated that it should be possible to run the sync tool directly to your working client without overwriting custom tax entries in client-specific tables. I have not been able to independently confirm this (we haven’t customized in this manner in my organization), but this would represent a relatively significant simplification of the process.

Additional Resources

The official user guide can be found at -> Country Information -> Americas -> United States of America -> Human Capital Management -> Resources -> User guides -> Synchronize Payroll Tax Data User Guide.

The FAQ can be found in Note 2082725.

An ongoing discussion and latest updates are found at Synchronization Tool notes and updates – TaxFactory 10.


Although the Sync tool has been available for a year, it continues to undergo fairly rapid improvement. Therefore, new Notes are likely to continue to be released for some time, and recommended practices with the tool will evolve. As this happens, I will update this blog with the latest recommendations. Also, I invite your comments and experiences, especially with regard to practices for more complex scenarios.

Update History

3/13/2015: Note 2127736 re-released, eliminating activation errors during Note application.

3/17/2015: Note 2128332 released, correcting issues with client-specific transport not correctly updating some tables.

4/1/2015: Notes 2130801, 2135503, and 2149145 released, correcting various issues, including sync problems with BTXFORM, T5UTR, and T5UTX.

4/23/2015: Notes 2155723 and 2160075 released, introducing a new tax type for North Carolina and correcting transport problems with T5UTR and T5UTW.

You must be Logged on to comment or reply to a post.
  • Tremendous help!!

    I have a question, Matt. Would 'SCC4' be the only option to process "Tax Authority Mapping only" in Quality/Production system? I'd like to have all the options before talking to BASIS.

    Thank you always.


    • Hi Euna,


      Yes, the tax authority mapping option only works if you set sync client-specific data to productive run. However, the tool won't let you set a run as productive unless the system is open for changes. In this case, only client-specific changes need to be enabled. Since these changes are typically locked down in QAS and PRD systems, that means using SCC4 to open the system temporarily to run this process.

      However, hopefully you won't need to run it very often, only when new tax authorities are delivered, and even then, you can get away without running it as long as none of the new authorities pertain to you. So, you can probably minimize how often you need to do this.

      If you run the client-specific sync in test mode, it will tell you whether or not there are unmapped tax authorities.

      In my case, I am the Basis team, so it's pretty easy to coordinate with myself.... 😉


      • Thank You Matt for very useful article on Tax Sync.

        In my Dev Configuration client i am running "Process Tax Authority Mappings Only"

        and its now updating BSI. In production mode i got the green message that everything is updated. But in TF i still have missing 195 unmapped Auth.

        Any suggestions?

        • Hi Kumar,

          Did you run both cross-client and client-specific syncs without checking "Process Tax Authority Mappings Only", in productive mode, at least once in your DEV client and get a full successful sync? There are a number of tables for tax authorities that get updated via the sync, and especially the first time you run it, one table (BTXTAXC) is made obsolete and its contents migrated to T5UTZC. You need to have a successful and complete productive sync of both cross-client and client-specific tables before the tax authority mappings will update properly.

          Additionally, if you run the client-specific sync in productive mode, it will also update the tax authority mappings. You only need to check this box if you don't want to run a full sync, but only update the mappings. The mappings are always updated every time you run this sync in productive mode. The checkbox is mainly there for QAS and PRD systems where you may not be running the sync, but rather importing a transport from DEV, yet still need to update the BSI mappings for those systems. For this reason, this checkbox isn't normally checked when running the sync in a DEV system.

          I hope this clears up any confusion. Let me know if this helps.



          • Hi Matt,

            How long does 'Tax Authority Mapping Only' run? I'm processing in QAS system and it seems like taking forever.

            When we import the trasnport, the regulatory bulletin information is not updated in Tax Factory either?



          • Hi Euna,

            For me, the tax authority mappings was quite quick. If it's taking a long time to run, perhaps you have a communication issue between your SAP and BSI systems?

            You are correct, importing the transport does not update the reported bulletin level in your SAP system. Only a sync does that. That doesn't mean that your bulletin level isn't updated, just that the table field where that status is stored doesn't get updated by the transport. You should still see the "Level in BSI Client" data, however, as that isn't related to the transport, but to the data in your BSI system. If you aren't seeing that, then perhaps you have a communication error, again.

            Or did you mean the transport doesn't update your BSI server? You are correct, it doesn't do that. It updates your SAP system. You still must import regulatory (and cyclic) bulletins to your BSI server manually, in DEV, QAS, and PRD.



          • Oh? I hope my BASIS team know they still have to apply TUB in BSI Server.

            It occured to me that processing time has something to do with the bulletin level in BSI Server. I have to get the bulletin level correct and re-test it.

            Thanks a LOT!!!, Matt.

  • Really excellent blog Matt as the combination of the Payroll Sync Tool, Upgrade to BSI 10 + all the issues with reciprocity and courtesy taxation at the state and local level has made this the most challenging period for SAP customers since I have been working with SAP Payroll (17+ years).  Personally I think SAP should have done a lot better and when you look at 15-20 OSS notes this year already on a product released over a year ago it is not up the standards customers have come to expect around SAP Payroll. 

  • Matt, this is a great blog and very well articulated and detailed documentation.

    This is going to be very helpful. Over a period of time this solution would become stable, I anticipate and wish.

    Nevertheless, your efforts to putting this together in a summarized, yet with all the details is really commendable.

    Thanks for sharing with us

    Baburaj S Avanathan

  • Hi Matt,

    Just want to check with you...

    While running the tool in production, I do see this error message: State American Samoa not found in table T005U.

    Please advise on how to correct this.

    Thank you.


    • Thanks, Kary. Yes, SAP just released this Note earlier today and it is in my "to-do" list to update the blog accordingly.

  • Nice blog. Greatly appreciated.

    Just my 2 cents. After running the sync tool, we go to the transport, under each table entries, delete all the entries and enter *. This way we no need to open a PRD system via SCC4. At my client place we are not allowed to make entries in PRD directly due to Audit issue. Hope it helps everyone.

    @Matt, if you are think it will be useful to others, please feel free to update the blog.

    • Hi Raja,

      Thank you!

      And yes, that's right. At the time when I wrote the blog, there were still some issues with transports, which should now all be fixed with the latest Notes (which I have updated the blog to include). However, transports do not change the way that tax authority mappings work, which is a sync back to TaxFactory from your ERP system. The tool requires a "productive" run to run a "tax authority mapping only" sync, and a productive run can only occur in an "open" client. The alternative is to use tools in the TaxFactory client to manually add the missing authority mappings -- there are several options for this, and later I may have a chance to experiment with them and write something up. Either way, however, mapping missing authorities should be an infrequent occurrence, not something that comes along with every regulatory bulletin.



      • Matt,

        I ran the tool with "Process Tax Authorities Mapping" in Productive Run with system open.

        They are still showing up in our BSI Client.

        Any ideas, did I miss anything that needs to be done manually.



        • Hi Jaya,

          So, you are not getting any more syntax errors? Have you gone through all the points in Cassiana's response to you in the other thread (Re: Synchronization Tool notes and updates - TaxFactory 10)? Have you followed precisely every step in my blog above, including the steps in the linked blogs for ensuring a correctly installed TaxFactory system and/or cyclic update?

          Have you confirmed that you ran the tool in your working client (not client 000), and that in TaxFactory you are connecting to the data set to match your working client?


          • Hi Matt

            No more syntax errors. It was because I had to update BSI License on the server.

            We are now on BSI Tax Factory 10.0 Cyclic F and Regulatory Bulletin 48.

            I am working in non-production systems to update BSI Regulatory Bulletins 49 and 50.

            Please see the following screenshot for the list of SAP Notes implemented.

            I believe some notes are saying "Cannot be implemented" because the changes are already present.

            I ran it in Regular Client and not 000.

            BSI Notes.JPG

            BSI Notes.JPG
          • That's right, from your list it appears that you are on HRSP 79, and that would be why most of your Notes "cannot be implemented." That's perfectly normal. Note 2082725 is an FAQ, with nothing to actually implement, but important to be familiar with. 2139409 (The system does not have the required TUB installed), not in your list, is another like that, no actual corrections, but good to be familiar with. You are missing Note 2128332 (BSI: Sync Payroll Tax Data does not save new client-specific data in transport) in your list, and this one does have important corrections. It is also a prerequisite for 2160075, which you do list as implemented, so I'm not sure how you could have missed this one and still put in 2160075. Probably you have implemented it and it's just not on your list. You might want to double-check that.

            So, it's probably not anything to do with missing Notes at this point. When you run the tool, do you get the General Message "No missing tax authority mappings found?" What happens if you run it for 'productive run' for client-specific changes and do not check the checkbox?

          • Hi Matt,

            I see 2128332 in the Transport, it probably got pulled in with 2160075. I will update my list.

            I am getting the following when I run the tool.Tax Mappings.JPG

            Tax Mappings.JPG
          • Ok, that would indicate that the tool is finding missing mappings in BSI and wants to create them. This is a test run, however. You can set "cross-client tables" to "do not run", assuming they are all sync'd, as they are not required for authority mapping. Set "client-specific" tables to productive, check the "process tax authority mappings only" box, and run the tool.

          • I have exactly same issue. its not updating BSI side. I rememer when i did a production run in the output i saw the green button on top and it has mentioned that records were updated. but they didnt. So not i also have these 195 missing Auh. sitting there in yellow.


          • Aman and Jaya,

            It is beginning to look like maybe there is a new bug, perhaps introduced with one of the new Notes. When I last updated the mapping authorities in my system, it was before the latest Notes were released, and it worked just fine. I would suggest that you mention this on the Synchronization Tool notes and updates - TaxFactory 10 thread, and/or open up an official Incident with SAP Support. It would be good to know if others are having the same problem.

  • Matt,

    I read your blog and it cleared up some questions I had but I am still a little confused.  I am running thesynchtool in our client 000 and I am able to add a cross client transport, but when I try to add a client specific transport, I get an error that the client is local only.  Do I need to run this toolinour other Dev Client 010 which is where we do all our configuration changes?  I see where you say to run it inproductivemode and then create your transports?  You're notsupposeto create the transports when you run it the first time? 


    Margaret Walter

    • Hi Margaret,

      You will normally run the tool in your dev client (010), not client 000. There are some exceptions to this, mostly around whether you are trying to protect customized entries in the tax tables. If you don't have custom entries, then there is no need to do anything in client 000 -- do it all in your dev client. If you do have custom entries, then the latest information is that the tool will respect those and not overwrite them when you sync. I haven't personally tried this, however, as we do not have custom entries in my organization. For a while, the advice was to run the sync in client 000, then use SM30 or SM31 "table compare" to adjust the client-specific tables in your dev client so that it would include all the sync'd entries placed in 000.

      Either way, once you have your dev client looking the way you want it to, this is the client you will use to create your transports.



  • Matt,

    Thanks for the blog!! I have to say that it helped a lot in executing the new tool.

    Per the new process, BSI TF is updated first with the Bulletin and then the tool is executed in SAP configuration client to create the transports. I just wanted to ask if it matters what goes first in Quality & Production systems. Is it required that BSI TF should be updated first with the Bulletin and then only the transports should be moved or transports can be moved first and then the Bulletin applied in BSI TF?



    • Hi Mitesh,


      For the QAS and PRD systems, it doesn't really matter whether you import the transports before or after applying the bulletins to their respective BSI servers. As a matter of protocol, I like to update the BSI systems first, but as long as you don't actually try to run a payroll in the respective systems while they are out of sync, it shouldn't matter.



  • Wonderful blog. The information you have given is invaluable and is helping us with our implementation. I do have a few questions though, so if they've been asked before, please forgive me.

    We had implemented TF 9.0.L1 TUB 162 throughout our SAP landscapes as listed below. We are implementing TF 10.0.F1 with TUB 45 already implemented and adding TUBs 46-49.

    Our SAP landscape -- SAPTEC -> SAPBOX; prod landscape - SAPDEV -> SAPTST -> SAPPRD

    Our environment -- BSI 10.0.f1, TUB 049; SAPTEC - TUB 45, client 020

      We have applied all of the Sync Tool notes up thru 2160075, version 2; and manually cascaded tables T5UTA, T5UTB, T5UTR, T5UTW, T5UTD, and T5UTZ, per note 2139049 version 1, from client 000 to client 020. We have 2 customized entries in table T5UTR for Pennsylvania. We successfully ran the Sync Tool for cross-client and client-specific data in a production mode for TUBs 46-49. We did NOT lose our customized entries in table T5UTR.

    For our SAPBOX environment, I have done everything listed for SAPTEC, EXCEPT for moving the Sync Tool cross-client and client-specific transports up to SAPBOX and running the Sync Tool there.

    So my questions:

    1. Since we only have 2 customizing entries in table T5UTR, do we need to update client 000 in SAPTEC and use that transport in addition to the client 020 transport that we already have from the Sync Tool?

    2. OR can I or do I need to manually update the client-specific tables in client 000 and move the transport up separately (with the help of my BASIS guy)? I ask this one because in TUBs 48 and 49 there are Tax Type 11 (FUTA) date changes for states that we have associates in. The compare of the table T5UTD shows the date changes in client 020 but not client 000.

    3. TUB 47 adds a new tax authority KYAW (Ryland Heights, KY), which changes the sort sequence in table T5UTZ. Since we have no customizing entries in this table, should I manually update these changes in client 000 for this table?

    4. If we have to run the Sync Tool in client 000, does that mean I have to load all of the OSS notes to that client? We have the RFC set up, but client 000 is giving us the following error message: Program error in remote function call of RFC_HRUS_TF_VERSION_10. We don't usually go into client 000 specifically to make changes, so I have NO specific authorizations for my user id in that environment. When we've had SAR files before, they've been imported for client 000 and I transport them in STMS in client 020 of the SAP system I'm on. Both the BASIS guy and I are a little confused on this one.

    We are in the process of moving all of this into our production landscape this week, starting with SAPDEV.

    Hopefully my questions make sense. Thanks in advance for any help you can give us.

    Beth Matthews

    • Hi Beth, and thanks! I've got to run at the moment, so I'll come back to address your questions more fully tomorrow, but wanted to let you know I did see them. Or, if someone else jumps in, that's great.

    • Hi Beth,

      It sounds as though you've already successfully confirmed that the sync tool works fine in client 020 without overriding your custom entries, which is the intended design. You do not need to do anything in client 000.

      The Notes, by the way, are client-independent. The reason for the error you get is probably due to customizing that is present in client 020, but not client 000. This is not a problem, as client 020 is the one you are going to use.

      So, run the sync tool in SAPTEC client 020, and create your transports from there. One thing to double-check is that the client-specific transport also contains your custom entries from T5UTR -- it should, but double-check.

      Then, in SAPBOX, client 020(?), apply all the same Notes as in SAPTEC (you probably already did this), then import the transports you created. Do not run the sync tool here, except if you find missing tax authority mappings. If that is the case, then you may need to temporarily open client 020 in SAPBOX for changes (though you won't change anything), then run a client-specific sync in productive mode with the "update tax authority mappings only" checkbox checked (turn cross-client sync off). Afterwards, close the client for changes again.

      Other than this purpose, however, you will typically only run the sync tool in your sandbox or DEV clients. In all downstream clients you will just import the transports you create in DEV after running the sync.

      Do you have separate BSI systems for each of these SAP systems, or are they all sharing the same BSI system?



      • Hi Matt,

        This works GREAT!. I did check table T5UTR for our customizing entries in the client-specific transport from TEC to BOX (client 020) and they are there.

        I moved the cross-client and client-specific transports from TEC to BOX and ran the Sync Tool in Test Mode. I found a date delimitation in table T5UTD for tax authority MD0P tax type 01 in BOX that was not caught in the table cascading. So I went ahead and ran the Sync Tool in Productive Mode to update the tax authority. This generated the 3 messages when choosing the Display Version button in Regulatory Bulletin Information. I'm fine with this BOX since this was just a testing-the-upgrade process run.

        We are starting the upgrading process in our DEV->TST->PRD environment this afternoon. I loaded the BSI 10 configuration and Sync Tool OSS notes to DEV and TST yesterday. I will cascade the client-specific tables this afternoon and tomorrow.

        We have 2 BSI environments: BSI_BOX links to TEC, DEV, and TST; BSI_PRD links to BOX and PRD. Both BSI environments have clients 020 and DEFAULT. We did not create a client 000 in BSI. Please let us know if we need to do this.

        Thanks so much for your help.

        Beth Matthews

        • Glad to hear! No, you don't need a 000 data set in BSI unless you plan to run syncs in 000 in SAP, which there is no need to do. So you're good with a 020 data set.

  • Hi Matt

    We are in the process of upgrading from:

    Level in BSI Client:    BSI TaxFactory 10.0.e.1 | Cyclic E1 | Regulatory 047 | Tax Locator N/A

    To 10.f.1 TUBs 52

    The upgrade was applied but when I run the Synch tool in production the Display verison stayed with the old version.

    What am I missing? Thanks

    • Hi Juanita,

      That's not really enough information to know what might be the issue. You might want to consider asking this as a question in a discussion thread so that more people can chime in with their suggestions. However, I would ask whether the sync was working fine before the upgrade, or whether this is the first time you're running the sync. Also, usually the sync isn't run directly in production, but in your development system, and then you use transports to move the changes up to QAS and PRD.



  • Juanita Perry,

    Make sure you first upgrade to the TF10f Client application and then apply the f cyclic bulletin (TFU10f.nrq file).  We had this same issue and I contacted BSI.



  • Hello, Everyone!

    This is my very first post in this forum, but I have been reading and following the blogs for a couple of months now and able to implement this new Synchronize Payroll Tax Data tool, so thank you all very much for that.

    With that, I do have a question. Since SAP no longer publishes TUBs (beyond 51) and a corresponding SAP Note, where can I find the BSI Code to SAP Code mapping for new tax authorities below?

    Tax Authority                                   Title                   County ID     BSI Code          Tax Code

    BULASKI-SOMERSET                      COUNTY                                       210394           ???

    WESTERN RIDGE JEDD                  TOWNSHIP     HAMILTON     391986            ???

    MERCY HOSPITALS WEST JEDD  TOWNSHIP     HAMILTON     391987            ???

    HOLLAND SPFLD TWP JEDD         TOWNSHIP     LUCAS               391989           ???



    • Hi Duong,

      Thank you. I'm glad you found the blogs useful, and welcome to SCN!

      New tax authorities are recorded in tables T5UTZ and the mapping to the BSI code is in table T5UTZC. These tables should be updated automatically when you run the sync tool.

      Occasionally new tax types are introduced, and these require an SAP Note to be applied. SAP will announce such Notes at For instance, the most recent of these is Note 2155723 which introduced tax type 93 for North Carolina, and which goes hand-in-hand with TUB 50. So, you'll need to monitor this area periodically to see if there are any new Notes.



  • Hi Matt,

    I came across  2176339 - BSI: Allow execution of Sync. Tax Data tool without effective dates. Have you installed this one? Any repercussions that you might know of?

    • Hi Kary,

      This is a very new Note, just recently announced. It's on my radar for our next round of tax updates, but no, I haven't yet had a chance to try it for myself. When I do, I will update the blog. Good question!

      • Matt,

        In our BSI and SAP DEV system, I was at BSI 10, tub 57 with zero unmapped authorities

        I then applied tub/bulletin 58 in BSI DEV

        I followed the instructions for the SYNC report in SAP DEV, got my config/dev transports after running the sync report.

        I checked BSI, and previously(before applying tub58), I was at "0" unmapped tax authorities.  But now it says "1 unmapped"...again in BSI dev connected to my SAP DEV.

        So I did your instructions for handling that.  But my DEV BSI system still says "1 unmapped".  Funny thing is that I took my tub58 config/dev transports, and after updating to tub58 in my BSI QA systems, I applied the transports in SAP QA.

        Then, saw the "1 unmapped" in BSI QA.  But when I followed your procedure in SAP QA, SYNC log said "System creates mapping between tax authorities 00210395 and KYAZ in BSI".

        the BSI QA now correctly states "0 unmapped".

        I've run the report several times in SAP DEV, but the SYNC log shows "no unmapped authorities"....but BSI DEV still thinks "1 unmapped"....crap!

        I have no idea why!  What do you think my next steps should be?

          • Nick, I can't count how many times this sort of thing has bitten me, and probably everyone. 😉 Sorry for not responding sooner; I was out on vacation the past couple weeks.

  • Hi Matt,

    Thanks a lot for your excellent blog, which helps me out to do initial analysis.

    We are in process of applying the TUBs 52 – 57 using the synchronize payroll data tool in BSI Tax Factory 10.g, while performing this we came across an issue with the effective dates. But have hit a road block which is preventing us from moving ahead and impacting the project timelines.

    In TUB 54 there is change for the various tax authorities as shown below with the highlight for the effective dates : 


    When we executed the sync tool in test mode enter the start date as all the effective dates mentioned in the TUB document.


    Issue 1: We cross checked the output of the table changes and found that EVEN the changes which are “immediately” are delimited with effective date 10/14/2014 for ALL the tax authorities. This date seems to be the lowest date in the list of effective dates entered.


    Issue 2 : There are entries that are getting deleted as shown in the screen shot below.

    This may cause problem with the retro for our business. How is SAP suggesting addressing this issue of retro for employees impacted


    please suggest...



    • Hi Siraj,

      My apologies about the delayed response -- I have been out on vacation for a couple weeks.

      I believe both issues you mention are actually the same issue, which is that the tool is delimiting your entries with the 10/14/2014 date. My suggestion would be to ensure you have installed both of the following Notes:

      • 2182954 (BSI: dictionary objects for SAP note 2176339)
      • 2176339 (BSI: Allow execution of Sync. Tax Data tool without effective dates)

      For good measure, have a look at Note 2082725 (BSI: Synchronize Payroll Tax Data - FAQ) and make sure you've applied all the Notes listed there.

      After applying the Notes, follow the instructions from 2176339 carefully. The key point here is to not use effective dates anymore. However, the Note states you will want to run it "wide open" like this, probably a few times until there are no more changes created, before you apply a new TUB. It sounds like it may be too late for you to do that, so you might just have to roll with it with the new TUB in place already.

      If that doesn't fix the problem, then I would try posting a question in the discussion forum at Synchronization Tool notes and updates - TaxFactory 10. There are a number of people there, including the SAP engineers who work on this tool, who may have encountered the issue before.



      • Hi Matt

        I have another issue related to HCM support packs update, that impacted BSI Sync Tool functionality.

        SAP Incident Number: 634194

        We are currently in the process of applying support packs to our SAP HCM System.

        And we have a problem with one of the BSI Notes.

        SAP Note - 2064814 - BSI: Hide Transport pushbuttorn of the Synchornize Payroll Tax Data.

        The Sync Tool stopped working for me as SPAU flagged this as an obsolete note and removed it from the system.

        PLEASE ADIVSE, this is now impacting our timeline of the update.

        Here is what I am getting:

        Snyc Tool Error.png

        Snyc Tool Error.png
        • Hi Jayakiran,

          I cannot look at your customer support incident, as I am not an SAP employee; I'm a customer, like you. However, I suspect that your short dump is caused by not having Note 2196332 (BSI: Errors when installing Sync. Tax Data tool related notes) in your system. Your error isn't identical to that described in the Note, but it's similar.

          Additionally, just as I advised Siraj, have a look at Note 2082725 (BSI: Synchronize Payroll Tax Data - FAQ) and ensure you have applied all the Notes in the list. You might need to ensure that any you have previously applied are up-to-date with the latest versions available.

          It's also possible that you may have Notes applied in an incorrect sequence. Mostly they should be applied in numerical order, but there are some notable exceptions (I call out most of them for the Notes I list in this blog; others are mentioned in the text of the Notes themselves, or handled via the identified prerequisites to correction instructions).



  • Hi Matt,

    Could you please help me with my issue?

    We ran the TUBS update 51 to 59 and when we create a transport, it shows a + sign for each table in SE10 but we could not open that node.

    On moving the transport to Q system, it does not update new tax authorities.

    There were 9 new tax authorities added in DEV but they are not moved to Q.

    Could you please suggest me what did I do wrong?



    • Hi Srini,

      First, are you referring to the cross-client or client-specific transport? The cross-client transport captures all entries in tables BTXAUTH, BTXFORM, and T5UTX, so in SE10 it will show "*" for the table contents. The client-specific transport, when expanding the table contents in SE10, should show the individual row keys.

      There were some known errors with capturing data in the client-specific transport in the past, which were corrected with Notes. Have you ensured that you have correctly applied every Note listed in the FAQ Note (2082725)? Several of the listed Notes specifically address issues with transporting tax authorities, and others address issues with some of the other tables.

      With regard to tax authorities, when you say they are not moved to Q, do you mean in your SAP system, or do you mean in your BSI system? The transports do not update the tax authority mappings in BSI; you must run the Sync Tool in QAS (and again in PRD) to update the mappings in BSI with the data from SAP. I address the procedure for this in the blog above.

      Also, be aware that tax authority mappings are no longer maintained in BTXTAXC, as they used to be. The first time you ran the tool, it will have migrated all entries into T5UTZC, and from then on new mappings will be contained in that table.

      Have a look through all the Notes from the blog above, and additionally in the FAQ Note, and make double-sure that you've applied them (or have a higher HRSP level that includes them), and then ensure you are following the process for creating the transports and the mappings correctly. Note that there is one change to the process from what I wrote above, in that a more recent Note removed the need to enter effective dates when running the sync; as long as you've applied all the Notes, you should leave the effective dates blank.

      If the above doesn't help you, then I recommend that you add the question as a comment to the thread at Synchronization Tool notes and updates - TaxFactory 10, which a great many people are following, or start a new thread as a question in the SAP ERP HCM Payroll North America space (i.e., this space where the blog and the discussion reside).



  • Hi Matt,

    Is there a way to avoid the SCC4 option in Assurance and Production? Our company would like to transfer the whole Tubs update process from IT to Business and for Production is quite sensible for an end user to get access for opening the System
    in order to run the Synchronization tool.

    Thanks in advance for your advice,


    • Hi Ionut,

      For the moment, this is the easiest way, though I anticipate this process to become more streamlined in the future (and indeed, may already be through Notes I have not yet applied myself -- I'll find out over the next few weeks as I update my system and apply year-end tax updates).

      The only way I know of to bypass the SCC4 option is to not process the mappings automatically, but instead to make them as manual edits in your BSI system. I don't advise this, as it's more labor-intensive and more error-prone, but it is the old way of handling this.

      Bear in mind, however, that this need to update tax authority mappings should be infrequent. You'll need to do it at least once, up front, of course, but afterwards it should be a relatively rare occurrence.



  • Hello,

    We just applied support packs SAPKE6482 to SAPKE60492 and we are now receiving a ‘messages’  when I run payroll (RPCALCU0).   The messages are:

    BSI Level:  BSI TaxFactory 10.0.h – Regulatory 061

    SAP client-specific level:  Not synchronized

    SAP cross-client level:  Not synchronized

    Mismatch between SAP client-specific level and BSI level

    Mismatch between SAP cross-client level and BSI level

    We have never run program RPUPAYUS_SYNC_TAX_DATA in Quality or Production since we only run this program in Development and create 2 transports which we then move up through to production.

    Until we loaded this round of support packs we did not received this message.

    It appears that all taxes are calculating correctly.


    Is there a note or a configuration step I need to do to stop this from happening OR do I need to run RPUPAYUS_SYNC_TAX_DATA in every client?

    Thank you!


    • Mike,

      We at Eastman Chemical is going thru the exact same issue and the solution this is to run the Synchronize Tool transaction (HRPAYUS_SYNC_TAX_DT) from DEV for both Cross and Client Specific and transport it to PRD. We tested in our QA system and it works.



      • Thank you,

        I read the note and did as you suggested.  I ran the RPUPAYUS_SYNC_TAX_DATA in our development client and it immediately took away the issues plus I am now getting the proper tables being updated (V_T77PAYUS_SYNXC & V_T77PAYUS_SYNTX).

        Thank you for your help!


    • Mike,

      SAP with this note

      2193769 - BSI: Regulatory Bulletin level validation in Payroll

      has introduced validation of SAP and BSI Tub level. it does not matter if you run tax sync client in each D/Q/P or you transport them. What matters is BSI and SAP both have Tax updates i.e. Tax Sync Transport  and Reg. Bulletin on BSI Side.

      If you run your Tax Sync Tool in test mode in Q or P, what do you see in the box

      "Regulatrory Bulletin Information"

      If you see somethng like this

      Level in BSI Client:     BSI TaxFactory 10.0.h | Cyclic H | Regulatory 061 | Tax Locator N/A

      Cross-client Tables:     BSI TaxFactory 10.0.h | Cyclic H | Regulatory 061 | Tax Locator N/A

      Client-specific Tables:  BSI TaxFactory 10.0.h | Cyclic H | Regulatory 061 | Tax Locator N/A

      and still getting message in schema

      BSI Level:  BSI TaxFactory 10.0.h – Regulatory 061

      SAP client-specific level:  Not synchronized

      SAP cross-client level:  Not synchronized

      Mismatch between SAP client-specific level and BSI level

      Mismatch between SAP cross-client level and BSI level

      then i guess you are missing some SAP notes.

      • Thanks Aman for including the note that I forgot to attached.

        For those that applying SP up to SAPKE60492, you will need to apply this

        Note: 2215294 - TAX: Incorrect number of exemptions in BSI interface.

        The issue/side effect was caused by

        Note: 2211140 - TAX: Incorrect data sent in BSI interface

        I just applied this to our system and it worked.

  • Hello,

    We just applied support packs SAPKE6482 to SAPKE60492 and we are now receiving a ‘messages’  when I run payroll (RPCALCU0).   The messages are:

    BSI Level:  BSI TaxFactory 10.0.h – Regulatory 061

    SAP client-specific level:  Not synchronized

    SAP cross-client level:  Not synchronized

    Mismatch between SAP client-specific level and BSI level

    Mismatch between SAP cross-client level and BSI level

    We have never run program RPUPAYUS_SYNC_TAX_DATA in Quality or Production since we only run this program in Development and create 2 transports which we then move up through to production.

    Until we loaded this round of support packs we did not received this message.


    It appears that all taxes are calculating correctly.


    Is there a note or a configuration step I need to do to stop this from happening OR do I need to run RPUPAYUS_SYNC_TAX_DATA in every client?

    Thank you!


    • Mike, this is an exact repeat of your question from six days ago on this same thread, and four days ago Aman Kumar and Duang Hoang, between them, answered your question. Others have also asked the question on the BSI TacFactory 10.0 thread and the Synchronization Tool notes and updates thread, and there the same answer was given by others. Please have a look at Note 2193769.

      • Matt, sorry, I am new to using this tool and I submitted my entry twice.  I did as Duong suggested and my system is now working as expected.

        Thank you everyone for all of your help!


  • Hi Matt,

    Happy New Year and all the best for 2016!!

    I have a question regarding an issue that we have after aplying the HRSP 92.

    When trying to apply the Tubs 67 through 69, it's seems that the entries for table T5UTD are not being transported in our QAS System ( please find below a printscreen after running the tool in QAS in Test mode). Is there any SAP Note that we were missed? The note 2128332 it's not available for our System as we are at SP92 level.

    Thanks in advance for your help,



    • Hi Ionut,

      So far, the only Note for the Sync Tool that I have applied that is newer than HRSP 92 is 2228365, which is about T5UTX. I have not, however, gone as far as you with TUBs -- I am still on Cyclic I and Regulatory Bulletin 63. I have not observed any problems in my system with transporting entries for T5UTD from DEV to QAS after running the sync in DEV.

      Have you confirmed that when you run the sync in DEV, you are running it:

      • With effective dates left blank.
      • In your working DEV client; not client 000.

      Then, likewise, when you create your client-specific transport in DEV, you are creating it from the working client, not client 000, right? And importing this transport to the working client in QAS?



      • Hi Matt,

        Thanks for your quick response, I'm doing the above steps you mentioned. I will wait for the next Tubs to see if the issue still persists.



  • Hi Matt,


    Post Applying Tax Factory Cyclic 'P, and TUBS 108-110,we're not able to generate the Client specific transports. When we ran the Sync tool in production mode, system is taking forever and not updating the tax tables. This is going to a end less loop.

    Please advise.




    • Hi Madhav,


      I’m afraid I can’t address your question directly. We are still on Cyclic N and TUB 097 (no income tax in our state, so not very frequent need for updates), and we are not having any issues. What Cyclic did you update from? Was it one of the early ones that still used the old RFC wrapper (i.e., pre-Cyclic J)? If so, see if helps you out. Though, that’s been a while, so this probably isn’t your issue.


      Have you searched in Notes, and in Questions here on SCN? If so, and you haven’t found anything, then I would suggest raising this as its own Question in the HCM Payroll USA tag, and/or as a Customer Incident directly with SAP against the PY-US-BSI component.