When you copy your production environment and use that copy as a test environment, you should not link the Isah production environment to the test environment of your financial application, or the other way around. There is an easy way to avoid this problem: Use the Financial databases form to link the logistic databases (production or test databases) to the financial databases (production or test databases).
The processes for assigning database codes and exporting data only use active financial databases and refer to the logistic database from which the process is started.
Tip: In the production environment, populate the Financial databases and Business code by database forms with data for the production environment as well as the test environment. When you then make a copy to a test environment, the required data will be available straight away.
Example Financial databases
Line |
Database |
Financial database code |
Description |
Active |
5 |
ProductionDB |
PROD12 |
Production Inc. 2012 |
Yes |
6 |
ProductionDB |
VKBIN12 |
Domestic Sales Inc. 2012 |
Yes |
7 |
ProductionDB |
VKBUIT12 |
International Sales Inc. 2012 |
Yes |
8 |
TestProductionDB |
TESTPROD12 |
TEST Production Inc. 2012 |
Yes |
9 |
TestProductionDB |
TESTVKBIN12 |
TEST Domestic Sales Inc. 2012 |
Yes |
10 |
TestProductionDB |
TESTVKBUIT012 |
TEST International Sales Inc. 2012 |
Yes |
Example Business code by database
Company code |
Description |
Fiscal year |
Database |
Financial database description |
10 |
Production Inc. |
2012 |
5 |
Production Inc. 2012 |
10 |
Production Inc. |
2012 |
8 |
TEST Production Inc. 2012 |
20 |
Domestic Sales Inc. |
2012 |
6 |
Domestic Sales Inc. 2012 |
20 |
Domestic Sales Inc. |
2012 |
9 |
TEST Domestic Sales Inc. 2012 |
30 |
International Sales Inc. |
2012 |
7 |
International Sales Inc. 2012 |
30 |
International Sales Inc. |
2012 |
10 |
TEST International Sales Inc. 2012 |