Skip to Content

So, you’ve installed or upgraded your TaxFactory 10 system and all has been going well, but now the time has come for your first Cyclic update. Perhaps this is driven by a functional requirement, perhaps it’s a mandatory prerequisite for a regulatory update (aka TUB), or perhaps you’re preparing to configure the Payroll Tax Data Synchronization Tool. Whatever the reason, eventually you will have to do this.

Overall, the process is very similar to how it was done in TaxFactory 9, so if you’re already experienced with the procedure in that release, this will look very familiar. The biggest change is the client, of course, as the TF10 client has a fundamentally different infrastructure from prior releases. If you haven’t previously applied a Cyclic update, rest assured, it’s quite easy, but the documentation on the procedure can be a little confusing.

In this blog I’ll demonstrate my own experience updating TF10 from Cyclic D to Cyclic F. TaxFactory is installed on a Windows 2012 R2 / SQL Server 2012 system, with a separate server for each environment (i.e., there are three servers, DEV, QAS, and PRD, but on each one only a TaxFactory ‘PRD’ environment exists).

Cyclic Update

Release, Cyclic, and Regulatory Bulletins

First, a quick definition of the difference between the three types of “bulletins” (updates) that BSI provides.

Release Bulletins

Release Bulletins are major upgrades of the TaxFactory software, i.e. from TaxFactory 9.0 to TaxFactory 10.0.

Cyclic Bulletins

Cyclic Bulletins are minor updates of the software, similar to applying a support package stack to an SAP system. Per BSI’s definition, Cyclic Bulletins “sometimes affect tax calculations, but may involve only interface upgrades or re-coding of program functions.” Cyclic Bulletins are often optional, but occasionally they are mandatory or a prerequisite for a particular Regulatory Bulletin. The reverse is sometimes also true, that a particular Regulatory Bulletin may be a prerequisite for a particular Cyclic Bulletin. Cyclic Bulletins are typically released a few times per year, and they are cumulative, meaning that you only need apply the most recent one.

Regulatory Bulletins

Regulatory Bulletins, sometimes also known as Tax Update Bulletins or TUBs, “supply changes to the taxes and tax formulas covered in your BSI TaxFactory System. These bulletins are in the form of data that is used to update BSI’s tax file or database.” Regulatory Bulletins are released relatively frequently, and they may include changes to Federal, State, and Local taxes. Not every Regulatory Bulletin includes Federal changes, so if a particular bulletin does not apply to your State or Locality, then you can wait to apply it. However, Regulatory Bulletins are incremental, not cumulative, so when you do apply them, it is necessary to apply all the intervening ones between your current and desired bulletin levels as well.

SAP Notes

Occasionally it may be necessary to apply an SAP Note to your ABAP system prior to applying a Cyclic update to your TaxFactory system. This is not always the case, but before applying any Cyclic it is prudent to check. Such Notes are usually announced by SAP at http://service.sap.com/hrusa. If in doubt, you can also search for recent Notes in application area PY-US-BSI.

If you are updating from Cyclic D or lower to Cyclic E or higher, you must first apply Note 2097432. The ABAP changes in the Note are backwards-compatible with earlier Cyclics, so you can apply it to your system in advance (for instance, if you update to a Support Pack that includes the Note, such as HRSP 82 for ERP 6.04, you are still OK if you haven’t yet applied a higher Cyclic to your TaxFactory system).

In our example, we are updating from Cyclic D to Cyclic F, and our ABAP system is still on HRSP 79, so we do apply the Note via SNOTE (incidentally, as part of a group of Notes for the Payroll Tax Data Sync Tool, but that is a topic for a different blog). It is straight-forward.

Obtain the Cyclic

Each new Cyclic requires a new installation password. When BSI releases a Cyclic, they email the password to the support contact for each customer organization. Make sure you have this password handy. If you didn’t receive the email, or have misplaced it, send an email to support@bsi.com and request it.

  1. Logon to http://www.mybsi.com/connect.
  2. Select Product Maintenance.
  3. Select product BSI TaxFactory.
  4. Under Maintenance, select Cyclic Bulletins.
  5. Select the most recent cyclic bulletin (i.e. BSI TaxFactory 10.0f Cyclic Bulletin)

Client Package

