To make the general setup of a new project easier, you can use the A.20.02 Copy Admin Setup screen to copy setup data from an existing project (source) to the new project (target). You must be logged in with the new project where you want the setup data to be copied into.
Select the source project from the LOV, and click the Run query 
button.
Then, select all setup data you want to copy by selecting the corresponding box. Finally,
click the 
button to start the copy job.
After the copy process has terminated, the message below will appear.
Acknowledge this message with OK to open the A.60.72 Show Log File screen displaying the log file of this admin setup copy job. Here you can see the name and the content of the admin setup copy process log file. This allows you to check the result of the copy process. For example, it’s possible that no data were copied because data are already present in some of the involved tables.
If you want to check this log file again after you have closed the A.60.72 screen, you can find this file in the directory of your database, which is specified with DBA setting LOG_FILE_DEST or with project default ZX_MAR_LOG. The name of the log file starts with CAS_ followed by a sequential number, with the extension .log.
The admin setup data can be copied from project to project:
-
Account Codes defined on A.10.30
-
Load File Formats defined on A.10.37
-
Delivery Designations defined on A.10.39
-
Email Templates defined on A.10.51
-
Distribution Categories defined on A.10.52
-
Email Template Sets defined on A.10.53
-
User Titles defined on A.20.04
-
User Securities defined on A.20.06.02
-
User Privileges defined on A.20.06.04
-
Attribute Securities defined on A.20.06.11
-
Disciplines defined on A.20.07
-
Report Layouts defined on A.20.09
-
Project Defaults defined on A.20.12
-
Project Discipline Defaults defined on A.20.13
-
Project Calendar defined on A.20.14
-
Approval Templates defined on A.20.45
-
Attributes defined on A.50.01
-
Attribute Sets defined on A.50.04
-
Tables defined on A.50.02/.03
-
Where Conditions defined on A.60.06
-
Formulas defined on A.60.08
-
Early Warnings defined on A.60.11/.12
All setup data for which the check box is checked will be copied from the selected source project to the project you are currently logged into, the target project. In some cases, there are dependencies among the data. This means for these cases a check box must be checked if another one is checked. Read the check box descriptions in the A.20.02 online help to find the dependencies.
The following points must be considered when starting the copy admin setup job:
-
Only setup data for which the check box has been checked will be taken into account during the copy process.
-
Only data of those disciplines that have been assigned to the target project will be copied. If you have checked the check box for disciplines, they will be copied prior to all other data to ensure that the data of all disciplines valid in the target project are taken over.
-
Data will only be created if no records can be found in the target project. This decision is made table by table, which means: If load file formats, for example, have already been defined in the target project but no report layouts, and you checked both check boxes, no load file formats will be copied from the source project. But the report layouts will be taken over.
There are two exceptions: If user securities or disciplines are copied, this check will not be done because these tables must contain at least one record. Otherwise, you cannot log in to the target project. In this case, all remaining records are taken over from the source project.
-
For all data for which language dependent descriptions exist, these descriptions will be copied as well.
-
The Start button can be used multiple times. For example, you want to copy the calendar from project A but the report layouts from project B. Then you use the Start button twice, once with project A and the calendar option checked, and then once with project B and the report layouts selected.
-
If some setup data were not copied because the tables already contained data, you can delete this existing data if it is no longer relevant and then start the copy procedure again.