PRTF.1 fails on TF11

We installed TF11 on our Test environment that has two product lines on it. We did the TF11 install but left the TF10 in place and our development product line was going to continue using that for a few more weeks for other testing.

The TF11 is set on our Test product line, however when we run PRTF.1 it fails and I believe it is because we don't have a system variable set for it. I can't set two DATASET variables with different values. I anyone else running both and if so how did you get around this?

Thanks in advance.

Lori

Find more posts tagged with

Accepted answers

All comments

Rommel Aquino

@lbrantley Most of the configuration I saw is that the DATASET for all BSI instance is set to the same name. Most of them are set to DEFAULT. In Windows, you will be getting error when you add another variable DATASET and it would not allow you.

The advantage of having the same DATASET name for all BSI instance is that you don't need to create another variable and it will recognized what DATASET you have for that BSI instance. I don't think it would cause any impact to each database since every instance of BSI has it's own DB instance/schema.

One more thing is we have the msgmnt that control what version to look at. If you have DEFAULT DATASET in TF10 then created the same DATASET for TF11 and switched to TF11 in msgmnt, it will look for the DEFAULT DATASET configured in it's own instance/schema of database.

bhillz

Just to be clear: you have one environment which has two product lines in it (TEST with TF11 and DEV with TF10).

I can't speak for Windows, but on Unix, you can change product lines via ". cv <prod_line>"

Each product line should have it's own DATASET value, +and+ DATABASE connection stings and TAXFACTORY code directory. Each product line would need different ones as they have difference BSI Code set.

Each product line would then have different code sets to pull the Taxfactory code from, and connect to the correct BSI database.

To muddy the water, the DATASET value +could+ be the same (DEFAULT), but that depends if the DEFAULT schema is defined in the TF10 database and the DEFAULT schema is defined in the TF11 database.

Note: managing CTPs and the correct patch compatibilities may be difficult in such a setup.

Legacy Contributor

Yes, I think that is our issue, the DATASETS are not the same. Our old 10 Dataset is not set to DEFAULT, but to TF10, our TF11 DATASET is set to DEFAULT, so not sure what I can do, short of redoing the DATASET on our TF10 instance?

Legacy Contributor

Yes, one environment, two product lines, and two TaxFactory versions. And each TF version has a different DATASET name. So I do have the DATASET variable set to TF10 which is for the old 10 version and that is working. And I did create the TF11_CONNECT_STRING variable, but because my DATASET's are different that is where the issue comes in.

serafino

DATABASE and DATASET need to be configured correctly for the environment, as others have said. You also need to have TAXFACTORY set to the root directory of the BSI tax software. Finally, you need to go into msgmnt for your producline, category PRTFX, and set message 700 to "TF11" (it's probably set to TF10). Lastly, you need to recompile the tax library by running "cmptfx<database>11". I am running Oracle, so I would use "cmptfxora11".

If you make changes to DATABASE, DATASET, or TAXFACTORY, you need to restart your environment before running cmptfxora11. After the library is linked, run the program PRTF to verify the software is talking to BSI and the database correctly. Run all the tests to make sure it is working correctly.

Legacy Contributor

Thanks Sal. I do have it working now. I did have everything set up correctly for the database and DATASET, and had changed my Env Variable "DATASET" to use DEFAULT, and had stopped the application services during the process of applying the CTP, but I had not restarted the server. Once I did that, the new variable and the change in the DATASET variable were being set and both product lines are working with their respective TF versions. We are windows, so don't need to run the cmptfx command.

Thanks everyone.

Lori

Legacy Contributor

Hi Lori - out of curiosity - are you on prem or SaaS BSI?

Legacy Contributor

We are on premise.

Copyright © 2025 Infor. All rights reserved.