Under Client Package, select TF10 Client Package for Windows. This will download TF10ClientInstall.zip. Save it to a temporary location and extract the files to a new folder, i.e. TF10fClient. Copy the folder to a temporary location on your TaxFactory server.

Server Package

Under Downloads, locate your server OS and database release, paying careful attention to the OS Bits (64 or 32) and Chipset (Itanium or otherwise). In our example, we are using Windows Server 2012 R2 and SQL Server 2012, 64-bit, so we select the line for OS Version = 2008 Thru 2012 R2 and Database Version = 2005 Thru 2014 64-bit. When you’ve located the correct line, click the link for Download File. This will download a self-extracting executable file with a name specific to your OS/DBMS. In our example, the file is wx64sql64tf100f_s.exe. Execute the file to extract the contents. You will need to supply the installation password to complete the extraction. Save the extracted files to a new folder, i.e. TF10fServer. Copy the folder, or at least the server subfolder within it, to a temporary location on your TaxFactory server.

Cyclic Data File

Under Documents, select Cyclic Data File. This will download TFU10f.nrq, or similar as appropriate for the Cyclic you have chosen. Please note that in late February 2015 BSI re-issued the data file for Cyclic 10.0.f, so if you downloaded the Cyclic prior to then, you may need to re-download (and reapply) the Cyclic Data File. Only the data file is affected by this, not the client or server packages.

Update the Client

Logon to the console of your TaxFactory server, open the TF10fClient folder you copied up, and execute TF10ClientInstall.exe. On the first screen, confirm that this is for the correct Cyclic, and click Next.

On the next screen, enter the cyclic installation password you received from BSI, click Next, then confirm the license agreement by clicking I Agree.

The next screen is the Configuration Analyzer. The analyzer should detect your currently installed environment(s) and Cyclic level. Click Next.

The next screen is WEB Server Configuration. The installer should automatically detect the correct location for your Apache Tomcat web server software. If not, use the Browse button to correct it. Click Next.

Next is XML Server Configuration. On this screen, the installer suggests a new base folder for the XML Server. It will default to C:\Program Files, so if you have previously installed your TaxFactory environment elsewhere, you will need to change this appropriately. In my case, I originally installed to E:\BSI\TF10d, so I made a new folder at E:\BSI\TF10f. Note that the choice of 32-bit or 64-bit is greyed out, as you cannot change this from your original installation option now. Click Next.

The next screen is Environments Install / Update Configuration. Here you have three options. Select the checkbox for Install / Review / Uninstall / Upgrade Standard (Production through Test 3) Environments and click Next.

On the next screen, select the checkbox for Replace existing TF10D Client with TF10F Client (or as appropriate for your start and end Cyclics). Click Next.

You will get a popup confirming your database authentication method (i.e., Windows Authentication) and the result of a connection test using the service user for your TF10DXMLPRD (or similar) service, and asking you to enter the login information for this user. Click OK. The next screen asks for the password for the service user. Enter it and click Next.

The next screen will bring you back to the Environment Configuration, except instead of Production it will now be Development. If you only have one environment (i.e. PRD) on the server, or if you don’t wish to update the other environments, leave all checkboxes unchecked (or check Review), and click Next. In my case, I use three separate servers for Development, Quality Assurance, and Production, so in TaxFactory terminology each one has only one PRD environment installed. Your configuration may be different.

You will likewise pass through the configuration option screen for QA, Test 1, Test 2, and Test 3. Click Next on each one.

Finally, you will be given the option to Update current Cyclic for PRD Environment(s) with TF10f Cyclic. Select this checkbox and click FINISH.

The next screen will show progress, stopping and starting services, removing obsolete XML folders, and extracting files. If you examine the detail log, you may notice some errors about services failing to start, but this doesn’t appear to matter, as afterwards you can confirm that they have in fact started (i.e., Apache Tomcat 7.0 Tomcat7, Apache Tomcat7 – PRD, and TF10FXMLPRD). When it’s finished, click Close.

Update the Server

The “Server” component is much easier to update, and indeed this process has not changed from TaxFactory 9. It is a simple matter of swapping the older executables with the new ones. These are the interface executables called by SAP via the RFC Destination.

