cancel
Showing results for 
Search instead for 
Did you mean: 

*BSI 8.0 becomes obsolete August 31st 2011, 9.0 troubleshooting guide here*

Former Member
0 Kudos

Dear customers,

Support for BSI Tax factory expires on August 31st 2011, there will be

no extension of support past this deadline, and BSI will not

issue TUBS for Tax Factory version 8.0 to enable tax compliance after

this date, therefore, please plan your upgrades now to ensure that your

system is tax compliant on September 1st 2011.

If your project is to implement US Payroll using BSI TaxFactory, you

need to be on BSI TF 9.0 by September 1, 2011, to be supported.

For both installation and upgrade, the minimum requirement is the June

2010 synchronization HRSP and the October 2010 CLC.

For more information on the upgrade and support package requirements please refer to our site:

service.sap.com/tubs

If you face issues when upgrading to 9.0 please review our WIKI page at

http://wiki.sdn.sap.com/wiki/display/ERPHCM/BSITaxFactory9.0 as an initial point for troubleshooting your issue.

Here are some important BSI notes to help with your upgrade

1469857 Central source of instructions/information for TaxFactory 9.0 installation

1484771 FAQ: TaxFactory 9.0 Installation/Upgrade Troubleshooting.

1484804 Installation Instructions for TaxLocator 9.0.

1150833 BSI TUBs for TaxFactory 8.0 - Consulting Note

1532493 TUB: Applying transport files from TUBS

Accepted Solutions (1)

Accepted Solutions (1)

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Community,

The following note is also relevant when upgrating to BSI 9.0:

1519016 Enabling TaxFactory via Switch Concept.

Kind regards,

Felipe Grandi

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello All,

Just for general knowledge, SAP has up two days to deliver a note for each TUB delivered by BSI. Please keep it in mind when BSI has delivered a new TUB and the respective SAP note is not right after delivered.

Kind regards,

Felipe Grandi

alicia_robinson
Participant
0 Kudos

Felipe -

Per an earlier reply you stated -- "Just for general knowledge, SAP has up two days to deliver a note for each TUB delivered by BSI. Please keep it in mind when BSI has delivered a new TUB and the respective SAP note is not right after delivered."

Why does it take longer for SAP to release some TUB's? We are trying to wrap up some changes for BSI 8.0 and BSI released TUB 213 on July 21st, but SAP still has to release this note? Can you tell me when it will be released?

Thanks,

Alicia

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Alicia,

Really the rule is to deliver the correspondent note for a TUB up to 2 days after. In some cases, depending on the complexity, it takes a bit longer. Anyway I've seen the note for TUB 213 was released today:

1616443 TUB 213: Tax Update Bulletin for TaxFactory 8.0.

Kind regards,

Felipe

Former Member
0 Kudos

We are upgrading BSI from 8.0 to 9.0.

We have followed all the steps in installing BSI, but we had the reciprocity issue and as per SAP Note 1500595.

Solution

To introduce the nexus indicator for withholding tax calulation, the U.S.

Payroll was enhanced to fully support the withholding tax to be calculated

based on a recriprocal method for a pair of resident/ non-resident

authorities.

The view V_T5UTRC was created to store the pair of resident/ non-resident

authorities per tax company.

The question here is. Where can we find State Reciprocal Tax Agreement for all the States??

And When we are running Payroll for some test employees

u2013 IT 207 is NY and 208 is CT. In Test System(BSI 8.0) both NY and CT taxes are withheld and wage base accumulated; in Development System(BSI 9.0) only CT taxes are withheld and wage base accumulated.

Similarly for u2013 IT 207 is MA and 208 is GA.

Can some one throw some light on this.

Thanks

C

Edited by: chaithanya k on Aug 5, 2011 5:04 PM

former_member1348745
Active Participant
0 Kudos

We have New Tax Factory 9.0. Pennsylvania locals aren't working correctly.

We have EE on infotype 207 as

Federal

PA

PA9J (Canon-McMillan SD)

PAAH (Cecil Township)

IT 208 is PA9J, consisting of:

PA

PA9J - (Canon-McMillan SD)

Currently its taking Tax only for PA9J - (Canon-McMillan SD) and Nothing for (Cecil Township).

We had issue with the Reciprocity but we have fixed that using V_T5UTRC.

