Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Upgrading Solutions Components

Depending on your system type and additional add-on products purchased, the following solution components can be upgraded or installed:

Solution Description

Solutions Framework

Provides database structures, tools, and templates. Required for all solution component installs or upgrades.

Note: Solutions Framework is deployed as part of Upgrading Longview Servers.

Longview Tax Provision

Provides database structures and settings, editors, and calculation logic for Longview Tax Provision.

Longview Task Management

Provides database structures and settings, editors, and calculation logic for Longview Task Management.

Longview Global Transparency

Provides structures, editors, and calculation logic for Longview Global Transparency.

Longview Multi-Regional Provision

Provides database structures and settings, editors, and calculation logic for Longview Multi-Regional Provision.

Longview Tax Planning

Provides structures, editors, and calculation logic for Longview Tax Planning.

Longview Close and Plan

Provides structures, editors, and calculation logic for Longview Close and Plan.

Longview Transfer Pricing

Provides structures, editors, and calculation logic for Longview Transfer Pricing.

Longview Pillar Two

Provides structures, editors, and calculation logic for Longview Pillar Two.

Note: Global Transparency and Tax Planning currently require Tax Provision or Multi-Regional Provision.  A Tax Provision system can be upgraded to use the Multi-Regional Provision product. Pillar Two, Task Management and Transfer Pricing may be installed without the Tax Provision or Multi-Regional Provision base.

The steps required to upgrade solutions components are the same steps required to install solutions components. For more information, see Installing Solution Components.

Supplemental Steps When Upgrading From a Version Prior to 22.2

As part of the upgrade to 22.2, rule merge and rule dependency files were updated to allow for multiple source files. As part of this update, the out-of-box rule merge and rule dependency files were deployed under different names.

Custom rule merge and rule dependency configuration is now stored only in the default files (RuleMerges.txt and Rule Dependencides.txt).

Depending on your system, you may see the following additional files in the config folder of the data server working directory after upgrading:

Solution Files

Tax Provision (ASC)

RuleDependencies_ASC.txt

RuleMerges_ASC.txt

RuleMerges_Common.txt

Tax Provision (IAS)

RuleDependencies_IAS.txt

RuleMerges_IAS.txt

RuleMerges_Common.txt

Multi-Regional Tax Provision (ASC)

RuleDependencies_ASC.txt

RuleDependencies_MRP_ASC.txt RuleMerges_ASC.txt

RuleMerges_Common.txt

RuleMerges_MRP_ASC.txt

Multi-Regional Tax Provision (IAS)

RuleDependencies_IAS.txt

RuleDependencies_MRP_IAS.txt

RuleMerges_IAS.txt

RuleMerges_Common.txt

RuleMerges_MRP_IAS.txt

Global Transparency

RuleDependencies_GT.txt

RuleMerges_GT.txt

Pillar Two

RuleDependencies_P2.txt

RuleMerges_P2.txt

Close and Plan

RuleDependencies_CPM.txt

RuleMerges_CPM.txt

To create a custom rule merge and rule dependency, complete the following steps:

  1. Open PowerShell in the data sever working directory.

  2. Execute the following command: .\CreateCustomRulesFiles.ps1.

  3. The PowerShell script will perform the following:

    1. Backup the RuleDependencie.txt file to old_RuleDependencies.txt.

    2. Backup the RuleMerges.txt file to old_RuleMerges.txt.

    3. Read in the out of box rule files for merges and dependencies.

    4. Generate a RuleDependecies.txt containing only custom rule dependencies configuration.

    5. Generate a RuleMerges.txt containing only custom rule dependencies configuration.

  4. If there is no custom rule dependency configuration, the RuleDependencies.txt file will not be generated.

  5. If there is no custom rule merge configuration, the RuleMerges.txt file will not be generated.

  6. If you have configured FILES_CUSTOM_ROOT_PATH in the Longview data server configuration file (lvsrvr.cfg):

    1. Move the RuleDependencies.txt file, if any, from the data server working directory to the location specified by FILES_CUSTOM_ROOT_PATH.

    2. Move the RuleMerges.txt file, if any, from the data server working directory to the location specified by FILES_CUSTOM_ROOT_PATH.

  7. Once you are satisfied that the custom rules files are correct, you can delete the old_RuleDependencies.txt and old_RuleMerrges.txt files from the data server working directory.

  8. You can also delete the CreateCustomRulesFiles.ps1 script.

 

If you need to rerun the custom rule file creation for some reason:

  1. Delete the generated RuleDependencies.txt and RuleMerges.txt files if they exist.

  2. Rename old_RuleDependencies.txt to RuleDependencies.txt.

  3. Rename old_RuleMerges.txt to RuleMerges.txt.

  4. Execute the steps to create a custom rule merge and rule dependency file.
Published:

Upgrading Solutions Components