First, identify the location of the executables. If you are not certain, you can look at the program location in your BSI10-US-TAX RFC Destination via transaction SM59 on your ABAP server. If you installed TaxFactory 10 following the directions in my earlier blog, this location will be something like E:\BSI\TaxFactory\server.

Make a backup copy of this folder, then locate the temporary TF10fServer folder you extracted earlier. Drill into the server subfolder and copy all the files within to the working server folder, i.e. E:\BSI\TaxFactory\server, allowing them to overwrite the older files in the destination folder.

Update the Cyclic Data File

Back on your own workstation, launch your web browser and open the client administration page. Note that the page URL is cyclic-specific, so if you saved it as a favorite, you may need to edit the favorite. It will be something similar to http://<taxfactory_host>:8091/eTF10f/PRD. Logon as your TaxFactory administrator user (i.e. TF10).

Connect to the appropriate Data Set (i.e., matching your ABAP client number), and jump to System Tools.

Under Maintenance Tools, select Manual Update.

Browse to the TFU10f.nrq file you downloaded earlier and then click Process.

The update will take approximately a minute. When it is done, check the Maintenance Output log for any error messages, and click View Summary to confirm that Cyclic Update F shows up in the log (cyclic updates appear after regulatory updates, so you may need to scroll to near the bottom of the log). After examining the logs, click Exit. Back on the System Tools page, under Maintenance Tools and “Currently installed:”, confirm that the appropriate Cyclic is displayed.

Test the Result

Logon to your ABAP system and run transaction HRPAYUS_SYNC_TAX_DT (even if you aren’t yet using the Payroll Tax Data Sync Tool). At the bottom of the screen, under Regulatory Bulletin Information, click Display Version and confirm that the correct cyclic data is returned.

You do not need to actually synchronize anything at this time, so this is just a test. If you get a short dump, or the output looks incorrect, you may need to apply Note 2125327 (BSI: Sync Payroll Tax Data generates a short dump when BSI version is not specified) and/or ensure you have correctly configured Payroll: USA -> Tax -> SAP/BSI Interface -> Specify BSI TaxFactory version for customizing settings in the IMG.

Via SA38, run report RPUBTCU0 to confirm correct execution of the TaxFactory system and connection to it from SAP. If you do not get the expected result, consult Note 1910127 (FAQ: TaxFactory 10.0 Inst./Upgrade Troubleshooting). Also, have a look at BSI TaxFactory 10 Installation for SQL Server – Part 4 for more information.

Conclusion

Thanks for following along, and I hope with the above guidance your Cyclic updates go smoothly.

To report this post you need to login first.

34 Comments