Please Helps us how this will be handled in tax Factory 9.0 and in SAP?

jhkoch
Participant
0 Kudos

Our initial testing with 9.0 showed that reciprocity between states no longer worked the same as it did in version 8, and our Pennsylvania local taxes didn't come close to working like they did in version 8. I even contacted BSI and I thought they were going to fix the Pennsylvania issue, but I must have mis-understood.

After reading the documentation and other posts, I set up the Nexus values on T5UTRC for every possible combination using our T5UTI table to show what states each company had every had taxes taken in. (7,014 entries).

We then went to 9.0d from 9.0 in our QA system hoping that would fix the Pennsylvania locals (because I thought they were going to fix it).

This week I ran a full payroll test in our QA system of over 30,000 employees across many states using version 8 and ran recon reports to get all the tax values. Then I ran with version 9 and ran recon reports again. I then compared the differences.

The end result is that even with the Nexus table entries reciprocity between certain states and particularly Washington DC doesn't work like it did in version 8.

And more importantly, our Pennsylvania local taxes are still really out of whack. Luckily between the two that effects probably 30 or less employees of our over 30,000.

So my plan as of now is to upgrade in the next week in production but:

1) Set the "reciprocity like version 8" flag in Tax Factory even though BSI says that should be only used for testing. That will take care of the few state reciprocity issues that the Nexus table didn't work on.

2) Use the new 10BSI feature so that for our Pennsylvania locations, we'll still call version 8. Everyone else will use version 9. That's only a temporary solution but not sure what else to do at this point.

I feel sorry for anyone that has a lot of employees in Pennsylvania...I'm not sure why BSI and SAP would roll something out that breaks functionality that worked fine in a prior version, but it looks like they're going to.

Former Member
0 Kudos

Hi John,

Thanks for the update. If possible can you please download the entries (7014) and send it across to my email.

Thanks,

C

alicia_robinson
Participant
0 Kudos

John -

Thanks for posting the information on the 9.0 issues you are having and some of the steps you applied. Unfortunately for us, we are going to fall into the category for more than 30 employees in PA so I'm not looking forward to the issues I know are going to be there.

I would like to know if you also created your 'nexus' entries on the BSI side under the "Modeling" section for "Custom Nexus Data" or did you just create then in the SAP table V_T5UTRC? Do we have to create both?

I have to agree with you that I don't understand why between BSI and SAP that they removed all of 8.0 rules from the 9.0 version because it just makes that much more work and customization of data on our part. I'm afraid that I will not be finished with all the testing and additional config before the Sept. 1 deadline because we do so much 'courtesy withholding' for local tax authorites,.

0 Kudos

Hi John,

Can you advice where have you set the Flag as reciprocity like version 8 in Tax factory.

Thanks for the info and help

DK

0 Kudos

H Alicia,

Unfortunately we also fall in the category of more than 30 employees in PA, were you able to figure out how to deduct the PA local taxes.

Thanks

Deepak

alicia_robinson
Participant
0 Kudos

Deepak,

Unfortunately, we are still working on testing the BSI 9.0 and all of its' issues (CT, PA, nexus, reciprcocity, etc). I really wish I could offer suggestions on how to help you, but I feel like I've been running in circles with all these problems and haven't found the light at the end of the tunnel yet!!

We have had so many issues and it's mainly because our employees travel everywhere and we do courtesy withholding - meaning they can have an IT207 of one tax authority and a totally different IT208 tax authority. We tried to set up nexus for all state tax authorities but of course this does not work for all tax combinations so it's a matter of finding who needs to have a nexus entry and who does not. We also found an error for MD residents who work in PA because there is an issue with BSI in which it stops withholding the MD local 'required' resident taxes and takes the PA state taxes instead. This is currently being worked on by BSI. There are really too many issues to list and this doesn't include the changes that are upcoming for PA ACT 32.

Answers (4)

Answers (4)

Former Member
0 Kudos

We are upgrading to BSI 9.0.d. Problem we are having is with Kentucky school taxes for employees living in Kentucky but working in Illinois. Kentucky state taxes are calculating, it's the county school taxes that are not calculating.

Employees that live and work in Kentucky are calculating correctly.

We have updated the reciprocal 'TF80 like Reciprocity Functionality' to yes.

