To copy the BOM setup data from an existing project (source/template) to the new project (target), you can use the B.10.11 Copy BOM Setup screen when logged in to the target project.
Furthermore, you can use the A.60.02.07 Project Setup Copy screen, which allows copying setup data from different Smart Materials modules in one step. For more information about copying project setup data, see Copy Project Setup Data.
This copy BOM setup function should be used at the beginning of a project, before any data is entered, because this function can only be used for tables that have not been filled with data already. If any setup data has been entered before using this function, the copy BOM setup function will not overwrite this data. The only exception is the list structure, it will always be copied.
You must be logged in with the target project to which you would like to copy the BOM setup. Only those projects with the same product group as the target project can be chosen as the copy base (source).
Select the source project from the LOV in the Copy from Project field, and click the Run query button. Then, select all setup data you want to copy by selecting the corresponding check boxes. Finally, click the Start 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, which displays the log file of this BOM setup copy job. Here you can see the name and the content of the BOM setup copy process log file. This allows you to check the results of the copy process. For example, it’s possible that no data was copied because data is already present in some of the tables involved.
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 utl_file_dir of your database. The name of the log file starts with CBS_ followed by a sequential number, with the extension .log.
This BOM setup data can be copied from project to project:
Verifications defined on B.10.01
List Status defined on B.10.02
Node Types defined on B.10.03
Position Attributes defined on B.10.04
BOM rules defined on B.10.05
BOM views defined on B.10.06
Node-type hierarchies defined on B.10.07
Issue status defined on B.10.08
Discipline BOM views defined on B.10.09
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 in, the target project. In some cases, there are dependencies among the data. This means for these cases a check box must be selected if another one is checked. Read the check box descriptions in the B.10.11 online help to find the dependencies.
The following points must be considered when starting the copy BOM setup job:
Only setup data for which the check box has been checked will be taken into account during the copy process.
Depending on the setting of the radio group at the bottom, data of different disciplines will be copied. If you select the Login Discipline option, only data of the discipline you are currently logged in will be copied from the source project to the target project. If you select the Discipline option, you must select disciplines from the LOVs in the From Discipline and To Discipline fields. Data will be copied from the source discipline entered in From Discipline to the target discipline entered in To Discipline. If you select the All Disciplines option, data of all disciplines assigned to both, the source and the target project, will be copied.
Data will only be created if no records can be found for the target project in the corresponding table (the only exception is the list structure, it will always be copied). This will be checked table by table, which means: If verifications, for example, have already been defined in the target project but no node types, and you checked both check boxes, no verifications will be copied from the source project. But the node types will be taken over.
For all data for which language dependent descriptions exist, these descriptions will be copied as well.
Project defaults are not copied by the procedure. You should check whether the values are set correctly. You can do this by calling the modules A.20.11, A.20.12, or A.20.13.
The Start button can be used multiple times. For example, you want to copy the verifications from project A but the node types from project B. Then you use the Start button twice, once with project A and the verifications indicator checked, and once with project B and the node types selected.
If some setup data is 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.