Setting up the currency-initialization environment

If you set up multiple companies (multisite environment), use the Maintain Logical Tables (ttaad4120m000) session to share the CRI tables between the companies that belong to one logistic area. The tables can be linked to any company of the logistic area. After entering the required information, you must convert the data to runtime.

In general, the associated archive companies must also be converted in the CRI process (see also "Currency-Initialization Process"), which means that these associated archive companies are included in the CRI cluster.

Caution!

Unless you are certain that no data corruption will occur, you must ensure that these "frozen" companies are no longer archived. You must also verify that no intercompany data links exist between the live and the archive environment. If such links exist, you must include the archive companies in the live CRI cluster.

For more information about logistic areas, see "Currency Systems and Company Structures."

The companies must share these tables:

  • CI Rates (tccri700)
  • CI Process Data (tccri701)
  • CI Process Data Internal Conversion (tccri702)
  • CI Clusters (tccri711)
  • CI Cluster Companies (tccri712)
  • CI Cluster Transaction Currencies (tccri715)
  • CI Error Log CI (tccri720)
  • CI Conversion Fields (tccri721)
  • CI Conversion Tables (tccri722)
  • CI Conversion Tables by Cluster Companies (tccri725)
  • CI Cluster Conversion Tables Update Groups (tccri726)
  • Conversion Progress Log (tccri730)

These tables must not be shared:

  • Audit Finalized Transactions (tccri703)
  • Audit Open Items Purchase (tccri704)
  • Audit Open Items Sales (tccri705)

Refer to table set R00900 – Table Sets (tltsm1100m000) session for possible additional sharing details. You can use a demo company to explore the CRI sessions before you start currency initialization for your production company