We've send an email to BSI because we're having trouble getting through on the help desk via phone. But no answer yet.

Any ideas how to correct?

Former Member
0 Kudos

Please go through the Wiki Links provided.

[http://wiki.sdn.sap.com/wiki/display/ERPHCM/BSITaxFactory9.0]

[http://wiki.sdn.sap.com/wiki/display/ERPHCM/BSI-Nexus+Indicator]

You have to maintain the reciprocity..

http://www.payroll-taxes.com/articles/175-state-tax-reciprocal-agreements.htm

[;

[;

Hope it helps...

Thanks,

CK

Former Member
0 Kudos

Hi Gayle, I had the same issue while doing the testing for BSI 9.0 upgrade. Please follow the instructions on how to override the tax reciprocity using Nexus indicator and it will resolve this issue. Please see the below mentioned scenarios what I tested:

I picked some PERNRs having IT0207 KY and KY2H and IT0208 IL.

Both of these states having legal agreement of state tax reciprocity and as per the law the tax should come out from their Residence State and not from where the wages were earned. I processed the payroll with default setting in the BSI 9.0 and it deducted the IL taxes, whereas in another environment where we still have the BSI 8.0, it deducted the taxes from KY+KY2H, as supposed to be.

Then I used the Nexus indicator and changed the settings to override the tax reciprocity to use the secondary indicator and then processed the payroll and it worked as supposed to be and deducted the taxes from Kentucky state+local instead of IL in the BSI 9.0 upgraded environment.

Diwakar

Former Member
0 Kudos

I have found a check box called u2018Use local placeholdersu2019 in BSI TaxFactory 9.0.d under u2018Manage dataset Optionsu2019 that was defaulted to YES when the 9.0.d client was downloaded.

Just as a process of elimination, I changed the value to NO and now the local KY02 tax is now being generated by the BSI interface..

I backed out all the other configuration changes (reciprocal overrides, etc.) that we were doing to try and get the tax to generate, and the tax is still generating.

We are going to run a bigger test population to do some regression testing in HS1 to make sure setting the flag to u2018NOu2019 does not affect other state/local taxes.

BSI provided this from User Documentation:

u2022Use Local Placeholder: Use this flag to activate or deactivate the usage of non-taxing local jurisdiction in reciprocal calculations.

In 8.0, this was set to 'no' for our system. Has anyone used this check box and if so, can you share your experiences?

Gayle Skinner

0 Kudos

Please disregard this message. I opened a new discussion thread instead.

Edited by: Thomas Campbell on Jul 19, 2011 12:21 PM

Former Member
0 Kudos

Can an SAP HR Consultant please share with me their most difficult experience or situation at work ever since the start of their career in consulting role.

Thanks

Andy

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Andy,

Could you please open a separate thread about this topic?

Thanks,

Felipe

Former Member
0 Kudos

Hi Filipe,

I previously opened a new thread for the question but no one respond to my question. I will be glad if you can share your own experinence with me.

Regards,

Andy

Former Member
0 Kudos

Hi,

Open a mew topic please i promise to share my own.

Regards,

Aiye

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Community,

We are restructuring the wiki pages for BSI with more useful contents. We just finished a wiki page about BSI TF 9.0 integration with SAP ERP. Please refer this wiki for further information about this topic:

http://wiki.sdn.sap.com/wiki/display/ERPHCM/BSITaxFactory9.0

Kind regards,

Felipe Grandi

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello All,

In case you face a SYSTEM_FAILURE error after upgrading to BSI 9.0 please refer the following thread for further information:

[;

Kind regards,

Felipe

felipegrandi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello community members,

We have seen some queries about what SP level to be in order to upgrade to TF 9.0. In notes 1469857 and 1469858 is described what SP customers need to be. The main query, however, is if you are at the CLC level but not in the SP level according to the notes. In order to work with TaxFactory 9.0 you can try one of the following approaches:

a) HRSP: customers can install directly the HRSP relevant for their releases which include the packages for BSI 90. E.g.: SAPKE60061.

b) HRSP + CLC: or customers can install the Synchronization HRSP plus the Country-Legal-Change package created for their release. E.g.: Support Package SAPKE60057 and CLC SAPKE60061.

Kind regards,

Felipe