You must be Logged on to comment or reply to a post.

  1. Vince Laurent

    The steps you show I do not encounter.  There never was an option or screen about XML, it went fromScreenshot_1.jpg

    to

    Screenshot_2.jpg

    to

    Screenshot_3.jpg

    to an error I can’t find anything about

     

    Screenshot_4.jpg

     

    Ideas?

    (0) 
    1. Matt Fraser Post author

      Hi Vince,

       

      The latest cyclic updates have changed some of the screens a bit, though overall the process is pretty much the same.

       

      Cyclic K, however, has apparently changed things considerably compared to earlier cyclics. I haven’t written about this myself, as I haven’t yet applied Cyclic K myself, but there is a great deal of discussion about it at BSI Tax Factory 10.0 (go to the comments at the end of the thread, on the last few pages). In particular, find this comment (Re: BSI Tax Factory 10.0) about the need to ensure that your ODBC connection, Tomcat, and BSI client are all on the same bit-width. It doesn’t matter so much whether you choose 32-bit or 64-bit, but all must be the same. Some have resolved this issue by choosing the 32-bit ODBC connection and client, but others resolved it by reinstalling Tomcat in a 64-bit version, which would be my preference. The bottom line is ensuring everything is the same throughout.

       

      Cheers,

      Matt

      (0) 
  2. Philip Seman

    One item I noticed after applying the version L update, is that the connection would throw a system failure, which is about as generic an error you can get with this software. I have found out by running the following from a command prompt, tf10serverdebug -a bsi10-us-tax -g <servername> -x 3300 -o c:\bsi10\error.txt. This should generate a file to review if there are issues, or in my case, it actually indicated I was missing the following file: libsapucum.dll

     

    I copied that file to the BSI folder, and all is working once again, at least from an SAP perspective.

     

    Ironically, the file returns an error, normally it stays running until I kill the command.

     

    The file returns the following:

    3 – SAP SE, Walldorf – Business API for BSI TaxFactory 10

     

     

    3 – Installing function RFC_PAYROLL_TAX_CALC_US

    3 – Installing function RFC_HRUS_TF_VERSION

    3 – Installing function RFC_HR_TAXLOCATOR_US

    4 – Installing function RFC_HRUS_RET_COMPANY

    4 – Installing function RFC_HRUS_RET_EMPLOYEE_GROUP

    4 – Installing function RFC_HRUS_RET_CUST_OVERRIDE

    4 – Installing function RFC_HRUS_SAVE_TAX_MAPPING

    4 – Installing function RFC_HRUS_RET_TAX_TYPE

    4 – Installing function RFC_HRUS_RET_MAP_TAX_CODES

    4 – Installing function RFC_HRUS_RET_FIL_STAT_INFO

    4 – Installing function RFC_HRUS_RET_CUSTOM_TAXAB

    4 – Installing function RFC_HRUS_RET_SUPP_INFO_TAX

    4 – Installing function RFC_HRUS_RET_DEF_UNEMPL_TAX

    4 – Installing function RFC_HRUS_RET_MAP_PAY_CODES

    4 – Installing function RFC_HRUS_MAR_STAT_FORMULA

    4 – Installing function RFC_HRUS_RET_VALID_FORMULA

    4 – Installing function RFC_HRUS_RET_EXP_RATES

    4 – Installing function RFC_HRUS_RET_CUSTOM_TAX

    4 – Installing function RFC_HRUS_RET_TAX_AUTHORITY

    4 – Installing function RFC_HRUS_RET_TAX

    4 – Installing function RFC_HRUS_RET_MAP_TAX_TYPES

    4 – Installing function RFC_HRUS_RET_TAXABILITY

    4 – Installing function RFC_HRUS_RET_WAGE_LIMITS

    4 – Installing function RFC_HRUS_RET_MAP_TCO_COUNTY

    4818 – Unable to start the server: RFC_COMMUNICATION_FAILURE –

    LOCATION    CPIC (TCP/IP) on local host <servername> with Unicode

    ERROR       hostname ‘-a’ unknown

    TIME        Fri Jun 10 07:50:12 2016

    RELEASE     742

    COMPONENT   NI (network interface)

    VERSION     40

    RC          -2

    MODULE      D:/depot/bas/742_REL/src/base/ni/ninti.c

    LINE        896

    DETAIL      NiPGetHostByName: ‘-a’ not found

    SYSTEM CALL getaddrinfo

    COUNTER     1

     

    My guess is that this is because my current system in NON-Unicode.

    (0) 
    1. Matt Fraser Post author

      Interesting, thanks for this detail, Philip. We haven’t updated to Cyclic L ourselves yet, but we only just very recently converted our systems to Unicode. I haven’t come across any documentation that specifically states that TaxFactory, as of a certain Cyclic, will only work with Unicode systems.

       

      If I understand you correctly, your system is working correctly (after adding libsapucum.dll), but the debug throws an error?

      (0) 
      1. Philip Seman

        That is correct, I just added that file to the location of where I was running the BSI executable from.

         

        If you are unicode now, my guess is that it would detect that file already from the kernel location, I was just able to copy it from the DAA location, as that is a unicode install to begin with.

         

        I run the following from the command line:

        tf10serverdebug -a bsi10-us-tax -g <servername> -x 3300 -o c:\bsi10\error.txt

         

        The error on the debug shows at the end:


        3 – Installing function RFC_HRUS_RET_MAP_TCO_COUNTY

        4842 – Unable to start the server: RFC_COMMUNICATION_FAILURE –

        LOCATION    CPIC (TCP/IP) on local host <servername> with Unicode

        ERROR       hostname ‘-a’ unknown

        TIME        Mon Jun 13 11:11:23 2016

        RELEASE     742

        COMPONENT   NI (network interface)

        VERSION     40

        RC          -2

        MODULE      D:/depot/bas/742_REL/src/base/ni/ninti.c

        LINE        896

        DETAIL      NiPGetHostByName: ‘-a’ not found

        SYSTEM CALL getaddrinfo

        COUNTER     1

         

        But the payroll test program works just fine.

        (0) 
        1. Matt Fraser Post author

          libsapucum.dll is part of the “new” NetWeaver RFC Library, which TaxFactory requires as of Cyclic J. Were you updating to L from a Cyclic lower than J?  See BSI TaxFactory Cyclic J and the New RFC Wrapper for more information about this. I can confirm that Cyclic J and the new RFC library work just fine with non-Unicode backends, as we hadn’t converted to Unicode yet when we updated to that Cyclic.

          (0) 
      2. Philip Seman

        Matt, you mentioned you converted to Unicode, did the schema for TF10 migrate as well? I am finding out that this did not occur on our conversion, and BSI stated that they are not unicode compliant.

         

        May I ask what you did if this didn’t occur to get BSI working again?

        (0) 
        1. Matt Fraser Post author

          The schema for TF10? Ah, you must have installed it into your SAP database? We did not do that (and I strongly recommend against it). We have TaxFactory installed on a dedicated server — three servers, actually, one each for DEV, QAS, and PRD.

           

          The only thing we had to do to make TaxFactory work with our system after converting to Unicode was to check the “Unicode” communication type on the Unicode tab in the BSI10-US-TAX RFC connection in SM59. That’s all. We didn’t do anything at all with TaxFactory itself.

          (0) 
          1. Philip Seman

            Interesting, I have been working with BSI I think since version 5, and it was installed on the SAP database to begin with, so I have always left it that way. I wasn’t aware a way to have this separate from the actual SAP database installation for configuration.

            (0) 
            1. Matt Fraser Post author

              I was just going to say that at the top of this blog I linked to my earlier blog in which I describe how to install a standalone BSI system, and I discovered to my horror that I had a broken link. Not sure how it happened, but apparently the embedded publication date in the URL to the blog changed by one day since I originally published it (timezone effect?). Anyway, I’ve now corrected the link in this blog, so it works again. Or you can just follow it here: BSI TaxFactory 10 Installation/Upgrade for SQL Server.

              (0) 
              1. Philip Seman

                Thanks,

                 

                Once slight issue, I am on DB2 on Z/OS 

                 

                I’ll hopefully get this working. My DBA was able to export the schema from the old and import to the new. The license installed, and the software for tomcat connected, now the problem is he test program won’t run. The dreaded System Failure on testing, the RFC works just fine though.

                (0) 
                1. Matt Fraser Post author

                  Ah yes. I’m sure you’re familiar with the troubleshooting Note, 1910127. Paragraph 6 in the Solutions section deals with this error message and the usual culprits.

                  (0) 
  3. Raman Ext SAP Support

    Hi Matt,

     

    I have updated cyclic bulletin from 10.0.h to 10.0.m and i followed all the steps for cyclic updates. But the version for cyclic update in BSI portal still showing older one H.

     

    Followed below steps:

    -> Install client application

    -> coped server files

    -> updated cyclic data in BSi portal.

     

    Is something I am missing from the above steps for 10.0.m?

    anyone facing the same kind of issue?

     

    Kindly help.

    (0) 
    1. Matt Fraser Post author

      Hi Raman,

       

      Between cyclics H and M there was a significant change in the structure used for reporting cyclic versions back to the backend system. Have a look at my blog BSI TaxFactory Cyclic J and the New RFC Wrapper, and also Note 2242290 (BSI: Changes for Cyclic J). Also, don’t forget that your backend system won’t report the correct Cyclic version until you run a sync in your DEV system, and then create cross-client and client-specific transports in the sync tool to move to your QAS and PRD systems.

       

      Cheers,

      Matt

      (0) 
  4. Kuruvila PUNNOOSE

    Hello Matt,

    The cover page of Cyclic bulletin 10.0 O shows that Cyclic Bulletin O is released on 17/02/2017 and last date to update in our BSI environment is 17-03-2017.

    But, I am not able to download the packages as the last package available to download is 10.0 N.
    There is no package for 10.0.O in download path for Cyclic Bulletin

    Am i missing something? Please help

     

    (0) 
    1. Matt Fraser Post author

      Hi Kuruvila,

       

      I’m not sure where you’re seeing this Cyclic O cover page. I subscribe to the email announcements from BSI about updates, and I haven’t received any such announcement. Looking at http://www.mybsi.com/connect, I still show Cyclic N as the most recent available.

       

      Cheers,
      Matt

      (0) 
  5. Kuruvila PUNNOOSE

    Hello Matt,

     

    Thanks for your reply

    I initially came to know regarding potential date of release from  Product release and cyclic schedule tab (BSI Portal–>  Product Maintenace –>Choose product “Tax-Factory” –>Product release and cyclic schedule)which was on 17-02-2017 in that article.

    Later when i was surfing The last tab LIBRARIES there i found 2 PDF TFU10O Cyclicdata cover page and TF10o cyclic bulletin cover page which was released a week ago stating 17-03-2017 as last date for applying in cyclic bulletin O in our bsi environment.

     

    Please verify and let me know.

     

    (0) 
    1. Matt Fraser Post author

      Those were expected dates for release of the new Cyclic, but obviously it was not actually released. You can ignore that. Also, with regard to “mandatory” dates for application, you can take that with a grain of salt as well, and here’s why.

       

      If you need to apply new Regulatory Bulletins (aka TUBs), and there is a new “mandatory” Cyclic Bulletin that has come out, then you should definitely apply the latest (available) Cyclic before applying the latest Regulatory bulletins. However, until you are ready to apply those new Regulatory bulletins, there’s not much point in applying the latest Cyclic, as your system isn’t going to suddenly stop working just because you didn’t do so. “Mandatory” just means it’s a prerequisite (or dependency) for some later Regulatory bulletin (it’s sometimes, but not always, clear which precise Regulatory bulletin this is).

       

      Do you always need to apply Regulatory bulletins as soon as they come out? Probably not. It depends on your state and locality. If you are in Philadelphia, or Ohio, then yeah, you probably have a full-time job just staying on top of the constant tax changes that those local governments put out.

       

      On the other hand, if you’re in a state with no income tax, like Washington or Texas, then Regulatory changes that actually impact you are likely to be few and far between. That means that you really only need to apply Regulatory bulletins if you see that one has been released with Federal changes, or State or Local changes that are actually for your State or Local governing authority (city, county, school board, whatever). In a no-income-tax state, that might mean you only apply Regulatory bulletins once a year, at the end of the year, to be up-to-date with year-end tax reporting.

       

      If your organization has multi-state employees or locations, then you are probably a bit busier with staying on top of Regulatory bulletins. But if you’re only in one state, and that state doesn’t change tax laws all the time, then perhaps not so much.

       

      So, bottom line, Cyclic N remains the latest available Cyclic as I write this. Cyclic O was meant to come out in mid-February, according to that announcement, but for whatever reason it didn’t happen, so you don’t need to worry about it. Forget the “mandatory” date — that just means you’ll need it for any Regulatory bulletins released after that date, but until you actually go to apply those bulletins, you don’t need the Cyclic.

      (0) 
  6. Szabolcs Ferenczi

    Hello Matt,

     

     

    Im facing an issue after the Cyclic O update.

    -> Updated BSI client with new Cyclic version “O”

    -> updated the server files

    -> updated cyclic data file in BSI portal.

    After the Cyclic upgrade I have SYNCRONIZED in production client in the DEV system: HRPAYUS_SYNC_TAX_DT,but the BSI  Taxfactory level is not showing the correct version:

     

     

    After this I have also updated the Regullatory Bulletin level from 73 until  102, but after the SYNC it’s the same issue in SAP.

    The BSI client shows the correct versions, but in HRPAYUS_SYNC_TAX_DT the versions does not SYNC correctly, even if they show no errorr:

     

    Please let me know if you have any recommendation or suggestion.

     

    thank you in advance

     

     

     

     

     

    (0) 
    1. Matt Fraser Post author

      Hi Szabolcs,

      Have you ensured that you’ve applied Note 2242290 in your system, or a higher Support Pack that includes it? And, done the necessary work around the “New RFC Wrapper“? If you were already on Cyclic M, that implies that both of these things have already been done, but it’s possible they weren’t, so worth double-checking.

      On a side-note, we’re still on Cyclic N in my shop, so I can’t speak to any problems that might have been introduced with Cyclic O.

      Cheers,
      Matt

      (0) 
  7. Guntaka Lakshmana

    On BSI 10 Client (Cyclic n) I am having an issue where the data set(s) are missing & the “Jump to” drop down does not work. I tested the ODBC connection works fine. This issue happens only on one of the systems in the landscape. Clients URL for other systems works fine.

    I am able to login using tf10 user and other users, but see nothing and cannot go to system tools. I thought it could be permissions issue, but cannot fix it since I cannot get to system tools.

    Did any one seen this issue? please help

    Thanks

     

     

    (0) 
  8. Kuruvila PUNNOOSE

    Hello Matt,

    Currently we are on Cyclic N and Regulatory Bulletin 102. The below Question was raised to us:

    Currently I login to DEV and upload the new annual UI rates into BSI TF and then end date the active record, then create a new record for the current year and rate. This is time consuming. Is there a way to upload the data rather than manually touch the records?

    Please let me know if you have any recommendation or suggestion.

    Thank you

     

    (0) 
    1. Matt Fraser Post author

      Hi Kuruvila,

      I’m not sure I can be of much help with this question. My specialty is Basis, and therefore keeping the TaxFactory system working and up-to-date with Cyclic and Regulatory Bulletins and so forth. These annual rate changes aren’t delivered via Regulatory Bulletin? Or do you mean table data changes in your backend ABAP system? For instance, I know that in our shop our Business Analyst responsible for Payroll uploads rate changes for industrial insurance every year into our backend system.

      I suspect this question would be better handled, as with Guntaka’s above, by posting it as a new question in the “HCM Payroll USA” tag, rather than as a comment to this blog.

      Cheers,
      Matt

      (0) 
  9. Atul Jain

    Hello Matt,

    We recently did our SAP QAS Refresh from SAP PRD along with TF10 BSI Schema but post refresh RFC is working fine but test Program RPUBTCU0 is giving System Failure with below details :

    Fatal Error: Unable to Connect to BSI Dataset

    Error String 4020 : “There is no valid License Installed for Host:”

    SYSTEM_FAILURE has been sent to Backend

    We checked license and its already installed. Do we need to re-generate licesne and re-apply. ?

     

    (0) 
    1. Matt Fraser Post author

      Atul,

      Because you installed your TaxFactory database as a schema within your SAP ECC database — something I do not recommend, though it is supported — that means you overwrote it in QAS when you refreshed that database from PRD. The license installed for TaxFactory is host-specific, and is based upon the server hostname you supplied when you created the license file on BSI’s website. Thus, although the license is installed in your QAS system, it’s wrong, as it’s the license for your PRD server, and the machine hostnames don’t match.

      You’ll need to re-apply the license you created for QAS.

      For more information, have a look at the Install License paragraph of my TaxFactory installation blog series: https://blogs.sap.com/2014/10/09/bsi-taxfactory-10-installation-for-sql-server-part-3/#jive_content_id_Install_License.

      As a side note, this is not really the best forum for asking questions of this nature, as it isn’t directly related to the subject of this blog post. It probably would be better to raise this as a new question — after searching to see if it has already been asked and answered — in the HCM Payroll USA tag.

      Cheers,
      Matt

      (0) 
    1. Matt Fraser Post author

      Hi Sen,

      Thanks for the compliment. I’m not aware of any Notes specific to Cyclic O or Bulletin 105. SAP generally only publishes a Note about a Cyclic if there is something specific and unusual that you must do in your backend system to support it. Cyclic J was an example of that, because it required switching to a new RFC wrapper. When this happens, it usually gets announced at http://service.sap.com/hrusa, but you can also always search in the Launchpad, restricting the component to PY-US-BSI. As a side note, we have not yet implemented Cyclic O, so I can’t speak to whether it has any particular problems associated with it. I’m not aware of any. We don’t generally implement a Cyclic, even a “mandatory” one, until we also have to implement a Regulatory Bulletin that is applicable to us, which isn’t that frequent (once or twice a year, usually, and at year-end as a minimum).

      Cheers,
      Matt

      (1) 

Leave a Reply