Skip to Content
Product Information

TaxFactory 11.0

Hello community,

BSI TaxFactory and TaxFactory SaaS released version 11.0 is available.

After our partner BSI has extended the maintenance for their offering/Product BSI TaxFactory 10.0 up to April 30,2021. SAP has also decided to provide support for BSI TaxFactory 10.0 up to April 30, 2021.

Regardless of the extended support period for BSI TaxFactory 10, SAP strongly recommends not to postpone your upgrade to BSI TaxFactory 11 and still plan to complete the upgrade during this year.

As announced on BSI website JAVA/Tomcat 32bits is not supported anymore by BSI after TaxFactory 11.0 cyclic C and TaxFactory 10.0 cyclic X.3. For any query about this, please contact BSI Support.

Upgrade 
your payroll system to the corresponding BSI TaxFactory 11.0 product way before the decommissioning of BSI TaxFactory 10.0 support.
There are NO options to extend the support for TaxFactory 10.0 after the decommissioning date.

If you have any questions about BSI TaxFactory 11.0, you can post it here. I´m going to keep this updated with tips, best practices, and, SAP notes.

Important SAP notes:

2760305 – BSI: Tax Factory 11.0 – Main Note

As a prerequisite, you must apply the following SAP Notes:

2760918– BSI: TaxFactory 11.0 – DDIC Changes

2763228 – BSI: TaxFactory 11.0 – Function Modules Changes

2770832 – BSI: TaxFactory 11.0 – General Technical Changes

2780204 – BSI: TaxFactory 11.0 – Changes required for TaxFactory SaaS

2868617 – BSI: Tax Profile Factory SaaS correction

2780716 – BSI: TaxFactory 11.0 – BSI Tools

2790902 – BSI: TaxFactory 11.0 – Payroll Driver Changes

2844516 – BSI: TaxFactory 10.0 – Additional Configuration Options While in Transition to BSI TaxFactory 11.0

2852878 – BSI: Technical Correction changes

2854888 – BSI: TaxFactory 11.0 – Configuration Option

2860747 – BSI: Tax Factory 11.0 – system not able to run TaxFactory SaaS

2864644 – BSI: Tax data synchronization error during transition from TaxFactory 10.0 to TaxFactory 11.0

2855926 – BSI: internat error US_UPDATE_TXIT_FROM_TAXES in BSI Tax Calculation

2865938 – BSI: Tax Factory 11.0 – system continues using TaxFactory 10.0 after upgrade – SaaS

2876817 – V_BTXRATE & V_BTXOVFR: not saving Experience Rate and incorrect number of digits for Tax Type

2853869 – TAX: Additional withholding not considered and Regular wages classified as Supplemental

2878074 –  BSI: Update to BTXRATE reader class usage

2904103 –  BSI: TaxFactory 11.0 – Missing Changes in Structures for Release 600

2915653 – BSI: Unemployment Override not Being Considered on TaxFactory

3008339 – TAX: Community Safety Payroll Taxes for Eugene

3013127 – BSI: Enablement of Tax Type 106 for Concurrent Employment

Important:

Before applying SAP note 2915653, you must apply note 2844646 – Ignore the local class definition, implementation, definition deffered, definition load , definition local friends changes this notes contains a fix to SNOTE transaction and without this you will get an error.

2919499 – TAX: Experience Rates Calculated Incorrectly in Tax Result Log

2920181 – TAX: TaxFactory Version Source in USVERS

2934419 – TAX: TaxLocator not proposing Tax Areas in TaxFactory 11

2944465 – TAX: Full refund of Unemployment tax when using BTXRATE override

Further irformation about the installation can be found on:

2844034 – TaxFactory 11.0 – On-Premise Installation

2843977 – BSI: TaxFactory 11.0 – SaaS Installation

2948446 – BSI: installation instructions for TaxLocator 11.0.

2977383 – BSI: Changes in Sync Tool Tax due to incorrect State

2988140 – IT0208: Performance issue when using Tax Locator

Frequently Asked Questions – FAQ

 

1) Which are the options for transition from TaxFactory 10.0 to TaxFactory 11.0?

  • In transaction SU3, define the user parameter BSI_TF_VERSION with value 11.
  • In transaction PE03, configure the BSI Tax Factory Version (10BSI) feature with value 11.
  • In transaction SM30, open table view Customer values for configuration options (V_T5F99K2) and set the value of constant BSI TAX FACTORY: CUSTOMIZING SWITCH (BSITF) to 11.Once your company switches to TaxFactory 11.0, you may no longer use TaxFactory 10.0, nor may you switch back to it later.

2) Which is the start date to be used in table V_T5F99K2 and constant BSITF?

The start date should be 01.01.1800, once you decide to upgrade the system to TaxFactory 11.0, as the system should use the version 11.0 for all the tax calculation, even in retroactive scenarios, where TaxFactory 10.0 where used.

 

3) When there is a negative value the system is not calculating taxes after the upgrade to TaxFactory 11.0, what is the cause?

Check if the Reverse Tax Engine is turned ON in your system, table V_T5F99K2, constant ADTMD, further information can be found on the KBA 2984562 – Reverse Tax Engine TaxFactory 11.0

4) Filing status/Marital status is missing or not updated in T5UTK. What should I do?

As T5UTK has delivery class C, you can update this table manually. To find the filling status that should be update in T5UTK you can go to MYBSI Portal (https://mybsiconnect.force.com/CustomLogin) with your credentials:

· Select Product Maintenance > TaxFactory ->  11.0
· Under Maintenance select Cyclic Bulletins -> BSI TaxFactory 11.0 Cyclic Bulletin
-> Bulletin Data nformation

 

5) There is a syntax error in LPBSUD01 after implementing SAP note 2915653, what is the cause and what are the steps fix it?

This is because SAP note 2844646 is not implemented in your system, or was applied after note 2915653.

To solve this SAP note 2844646 must be applied.

Detailed steps:

1) Perform the de-implementation of SAP note 2915653
2) Apply note 2844646
3) Retrieve the version of objects LPBSUD01 -> To do it go to transaction SE38 select LPBSUD01 -> Utilitiles -> version -> version management -> select version prior the note implementation
4) Re-apply note 2915653

 

6) Is it possible to extend the validity date of TaxFactory 10.0?

There is no extension to TaxFactory 10.0. Support for BSI TaxFactory 10.0 will be decommissioned on April 30, 2021.

7) How Local Reciprocity is working in BSI Tax Factory 11.0?
Detailed information is available on the KBA 2973907 BSI TaxFactory Local Reciprocity Process (Basic Local Reciprocity and Advanced Local Reciprocity)

 

8) I don´t see the WF parameter in BSI script, why?

The parameter WF: 0,0 is not being sent in all scenarios in the BSI script, as BSI considers it as WF: 0,0 if there isn´t this parameter in the BSI script. Parameter WF: 1,0 is always being sent in case the employee has IT0210 in 2020 onwards.


9) Parameter WF is not in the correct line in BSI interface in TaxFactory 11.0?

There is a change in TaxFactory 11.0 cyclic B the parameter WF should be placed in other line in BSI script. This change has been delivered in the W-4 notes for States, after you apply the notes this parameter will be send in the line BSI expects to do the calculation for FED taxes.

