BSI Connectivity

Hi all,
We are upgrading to ECC 6.0 from 4.6 C
we would like to test the payroll scenarios in the ECC version.
Unfortunately, for the ECC 6.0 the BSI has not been connected.  Rest of all the configuration has been moved from 4.6c to ECC 6.0.  Could any one let me know how to make the connectivity to BSI. 
Any help on this will be highly appreciated.

To implement BSI 8.0 (the last one) SAP delivered notes that explains how to do that.
1064089 - Installing TaxFactory 8.0, but not as an upgrade.
1022656 - Upgrading to TaxFactory 8.0 from TaxFactory 7.0.
1068271 - FAQ: TaxFactory 8.0 Inst./Upgrade Troubleshooting.
Please check which one is more applicable to your scenario and go thru.
Cheers
Márcio Leoni

Similar Messages

  • US Payroll upgrading from Ecc 5.0 to Ecc 6.o

    Hi Experts
    My client want to upgrade from Ecc 5.0 to Ecc 6.0 for all modules including US payroll.
    please advise me what are the tables in i need to take care? means i need to have copy for double check?
    Is any tables which was there in Ecc 5.0 and not available in Ecc 6.0?
    I know that we need to have the backup of table T512w and T5uj tables, Apart from these table what other tables i need to check and have backup for double check?
    Thanks in advance
    Regards

    Use following...Good luck...
    Tables:
    T52D2     This table is used to store processing class values
    T512W     In this table, we want to check if someone made changes to the wage types in the SAP name range. We will therefore compare the wage types (only for country code = 10) in the SAP name range (/, M, B*) between two systems.
    T512T     In this table, we want to check if someone made changes to the wage types in the SAP name range. We will therefore compare the wage types (only for country code = 10) in the SAP name range (/, M, B*) between  two systems
    T77S0     For table T77S0, we want to compare the switches that were changed in the SAP name range between  two systems.
    T511K/P     For these tables, we want to check which constants in the SAP name range were changed that may be reset back to standard.
    T591A     For table T591A, we want to check which time constraints and subtypes have been changed, created and deleted
    T52EL/Z     For these tables we want to check if any posting attributes of wage types in the SAP name range have been altered.
    T556U     This table has a delivery class of E which means that SAP and the customer shares this table but with separate name ranges.
    T52D7     This table has a delivery class of E which means that SAP and the customer shares this table but with separate name ranges. Customers are supposed to use name range /9** and 1*** - 9***. This table is used to group wage types.
    T54C3     This table has a delivery class of E which means that SAP and the customer shares this table but with separate name ranges. Customers are supposed to use name range /9** and 1*** - 9***. This table is used cumulate wage types.
    T52OCR     This table is used to store off-cycle reasons.
    Tax Reporter tables     Verify the tax reporter configuration tables to make sure that the standard entries were not changed and overwritten.
    Programs:
    RPUMKG00     Re-generate all features
    RPUBTCU0     Validate BSI connectivity for tax calculation
    RHTTCP77     Table configuration needed for process models
    RHSOBJCH     Table configuration needed for process models
    RPUCT700     Generate all payroll functions and operations
    Arti

  • Payroll - Technical wagetypes not appearing on some empleyees payroll log

    Hi experts
    I am running a payroll. My problem is that some technical wagetypes dont appear on the payroll log of some employees eg /400 (tax). How can i fix the problem.
    Your assistance will be appreciated.

    Hello mathias ,
    The information provided is not sufficient to answer your questions. But since you have mentioned about /400 series, this means  tax wage type series. Have you configured Tax model, BSI connection etc.
    Arti

  • BSI server RFC connection

    I am trying to setup an RFC connection to BSI server. I looked up the SAP notes which said that I need to point my connection to a file called TF80SERVER.exe.
    I downloaded the client/server files from the BSI website but it did not have this file(TF80SERVER.EXE). On contacting BSI support, they said a file ; 'TF8API.DLL' needs to be copied to the c:\windows\system\ folder. The RFC connection should point to this file.
    I did exactly as directed. but I still get a communication failure with the message that the DLL file is not registered. I have hit a hard wall here because I cannot find any documentation to help me make it work. Please help.

    You may want to check with BASIS people who load / set up BSI dbase on the server site. Depending on the OS of the appl server, BSI executable could have different name (e.g. for UNIX, it's tf80server) . 
    When configuring RFC connection, in technical setting tab, you need to key in the script to trigger BSI (e.g. /usr/sap/.../tf80server.ksh). In this script, it would define the dbase instance, library path, ... prior to actually executing
    tf80server. This  script is pre-delivered by SAP, and you just have to twig it to fit your need.
    Rgds.

  • BSI ConnectToDataSet...failed

    Hi
    We have a problem with the BSI, we had been getting a dump "RFC_ERROR_SYSTEM_FAILURE", I followed the SAP Note 1068271 for the debug, and the result is:
    =Thu Jan 22 11:53:37 2009
    =SAP AG, Walldorf - Business API for BSI TaxFactory 8.0
    =RfcAccept called
    =Mapping ABAP RFC_PAYROLL_TAX_CALC_US_80 to C function srv_Payroll_Tax_Calc_US_80
    =Mapping ABAP RFC_HR_TAXLOCATOR_US_80 to C function srv_hr_taxlocator_us_80
    =Waiting for ABAP function calls
    =Running function srv_Payroll_Tax_Calc_US_80
    =Loading import parameters
    =Loading export parameters
    =Loading internal tables
    =Calling Payroll_Tax_Calc_US
    =Running Connect_DB_Payroll_Tax_Calc_US
    BSI dataset                  -> 110
    ConnectToDataSource...Succeeded 
    ConnectToDataSet...failed 
    Error String ->  7777 - [Oracle][ODBC][Ora]ORA-00933: SQL command not properly ended
    =RFC error
    operation/code Connect_DB_Payroll_Tax_Calc_US
    key RFC_ERROR_SYSTEM_FAILURE
    status
    message See RFC trace file or SAP system log for more details
    internal status
    The RFC under sm59 is working fine, the error is on the connection to the Dataset according to the Debug log "ConnectToDataSet...failed".
    I don't know what to check about the Dataset, could you please help me?
    Best Regards

    Yes, it's correct.
    I checked it's 8.0.
    I think is a problem with the parameters under tf80server.bat.
    SET
    TF80_CONNECT_STRING=DSN=;UID=;PW
    D=;
    SET TF80_SCHEMA_NAME=.TF80
    REM for SAP trace debugging, uncomment below & see file
    errors.txt in gateway working directory
    REM C:\BSI\TAXFACTORY\tf80serverdebug.exe %*
    REM else for usual operation
    C:\BSI\TAXFACTORY\tf80server.exe %*
    I don't know what is the "ODBC_DSN_NAME"
    I have the user, password, the database name...
    Best Regards

  • BSI Tax Factory Upgrade 8.0 to 9.0

    Hi BSI,
    We are upgrading our BSI tax Factory from 8.0 to 9.0. We are running:
    Windows 2008 R2
    SQL Server version 10.50.1777
    I'm able to connect to the database using login TF90 through SQL Server Management Studio, the ODBC Data Source Administrator and the TaxFactory Client is connecting fine too.
    But when running report RPUBTCU0 from the SAP system , its caught under ABAP dump-> SYSTEM FAILURE.
    Looking at the error.txt.
    =Running connect_db_taxfactory
    BSI dataset                  -> 101
    ConnectToDataSource... Starting 
    ConnectToDataSource...Succeeded 
    Connect to Dataset Error string =  101
    ConnectToDataSet... Starting 
    ConnectToDataSet...failed 
    Error String ->  4020 - THERE IS NO VALID LICENSE INSTALLED FOR HOST HCA-MSAP68:UNKNOWN.
    =RFC error
    operation/code connect_db_payroll_tax_calc_us
    key RFC_ERROR_SYSTEM_FAILURE
    status
    message See RFC trace file or SAP system log for more details
    internal status .
    The machine key is successfully installed.
    Please guide what we are missing here.
    Please contact me at +60123675076 (malaysia) at anytime.
    Thanks.
    Thava

    We managed to solve this by changing tf90server.bat file.
    from - I:
    CD I:\BSI\Server9.0
    tf90server.exe %*
    To - I:\BSI\Server9.0\tf90server.exe %*
    Now we could run report RPUBTCU0 without error.
    Thanks.
    Thava

  • BSI Tax Factory 9.0 Upgrade

    Can folks give me an idea what kind of timelines they are facing to upgrade from BSI 8.0 to 9.0 assuming HR SPs and TUBS required?  I am trying to get a rough scope (weeks, months) for planning purposes.

    Hello All
    We are upgrading TaxFactory from 8 to 9 by following the SAP note 1469858.
    when we run the report RPUBTCU0, SAP system is giving system failure error. We are in contact with BSI support but no use, as suggested by them we have changed the password of user ID (OS user) tf90 to password bsi and it did not work.
    With our tf90 Os user ID and password abcdef, we are able to connect to tf90 database but when we run report RPUBTCU0, it is throwing system failure dump.
    Please advice on the below error message.
    Thanks
    Hinge
         db2 connect to TF90 user tf90 using abcdef
       Database Connection Information
    Database server        = DB2/AIX64 9.1.2
    SQL authorization ID   = TF90
    Local database alias   = TF90
          tf90lic -i tf90license.txt
    ConnectToDataSource() failed: 7777 - [IBM][CLI Driver] SQL30082N  Security processing failed with reason "3" ("PASSWORD MISSING").  SQLSTATE=08001
          more tf90server.csh
    #!/bin/csh
    #tf90server.csh: Set execution environment for SAP TaxFactory 9.0
    Set your DB2/UDB environment variables
    Remember to grant database rights to the user invoking this
    setenv DB2INSTANCE db2sid     #Replace with your DB2 unix instance owner
    setenv DB2DBDFT    TF90       #Replace with your DB2 Database Name
    setenv DATABASE    TF90       #Replace with your DB2 Database Name
    setenv DB2USER     tf90       #Replace with your DB2 User ID
    setenv PASSWD      abcdef  #Replace with your DB2 Password
    Change directory to the TaxFactory Server Directory
    Set the TaxFactory Default Database connection
    cd /sapmnt/SID/exe
    For SAP Trace Debugging, Uncomment Below & Refer to /tmp/error.txt
    ./tf90server $1 $2 $3 -o /tmp/error.txt
    log of /tmp/error.txt:
    =Running function srv_payroll_tax_calc_us_90
    =Loading import parameters
    =Loading export parameters
    =Loading internal tables
    =Calling payroll_tax_calc_us
    =Running connect_db_taxfactory
    BSI dataset                  -> 030
    ConnectToDataSource... Starting 
    ConnectToDataSource...failed 
    Error String ->  7777 - [IBM][CLI Driver] SQL30082N  Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"
    ).  SQLSTATE=08001
    =RFC error
    operation/code connect_db_payroll_tax_calc_us
    key rfc system error raised
    status
    message for more information: see tracefile dev_rfc
    internal status
    dev_rfc log file:
    Trace file opened at 20110314 085512 EDT SAP-REL 640,0,162 RFC-VER 3 878571
    ======> CPIC-CALL: 'CMACCP'
    LOCATION    SAP-Gateway on host xxxxxx / sapgw03
    ERROR       Conversation 88399050 not found
    TIME        Mon Mar 14 08:55:12 2011
    RELEASE     700
    COMPONENT   SAP-Gateway
    VERSION     2
    RC          728
    MODULE      gwxxrd.c
    LINE        6254
    COUNTER     3664

  • BSI upgrade from 8.0 to 9.0

    Hi Experts,
    New BSI Tax factory 9.0 has been released recently. I would like to know what are the steps needed to upgrade tax factory from 8.0 to 9.0.
    I have gone through SAP Note 1469858 for details and found that major activities are related to basis. Can somebody help to determine what is the functional impact on payroll due to this upgrade.
    Looking forward for your responces.
    Regards,
    Ooba

    Hello All
    We are upgrading TaxFactory from 8 to 9 by following the SAP note 1469858.
    when we run the report RPUBTCU0, SAP system is giving system failure error. We are in contact with BSI support but no use, as suggested by them we have changed the password of user ID (OS user) tf90 to password bsi and it did not work.
    With our tf90 Os user ID and password abcdef, we are able to connect to tf90 database but when we run report RPUBTCU0, it is throwing system failure dump.
    Please advice on the below error message.
    Thanks
    Hinge
         db2 connect to TF90 user tf90 using abcdef
       Database Connection Information
    Database server        = DB2/AIX64 9.1.2
    SQL authorization ID   = TF90
    Local database alias   = TF90
          tf90lic -i tf90license.txt
    ConnectToDataSource() failed: 7777 - [IBM][CLI Driver] SQL30082N  Security processing failed with reason "3" ("PASSWORD MISSING").  SQLSTATE=08001
          more tf90server.csh
    #!/bin/csh
    #tf90server.csh: Set execution environment for SAP TaxFactory 9.0
    Set your DB2/UDB environment variables
    Remember to grant database rights to the user invoking this
    setenv DB2INSTANCE db2sid     #Replace with your DB2 unix instance owner
    setenv DB2DBDFT    TF90       #Replace with your DB2 Database Name
    setenv DATABASE    TF90       #Replace with your DB2 Database Name
    setenv DB2USER     tf90       #Replace with your DB2 User ID
    setenv PASSWD      abcdef  #Replace with your DB2 Password
    Change directory to the TaxFactory Server Directory
    Set the TaxFactory Default Database connection
    cd /sapmnt/SID/exe
    For SAP Trace Debugging, Uncomment Below & Refer to /tmp/error.txt
    ./tf90server $1 $2 $3 -o /tmp/error.txt
    log of /tmp/error.txt:
    =Running function srv_payroll_tax_calc_us_90
    =Loading import parameters
    =Loading export parameters
    =Loading internal tables
    =Calling payroll_tax_calc_us
    =Running connect_db_taxfactory
    BSI dataset                  -> 030
    ConnectToDataSource... Starting 
    ConnectToDataSource...failed 
    Error String ->  7777 - [IBM][CLI Driver] SQL30082N  Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"
    ).  SQLSTATE=08001
    =RFC error
    operation/code connect_db_payroll_tax_calc_us
    key rfc system error raised
    status
    message for more information: see tracefile dev_rfc
    internal status
    dev_rfc log file:
    Trace file opened at 20110314 085512 EDT SAP-REL 640,0,162 RFC-VER 3 878571
    ======> CPIC-CALL: 'CMACCP'
    LOCATION    SAP-Gateway on host xxxxxx / sapgw03
    ERROR       Conversation 88399050 not found
    TIME        Mon Mar 14 08:55:12 2011
    RELEASE     700
    COMPONENT   SAP-Gateway
    VERSION     2
    RC          728
    MODULE      gwxxrd.c
    LINE        6254
    COUNTER     3664

  • Error BACKINT for Oracle Connection

    hi @ maxdb gurus...
    i have a problem backing up my maxdb 7.6.0.033 (serving for a mysap.erp2005 on aix 5.3) using the backint mechanism.
    -> backup media created: two pipes and one parallel medium containing these pipes
    -> bsi.env has been created
    -> backint4sapdb.sar contains
       4 staging areas each with 4096 MB
       files per backint call 2
    -> maxdb is about 57 gb perm. data area (and 6 gb temp.)
    i use the backup wizard (dbmgui) to invoke a complete data backup which starts (pipes are created in the file system) and runs until approx. 4 gb...then the backup terminates with error "-24920 backup operation was unsuccesful. The database request failed with error -8020"
    what might be the problem? are the staging areas too small? is says that when using only one stage area it must hold the complete database...can i then conclude that 4 staging areas must hold the database as well - meaning they must be around 15 gb each?
    GreetZ, AH

    yup...but that also means that the sum of the staging areas need as much space as the database ie. around 70 gigs netto! the staging files will be filled and thus grow until the defined size, meaning that the file system(s) need to be big enough!
    everything works fine until the stage files are filled (up to the defined size) and then stops...when i change the sizes of the staging areas i can reproduce the error!
    i compared the tsm implementation of that system with another system (live cache...kind of small regarding db size...) and found nothing serious...
    -> dbm.ebp (AIX 5.3, MaxDB 7.6.0.033, ERP2005, TSM 5.3.3.0)
    2006-11-09 13:56:50
    Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.
    Using environment variable 'TMP' with value '' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2006-11-09 13:56:50
    Checking existence and configuration of Backint for MaxDB.
        Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/TDV/bsi.env' as path of the configuration file of Backint for MaxDB.
        Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB from '/sapdba/data/wrk/TDV/bsi.env' to configuration value '/sapdb/data/wrk/TDV/bsi.env'.
        Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/TDV/bsi.env'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'BACKINT' with value '/sapdb/TDV/db/bin/backint'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'INPUT' with value '/sapdb/TDV/backup/backint4sapdb.in'.
            Found keyword 'OUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.out'.
            Found keyword 'ERROROUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.err'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/TDV/backint4sapdb.par'.
            Found keyword 'TIMEOUT_SUCCESS' with value '6000'.
            Found keyword 'TIMEOUT_FAILURE' with value '300'.
        Finished reading of the Backint for MaxDB configuration file.
        Using '/sapdb/TDV/db/bin/backint' as Backint for MaxDB program.
        Using '/sapdb/TDV/backup/backint4sapdb.in' as input file for Backint for MaxDB.
        Using '/sapdb/TDV/backup/backint4sapdb.out' as output file for Backint for MaxDB.
        Using '/sapdb/TDV/backup/backint4sapdb.err' as error output file for Backint for MaxDB.
        Using '/sapdb/data/wrk/TDV/backint4sapdb.par' as parameter file for Backint for MaxDB.
        Using '6000' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using '/sapdb/data/wrk/TDV/dbm.knl' as backup history of a database to migrate.
        Using '/sapdb/data/wrk/TDV/dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2006-11-09 13:56:50
    Checking medium.
    Check passed successfully.
    2006-11-09 13:56:50
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c'.
        Created temporary file '/sapdb/TDV/backup/backint4sapdb.out' as output for Backint for MaxDB.
        Created temporary file '/sapdb/TDV/backup/backint4sapdb.err' as error output for Backint for MaxDB.
        Writing '/sapdb/TDV/backup/back-tdv-data-m10.pipe #PIPE' to the input file.
        Writing '/sapdb/TDV/backup/back-tdv-data-m11.pipe #PIPE' to the input file.
    Prepare passed successfully.
    2006-11-09 13:56:51
    Creating pipes for data transfer.
        Creating pipe '/sapdb/TDV/backup/back-tdv-data-m10.pipe' ... Done.
        Creating pipe '/sapdb/TDV/backup/back-tdv-data-m11.pipe' ... Done.
    All data transfer pipes have been created.
    2006-11-09 13:56:51
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '/sapdb/TDV/backup/back-tdv-data-m10.pipe' PIPE,'/sapdb/TDV/backup/back-tdv-data-m11.pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACK-TDV-DATA-G1'' from db-kernel.
    The database is working on the request.
    2006-11-09 13:56:51
    Waiting until database has prepared the backup.
        Asking for state of database.
        2006-11-09 13:56:51 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2006-11-09 13:56:52 Database is still preparing the backup.
        Waiting 2 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:56:54 Database is still preparing the backup.
        Waiting 3 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:56:57 Database is still preparing the backup.
        Waiting 4 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:57:01 Database is still preparing the backup.
        Waiting 5 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:57:06 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2006-11-09 13:57:06
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c >>/sapdb/TDV/backup/backint4sapdb.out 2>>/sapdb/TDV/backup/backint4sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2006-11-09 13:57:06
    Waiting for end of the backup operation.
        2006-11-09 13:57:06 The backup tool is running.
        2006-11-09 13:57:06 The database is working on the request.
        2006-11-09 13:57:11 The backup tool is running.
        2006-11-09 13:57:11 The database is working on the request.
        2006-11-09 13:57:21 The backup tool is running.
        2006-11-09 13:57:21 The database is working on the request.
        2006-11-09 13:57:36 The backup tool is running.
        2006-11-09 13:57:36 The database is working on the request.
        2006-11-09 13:57:56 The backup tool is running.
        2006-11-09 13:57:56 The database is working on the request.
        2006-11-09 13:58:21 The backup tool is running.
        2006-11-09 13:58:21 The database is working on the request.
        2006-11-09 13:58:51 The backup tool is running.
        2006-11-09 13:58:51 The database is working on the request.
        2006-11-09 13:59:21 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-8020
            Date                  :20061109
            Time                  :00135703
            Database              :TDV
            Server                :r4335
            KernelVersion         :Kernel    7.6.00   Build 033-123-130-873
            PagesTransfered       :377688
            PagesLeft             :6903331
            MediaName             :BACK-TDV-DATA-G1
            Location              :/sapdb/TDV/backup/back-tdv-data-m10.pipe
            Errortext             :end of file
            Label                 :DAT_000000017
            IsConsistent          :true
            FirstLogPageNo        :247812
            DBStamp1Date          :20061109
            DBStamp1Time          :00135651
            BDPageCount           :7280971
            DevicesUsed           :2
            DatabaseID            :r4335:TDV_20061109_135703
            Max Used Data Page    :0
            Converter Page Count  :5201
        2006-11-09 13:59:21 The backup tool is running.
        2006-11-09 13:59:22 The backup tool process has finished work with return code 2.
        2006-11-09 13:59:22 The backup tool is not running.
    The backup operation has ended.
    2006-11-09 13:59:22
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2006-11-09 13:59:22
    Cleaning up.
        Removing data transfer pipes.
            Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe ... Done.
            Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe ... Done.
        Removed data transfer pipes successfully.
        Copying output of Backint for MaxDB to this file.
        ---------- Begin of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
            Reading parameter file /sapdb/data/wrk/TDV/backint4sapdb.par.
            Using staging area /sapdb/TDV/backup/stage1 with a size of 1585446912 bytes.
            Using staging area /sapdb/TDV/backup/stage2 with a size of 1585446912 bytes.
            Using 1 file per Backint for Oracle call.
            Using /sapdb/TDV/dbs/backint as Backint for Oracle.
            Using /sapdb/TDV/dbs/initTDV.utl as parameterfile of Backint for Oracle.
            Using /sapdb/data/wrk/TDV/backint4oracle.his as history file.
            Using /sapdb/TDV/backup/backint4oracle.in as input of Backint for Oracle.
            Using /sapdb/TDV/backup/backint4oracle.out as output of Backint for Oracle.
            Using /sapdb/TDV/backup/backint4oracle.err as error output of Backint for Oracle.
            Using a maximal delay for a Backint for Oracle call of 60 seconds.
            Reading input file /sapdb/TDV/backup/backint4sapdb.in.
            Backing up pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe.
            Backing up pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe.
            Found 2 entries in the input file.
            Starting the backup.
            Starting pipe2file program(s).
            Waiting for creation of temporary files.
            1 temporary file is available for backup.
            Calling Backint for Oracle at 2006-11-09 13:59:20.
            Calling '/sapdb/TDV/dbs/backint -u TDV -f backup -t file -p /sapdb/TDV/dbs/initTDV.utl -i /sapdb/TDV/backup/backint4oracle.in -c' .
            Backint for Oracle ended at 2006-11-09 13:59:20 with return code 2.
            Backint for Oracle output:
            Backint for Oracle output:                          Data Protection for mySAP(R)
            Backint for Oracle output:
            Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
            Backint for Oracle output:              - Version 5, Release 3, Modification 2.0  for AIX LF 64-bit -
            Backint for Oracle output:                    Build: 275  compiled on Nov 20 2005
            Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2005, All Rights Reserved.
            Backint for Oracle output:
            Backint for Oracle output: BKI2027I: Using TSM-API version 5.3.3.0 (compiled with 5.3.0.0).
            Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
            Backint for Oracle output: BKI0005I: Start of program at: Thu Nov  9 13:59:20 MEZ 2006 .
            Backint for Oracle output: BKI5014E: Tivoli Storage Manager Error:
            Backint for Oracle output: ANS1035S (RC406)  Options file '*' could not be found.
            Backint for Oracle output:
            Backint for Oracle output: BKI0020I: End of program at: Thu Nov  9 13:59:20 MEZ 2006 .
            Backint for Oracle output: BKI0021I: Elapsed time: 00 sec .
            Backint for Oracle output: BKI0024I: Return code is: 2.
            Backint for Oracle output:
            Backint for Oracle error output:
            Finished the backup unsuccessfully.
            #ERROR /sapdb/TDV/backup/back-tdv-data-m10.pipe
            #ERROR /sapdb/TDV/backup/back-tdv-data-m11.pipe
        ---------- End of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
        Removed Backint for MaxDB's temporary output file '/sapdb/TDV/backup/backint4sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
        ---------- Begin of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
            Backint for Oracle was unsuccessful.
        ---------- End of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
        Removed Backint for MaxDB's temporary error output file '/sapdb/TDV/backup/backint4sapdb.err'.
        Removed the Backint for MaxDB input file '/sapdb/TDV/backup/backint4sapdb.in'.
    Have finished clean up successfully.
    i invoke the backup through dbmgui, not dbmcli!
    any clues? thx in advance!
    GreetZ, AH

  • BSI version upgrade from 8 to 9 query

    Hello All
    We are upgrading TaxFactory from 8 to 9 by following the SAP note 1469858.
    when we run the report RPUBTCU0, SAP system is giving system failure error. We are in contact with BSI support but no use, as suggested by them we have changed the password of user ID (OS user) tf90 to password bsi and it did not work.
    With our tf90 Os user ID and password abcdef, we are able to connect to tf90 database but when we run report RPUBTCU0, it is throwing system failure dump.
    Please advice on the below error message.
    Thanks
    Hinge
         db2 connect to TF90 user tf90 using abcdef
       Database Connection Information
    Database server        = DB2/AIX64 9.1.2
    SQL authorization ID   = TF90
    Local database alias   = TF90
          tf90lic -i tf90license.txt
    ConnectToDataSource() failed: 7777 - [IBM][CLI Driver] SQL30082N  Security processing failed with reason "3" ("PASSWORD MISSING").  SQLSTATE=08001
          more tf90server.csh
    #!/bin/csh
    #tf90server.csh: Set execution environment for SAP TaxFactory 9.0
    Set your DB2/UDB environment variables
    Remember to grant database rights to the user invoking this
    setenv DB2INSTANCE db2sid     #Replace with your DB2 unix instance owner
    setenv DB2DBDFT    TF90       #Replace with your DB2 Database Name
    setenv DATABASE    TF90       #Replace with your DB2 Database Name
    setenv DB2USER     tf90       #Replace with your DB2 User ID
    setenv PASSWD      abcdef  #Replace with your DB2 Password
    Change directory to the TaxFactory Server Directory
    Set the TaxFactory Default Database connection
    cd /sapmnt/SID/exe
    For SAP Trace Debugging, Uncomment Below & Refer to /tmp/error.txt
    ./tf90server $1 $2 $3 -o /tmp/error.txt
    log of /tmp/error.txt:
    =Running function srv_payroll_tax_calc_us_90
    =Loading import parameters
    =Loading export parameters
    =Loading internal tables
    =Calling payroll_tax_calc_us
    =Running connect_db_taxfactory
    BSI dataset                  -> 030
    ConnectToDataSource... Starting 
    ConnectToDataSource...failed 
    Error String ->  7777 - [IBM][CLI Driver] SQL30082N  Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"
    ).  SQLSTATE=08001
    =RFC error
    operation/code connect_db_payroll_tax_calc_us
    key rfc system error raised
    status
    message for more information: see tracefile dev_rfc
    internal status
    dev_rfc log file:
    Trace file opened at 20110314 085512 EDT SAP-REL 640,0,162 RFC-VER 3 878571
    ======> CPIC-CALL: 'CMACCP'
    LOCATION    SAP-Gateway on host xxxxxx / sapgw03
    ERROR       Conversation 88399050 not found
    TIME        Mon Mar 14 08:55:12 2011
    RELEASE     700
    COMPONENT   SAP-Gateway
    VERSION     2
    RC          728
    MODULE      gwxxrd.c
    LINE        6254
    COUNTER     3664

    Hello hingekumar,
    Please refer the thread below where many community members have contributed with hints:
    TaxFactory 9.0 Install - Short Dump - System Failure
    Please also refer the following threads:
    *BSI 8.0 becomes obsolete August 31st 2011, 9.0 troubleshooting guide here*
    US - SYSTEM FAILURE after upgrading to BSI 9.0
    Kind regards,
    Felipe

  • BSI tf90lic ERROR

    Hello All,
    We upgrade to BSI 9.0 recently and everything was successfull.
    We then upgraded our Oracle system from 10..2.0.4 to 11.2.0.2 and the BSI failed.
    So I downloaded the one for 11.2 oracle version and changed the TF90SERVER and TF90SERVER.CSH accordingly.
    But when i try to run the tf90lic I get the below error:
    cgunx201:dv2adm 52> tf90lic -v
    exec(): 0509-036 Cannot load program tf90lic because of the following errors:
            0509-130 Symbol resolution failed for tf90lic because:
            0509-136   Symbol strcat (number 106) is not exported from
                       dependent module /oracle/client/10x_64/instantclient/libclntsh.a[shr.o].
            0509-136   Symbol strcpy (number 107) is not exported from
                       dependent module /oracle/client/10x_64/instantclient/libclntsh.a[shr.o].
                 0509-192 Examine .loader section symbols with the
                     'dump -Tv' command.
    But the  /oracle/client/10x_64/instantclient/libclntsh.a file does exist in /oracle/client/10x_64/instantclient directory and has 777 permisssions.
    Please help!

    tf90server.csh
    SID is where we have our system name, i also changed it point to the new oracle home.
    #tf90server.csh: Set execution environment for SAP TaxFactory 9.0
    Set your Oracle environment variables
    Remember to grant database rights to the user invoking this
    setenv ORACLE_SID  SID              #Replace with your Oracle SID
    setenv ORACLE_HOME /oracle/SID/112_64             #Replace with your Oracle Home
    setenv LIBPATH /oracle/SID/112_64/lib                    #Replace with $ORACLE_HOME/lib
    Change directory to the TaxFactory Server Directory
    Set the TaxFactory Default Database connection
    cd /sapmnt/SID/exe
    setenv DATABASE tf90/tf90bsi                      #Replace with your Oracle Connect
    For SAP Trace Debugging, Uncomment Below & Refer to /tmp/error.txt
    ./tf90server $1 $2 $3 -o /tmp/error.txt
    ./tf90server $1 $2 $3
    Also when I try to run the BSU Tax calcuation Test program for BSi 9.0  (RPUBTCU0) it runs successfully.
    I also check the TF90 user is unlocked and the password is correct in oracle.
    But when trying to run the simulation we still get the error BSI system failure.

  • BSI Machine Key failed dut to Communication Error - Version 9.0

    Hello All,
    We upgraded to BSI 9.0 from 8.0.
    We have configured everything except for the Machine key.
    1. We downloaded the key from BSI with our hostname and FTP the file to /sapmnt/SID/exe .
    2. This is where I put the tf90lic (FTP in Ascii)
    3. I also set the env variables as
    setenv DATABASE=tf90/[email protected]
    export DATASET=DEFAULT
    4. Now when I give the command, tf90lic -i test.txt I get this error message:
    > tf90lic -i test.txt
    ConnectToDataSource() failed: 8886 - UNABLE TO CONNECT TO TF90/TF90BSI@@ORACLE10.2.0.4.0 SQLCODE RETURNED : -12154
    What am I doing wrong?

    Hello All,
    We upgraded to BSI 9.0 from 8.0.
    We have configured everything except for the Machine key.
    1. We downloaded the key from BSI with our hostname and FTP the file to /sapmnt/SID/exe .
    2. This is where I put the tf90lic (FTP in Ascii)
    3. I also set the env variables as
    setenv DATABASE=tf90/[email protected]
    export DATASET=DEFAULT
    4. Now when I give the command, tf90lic -i test.txt I get this error message:
    > tf90lic -i test.txt
    ConnectToDataSource() failed: 8886 - UNABLE TO CONNECT TO TF90/TF90BSI@@ORACLE10.2.0.4.0 SQLCODE RETURNED : -12154
    What am I doing wrong?

  • BSIS showing wrong entries

    Hello,
    At my company, they run the MR11 to check for GR/IR variances and then clear these variances using the F.13 transaction. Finally, the F.19 transaction is run to check for PO's having the GR/IR variance.
    There are some old PO's of 2005/2006 which are showing up on the F.19 report despite the fact that they have no GR/IR variance. I checked the PO's and they have no mismatches wither in GR/IR quantity or amount. 
    Some of these PO have different GR and IR dates but some others have the same date on the GR and IR. So even if it is the former case, as the F.13 clearing is done every month end, these PO's have been picked up for clearing.
    I notice that these PO's are in the BSIS table (as they belong to the GL 211005 - A/P Accrual (Goods Received/Invoice Received) and so they appear in the F.19 output. However, once the F.13 clearing is done, the entry should disappear from the BSIS table. I am not sure why it is still there in
    the table.
    Could someone please explain why these PO's still show up on the F.19 report and in the BSIS table and if there is any way to remove these entries from the F.19 report?
    Any help will be greatly appreciated.
    Thanks,
    Rugmani

    I am having this same problem! It is happening whether I am connected to WiFi or not. I have tried to reset my location settings and that did nothing. I am hoping to find a solution.

  • Table contents of BSIS

    Dear All,
    What item does table BSIS contain?
    My understanding was, it contains only Open items and when the same is cleared, these items will be moved to BSAS table. If an item to be treated as open/cleared, OPEN ITEM MANAGEMENT tick needs to be maintained in GL account master. If an account does not have this tick maintained, then the documents posted to this account will not come in BSIS table and it gets posted to BSEG table.
    Please tell me know if my understanding is wrong....
    Now, when user is trying to post a document with 2 accounts (one with open items mgmt and other without), i am getting both lines in BSIS.....I am confused.
    Can some one please clarify?
    Regards,
    Gangadhar

    Hi,
    BSEG is the common table for all posted FI documents. Additionally, you have seconday tables like BSIK, BSIS, BSID, etc. When a document is posted on G/L (not vendor/customer) it will go both to BSIS and BSEG (with no connection to open item).
    Regards,
    Eli

  • Hlep me out on providing information on BSI

    Hi Gurus,
    Please provied me information about BSI like 1) wether we need to take licence from BSI to connect to our SAP.
    2) do we need to install BSI in SAP R/3
    3) how to send the information to BSI for calculating taxes for my employee and what information we need to send like gross....
    4) what information or details we get from the BSI after calcultaing the taxes like do we get the next salary or amount of tax that need to be deducted etc...
    5) and where the data that we received from BSI will be stored.
    6) do we need to maintain any infotypes from BSI.
    Please help me out.

    Hi,
    1. BSI license comes with SAP now.
    for rest check this link -
    <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/d8/c9e93401bdee06e10000009b38f83b/frameset.htm">BSI</a>
    This is the added information -
    USTax™ Engine
    This Engine processes regular, supplemental, cumulative, etc. taxes for all federal, states, possessions and localities. A detailed description of the Engine's tax coverage follows:
    Federal Tax Coverage     State Tax Coverage
    •     Withholding Tax
    &#61607;     all required marital statuses
    &#61607;     all preferred and alternate calculation methods
    &#61607;     cumulative
    &#61607;     5 supplemental methods
    •     Employer Unemployment (FUTA)
    •     Employer and Employee Social Security
    &#61607;     3 calculation methods
    •     Employer and Employee Medicare
    &#61607;     3 calculation methods
    •     Advanced Earned Income Credit (EIC)
    &#61607;     all appropriate EIC statuses
    •     Railroad Retirement
    &#61607;     all Employee Social Security
    &#61607;     all Employer Social Security
    &#61607;     all Employee Medicare
    &#61607;     all Employer Medicare
    &#61607;     all Unemployment and Supplemental annuity      •     All Withholding Taxes
    &#61607;     all required marital statuses
    &#61607;     all preferred and alternate calculation methods
    &#61607;     cumulative
    &#61607;     10 supplemental methods
    &#61607;     all miscellaneous taxes
    •     All Occupation Taxes
    &#61607;     all miscellaneous taxes
    •     All Employer and Employee Unemployment Taxes (SUI)
    &#61607;     2 calculation methods
    &#61607;     all miscellaneous taxes
    •     All Employer and Employee Disability Taxes(SDI)
    &#61607;     2 calculation methods
    Local Tax Coverage     Possession Tax Coverage
    •     All County and City Withholding Taxes
    &#61607;     all required marital statuses
    &#61607;     all resident and nonresident formulas
    •     All City, Borough, Township, Village and Municipal Taxes
    &#61607;     all resident and nonresident formulas
    &#61607;     all maximums covered as required
    •     All Occupation Privilege Taxes
    &#61607;     all minimums covered as required
    •     All Payroll Head Taxes
    &#61607;     all maximums covered as required
    •     All School District Taxes
    •     All Transportation District Taxes      •     All withholding Taxes
    &#61607;     all required marital statuses
    &#61607;     all supplemental methods
    &#61607;     all miscellaneous taxes
    &#61607;     all preferred and alternate calculation methods
    •     All Employer Unemployment Taxes
    &#61607;     2 calculation methods
    •     All Employee Disability Taxes
    &#61607;     3 calculation methods
    •     All Employer Disability Taxes
    &#61607;     3 calculation methods
    The  USTax™Engine comes with complete override capabilities to cover your  special needs. 
    This Engine has many other capabilities, too.  Tax rates may be overridden with your tax rates.  Entire regular, supplement and/or other tax formulas may be overridden with one or more tax formulas of your own.  Your override formulas may be used for:
    •     the entire organization
    •     one or more companies
    •     one or more departments
    •     one or more employees
    •     and more
    This gives you the flexibility to use your own override formula for all employees or for specific ones, and the BSI formulas for all others.
    The Engine allows you to use override data to make adjustments for employees whose taxes have been overwithheld or underwithheld.  Employee taxes may be adjusted over any period of time, which lets   underwithheld employees catch up gradually and avoid a large one-time adjustment.  Custom tax capabilities for taxes you might need (such as Barbados taxes) are also included. An unlimited number of such custom taxes may be added.     
    ReciprocalTax™ Engine
    This Engine processes all types of reciprocal taxes for any combinations of states, possessions and localities.
    The ReciprocalTax™Engine recognizes all official (formal) reciprocal agreements that exist for taxing authorities, including those between
    •     two states
    •     a state and a county or city, or
    •     two counties and/or cities
    In addition, the ReciprocalTax™Engine recognizes all official reciprocal agreements that exist for every other possible combination of state, possession, county and city. The Engine calculates all appropriate taxes in accordance with these agreements. It also computes all reportable wages.
    In the absence of official reciprocal agreements, the Engine figures all appropriate offsets (credits) and applies them to the resident state tax. In addition to resident state offsets, the Engine calculates all tax offsets for all possessions, counties and cities, where appropriate, and applies them as required by law.
    The software computes all wage offsets and reportable wages too. In addition to official reciprocal agreements and offsets, the ReciprocalTax™Engine recognizes all other types of relationships and calculates taxes and reportable wages accordingly.
    The number of work taxing authorities that may be processed for an employee is limited only by what is practical. The Engine will process any number of work states, possessions, counties and cities for an employee.
    By far the most comprehensive available anywhere, the ReciprocalTax™Engine can recognize any of the mind-boggling tens of millions of possible state, possession, county and city combinations, and then calculate the appropriate taxes and reportable wages.
    Note: The ReciprocalTax™ engine was added to the PayrollTaxes™ application at no additional cost to our customers, increasing their value.
    Regards,
    Amit
    Reward all helpful replies.

Maybe you are looking for