Depending on your system type and additional add-on products purchased, the following solution components can be upgraded or installed:

Solution Description

Solutions Framework

Provides database structures, tools, and templates. Required for all solution component installs or upgrades.

Note: Solutions Framework is deployed as part of Upgrading Longview Servers.

Longview Tax Provision

Provides database structures and settings, editors, and calculation logic for Longview Tax Provision.

Longview Task Management

Provides database structures and settings, editors, and calculation logic for Longview Task Management.

Longview Global Transparency

Provides structures, editors, and calculation logic for Longview Global Transparency.

Longview Multi-Regional Provision

Provides database structures and settings, editors, and calculation logic for Longview Multi-Regional Provision.

Longview Tax Planning

Provides structures, editors, and calculation logic for Longview Tax Planning.

Longview Close and Plan

Provides structures, editors, and calculation logic for Longview Close and Plan.

Longview Transfer Pricing

Provides structures, editors, and calculation logic for Longview Transfer Pricing.

Longview Pillar Two

Provides structures, editors, and calculation logic for Longview Pillar Two.

Note: Global Transparency and Tax Planning currently require Tax Provision or Multi-Regional Provision.  A Tax Provision system can be upgraded to use the Multi-Regional Provision product. Pillar Two, Task Management and Transfer Pricing may be installed without the Tax Provision or Multi-Regional Provision base.

The steps required to upgrade solutions components are the same steps required to install solutions components. For more information, see Installing Solution Components.

Supplemental Steps When Upgrading From a Version Prior to 22.2

As part of the upgrade to 22.2, rule merge and rule dependency files were updated to allow for multiple source files. As part of this update, the out-of-box rule merge and rule dependency files were deployed under different names.

Custom rule merge and rule dependency configuration is now stored only in the default files (RuleMerges.txt and Rule Dependencides.txt).

Depending on your system, you may see the following additional files in the config folder of the data server working directory after upgrading:

Solution Files

Tax Provision (ASC)

RuleDependencies_ASC.txt

RuleMerges_ASC.txt

RuleMerges_Common.txt

Tax Provision (IAS)

RuleDependencies_IAS.txt

RuleMerges_IAS.txt

RuleMerges_Common.txt

Multi-Regional Tax Provision (ASC)

RuleDependencies_ASC.txt

RuleDependencies_MRP_ASC.txt RuleMerges_ASC.txt

RuleMerges_Common.txt

RuleMerges_MRP_ASC.txt

Multi-Regional Tax Provision (IAS)

RuleDependencies_IAS.txt

RuleDependencies_MRP_IAS.txt

RuleMerges_IAS.txt

RuleMerges_Common.txt

RuleMerges_MRP_IAS.txt

Global Transparency

RuleDependencies_GT.txt

RuleMerges_GT.txt

Pillar Two

RuleDependencies_P2.txt

RuleMerges_P2.txt

Close and Plan

RuleDependencies_CPM.txt

RuleMerges_CPM.txt

To create a custom rule merge and rule dependency, complete the following steps:

  1. Open PowerShell in the data sever working directory.

  2. Execute the following command: .\CreateCustomRulesFiles.ps1.

  3. The PowerShell script will perform the following:

    1. Backup the RuleDependencie.txt file to old_RuleDependencies.txt.

    2. Backup the RuleMerges.txt file to old_RuleMerges.txt.

    3. Read in the out of box rule files for merges and dependencies.

    4. Generate a RuleDependecies.txt containing only custom rule dependencies configuration.

    5. Generate a RuleMerges.txt containing only custom rule dependencies configuration.

  4. If there is no custom rule dependency configuration, the RuleDependencies.txt file will not be generated.

  5. If there is no custom rule merge configuration, the RuleMerges.txt file will not be generated.

  6. If you have configured FILES_CUSTOM_ROOT_PATH in the Longview data server configuration file (lvsrvr.cfg):

    1. Move the RuleDependencies.txt file, if any, from the data server working directory to the location specified by FILES_CUSTOM_ROOT_PATH.

    2. Move the RuleMerges.txt file, if any, from the data server working directory to the location specified by FILES_CUSTOM_ROOT_PATH.

  7. Once you are satisfied that the custom rules files are correct, you can delete the old_RuleDependencies.txt and old_RuleMerrges.txt files from the data server working directory.

  8. You can also delete the CreateCustomRulesFiles.ps1 script.

 

If you need to rerun the custom rule file creation for some reason:

  1. Delete the generated RuleDependencies.txt and RuleMerges.txt files if they exist.

  2. Rename old_RuleDependencies.txt to RuleDependencies.txt.

  3. Rename old_RuleMerges.txt to RuleMerges.txt.

  4. Execute the steps to create a custom rule merge and rule dependency file.
For an optimal Community experience, Please view on Desktop