Copy MSCM Setup - Intergraph Smart Materials - Version 10.1 - Help - Hexagon

Intergraph Smart Materials Classic Help

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.1

To copy MSCM setup data from an existing project (source/template) to a new project (target), you can use the P.10.01 Copy MSCM Setup screen when logged in to the target project.

Further, 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, read Copy Project Setup Data.

This Copy MSCM 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 MSCM setup function will not overwrite this data.

You must be logged in with the target project to which you would like to copy the MSCM setup. Only those projects with the same product group base 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 MSCM setup copy job.

Here you can see the name and the content of the MSCM setup copy process log file. This allows you to check the result of the copy process. For example, it’s possible that no data was copied because data is 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 CPS_ followed by a sequential number, with the extension .log.

The following MSCM setup data can be copied from project to project:

General:

Progress Payments defined on P.10.31

Other Costs defined on P.10.33

Inq/PO number ranges defined on P.10.35

Delivery Places defined on P.10.37

PO Closeout Activities defined on P.10.51

Destinations defined on P.10.52

Routing Methods defined on P.10.53

Text and Terms defined on D.20.11

VDRs defined on D.40.11

VDR Sets defined on D.40.12

VDR Approval Codes defined on P.10.71

Pertinent Areas defined on P.10.75

Selection Codes defined on P.10.76

Fabrication Types defined on P.10.91

Project Suppliers defined on P.20.01

Expediting:

Expediting Levels defined on P.10.55

Events and Tasks defined on P.10.56

Events to Levels defined on P.10.57

Fab/Inspection Locations defined on P.10.58

Milestones:

Milestone Labels defined on P.10.61

Milestone Sets defined on P.10.62

Milestone Label Derivations defined on P.10.61

Subcontracts:

Goods and Services Types defined on P.10.65

Pricing Types defined on P.10.66

Function Lists defined on P.10.67

Functions Sets defined on P.10.67

Sourcing Strategies defined on P.10.68

Eval. and Sel. Processes defined on P.10.69

Extended Traffic:

Date Ranges defined on PT.10.01

Transport Costs defined on PT.10.02

EML Numbers defined on PT.10.03

Methods of Transportation defined on PT.10.04

Geographical Areas defined on PT.10.05

Account codes are not available to be copied because these tables contain project-specific information.

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 P.10.01 online help to find the dependencies.

The following points must be considered when starting the Copy MSCM 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.

  • Data will only be created if no records can be found for the target project in the corresponding table. This will be checked table by table, which means: If other costs, for example, have already been defined in the target project but no destinations, and you checked both check boxes, no other costs will be copied from the source project. But the destinations will be copied over.

For all data with language dependent descriptions, 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 text and terms from project A but the VDRs from project B. Then you use the Start button twice, once with project A and the Text and Terms indicator checked, and once with project B and VDRs selected.

If some setup data is not copied because the tables already contain data, you can delete this existing data if it is no longer relevant and then start the copy procedure again.