The change in the parameter has been delivered in SAP notes:
2895426 – Prerequisite objects for SAP Note 2878657
2878657 – 2020 State Withholding Tax Calculation – Based on the State (or State-equivalent) Withholding Certificate (SAP_HR) – Phase I

10) After the Support Package the system is calculating higher taxes when employee has IT0161, why?

After SAP notes 2888094 TAX: Lock-in letters override for W-4 exempt and 2880846 TAX: Lock-in letters not overriding New W-4 is now considering the values of IT0161 and now the system is calculating more tax, which is expected.

Refer to KBA for further details 2984188– Tax calculation for an employee with both IT0161 and IT0210.

Regards,

Graziela

344 Comments
You must be Logged on to comment or reply to a post.
  • Hello Graziela,

    I am getting the following error after applying all the pre-req notes mentioned in main note 2760305. I believe someone else on this forum has already mentioned this error and I am not sure if the error was ever resolved. We are currently on 608-72 (ECC on-premise).

    In include "RPC_PAYUS_BSI_BLR_CLIENT_CHECK ", in line 27 of program
    "RPCALCU0 ", the following syntax errors
    have occurred:
    Type "LCL_BAS_LOC_RECIP_VERS_CHECKER" is unknown.

    Now I have only applied notes mentioned in 2760305.

    I am going to apply notes 2852878, 2864644, 2855926, 2876817, 2853869, 2878074, 2915653, 2919499, 2920181 and 2944465.

    You mentioned above that I have to apply note 2844646 before applying note 2915653 which I will do. Someone followed this step and still got an error. Then you mentioned backing out and de-implementing 2844516.

     

    So what is the correct steps to follow to correct this error. Should I de-implement 2844516 first before applying 2844646 and 2915653? Please advise.

    Thank you.

    Thomas

     

  • Hi Team,

    We just upgraded to BSI 11.0, when we run payroll in quality i get an message that "Basis local reciprocity is activated in tax factory client" & i see /TR1 wage type in RT with a value 1.00. Screenshot from SAP quality is attached below for references.

    Now we moved our transport to PROD. when i run payroll i dont see ""Basis local reciprocity is activated in tax factory client" & /TR1 wage type is not there in RT anymore. Will this cause issue with reciprocity between states "Incorrect state calculation" when we have maintained custom nexus indicator in BSI 11.0. Screenshot from PROD is attached below for references.

     

  • Hi TEam,

     

    During my BSI 11.0 testing i kept FEATURE 10BSI to 10.0 and through user profile (SU3 TCODE) i maintained  "BSI_TF_VERSION" as 10.0/11.0 and i was doing my testing and comparing taxes between both BSI 10.0/11.0.... in both instance ie in both BSI 10.0 and BSI 11.0, system bought /TR1 wage type with a value 1.00 in employee RT.

    Once when we go live with BSI 11.0 in PROD. i changed the value of FEATURE "10BSI" to 11.0.

    now when i was doing some simulation payroll in production client which is connected to BSI 11.0... system stopped creating wage type /TR1 with a value 1.00 for all employees in RT.

     

    Is this a issue? because i have maintained custom nexus indicator for states in BSI for some particular company code???? will this cause incorrect payroll tax calculation.... need your input.

      • Hi Graziela,

         

        Yes it related to my last question and thanks a ton for releasing a KBA with all information.

        My question is with BSI 11.0, I don't see /TR1 wage type in RT, will this impact payroll taxes when we run payroll??? do we have any significance to this wage type? will my reciprocity between taxes wont work according to custom nexus data configured in BSI 11.0????

         

        Need your input.

        • Hello Hemanth,

          Wage type /TR1 is to identify the employees that were affected by the Basic Local Reciprocity.
          The Basic Local Reciprocity should not be used anymore.

          This note also contains some information that can help you:

          2685179 - BSI: Changes in TaxFactory Local Reciprocity process - FAQ

          Kind regards,

          Graziela

           

          • Hi Team

            We have successfully updated to BSI 11.0... we have employee who reside in Hamilton ohio (OH81) and work in OHA6 (mason)... this employee has unemployment in ohio...

             

            in BSI 10.0 we have taxes calculated for both hamilton and mason... After BSI 11.0 we have taxes calculated only for MAson (OHA6) and no hamilton...

             

            Can you please identify and kindly let me know where the issue is...

          • Hello Hemanth ,

            We have the same kind of issue.

            We have upgraded our system to BSI 11 and while processing Payroll for Dec 2020 we could see that the system is not calculating correctly for the employees having 2 or more City Taxes as it is not calculating the Tax for the Second Tax and even refunding the same when there is a Retro.

            Could you please help us if you find any solution for this.

            Thanks,

            Satish.

          • Hi Satish / Hemanth:

            Did you ever receive a response on this question - I am not seeing any answer to the problem where there is a local tax withheld in v10 that drops off in v11.  We have a few employees also who have this problem when we ran a regression test comparing v10 results to v11 for the same employees and keeping everything else constant.  Specifically MI05, OH59 and IN0E when other Locals are also existing for the employee.  Are there any new OSS Notes in this area or other solution?  Thanks. Kathie

          • Hi Kathie,

            Please turn on the Courtesy Withholding for these locals on view V_T5UX9_COUWH. Make sure to use the Advanced Local Reciprocity. This should make the tax to compute.

            In case the issue persists, I would recommend you to reach out BSI to check with them what they are expecting on the script to calculate the wished tax.

            You may refer to the following documentation:
            2667916 - BSI: Changes in TaxFactory Local Reciprocity process
            2685179 - BSI: Changes in TaxFactory Local Reciprocity process - FAQ
            2973907 - BSI TaxFactory Local Reciprocity Process (Basic Local Reciprocity and Advanced Local Reciprocity)

            Regards,
            Carlos

          • Carlos,

            When using TF11, will both tables V_T5UTX9_COUWH and V_T5UTRC be applicable for Advanced Local Reciprocity?  If so, would identical entries be needed in each table?

            The notes and FAQ don't clearly explain what parts serve what purpose and if any are obsolete once TF11 is live.

            Thank you,

            Stanette

             

  • Hi Graziela,

    SAP note 2917910 (We implemented this as part of BSI 11.0) has bought new wage types "/3K0 to /3K4" and "/3KA till /3KI", "/4K0 to /4K4" and "/4KA till /4KI", "/6K0 to /6K4" and "/6KA till /6KI" , "/7K0 to /7K4" and "/7KA till /7KI".

    Now when we run payroll recon report for current year with wage type application "TURK". i get error message "You must include the corresponding /4XX wage type" and recon report stops executing. After debugging i found that /4K0 and /4K1 wage type processing class 72 (employee or employer tax wage type) is missing a value as currently its blank in our development and quality. Screenshot of /4K0 is given below.

     

    Now when i maintain processing class 72 as "2" employer wage type, report run fine without any issues.

    QUESTION:

    Is it ok to maintain /4K0 wage type value as 2 for processing class 72... Please confirm as other wage type like /4K1, /4K2...etc has processing class 72 maintained and they dont error out.

    Need your input.

    /
      • Hello Graziela,

        We have applied note 2951336 (we're currently on 608-85) and we're still getting this error "You must include the corresponding /4XX wage type" when we run our payroll reconciliation report.

        We've checked with out Basis admin and they've confirmed that this note is applied. We are running the report with wage type appliction C941 and CCW2.

        I appreciate your response to this question.

        Thank you.

        Thomas

         

         

         

  • Hi Graziela,

     

    After upgrading to BSI TF11 in the BSI portal end, we need to run the HRPAYUS_SYNC_TAX_DT this transaction? we just want to know how below details will get updated?

    sap%20image

     

    Can you please help me on this one.

     

    Regards,

    Suryasai K

     

     

    /
    sap%20image
    • Hello Suryasai,

      Did you switch to BSI TaxFactory 11?

      1) Which are the options for transition from TaxFactory 10.0 to TaxFactory 11.0?

      • In transaction SU3, define the user parameter BSI_TF_VERSION with value 11.
      • In transaction PE03, configure the BSI Tax Factory Version (10BSI) feature with value 11.
      • In transaction SM30, open table view Customer values for configuration options (V_T5F99K2) and set the value of constant BSI TAX FACTORY: CUSTOMIZING SWITCH (BSITF) to 11.Once your company switches to TaxFactory 11.0, you may no longer use TaxFactory 10.0, nor may you switch back to it later.

      KInd regards,
      Graziela

      • Hi Graziela,

         

        I have upgraded my system to BSI TF11 in the BSI portal end, and need to apply additional Tubs to get the system current.  When I went to run the HRPAYUS_SYNC_TAX_DT transaction only the Level in BSI Client is reflecting TF 11.0.  The Cross-Client and Client-specific tables are still reporting TF10.0 levels.

        I have all the entries updated that you mentioned for switching to BSI TF11.0.  Can you tell me why the snyc tool is reflecting TF10.0 for those 2 options and what I need to do to move forward?

         

        thank you,

        Juli T.

         

         

        • Hello Juli,

          After you run the Sync tool in Productive mode tables V_T77PAYUS_SYNTX and V_T77PAYUS_SYNXC will be update with the data for TaxFactory 11.0.

          Did you already run the Sync tool after the upgrade to TF11?

          Kind regards,
          Graziela

          • No, I have not ran in Productive mode yet as we are in the process of upgrading.  I will run now as I wanted to make sure that would be the reason that I'm still seeing the TF10.0 in these 2 tables.  BSI has been upgraded and does show the TF11.0 level as expected.

            thanks,

            Juli

             

          • Hi Juli,

            The reason is because these tables are just updated with the value that is in BSI after you run the Sync Tool.

            Hope this clarifies.

            Kind regards,
            Graziela

        • Hi Graziela,

          We cutover to V11 this morning.  I have the 10BSI feature showing only 11 and the RFC connection to V10 is disabled/stopped.

          We transport changes for TUBS and Cyclic rather than execute the sync tool in each system.  I have checked V_T77PAYUS_SYNTX and V_T77PAYUS_SYNXC show V11 bulletin 45.

          When I run a simulation I no longer see the BSI Client, Cross Client, Client Specific messages.  This is only in my production system.

          Is there an expectation the Sync tool is run live in each system?

           

          Thanks,

          Stanette

  • when we creating webservice for SAAS not creating logical port.no error message. log showing green and created. but in soamanager not showing the logical port 0

    HR and CUS 608 patch 79

    • Hello Ajai,

      Have you performed the IMG steps as note 2843977 assists?

      To enable the integration of the SAP SuccessFactors Employee Central Payroll U.S. solution with BSI TaxFactory 11.0 SaaS, you must perform the following migration steps under Customizing for Payroll US -> Tax -> BSI TaxFactory SaaS Integration:

        1. Re-enter your credentials for datasets in the customizing activity Store the BSI TaxFactory SaaS Credentials. You may need to delete the existing credentials first. Choose Update to confirm.
        2. Please contact SAP Hosting to apply the necessary Support Package. These files are used by SuccessFactors Employee Central Payroll services to create the logical ports for consuming web services for BSI TaxFactory SaaS and to notify BSI eFormsFactory about changes.
        3. In the customizing activity Logical Ports: BSI taxFactory SaaS and communicating with BSI eFormsFactory, under BSI TaxFactory SaaS, choose BSI TaxFactory 11. Give the user name and password for the new Web service for BSI TaxFactory 11.0 SaaS for each system - development, quality assurance, and the production system.
        4. Edit the Specify Version of BSI TaxFactory for Customizing activity and, under Value, change the entry to V11. Give the appropriate start and end dates.

      Best Regards,
      Carlos

      • Hello Carlos,

         

        Thanks for reply

        Yes, we follow that note to create web services. Log showing created succesfully. but when we see in soamanager logical port is 0. Not creating the proxy. and logical port

        Patch level is 608  Patch 79

         

        Thanks,

        Ajai

  • We are getting the same message reported in an earlier post.  'Error while connecting to BSI TaxFactory:  Program error in remote function call of RFC_HRUS_TF_VERSION_10.

    • Feature 10BSI is set to 11.
    • Table V_T5F99K2 is set to version 11 from 1/1/1800 - 12/31/9999.
    • I have also set parameter BSI_TF_VERSION in SU3 to 11 and that has had no impact.

    I have looked through everything else and cannot see what is causing the issue.

    Any guidance you can share would be very helpful.

    Thanks,

    Kim

    • Hello Kim,

      It seems that there is some missing point regarding the configuration of the RFC connection on your system.
      Please review this configuration as per SAP Note 2844034 - TaxFactory 11.0 - On-Premise Installation.

      Kind Regards,
      Carlos

  • Hello Graziela,

    We are testing BSI TF11 in DEV system. We have to add two Employee Groups in BSI TF11, we are able to add the entry and save it. Once we save it we are not seeing the newly added Employee Groups in MYBSI.

    We checked the IMG config and we are seeing the employee groups in the SAP table.

     

    Thanks

    Kumar

    • Hello Kumar,

      Please reach out BSI to check on your issue.
      If you are able to see the update on SAP table, it seems that the configurations per our side are all ok.

      Best Regards,
      Carlos

  • Due to some issues, we are looking into BSI SaaS and SAP on-premise solution. As part of this evaluation, we would like to hear from other sap clients, who have this unusual setup. Please contact me if you or someone you know would be willing to share your experience ( such as performance or else..)

    Thank you;

    Judit

     

  • Hi Team,

    This is regarding California Disability limit

     

    which has Increased from the maximum wage base FROM $118,371 TO $122,909.(Attached the RB009)

     

    the /741 is capped at 104,378.00.  It should be capping at 122,909 but it is stopping early.

    The /441 for the tax should also be capping at 1229.09 but it capped early at 939.40

     

    It is using an old 2015 rate.

     

     

     

     

     

    T5UTX:

     

     

    BTXRATE:

     

     

    Can you please advise on this?

     

    Thanks

    SatyaPrakki

  • Hello Graziela

    We have upgraded to the BSI V11 in the Non-Production system and awaiting to move this to Production. While testing it is noticed that California Disability limit is incorrectly captured by the system. in Non-Prod environment. Which is capping at 104,378.00 a quite a older rate belongs to 2015. However it should be capped at 122909/- and calculated at 10%

    In V_T5UTX view it is seen that tax type 41 limit is 122909/- and percentage at 10%

    In BTXRATE there is NO latest change. can you advise of any fixes to this??

     

    Thanks

    Satya

    • Hello Satya,

      Please create an entry on table BTXRATE with the wished inputs.
      Then, kindly guarantee that the below notes are applied on your environment:

      I) 2877989 – PY-US: Technical changes for future development and corrections
      II) 2878074 – BSI: Update to BTXRATE read
      III) 2919499 - TAX: Experience Rates Calculated Incorrectly in Tax Result Log
      IV) 2876817 – V_BTXRATE & V_BTXOVFR: not saving Experience Rate and incorrect number of digits for Tax Type
      V) 2944465 - TAX: Full refund of Unemployment tax when using BTXRATE override
      VI) 2915653 - BSI: Unemployment Override not Being Considered on TaxFactory 11.0

      Afterwards, please retest the scenario and check the results.
      This should solve the case.

      Best Regards,
      Carlos

          • Hi Team,

            We are too facing the same issue “California Disability limit is incorrectly captured by the system”.

            Though, we have maintained the record in BTXRATE table & BSI, we are still getting the issue for some employees.

            Could you please advise on this.

             

            Thanks,

            Anand

          • Hello Anand,

            Please check the maintenance of this data on SAP and BSI side.
            It should be exactly the same on both sides.

            If that's ok, I might say that you are facing the issue because of the configuration of your datasets.
            Each client on your system should be configured under a different and unique dataset, and the client number and the DataSet ID must be identical.
            If this is not accomplished, you might face some issues just like this one you are reporting.

            Further information about this client/dataset configuration can be found on the following note:
            2844034 - TaxFactory 11.0 - On-Premise Installation

            Best,
            Carlos

          • Hello, we are facing the California Disability issue as well.  Data set is identical and so is the data on SAP & BSI.  Any updates on this issue?  Thank you for your help

          • Hello Ashley,

            As per the updates of the other customers, I might assume that you are maintaining an entry on BTXRATE for this tax, am I right?
            If so, please check KBA 2998362 - BTXRATE entry is not being considered on the payroll calculation.

            Please also make sure that each client on your system is configured to a different and unique dataset.

            Kind Regards,
            Carlos

          • Hey Carlos, there was a very old entry on the btxrate table for CA type type 41.  I have removed this entry from both SAP & BSI and it is still not calculating correctly.  Plus we do have unique datasets.  Are there any updates to the ticket Satya put in?

          • Hi Ashley,

            I had worked on the ticket with Satya and it was identified that 2 client IDs were set to the same dataset, hence that should be the issue on this case.
            As the issue persists for you, please make sure that all entries set on BTXRATE match with BSI Override entries, with the exact same data. Please take a look if more than one entry is valid on SAP/BSI for CA, TT041, and the used Tax Company. This could make the system to combine the rates and compute the tax on an undesired amount.

            Regards,
            Carlos

  • Hi Graziela,

     

    We have upgraded to 11

    Our tables are not getting updated V_T77PAYUS_SYNXC and V_T77PAYUS_SYNTX when we run the tool?

     

    Can you please help us!

     

    Thanks

     

    Sunil

    • Hello Sunil,

      Could you confirm the user that is running the Sync Tool has the required authorization?

      Also, is your system SaaS? If so, make sure you have note 2865938 – BSI: Tax Factory 11.0 – system continues using TaxFactory 10.0 after upgrade – SaaS.

      Regards,
      Graziela

  • Hi Graziela,

     

    The user has full authorization to run the tool. We are not on SaaS but On Premise system SAP ECC system( EHP7 SP14  and HRSPs on F4).

    Regards,

     

    Sunil

     

     

     

  • Hi Graziela,

     

    Thanks for checking and refered to KBA 2550829. We are able to identify the issue. The table entires were incorrect and we adjusted.

    Everything is working as expected.

     

    Thank you once again for helping us.

    Regards,

    Sunil

  • Hi Team

    We have successfully updated to BSI 11.0... we have employee who reside in Hamilton ohio (OH81) and work in OHA6 (mason)... this employee has unemployment in ohio...

     

    in BSI 10.0 we have taxes calculated for both hamilton and mason... After BSI 11.0 we have taxes calculated only for MAson (OHA6) and no hamilton...

     

    Can you please identify and kindly let me know where the issue is...

  • Hi Graziela Dondoni / Team,

     

    We have upgraded our BSI to V11 today in our LIVE clients and to our surprise system is stopped calculating taxes after this upgrade activity. This was never a case in any of our Non-Productive environments. At USTAX function we are seeing all values as ZERO. Can you please help on this priority?? Simultaneously raised OSS 809406/2020

    Thanks

    SatyaPrakki

  • Hi Satya,

    We had the same issue.  I had to do the following.

    1. Log into BSI client and Map all the tax types (Just executed default mapping).
    2. There will also be a few unmapped Authorities.  Complete this mapping as well.
    3. Also, if the BSI client dataset is gone with the upgrade, you will have to restore the dataset from your backup.   (I think this second step was necessitated by some mistake by the Basis person.)

    Regards

    Paddy

  • Hi, I created two datasets in TF 11, when I go to datasets I get the list for dataset id 010 and 037. When I go to connect to dataset I only get  the default listed. How do I get the other two to list on the connect to dataset? Thank you,

    Joe

    • Hello Joe,

      You will need to go to system tools > logins and permissions: click the logon ID and then click link to manage permissions.  On that page, select the data set ID, scroll to the bottom of the page and click to select all and then scroll to bottom again to save.  Repeat this for each logon ID / dataset ID combination.

      Best regards, Anna

          • Hi Anna, one more question (I hope just one more). When you applied to TUBs to TF 11 for the first time (mine is showing none installed). Did you apply all them starting at 1 - 36 (36 is the latest one) individually? I can do that after updating TF 11 with Cyclic 11.0c.

          • Hello Joe,

            The TUB level you are currently on depends on the master file you used in the installation.  Usually, BSI keeps the master file updated with the latest TUBs for the version.  I think the master file is even named accordingly.  When we did this back in July/August, we did not have to apply but one or two TUBs that came in while we were upgrading.  It looks like BSI has not provided a master file for cyclic c.  The latest for cyclic b is TFU11036.PKG.  So if you are using this master file, you would not need to apply any TUBs.  If all is installed per the instructions and you do not see cyclic and TUB levels in System Tools, then you need to contact BSI.

            Good luck, Anna

  • Hello,

    We are fairly new to ECP Cloud.  We are testing the upgrade of BSI to 11 from 10.
    We have completed the following:-
    1) upgraded to SP88
    2) Define web service for BSI TaxFactory SaaS integration
    3) Define user credentials for BSI TaxFactory SaaS integration
    4) Tested BSI TaxFactory SaaS Communication

    I would like to confirm this step 5) Specify BSI TaxFactory Version

    I have gone to SU3, and set BSI_TF_Version to 11 for my profile.
    I am not clear on what this step actually is.  There are 2 table views that I see in the documentation that requires the Version to be set.
    - V_T5F99K1
    - V_T5F99K2
    I do not want to set VT5F99K2 to 11 as I do not want to activated 11.0 for the whole client as you cannot change back to V10

     

    Another question -

    For
    6) Synchronize Payroll Tax Data - should this be run after a config is done for V11?
    If I go to SU3 and set BSI_TF_Version before running the synchronization, the synchronization will work.

    If we want to TEST only in the non-productive systems for specific users only and not impact other users in the system, i.e. use V11 only for certain users and others remain on V10
    - To switch, we would go to SU3, and set BSI_TF_Version to 11

    However, if I delete the entry in  SU3 BSI_TF_Version, and I do a simulation, I get the following

    Messages

    BSI Level: TaxFactory 10.0.x.3 - Regulatory 208
    SAP client-specific level: TaxFactory 11.0.c - Regulatory 041
    SAP cross-client level: TaxFactory 11.0.c - Regulatory 041
    Mismatch between SAP client-specific level and BSI level

    It appears that you can only test one version of BSI at one time for all users?  Please can you advise as to what is the best way to test this without switching to V11 permanently?

    • Hello Ursula,

      It is not necessary to fully upgrade to TF11 to test TF11 scenarios on your system.
      You can define the parameter BSI_TF_VERSION for your user and perform the tests accordingly.

      In order to do that, you should define the parameter as following on your system:

      System -> User Profile -> Own Data -> Parameters

      Parameter ID = BSI_TF_VERSION
      Parameter Value = 10 or 11

      As per Synchronize Payroll Tax Data, this should be run every time you perform some change on your system, as it's necessary to ensure that the BSI Client, Cross-client and Client-specific Tables are always matching.
      If that's not the case, you will get mismatch error. Kindly refer to KBA 2382644 - Mismatch between SAP and BSI level.

      Additionally, it seems that you still have some systems running TF10.
      This way, I'd like to mention that effective on April 30th, TF10 will be decommissioned and we will no longer support it.
      Based on that, kindly ensure that you fully upgrade to TF11 before April 30th, as there will be no exceptions to support it after this date.

      Kind Regards,
      Carlos

      • Hi Carlos,

        Yes, we are currently on TF10 but working on moving to TF11.

        I am not clear on one thing.  There are 2 table views that I see in the documentation that requires the Version to be set.
        – V_T5F99K1
        – V_T5F99K2

        Are both the above tables view used to switch to V11 when we are ready on the instance?  So, each non-prod instance will switch separately?

        Thanks

        • Hello Ursula,

          Please refer to the FAQ questions numbers 1 and 2 of this blog.
          View V_T5F99K1 storages the options that can be used on V_T5F99K2, and your system will start using TF11 when you update V_T5F99K2 to use TF11.
          As from the switch to TF11, each system will switch when V_T5F99K2 is set on the given system to use TF11. Hope this clarifies your scenario.

          Best Regards,
          Carlos

          • Hi Carlos,

            I updated user A,  ‘BSI_TF_VERSION’ to 11 and ran the synchronization RPUPAYUS_SYNC_TAX_DATA and it updated successfully and showing

            Level in BSI Client: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
            Cross-client Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
            Client-specific Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19

             

            However, for user B, which I have not set t ‘BSI_TF_VERSION’  to 11, it shows the

            Level in BSI Client: TaxFactory 10.0.x.3 | Cyclic X3 | Regulatory 208 | Tax Locator 101
            Cross-client Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
            Client-specific Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
            Mismatch between SAP client-specific level and BSI level

            If User B runs the synchronization, it does not change to V10

  • Hi Carlos,

    I updated user A,  'BSI_TF_VERSION' to 11 and ran the synchronization RPUPAYUS_SYNC_TAX_DATA and it updated successfully and showing

    Level in BSI Client: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
    Cross-client Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
    Client-specific Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19

     

    However, for user B, which I have not set t 'BSI_TF_VERSION'  to 11, it shows the

    Level in BSI Client: TaxFactory 10.0.x.3 | Cyclic X3 | Regulatory 208 | Tax Locator 101
    Cross-client Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
    Client-specific Tables: TaxFactory 11.0.c | Cyclic C | Regulatory 041 | TaxLocator 19
    Mismatch between SAP client-specific level and BSI level

    If User B runs the synchronization, it does not change to V10

     

      • Thank you for responding.  The issue is that the user B that does not have the BSI_TF_VERSION set to 11 is not able to run simulation and getting the 'Mismatch between SAP client-specific level and BSI level' error

        • Hi Ursula,

          By default in standard this message is a warning message.
          So, the user should be able to run the payroll, even receiving this warning message.

          Kind regards,
          Graziela

          • /
          • What is the reason why User B is not able to run simulation, if they have not set their parameter to version 11.  Should it still process as v10 for BSI?

            User A who is set to Version 11 is working fine

          • Ursula,

            In feature 10BSI, create 2 entries -- one for &10BSI=10 and one for &10BSI=11. When you go live, comment out the &10BSI=10. That's how we parallel tested in our SAPTST environment.

            Also, have you run program RPUBTCU0 to test the BSI TF calculations? There are a couple of differences between 10 and 11, but it's just a test to run.

            Beth Matthews

          • Beth,

            Do you have a screenshot of the entries that would be created?  I'm not familiar with PE03 and having some trouble creating these entries as you noted

            Thanks

          • I tried to send a screenshot before but it won't let me attach it. Feature 10BSI looks like this for us:

            Line       Variable Key     F     C     Operations

            000010                           *      *       &10BSI=10,

            000020                                           &10BSI=11,

             

            Line 000010 has been commented out because we are live with TF 11.0. We are currently at 11.0.C, TUB 038. Hopefully you can leave Line 000010 "active".

            Make sure you put the comma at the end of the Operations entry. Run a Check (little scales icon) and then Activate the feature.

            Hope this helps.

            Beth

             

             

          • /
          • Hello Ursula,

            As mentioned in standard this is a warning message.

            Check in your system if you don´t have implemented badi HRPAYUS_B_REG_BUL_LEVEL, this could be the reason for the hard error.

            Refer to SAP note for further information about this message:

            2193769-BSI: Regulatory Bulletin level validation in Payroll

            Kind regards,
            Graziela

  • During my testing, I have been unable to trigger the reverse tax engine setting ET:3 in the BSI Interface.

    Is it possible schema parameter choices could prevent it from triggering for V11?  Are other parameter choices now required for this functionality to work properly? Note, our V10 processing was not changed to use the reverse tax engine in January 2020.

     

    Thank you for your assistance,

    Stanette

    /
  • Hi Graziela,

    My client is in the process of testing TF11 and we have a question about the list of prerequisite notes in the main post of this blog (section "As a prerequisite, you must apply the following SAP Notes:").

    1) Specifically, are these notes required before we can upgrade to TF11? I know many clients went live with TF11 before these notes were published, which is why I'm asking.

    • 3008339 – TAX: Community Safety Payroll Taxes for Eugene
    • 3013127 – BSI: Enablement of Tax Type 106 for Concurrent Employment
    • 2999318 - TAX: HR Renewal - Source Tax Authority

    2) Also, we have not implemented the Source tax notes on our parallel testing client, and we would prefer to test TF11 without having to also implement the Source tax solution. Is this okay, or is the Source tax solution a prerequisite for TF11?

    Thanks again for the great blogs!

    Vicky

     

    • Hi Vicky,

      1) No, they are not required. You can proceed with the upgrade to TF11, and afterwards apply notes 3008339, 3013127 and 2999318 on your system.
      2) That's ok! The Source Tax Authority delivery is not a prerequisite for TF11.

      Best Regards,
      Carlos

  • Hi Graziela:

    I have a question about the exempt wages as described in OSS note 2760305. I have tried testing every exempt tax scenario I can think of including using a person under 18 years old, making the IT 0210 as exempt (both reportable and unreportable) as well as overriding taxes to be exempt using IT 0234 / 0235, and I do not see the YE: parameter being passed to BSI in the "BSI Interface" log output except that I saw the OSS note 2973826 related to NY expense tax and we can see the YE parameter and the /919 wage type generated for the scenario where the employee has not yet earned $40K in NY earnings. I do see /9XX wage types in the input table TAX_LGART to USTAX in every run. None of the output tables have /9XX wage types except the NY TT 19 scenario. What causes the system to use the YE parameter and what are the overall rules to expect /9XX wage types for exempt taxes -- is it only if the tax authority itself exempts the wages or are there other scenarios?  We are on cyclic C and Regulatory Bulletin #41 on Tax Factor for SaaS.

    Thanks.

    Kathie

    • Hello Kathie,

      The system creates this wage types when the following conditions are met:

      1) Tax Authorities: KY24, KY0S, KY65
      2) Low Salary
      3) Employee most have more than 65 Years.

      In this case, system will sent the parameter YE in the script in the scenario mentioned by note 2760305.

      Kind regards,
      Graziela

  • Can you please provide info in which scenarios ET:3 parameter will shown in the BSI interface?
    Reverse tax engine parameter ET:3 is not showing in the BSI interface when I tested the below
    scenario.
    Note: Reverse Tax Engine is enabled by constant ADTMD of view V_T5F99K2 .
    Scenario:
    Step:1 I have run the payroll with IT 15 bonus payment in the PP01 2021 period.
    Step:2 In the PP02 2021 period, I have removed the IT 15 bonus payment to get the negative pay period wages and to get the ET:3 Parameter but in the BSI interface not showing this parameter.
    Can you please provide info in which scenarios ET:3 parameter will shown in the BSI interface?
    Thanks,
    CNR
    • I found the key is keeping /5PY positive while generating enough negative amount on a bonus wage type to trigger the negative calculations.  The attached should help you reproduce.  Keep in mind, we don't use separate aggregate method for any calculations and I was using a regular payroll run.

      We don't not have a large number of these scenarios given how we process our payroll.

      Good Luck!

      Stanette

      • /
          • Hi Stanette or CDR or any other customers:

            Do either of you use the SAP US Overpayment Recovery module?  I am wondering how using this module factors into the scenario since we have our configured earnings set to generate claims and go into Overpayment recovery using Infotype 0909 rather than to deduct.  Maybe we will need to increase a prior pre-tax benefit deduction to see a reduction of taxes.  Let me know if either of you are using the Overpayments module or if anyone has generated the negative ET: 3 parameter without using earnings.  Thanks.  Kathie

  • Hi All,

    We are checking the scenarios on Negative Net Wages.

    We have followed the below steps to generate the -/101(-ve gross) to get the negative net wage and to called out the Reverse tax engine.

    Step1: Run payroll  bonus wage type amount for the current period

    Step:2 Maintain the more -ve  bonus wage type amount in the next period and run the payroll so that system generates - /101.

     

    Can you provide the info how to called out reverse tax engine in case of -ve net wages in the system?

     

    Thanks,

    CNR

     

  • Hi Graziela,

    We are in the process of upgrading the BSI SAAS to TF 11. I have maintained BSI_TF_VERSION parameter for a test employee and ran the Sync tool without maintaining the table V_T5F99K2 with version 11.  Is it mandatory to maintain the parameter and the table as well for testing?

     

    Please advise.

     

    Upendra

    • Hello Upendra,

      In my internal system I just tested using the parameter BSI_TF_VERSION in SU3, without the entries in V_T5F99K2 and that worked fine.

      Kind regards,
      Graziela

  • Hello Graziela,

    For a first time BSI - SAP on premise payroll user do we have any guide/ documents describing the various steps &  possible options available for the integration. It would also be nice if you can throw some light on who needs to configure the Tax factory server and connections, is it the Basis team?

    Regards,
    Pankaj

    • Hello Pankaj,

      Please refer to note 2844034 – TaxFactory 11.0 – On-Premise Installation.
      This note is for both its Installation or Upgrade on your system.

      Best Regards,
      Carlos

  • Hi Graziela, We installed TF11 and receiving below error while trying to run program,RPUPAYUS_SYNC_TAX_DATA or RPUBTCU0. Basis followed all the steps required according to the note On-Premise Installation.

    RPUPAYUS_SYNC_TAX_DATA Error:

    RFC connection BSI11-US-TAX for BSI Taxfactory version 000 is not available.

    Message no. HRPAYUS_BSI002

    RPUBTCU0 Error:

    • Sorry, connection to BSI TaxFactory version 11.0 is not working
    • RFC connection for BSI Taxfactory version 11 is not available.

    Thanks

    Punna

    • Hello Punna,

      Please check if you are seeing connections errors while testing the connection directly on transaction SM59.

      In any case, I would recommend you to review your setup configurations described on note 2844034 - TaxFactory 11.0 - On-Premise Installation.
      You may also refer to note 1938756 for troubleshooting (note 1938756 is specified for TF10, but the same should apply for TF11).

      Best Regards,
      Carlos

    • Hi Punna,

       

      I am also facing the same issue. Please help me to provide the fix.

      I have checked the RFC it is working fine. I have checked the ODBC connection it is working fine. But when  run the RPUPAYUS_SYNC_TAX_DATA or RPUBTCU0 iam getting the RFC error.

       

      Kindly help us.

       

      Thanks,

      Shyam.

       

      • Punna and Shyam,

        Make sure your Basis team is pointing the BSI environment to the correct SAP environment. We have BSI_BOX and BSI_PRD environments. We point SAPDEV/TST to our BSI_BOX environment and SAPPRD to our BSI_PRD environment. We sometimes point SAPTST to our BSI_PRD environment depending on what we are doing to BSI_BOX (i.e. updating to a new Cyclic or applying new TUBs).

        Just a thought.

        Beth Matthews

         

  • Hi Graziela,

     

    We're in the process of setting up TF11 in our system & I had a question as it relates to the User Parameter (SU3) update that is needed for this.  Why is this user parameter needed for this new version when it wasn't needed for previous versions?  I tried testing without the user parameter & got an RFC error, but once I added the user parameter in it ran fine.  Just curious why it's needed because I have a feeling our security team will want to know why this change is needed.

    Thanks.

    • Hello Adam,

      This is not a mandatory customizing, this is just for the specific user to test it.
      Once the constant BSITF is updated in V_T5F99K2, the SU3 parameter is not required.

      There is any change since TF 9.0.

      Kind regards,
      Graziela

  • I have upgraded my system to BSI TF11 in the BSI portal end, and need to apply additional Tubs to get the system current.  When I went to run the HRPAYUS_SYNC_TAX_DT transaction only the Level in BSI Client is reflecting TF 11.0.  The Cross-Client and Client-specific tables are still reporting TF10.0 levels.

    I have all the entries updated that you mentioned for switching to BSI TF11.0.  Can you tell me why the snyc tool is reflecting TF10.0 for those 2 options and what I need to do to move forward?

     

    thank you,

    Juli T

  • Hi: We are testing Tax Factory v11 and holding all else constant except executing Payroll and comparing v10 to v11 in the user profile.  In the BSI instance dataset, we have many optional rate overrides which were set up with a begin date of 1/1/2017-12/31/9999 and a rate of 0% because these are tax authority / tax types not applicable to our employees.  When we compare v10 to v11 results, we found in at least one case, the BSI instance Optional Rate override did not stop the calculation of the tax.  The scenario is a Massachusetts employee who has Tax Type 92 taxes taken.  In Production and v10 of our QA test, only wage type /392, /692 and /792 are produced because the BSI instance Optional Rate override was stopping the /492 from being created.  However, in v11 without changing any configuration, we are finding that when we run the same pay period, the YTD earnings are generating a /492 value for tax even though the v11 BSI Dataset still includes the exact same Optional Rate Override of 0% for this tax authority, tax company and tax type.  We have never needed to configure these overrides in the BTXRATE table previously.  Also, in v11 we notice a message appearing in the "BSI Messages" area of the Log under USTAX -- "2058 - No Company Optional Rate information for the Massachusetts ER Medical Asst Contribution Tax was found.  This tax has been calculated using the Base rate.  This result may or may not be valid for your company."  We have double checked the Optional Rate overrides to verify the 0% entry still exists for the correct tax company, authority and tax type and the correct v11 BSI dataset, and do not believe any new transports have been applied to QA which would impact this test.  This would be alot of work if every single override in our BSI dataset that was set to 0% at go-live would now need to be re-configured in BTXRATE.  Can you please advise?  (Also, we do think we have all the BTXRATE OSS notes although as mentioned earlier, we never had to make any BTXRATE entries previously in order for these 0% overrides to block taxes in v10 of Tax Factory.)  Thanks!  Kathie

    • Kathryn,

      Have you marked the check box in V_BTXRATE when there is a 0 amount for either the experience rate or the wage base? You need to do that, otherwise SAP will go with the amount listed by the State and your override is disregarded. We have that issue with Missouri, so we checked the 'Experience Rate Zero' box and it works fine. We've been on TF 11.0 since October 2020.

      Beth Matthews

      • Thanks Beth for the suggestion.  I guess that goes to the heart of my question -- we have Optional Tax overrides which only exist in the BSI datasets which we have never maintained in the SAP BTXRATE table at all, and in v10 these still suppressed the taxes when using a 0% rate.  It appears that in v11, based on our regression test results, the BSI dataset override alone is not suppressing this tax for some reason, so my question is whether we now need to maintain all of these 0% entries in the SAP BTXRATE table and was looking to confirm this is a new v11 behavior or a system defect which I should raise an incident for, because we weren't seeing this in v10.  In v10, a BSI dataset Optional Tax Override was sufficient to suppress a tax from being calculated but in v11 we are not seeing the same behavior.

        • Hi Kathryn,

          We use Optional Tax overrides as well, in both BSI and SAP. We put them in SAP BTXRATE table and BSI TF Optional Rate Overrides . None of our Optional Tax overrides are 0, but we put them in there anyway. We've done that for years, regardless of the BSI TF version (TF 8, TF 9, TF 10, TF 11). SAP introduced the check boxes for 0 experience rates and wage bases while we were still on TF 10. We applied a TUB (can't remember which one) that impacted Missouri and found that it was not pulling in the override anymore. That's when we turned the check box on.

          TF 11.0 just may have tighter editing within the interface with SAP for the overrides. If SAP doesn't see an override, then it's probably sending the tax rate out of table T5UTX, and BSI goes with what is being sent by SAP.

          I would add an entry in SAP BTXRATE and test to see if it fixes your issue.

          Beth

           

        • Hello Kathryn,

          Until version 604, SAP recommendation was to update BSI Tax Factory and V_BTXRATE.

          From version 608, you just need to maintain V_BTXRATE.

          Kind regards,
          Graziela

  • Hello,

    We are on SAP 604 F7 and EAHR A8 with BSI V10x3 TUB 212 and V11c TUB 45 in our QHR system.

    Our Fed W/H is not calculating correctly in V11 but our V10 continues to match our PRD system calculations.  The only difference for my test pernrs is in our BSI Interface between V10 and V11 for the location of WF:1,1 parameter.

    Both of my test cases have WF:1,1 noted on the FED 001 tax grouping on V11. Unfortunately, the tax is incorrectly calculating with the higher Single rate equivalent.

    ATC ET: 0
    IPC CC: BWCC GC: EG99
    EPC PP: 24 CD: 03/15/2021 PT: REG
    YP: 4 PH: 88.00
    GU: 0
    BD: 03/22/1968 RS: IN PS: IN
    RC: 1
    EP: 0
    GW: 13208.60
    ADC TC: FED NR: 0 RP: 0 RC: 0 SE: 0 NX: 0 WF: 1,1
    HUD TT: 001 FN: 1 PW: 13208.60 HW: 88.00 MS: 4 NE: 0
    ADD TE: 0 YW: 192101.40 YT: 42321.98 RN: 0 PW: 1.00 RF: 0 YG: 192101.40
    VDC AT: 2 AA: 500.00
    SDC SM: 9 BW: 14583.33
    EDC DE: 0 NA: 0
    LUD ES: 0 SA: 0 QW: 192101.40 QT: 42321.98 PND: 0 MND: 0 QND: 0 YND: 0

    We do not have any entries in the V_T5UTZC_W4_OVR table. Is there a requirement for this table to have entries so the WF parameter for FED will properly calculate for Post 2020 W4 Married Filing Jointly?

    Please advise

    Thanks,

    Stanette

    • Hello Stanette,

      On TaxFactory 11.0, the WF will be sent on the script only if it assumes the values of 1,1 or 1,2.
      Otherwise, it will be 0,0 and will not be on the script.

      From TaxFactory 10.0 to TaxFactory 11.0, the position of this parameter on the script have changed.
      Please refer to KBA 2985123 - The Parameter WF on the BSI Interface: TaxFactory 10.0 and TaxFactory 11.0.

      As per table V_T5UTZC_W4_OVR that you mentioned, this is used to set the W-4 Indicator for the Authorities, and will override the W-4 Indicator set on V_T5UTZ, in case it has a valid entry.
      Please make sure that the W-4 Indicator that you have set for the used Authority is indeed reading an IT0210 record that follows the 2020 format, which should impact on WF: 1,1 or WF: 1,2 on the BSI Interface.

      Best Regards,
      Carlos

      • Thank you!

         

        I have been digging deeper and see one commonality.  All people who have a FED W/H /401 discrepancy between versions, also have one or more W4's since 1/1/2020.  They are all using the Single Higher Rate calculation even though they have post 2019 W4 forms.

        Is this behavior applicable to a particular note?

        I am reviewing the details in your KB 2985123 but since FED is our focus at the moment, I am not sure the notes referenced in the KB apply.

        Regards,

        Stanette

        • Hi Stanette,

          I don't see how this should be related to a particular note, but with the maintenance of the filing status.
          Please check if the FED IT0210 of the employee is being maintained with a valid filing status.
          The ones that are valid as from 01/01/2020 are 01, 03, 04, 06 and 08 (refer to this blog).

          If you are getting the taxes computed under single rate, I might say that you are using an incorrect value of filing status, which provokes the calculation to be made under single rate, as BSI Message 1008 should illustrate on the log.

          As per the notes mentioned on the KBA, they are valid for FED level as well.

          Kind Regards,
          Carlos

    • Hi Stanette,

      We are having the same issue when we compare the taxes in between BSI 10 & 11. The BSI 11 taxes are pretty high when compared to BSI 10.

      Did you find any solution for this issue?

      Regards,

      Mohammed.

      • Hi Mohammed,

        I worked with some customers and the issue was due the program that was not updated in BSI.
        This could be the reason for this.
        Could you check KBA:

        2443834 - TaxFactory cyclic upgrade doesn´t show the new version

        Kind regards,
        Graziela

        • Thank you, Graziela.

          The cyclic version looks fine in our system. I have identified the actual problem and I see the below message in the system and hence the calculations are higher.

          1008
          YOUR REQUEST TO USE 4 MARITAL STATUS FOR THE FEDERAL WITHHOLDING TAX IS NOT ALL
          OWED. THIS TAX HAS BEEN CALCULATED USING THE 1 MARITAL STATUS.

          I have already reviewed the below list of notes and all the notes have been applied in the system including manual activities.

          2845128;

          2850174;

          2845529;

          2855896;

          2933305

          2878657

          2878657

          Regards,

          Mohammed.

           

  • Cyclic D for TF 11 is supposed to be released today from BSI. We are trying to go-live before the April deadline. Is this a mandatory cyclic upgrade or should we proceed on C?

    • Hello Jeff,

      I logged into BSI this morning and do not see a new cyclic.  Even latest TUB 048 is still showing cyclic C.  I have been watching for this cyclic as there is an issue with some of the unemployment wage bases - see screen shot.  I have overridden the ones I need.  If you are already including wage in the override then there should be no concerns.

      Thanks, Anna

       

      /
    • Hello Jeff,

      From SAP side you can start using the cyclic C for the upgrade.
      However, the recommendation is to upgrade as soon as possible.
      I talked to the developer and he recommended to reach out BSI to see if there is any issue under they side, starting useing Cyclic C.

      P.S.: Cyclic D is already available in BSI page.

      Kind regards,
      Graziela

  • We are getting a message when creating a 207 using Tax Locator after upgrading to TF 11, cyclic C. We have V3 version 20 of tax locator installed.  Is there something similar to feature 10BSI? We could not find any documentation around it.

    BSI TaxLocator version 011 is not a valid version

    Message no. 5BSI014

    Diagnosis

    You are trying to edit master data using a TaxLocator version that is not valid

    • Hello Jeff,

      Please check the TaxLocator level on sync tool, as it should be the same on the Level in BSI Client, Cross-client Tables and Client-specific Tables.
      I also recommend you to check the results of report RPUTLTU0. In case there's an issue on the TaxLocator configuration, this report should indicate it.

      For feature 10BSI, please refer to the FAQ number 1 of this blog. As you are using TaxFactory 11.0, it should be set to 11.

      Best Regards,
      Carlos

  • Hi,

     

    Has anyone applied cyclic 11d yet?  I'm getting the below results when I use the sync tool.  It says both 11.0.c and Cyclic D.  I opened a ticket but not sure if was something we did wrong.

     

    Level in BSI Client: TaxFactory 11.0.c | Cyclic D | Regulatory 040 | TaxLocator 11
    Cross-client Tables: TaxFactory 11.0.c | Cyclic D | Regulatory 040 | TaxLocator 11
    Client-specific Tables: TaxFactory 11.0.c | Cyclic D | Regulatory 040 | TaxLocator 11

    Thanks

    Brenda

  • We have moved BSI 11 to PRD and "now" tax has determined that the calculations are incorrect. The error message comes back in Message Viewer in BSI TF that :

    5026 Keyword EDC  TC is not recognized and is ignored

    5026 Keyword ADC WF is not recognized and is ignored.

    Employees are being taxed at single with no tax credits which is way too high and not what is on their Infotype 210 for FED.  Can anyone tell me what manual step we may have missed so that BSI will read and understand the values we send in the Interface for V11.  Is there config we missed?

  • Hi,

    We are in the process of upgrading to BSI 11 from BSI 10 and my question is, when I run RPUBTCU0 for testing BSI 10 and BSI 11, I am getting different results for the withholding tax for BSI 10 and BSI 11. I have attached screen shots to show the differences. Can someone help with why there is a increase of $14.17 between BSI 10 results and BSI 11 results for the calculation results? Thanks in advance

    BSI 11 Results

    BSI%2011%20Results

    BSI 10 Results

     

    Thanks,

    Scott

      • Thanks for the quick reply, I will get the Basis team to bring the TUB level to 047 on BSI 11 and rerun and see if that corrects the results

         

        Thanks,

        Scott

        • Scott,

          When you update to TUB 047, you will need to be on Cyclic C (11.0.C). Cyclic C is mandatory, so have your Basis team apply Cyclic C and then TUBs up through 047.

          Thanks,

          Beth Matthews

           

  • Hello Team

    Good Morning

    We are using BSI TaxFactory 11.0.c in Production since February and last week we updated our DEV environment with Cyclic Bulletin D, and now we are getting errors related to tax calculation:

     

    I checked the Payroll Tax Data (HRPAYUS_SYNC_TAX_DT) and seems to be corrected.

     

    I reviewed some the information from this blog related to Schema and users parameters and everything seems correct.

    Please can you provide some directions?

    Thank you.

     

    Paulo Codello

     

     

     

    • /
      • Bom dia, Paulo!

        Did you run the sync tool using the option "Process Tax Authority Mappings only"?
        If not could you try it?

        If so, could you please open a case? So we can check directly in the system?

        Thanks,
        Graziela

        • I did a test run and I got a few warnings and I worked with my basis team to run on client 0 and everything was clear, but after the move the transport to the DEV test the warnings came back.

          I requested Basis to open a case, but if you see something from the screen shot that can help please let me know.

          Thank you.

          /
  • Is anyone else missing the Tax Locator node in the IMG? We are on 608 and have followed the steps in the old oss note 1353429. We created a new project IMG and generated it, but it did not create the steps. I submitted oss incident 254312.

  • Hi Graziela,

    We have completed our move from BSI10 to BSI 11.0.c in DEV and QA and did the switch setting.  We updated the BSI client with everything for production and we were preparing for doing the production SAP side. when we ran the sync tool, we see that the BSI client still says BSI 10.  in a production client must you do the sm30 switch before you go to the sync tool so that the proper BSI client level is reflected.  We didn't have that in DEV and QA.  Does the code for the sync tool force you to do the switch first in sm30 for a productive client?

    please let me know ASAP.

    Regards,

    Barbara Garrett

  • Hello Graziela,

    We have completed upgrade from BSI10 to BSI 11.0.b in DEV and QA  and ready to move to production. We noticed that in R system which is our production test system before we move to production,  if we did not enter user parameter BSI_TF_VERSION with value 11 we have mismatch between BSI and SAP client level. Switch is present and payroll runs without any problems. if we enter user parameter in SU3 everything is fine, no mismatch.

    All configuration is  completed,  10BSI set up to 11 and SWITCH (BSITF) to 11.

    We kind of puzzling right now , we were assuming this parameters  should be working without switch.

    Please advice.

    • Hi Prashanth,

      Do you run the sync tool in all systems or do you transport the data? If you run in all the clients you need to execute the Sync Tool after the switches.

      If you transport you need to transport the information from V_T77PAYUS_SYNTX and T77PAYUS_SYNXC.

      Refer to note:
      2193769-BSI: Regulatory Bulletin level validation in Payroll

      Kind regards,
      Graziela