Skip to Content

BSI 10.0 and Unicode

I find it hard to believe that BSI does NOT support unicode? Are they looking to put them out of business with SAP as all installations are now unicode only?

We went through a conversion for our database from non-unicode to unicode, and cannot get this working now for the RPUBTCU0 program.

Has anyone done this and got BSI working again? We did an export/import of the BSI schema/tables and get the tomcat website working, but have an error as it doesn't think a license is installed when testing the payroll tax program, when a valid one displays on the tf10lic -v command.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Feb 27, 2017 at 06:09 PM

    Hi Philip,

    BSI TaxFactory absolutely works fine with a Unicode ECC system. We converted our ECC system to Unicode about a year ago, and there are no problems. I should point out that we do not run TaxFactory in the same database or even on the same server as ECC -- I strongly recommend against that practice. Give BSI its own server.

    What DBMS do you use for BSI? We're using SQL Server, and we installed it with the SQL_Latin1_General_CP1_CS_AS collation. This is how we initially installed BSI.

    Then, for the conversion, in the RFC Destination BSI10-US-TAX we have the target system communication type set to Unicode, with Character Conversion at Default Setting. That's really all we had to do.

    Cheers,
    Matt

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Jean E Lovitt,

      We are also getting the same error after executing the tf10server.bat file which says at thebegining

      15 - installing function RFC_PAY.

      15.. Installingfuncction RFC_HRUS..

      15 Unable to start the server: RFC_INVALID_PARAMETER - ParameterASHOST,GWHOST,MSHOST or SERVER_PORT ismisssing.

      Were u able to fix it? any suggestion helps

  • Apr 11, 2017 at 02:15 PM

    We have always run the BSI database schema within the SAP ECC database, as that is how it was originally setup back with version 6 I think, and we never ran into an issue.

    We managed to get around this by copying the tables/schema/data from the non-unicode database over to the unicode database, as SAP doesn't handle that schema on the conversion, and making sure the permissions were set correctly.

    I couldn't get a straight answer from BSI on how to "properly" set this up, as to whether it should be on its own database or integrated with the ECC system.

    Maybe on the next version, I'll convert it to be on its own.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Philip,

      BSI has always maintained that they support TaxFactory either way, i.e. as a separate schema within the SAP database, or on its own. I myself maintain that it's a best practice to use a separate server (a smallish VM instance is typically enough, so it doesn't have to be big). Doing so saves a lot of headaches. Yes, it's another server, but it's far less complicated when it's isolated from changes you make to either one.

      So does this mean your BSI system and connection are working now?

      Cheers,
      Matt