Copy Requisition Setup - Intergraph Smart Materials - Version 10.2 - 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.2

To copy requisition setup data from an existing project (source/template) to a new project (target), you can use the R.10.01 Copy Req 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 see Copy Project Setup Data.

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

You must be logged in with the target project to which you would like to copy the Req setup. Only those projects with the same product group base as the target project can be chosen as 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. A message will appear; click Yes to continue.

After the copy process has terminated, the message below appears.

Acknowledge this message with OK to open the A.60.72 Show Log File screen, which displays the log file of this Req setup copy job. Here you can see the name and the content of the Req 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 CRS_ followed by a sequential number, with the extension .log.

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

  • Req Status defined on R.10.11

  • Req Buy Cycles defined on R.10.12

  • Req Number Rules defined on R.10.13

  • Req Categories defined on R.10.14

  • Req desc rules defined on R.10.15

  • Disposition rule sets defined on R.10.21

  • Disposition rules defined on R.10.22

  • Disposition rule details defined on R.10.23

  • Document types defined on R.10.24

  • Document type sets defined on R.10.25

  • Req nodes defined on R.10.41

  • Req templates defined on R.10.41

  • Req split criteria defined on R.10.42

Account codes, Requisition BOM setup nodes, and MTO types 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 R.10.01 online help to find the dependencies.

The following points must be considered when starting the Copy Req setup job:

  • Only setup data for which the check box has been checked will be taken into account during the copy process.

  • The data to be copied depends on the setting of the radio group at the bottom. 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. This will be checked table by table, which means: If req number rules, for example, have already been defined in the target project but no req categories, and you checked both check boxes, no req number rules will be copied from the source project. But the req categories will be taken 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 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 req number rules from project A but the req categories from project B. Then you use the Start button twice, once with project A and the Req Number Rules indicator checked, and once with project B and the Req Categories 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.