Hello, Larry -
Since the message is specific to BSI TF data, this would not be an issue with SAP tables. So when you look at the mapped/unmapped tax authorities in BSI, what does this show?
In our system, I always map the authorities each time we apply TUBs. I run a test sync and check the warning messages so that I know the four character SAP code to use. Then I map in BSI as shown in the image below. Hope this helps!
Thanks Anna, I really appreciate your helping me.
We found in BSI where we would add the Tax Code, per your screen shots, but none of the Tax Authorities are mapped. This is so strange for 2 reasons.
- How can the payroll program be producing correct results for all of our tax authorities, yet none are mapped in BSI?
- Why does the Synchronize Payroll Tax Data program show all of our authorities are mapped, except for the one we need to add.
I sat with my basis person (who has access to BSI software) and we checked all instances for BSI (DEV, QA and Production) and all have no mappings present.
If you can answer this, I’ll be happy to buy you lunch someday.
Larry
Hello, Larry -
This is very bazaar since in my experience, BSI returns error messages when the SAP tax code is passed and no mapping exists. So in the BSI interface that SAP builds the ADC TC: will have the two to four character code and that is used by BSI to determine the tax authority via the mapping in BSI. So I am curious what the BSI interface looks like prior to the call to BSI. I am also curious as to what the BSI Messages and Status has after the call is completed.
Just to see what would happen in our test system, I removed the mapping for IN05 and ran an employee with IN05 set as residence tax area. I got the following in BSI Messages and Status:
All other taxes processed as expected - FED and IN - but the only WT's generated for IN05 are the /3xx, /6xx and /7xx.
So this is the standard but maybe you have something custom that is happening for the BSI interface.
What ever you do, do not click on the "create default mapping" for tax types or tax authorities.
I also ran the sync tool to see what would happen - I got that there are no missing mappings. HA!
Hope this helps but it seems you have opened a can of worms... But at least you don't owe me a lunch. Darn!
Best regards, Anna
Hello, Larry -
One more thought on this... if you have multiple BSI datasets, make sure you are looking at the one for the SAP client you are using. We have a lot of old datasets that are no longer used and these are not kept up to date.
Best regards,
Anna
Can someone at BSI explain why there is no correlation between
the BSI web release package and system tools for Tax Locator? This is somewhat
annoying in determining if we have the most recent package installed. Unless I
have a translation table saved I can’t tell by looking at the notice and system
tools. For Regulatory Bulletins and Cyclic releases this isn’t a problem
because they are one for one.
| BSI Website | BSI System |
Regulatory Bulletin | BSI TaxFactory™ Release 10.0 Regulatory Bulletin Number | Regulatory bulletin is : 77 |
Cyclic Release | BSI TaxFactory™ 10.0.k Cyclic Bulletin | Cyclic is : K |
Tax Locator | TFL10079.pkg | Locator package is : 37 |
Thanks,
Greg
Hello Anna,
I sat with Basis again and we verified all our setting to ensure we are pointing to the correct BSI data set, and all looks good. For your curiosity, the below is provided:
I have already submitted an Incident to SAP and I will wait to see what they have to say.
Thanks again for your time and I will buy your lunch anyways. Will be at ASUG next week, look me up.
Larry
We are getting message 1005 that our request to use Formula 2 for WA is not allowed. We cannot determine where this is coming from as wherever we check, we are using Formula 1. Can you please advise what we have missed.
Most appreciated.
Connie
Hi everyone,
Wondering if anyone is encountering the following warning message in BSI :
2103 - FINAL PAYCHECK NET AMOUNT WAS NOT CALCULATED BECAUSE GROSS WAGES AMOUNT WAS NOT PROVIDED.
I am not finding much information on this message...any feedback would be appreciated.
Thanks,
Evelyn
Hello,
Has anyone had issues installing the latest (mandatory) Cyclic "L"?
Our Basis Team installed Cyclic "L" in our test system (appeared successful from their side) but both the SM50 connection and RPUBTCU0 are failing. Basis also noticed the file size between Cyclic K and L appeared significantly different. We reverted back to "K" and that works fine so it appears to be related to "L" somehow.
We had already upgraded to the new SAP NetWeaver RFC Library back in April. We did submit a ticket to BSI and they initially referenced that the error occurs because the new RFC Libraries are not being found by the application and to look at Note 2219445. However, after updating them that we are on the latest RFC Libraries; Version 39 released on 04/20/2016, they advised that we should submit an Incident to SAP and identify we are on this version of RFC Libraries and Note 2219445 so they can provide us with assistance. The deadline for this Cyclic is June 23rd.
Any assistance is greatly appreciated!
Stacey
At first glance...
Check the executables named in your tf10server batch files. Make sure you're calling the new exe and that the name is correct.
If that looks good, enable debug mode, check the RFC again, then review the contents of the debug log file on the server from which you ran the RFC test.
mike
BSI has reverted the executable back to tf10server.exe. In cyclic J & K the executable was changed to tf10server_new.exe.
Mike, thank you for your response. However, we use Linux rather than Windows. Here is a screenshot from our TF10server.csh.
Any suggestions?
Thank you,
Stacey
Stacey DeGarmo wrote:
Mike, thank you for your response. However, we use Linux rather than Windows. Here is a screenshot from our TF10server.csh.
Any suggestions?
Thank you,
Stacey
With cyclic L I had to add the NWRFCSDK path to LD_LIBRARY_PATH within tf10server.csh and tf10server.ksh scripts. In our case, this is how we set that environment variable:
setenv LD_LIBRARY_PATH /oracle/DCA/11204/lib:/sapmnt/DCA/exe/nwfrcsdk/lib
If you use ldd to find the library dependencies for tf10server you'll see that it needs to have libsapnwrfc.so available now. That wasn't the case with the previous version.
Also, if you set all 4 environment variables listed in the script at the command line and then execute tf10server.csh manually you should see if there is a library dependency issue. If there is no response at the command line then the script is working correctly. The RFC connection test should be successful at that point.
Regards,
Mike
Alicia...I think that local option in version 9 was never meant to be permanent (although we left it on because it worked). If you go to the BSI website and look at TF 10 user documentation, there's an entire document called the "Basic Local Reciprocity Feature Overview". I can't seem to cut and paste in here, but the document basically indicates this is a Feature and doesn't say anything about it not being a permanent solution.
It says "BSI TaxFactory has been enhanced to provide an option to process basic local reciprocity".
We wouldn't have been able to go live with version 10 without that option because we had many issues with local taxes in OH, KY, IN, etc where employees worked in one state and lived in the other.
John -
I will definitely check that out. We had those same issues but we were able to create overrides to make everything work for us during the BSI 10 upgrade. I wasn't involved at the beginning of the BSI 10 upgrade, but had to come in at the end to help get it moved forward. By that time we were so far behind and just made it work the best we could. The NEXUS entries did not work for us for most tax authorities, but we had a few that we had to create. 99% of our changes were made in the BSI override settings.
Andrew, those two notes only apply to SAP version 470. We are on 604.
Alicia,
When you did the overrides, did you have to configure Employee Override Groups in SAP and then also in Tax Factory? I still need to try that to fix our DC\MD issues.
Hi John,
Which Support Package you are on for 604?
Tarcisio
For the SAP_HR components we are on release 604, SP 93
For the EA_HR components, we are on release 607, SP 44
Hello John
You can check this SAP note below:
2198687 - TAX: Taxes reciprocity is not being set correctly for gross up payments
This note is valid for the following support packages:
SAPK-60476INSAPHRCUS - SAPK-60497INSAPHRCUS
Cheers!
