# Introduction
Since PDS 6.4, Intergraph has supplied the Material Data Publisher with PDS. This makes it possible, for the first time, to write almost all data available in PDS, from the database, libraries, and design files, into a single database. This opens up entirely new possibilities for evaluation.
The **MDP-Manager** makes this data practical to use. It offers the following benefits:
- Extremely fast extraction to Access
- No costly or error-prone ODBC configuration
- Quality checking of data
- Easy operation
- Data indexed in a practical way for significantly faster queries
- Date and time converted into a readable format
- Nominal widths in inches decoded automatically
- Files can be deleted from the MTO schema
- Validation of entries against company-specific input rules
- A comprehensive training programme with several videos, making it possible to use the data even without prior knowledge of PDS
- Data can be sent to customers, suppliers, and sites by email so that recipients can create evaluations quickly and easily
## Main window
## PDS Project
After the software has been started, the project-specific `.ini` file must be selected.
## MDP-Manager Configuration File
The `.ini` file contains all required project-specific settings, for example the project name.
The configuration file can be selected either by using the file-open dialogue and the **Browse** button, or by drag and drop.
Press **Open** to open the file in the default text editor.
### Oracle User and Password
To access the Oracle database and store this information, use the `OracleUsername` and password fields in the **MDP-Manager** configuration file. Create this file by running the configuration wizard in **Custom** mode and using **Advanced Settings** to edit the project file. Test the settings by pressing **Test connection**.
This makes it possible to create a separate server, user, and password definition and save it in a `project.ini` file by using a 128-bit encryption procedure. This provides a high level of security and supports maximum flexibility in database and project administration. Create a separate database-access definition for each project. See also item `6.2.11`.
Project `.ini` configuration:
\[Oracle\]
User=system
Password=edacmncmlpcclp
Server name entry in `[MDPmgr]`
OracleServer=S_CX240
Specify the host name of the database server.
If there is no `[Oracle]` entry in `project.ini`, the software searches for it in `mdpmgr.ini`. Copy it from a `project.ini` file, as it cannot be created by the configuration wizard. It then becomes the default value for all projects without an `[Oracle]` entry. If there are no entries in either file, `project.ini` or `mdpmgr.ini`, the project-specific `[SchemasPass]` entry is used.
## Project Structure
The project structure is displayed in the tree hierarchy on the right-hand side. This allows you to select the disciplines, design areas, and models to be extracted.
Model items shown in red are missing in the `mto` schema but exist in the `pd` schema. These cannot be transferred to the Access database automatically.
To extract the missing models from the `pd` schema, activate the relevant checkbox and run **MDP-Manager** with **Only transfer to Access** disabled.
## Access Database
Specify the Access file into which the data is to be extracted. You can either select an existing file or create a new one.
If **Access Seed Database** is defined in the **MDP-Manager** configuration file, it is used only by **Create new database**.
## Publishing Options
The \"Publishing Options\" section specifies whether or not the
libraries are to be extracted as well. Options are only then active, if
the switch "Only transfer to Access" is deactivated.
### Forced Publishing
The \"Forced Publishing\" check box specifies whether data is to be
completely deleted from the database (MTO schema) and then extracted
entirely from scratch
() or only changes are to be taken into
account
().
> If the **Forced** option is selected, the run may take several days in the case of large projects.
## Transfer Options
### Only transfer to Access
If this option is selected, only the data from the existing MTO schema are transferred to the Access file, where they are checked, indexed, and processed.
If the option is not selected, the Intergraph MDP is run first.
### Transfer only selected models
If **Transfer only selected models** is selected, only the selected models from the `mto` schema are loaded into the database. Otherwise, all data from the `mto` schema are loaded.
### Load all tables from
All tables from the selected schema items in the project are loaded.
`other schemas` means all other schemas of the project except the listed schemas and the `dd` schemas.
The **Extended select Table** button is used to select tables that are to be ignored and not loaded.
### Extended Select Tables
By pressing **Extended select tables**, you can select individual tables from all schemas of the project except the `dd` schema.
All available tables are listed on the left-hand side. The right-hand side lists the tables that will be loaded.
By using drag and drop, you can select either the whole schema or an individual table from left to right.
Press **OK** to save all changes and close the window.
Press **Close** to close the window and discard all changes.
## Quality Scripts
### Check Pipeline-ID & EQP Name
This option makes it possible to locate pipelines and equipment whose name, `LineID`, does not comply with the defined rules.
Rules:
n (lowercase) -- any digit
c (lowercase) -- any alphabetic character
other character (A, X, -, \_, .) to be used as written
Examples:
nnn-ABC-ccc
| Correct | Incorrect |
|---|
|
123-ABC-RKL
|
12-ABC-RKL
|
|
007-ABC-NIX
|
007-ABX-NIX
|
|
471-ABC-XXX
|
471-ABC-XX
|
These pipelines are **not** deleted automatically, but are listed in an access table (bad_lines). These pipelines can be deleted at a later stage with the \"Tools Bad Lines\" option.
In this way, the user can decide which pipelines to delete.
### Coordinates out of Limit
This option makes it possible to locate pipelines and equipment that lie outside a defined volume. This volume, between two space points, defines the limits of the plant.
The pipelines are **not** deleted automatically, but are entered in an access table (bad_lines). These pipelines can be deleted at a later stage with the \"Tools Bad Lines\" option.
## Start Time
This option allows the run to be scheduled to start at a later time.
- Select the checkbox.
- Set the time.
- Press **Start**.
**MDP-Manager** checks whether all settings are correct and waits until the specified time is reached. The program run then begins. In the meantime, the window is minimised.
## Events Log
Shows the last five lines of the log file. Right-click once to open the log file in a text editor.
## Menu
## File
### Configuration Wizard
Creates a new configuration file or edits an existing one. See also the **Quickstart guide** for details on using the configuration wizard.
### Open Config File
Loads the project and settings from the selected configuration file.
### Save config file as
Saves the current configuration file under a specified file name.
### Create RIS dump
Unloads the `pd` and `mto` schemas of the current project, archives them, and stores them in the specified `.zip` file.
### Transfer from RIS dump
Loads files from the RIS dump file into the `mto` schema of the current project. The data are then loaded into the Access database automatically.
### Apply functions on Access database
All functions of **MDP-Manager**, such as quality scripts and decoding, can be used after the data have been unloaded into the database.
### History
Lists the five most recently used configuration files in chronological order.
### Exit
Closes the application.
## View
### View MDP Errors
Shows the decoded MDP error table, `pd_table_180`. In addition to the navigation functions, such as **First**, **Last**, **Previous**, and **Next**, it is possible to display the error directly in MicroStation by pressing **Open in MicroStation**.
### Project Control
Lists the selection queries from the **MDP-Manager** configuration file. If the first column in one of these SQL statements is `pipeline_id`, right-clicking in the Project Control window opens a pop-up menu containing all corresponding drawings for that pipeline. These can be opened with SmartPlant Review or MicroStation.
Example:
\[ProjectControl\]
LineList=SELECT pipeline_id FROM pdtable_12
## Tools
### BadLines Module
Manages incorrect or erroneous lines in the Access database.
After the Access database has been created, the quality scripts are run. These consist of the following parts:
- Verification of pipeline names and equipment names against the defined rules, configured under **Check Pipeline-ID and EQP Name**
- Verification that all components of a pipeline exist within the defined working area, configured under **Coordinates out of limit**
- Detection of redundant data records in the database
All erroneous pipelines are stored in the `bad_lines` table and are managed by the **BadLines Module**.
One or more pipelines can be deleted from the database by selecting the items in the list and pressing **Delete**. A printable report can be created by pressing **Report**.
Click a column header to sort the values. To display only items that meet user-defined criteria, set a filter by entering the criteria in the first row. Multiple filters can be set at the same time.
### DeleteModels Module
Manages the models in the `mto` schema of the PDS project.
One or more models can be deleted from the `mto` schema without running the MDP job again. Select the items to delete and press **Delete**.
- Blue data records are equipment models
- Green data records are piping models
- Red data records are structural models
Click a column header to sort the values. To display only items that meet user-defined criteria, set a filter by entering the criteria in the first row. Multiple filters can be set at the same time.
### PartsList Module
This tool is used for creating and managing parts lists.
An `ident_alloc` table containing all component parts of a project is created. Each part receives its own unique number, `Ident-Number`, either manually or automatically. This number can then be used to assemble parts lists and define increases or decreases in component quantities.
If new component parts are added, the `ident_alloc` table is updated and the part receives an additional number.
Procedure:
- Select the current Access database containing the project data.
- Select the database containing the `ident_alloc` table with the `Ident-Number`.
Within this database, a table containing all component parts of the project is created. This table contains a unique number for each part. Save this database so that it can be reused on the next run.
- Press **Update ident_alloc table**.
This creates a new table with all component parts of the project. If the table already exists, any missing parts are added. The user can also add additional columns.
- Press **Generate IdentNo**.
All parts that do not yet have a number are assigned a new one. The first number is taken from the **starting IdentNo** field. A number can also be assigned manually by entering the required value, numbers only, in the `ident_alloc` table in the `ident_no` column.
To assign all numbers again, enable **Remake all IdentNo**. Any existing numbers are overwritten.
- Press **Write IdentNo to siz_dep_comm_code**.
This writes the newly assigned numbers into the database containing the project data.
User-defined colums can be add into table "ident_alloc" by calling
Config custom colums in the option menu.
For any new column, which is to add in table "ident_alloc", there is one
row to enter.
Define name for the new column (col_name), that is not necessary.
Select a column for each table from which data will be add in table "ident_alloc".
Select either from pdtable_12 or any other tables. It is not necessary to define colums for all tables (a single table is sufficient).
If you need more tables, go back to Step 1.
Press button "OK", to save changes, to quit without saving, press button "Close".
With help of MatReq two Access databases will be compared against each other and load the increase/decrease in a list for differences by pressing the button "calc difference". Thereby it is possible to evaluate the temporarily created parts lists with its quanitity changes.
### VerifyData Module
This powerful tool enables user-input errors to be identified early in a simple and efficient way.
Run verification in the following order:
Choose the table to verify
Select column
Choose logic
If you choose the logical operators **IN** or **NOT IN**, `expr_table_name` and `expr_column_name` must be set, see Step 1. In this case, it is not possible to enter values in the `expression` column.
For all other cases, `expression` must be entered.
If additional rules are required, return to Step 1.
Press **Start** to display the results and write them to the `verify_data` table.
Press **Report** to create a printable report.
Click a column header to sort the values. To display only items that meet user-defined criteria, set a filter by entering the criteria in the first row. Additional filters can also be set.
The rules define valid values. Values that do not fulfil the rules are not displayed.
There is also a powerful but simple function for validating text values.
------------------------ ------------- --------------------------------- ----------------------------------------
Entsprechung Muster Entsprechung (gibt True zurück) Keine Entsprechung (gibt False zurück)
Mehrere Zeichen a%a aa, aBa, aBBBa ABC
Mehrere Zeichen %ab% abc, AABB, Xab aZb, bac
Sonderzeichen a\[%\]a A%a Aaa
Mehrere Zeichen ab% abcdefg, abc cab, aab
Einzelne Zeichen A_a aaa, a3a, aBa ABBBa
Einzelne Ziffern a\#a a0a, a1a, a2a aaa, a10a
Zeichenbereich \[a-z\] f, p, j 2, &
Außerhalb des Bereichs \[!a-z\] 9, &, % b, a
Keine Ziffern \[!0-9\] A, a, &, \~ 0, 1, 9
Kombination a\[!b-m\]\# An9, az0, a99 abc, aj0
------------------------ ------------- --------------------------------- ----------------------------------------
### WriteToPDS Module
(available only in Professional Version)
This module allows the design schema of the project to be changed easily and efficiently.
[Note:]{.ul} This module can damage the entire project. Create a backup of your PDS project before using this module.
CAXperts GmbH accepts no responsibility for data loss.
Procedure:
- Select the Access database for input. It contains the tables or queries with the values to be written to PDS.
- Select a table or query from the input database. All column names and data types must match the column names and data types in the output database.
- Values in the columns of the tables or queries can be decoded. Use drag and drop with the appropriate key. Drag the key on to the column you want to decode. To remove a decoding, drag the key `0000-No key` on to the relevant column.
- Define the criteria columns. These are the conditions considered when writing data to PDS. Values from criteria columns are not written back to PDS. More criteria columns can be defined, but this is optional.
- Choose the output table, that is, the design schema table of the project, into which the data are to be written.
**Forced** switch
If **Forced** is not enabled, only values that do not already exist are written to PDS, existing values are not overwritten. If the switch is enabled, all values are written to PDS, including existing values.
- Select the change area. Changes can be applied to the complete project, to defined areas, to models, or even to defined pipelines.
- Activate **Log** and choose the log Access database. All changes made to the project's design schema are then recorded.
- Press **Write to PDS** to write the data to PDS.
By default, it is not possible to change values in PDS by using **WriteToPDS**.
Each column must be enabled explicitly by answering the following question with **Yes**.
### Schedule Module
This task planner makes it possible to schedule the start of **MDP-Manager** at any time. A configuration file must be selected so that it can be passed to **MDP-Manager** as a parameter.
### Integrate with Batch Isogen Processing
Integrates **MDP-Manager** into Batch Isogen Processing. This makes it possible to update or change values in the design schema of the current project before generating ISO files by using the **WriteToPDS** module in **MDP-Manager**.
## Help
### Help
Shows the Help file.
### MDP-Manager on the web
Opens the CAXperts GmbH homepage, , in a new browser window.
### E-Mail Technical Support
Opens a new message in your default email client addressed to [mailto:support\@caxperts.de](mailto:support@caxperts.de).
### Update Licence
- **Test licence** checks the licence number.
- **OK** saves the entered licence key.
- **Cancel** closes the window without saving any changes.
### About
Shows a dialogue window with information about **MDP-Manager**, for example the version and licence data.
## System Administration
## Preparations for MDP
The `mto` database user and RIS schemas must exist. Before the first MDP run of a new project, the database tables must also exist.
Procedure:
- Start Intergraph MDP.
- Select the project.
- Confirm the message by pressing **OK**.
- Exit MDP.
## Batch Mode
In order to run all commands in batch mode, all environment variables, for example `RIS_PARAMETERS` and `TEMP`, must be set correctly. In addition, users must have the relevant system rights.
## Unload data in Access database
To run the software in batch mode, call **MDP-Manager** with the configuration file as a parameter.
Example:
c:\\path\\mdpmgr.exe c:\\path\\project.ini
## Write data back to PDS
It is also possible to write data back to PDS in batch mode. In this case, **MDP-Manager** must be called with two parameters:
- parameter 1: directory containing the configuration files, or the full file path
- parameter 2: Isogen batch input file
Example:
c:\\path\\mdpmgr.exe c:\\path\\to\\config_files\\ c:\\path\\isobatch.txt
or
c:\\path\\mdpmgr.exe c:\\path\\project.ini c:\\path\\isobatch.txt
If the first parameter is a directory with config files,config file and
project name must be equal (e.g. settings for the PDS project "project"
must be saved in file("project1.ini").
# Appendix
## Description Configuration file
### Main configuration file
The main configuration file, `mdpmgr.ini`, must exist in the same directory as `mdpmgr.exe`, that is, the program directory.
#### \[MDP-Manager\]
Licence=1234567
Software licence number.
#### \[PDTablesDescr\]
Short descriptions of the tables shown in the **Extended Select Table** window.
Format: `table name=description`
Example:
\[PDTableDescr\]
pdtable_101=Project Description Data
#### \[MTOTablesDescr\]
See chapter `[PDTableDescr]`.
#### \[RaTablesDescr\]
See chapter `[PDTableDescr]`.
#### \[DecodedMDPErrors\]
MDP error descriptions used for decoding in `pdtable_180`, see `mdp_error_table`.
Format: `Error number=Description`
Example:
\[DecodedMDPErrors\]
210=failed to read linkage
#### \[MDPErrorViewerColumns\]
Column widths used in the **ViewMDPErrors** module.
Format: `Column name=Length`
Example:
\[MDPErrorViewerColumns\]
error_code_decoded=1530.142
area_name=1514.835
#### \[Oracle\]
Defines the decoded password and the username for the Oracle database, and has a higher priority if this item is missing in the project file. See also items `2.2.1` and `6.2.11`.
\[Oracle\]
User=system
Password=edacmncmlpcclp
#### \[History\]
List of the five most recently used configuration files, available from the **File** menu.
Example:
\[History\]
INIFile1=c:\\temp\\config1.ini
INIFile2= c:\\temp\\config2.ini
### Project Configuration File
#### \[MDPmgr\]
**Project**=projname
PDS project name used by **MDP-Manager**.
**MDBFile**=C:\\Temp\\Project.mdb
Path to the Microsoft Access database, in this case the extraction target file. If no file name is given, MDP-Manager generates one automatically.
**Temp**=C:\\TEMP
Directory in which temporary data are stored. If the `Temp` variable is set in the MDP-Manager configuration file, that value is used. Otherwise, the system variable `TEMP` is used.
**RISPath**=C:\\Win32App\\RIS\\
Directory containing the RIS utilities. If these paths are not set in the environment variables, they must be set here.
OracleServer=ServerName
Oracle server containing the PDS projects. If a connection can be established to the Oracle server `ServerName`, data are unloaded by using the PDS Oracle client. MDP-Manager access through the Oracle client is faster than RIS.
**MDBSeed**= C:\\Temp\\mdbseed.mdb
Path to the standard template Microsoft Access database. The file is copied to **MDBFile** before loading data from PDS. If `CreateNewAccessFile=0`, the seed file is ignored.
**DGNSeed**= C:\\Temp\\dgnseed.dgn
Path to the standard template DGN drawing. This DGN seed file is used to display errors in the **ViewMDPErrors** module.
OnlyTransferToAccess=0
If `OnlyTransferToAccess=1`, data from `mto_schema` are extracted without starting the MDP batch job. If `OnlyTransferToAccess=0`, the MDP batch job is started first, after which the data from `mto_schema` are extracted.
StdNote=1
Republish Standard Note Library.
LongMat=1
Resolve long material descriptions.
ShortMat=1
Resolve short material descriptions.
Forced=1
Force publishing of the specified selection set.
CreateNewAccessFile=1
If `CreateNewAccessFile=1`, data are loaded into a new Access file and the old file is stored. If `CreateNewAccessFile=0`, data are loaded into the existing Access file. In this case, only tables are overwritten and queries are ignored.
TransferOnlySelectedModels=1
If `TransferOnlySelectedModels=1`, only the data for selected models from PDS are loaded into the Access database. Otherwise, all data are loaded. This limitation applies only to `mto_schema`. All other schemas and their data are loaded independently.
#### \[LoadTable\]
This section defines the table names that are to be loaded into the Access database.
Format: `Table[1-100]=TableName|Prefix of Schemaname`
If no schema-name prefix is specified, the table is loaded from `mto_schema`. If the project's `ra_schema` uses a different format from `ra_projectname`, enter the full name of the `ra_schema` after the pipe sign.
Example:
The ra_schema of PDS-Project „test1" is called ra_test1. In MDP-Manager
config file it looks like this:
\[LoadTable\]
Table1=pdtable_500\|ra
Table2=pdtable_12
Table3=pdtable_113\|pd
But if ra_schema for PDS-Project „test1" is called ra_standart, you have
to change the config file as follows:
\[LoadTable\]
Table1=pdtable_500\|ra_standart
Table2=pdtable_12
Table3=pdtable_113\|pd
The `[LoadTable]` section is ignored completely if the `[LoadAllTablesFromSchema]` section is not empty. Up to 100 tables can be defined.
#### \[LoadAllTablesFromSchema\]
This section defines the schema names that are to be loaded into the Access database.
Format: `Schemaname=1`
The entry `other schemas` means all other schemas except `pd_schema`, `mto_schema`, `ra_schema`, and `dd_schema`.
Example:
\[LoadAllTablesFromSchema\]
pd_test1=1
mto\_ test1=1
ra\_ test1=1
other schemas=1
The `[LoadTable]` section is ignored completely if the `[LoadAllTablesFromSchema]` section is not empty.
#### \[Quality\]
If coordinates borders are set, MDP-Manager will check, if all component
parts are within these borders. Data records with erros will add to
table „bad_lines".
Example:
\[Quality\]
Loweast=0
LowElev=0
HighNorth=999999999
HighEast=999999999
HighElev=999999999
If PipeLineID and/or EQPLineID are set, Pipelines (Line-ID) and/or
Equipments (EQP-Name) will check, if they fulfill the rules as follows:
Rules:
n (lower case) - any number
c (lower case) - any character
Other signs (A, X, -, \_, .) will used as written.
Example:
\[Quality\]
PipeLineID=nnn-ccc-nnn
EQPLineID= nnn-ccc-nnn
#### \[CustomIndex\]
Define columns in this chapter for which an index will created, after
loading data from PDS.
Format: Index\[1-100\]=tablename\|columnname.
Example:
\[CustomIndex\]
Index1=pdtable_12\|LINE_SEQUENCE_NO
Index2=...
Up to 100 entries can be defined in this chapter.
#### \[SQL\]
This chapter describes SQL-Statements, which execute after loading all
tables. Format: SQL\[1-100\]=SQL-Statement.
Example:
\[SQL\]
SQL1=INSERT INTO table SELECT line_id FROM pdtable_12;
SQL2=...
Up to 100 entries can be defined in this chapter.
#### \[Query\]
Define queries here, to import it into Access database. Format:
Query\[1-100\]=Queryname\|Querytext.
Example:
\[Query\]
Query1=Surface per line\|SELECT \* FROM pdtable_12;
Query2=...
Up to 100 entries can be defined in this chapter.
#### \[ProjectControl\]
Define Selection queries here. Display query results in MDP-Manager Menu
(Tools-\>Project Control-\>"Name"). „Name" is the query's name (in this
case „LineList").
If „line_id" is the first column name of the query then all DGN-Drawings
according to this pipeline will displayed by right click in Project
Control PopUpMenu window. Open with SmartPlantReview or Microstation.
Example:
\[ProjectControl\]
LineList=SELECT line_id FROM pdtable_12
#### \[RunBefore\]
Define command line statements here to run before extraction.
Format: Run\[1-100\]=DOS-Commands
Example:
\[RunBefore\]
Run1=copy c:\\temp\\project.mdb c:\\temp\\project.mdb.old
Run2=...
Up to 100 entries can be defined in this chapter.
#### \[RunAfter\]
Define command line statements here to run after extraction.
Format: Run\[1-100\]=DOS-Commands
Example:
\[RunAfter\]
Run1=copy c:\\temp\\project.mdb c:\\temp\\project.mdb.old
Run2=...
Up to 100 entries can be defined in this chapter.
#### \[Oracle\]
Define here the project specific decoded password and the according
username. Use Copy&Paste to paste this entry into mdpmgr.ini and make it
available for all projects.
\[Oracle\]
User=system
Password=edacmncmlpcclp
#### \[ColDescr\]
Define comments for columns in Access database here.
Format: Desc1=tablename\|columnname\|description.
Example:
\[ColDescr\]
Descr1=bad_lines\|line_id\|Leitung
Up to 100 entries can be defined in this chapter.
#### \[ColCopy\]
Define columns to copy in this chapter.
Format:
Copy\[1-100\]=source_table.source_column\|target_table.target_co-lumn
If target columns doesn't exist, it will created.
Example:
\[ColCopy\]
Copy1=pdtable_34.commodity_code\|pdtable_34.siz_dep_comm_code
Copy2=...
Up to 100 columns to copy can be defined in this chapter.
#### \[Relation\]
Define new relationships between tables.
Format:
Relation\[1-100\]=Table\|Column1\[,Column2\[,ColumnN\]\]\|ForeignTable\|ForeignColumn1\[,ForeignColumn2\[,ForeignColumnN\]\]
Example:
\[Relation\]
Relation1=pdtable_12\|system_unique_no,partition_no\|pd-table_80\|idx_12,partition_no
Relation2=pdtable_12\|partition_no\|pdtable_900\|par-tition_no
#### \[Decode\]
In addition to the automatically decoded columns by MDP-Manager, you can
define self created columns, which will decoded.
Format: Decode1=table name\|column name\|decoding key
Example:
\[Decode\]
Decode1=pdtable_12\|fluid_code\|125
Decode2=...
Up to 100 entries can be defined in this chapter.
#### \[DecodeSteel\]
Decoding columns from table pdtable_532 (Steel).
Format: Decode1=column name\|attribute name
Example:
\[DecodeSteel\]
Decode1=design_status\|Design_Status
Decode2=fabr_note\|Fabricator_Note
Up to 100 entries can be defined in this chapter.
#### \[ReplacePath\]
Replace path to DGN-Files in ViewMDPErrors-Module.
Format: Path1=Search\|Replace
By viewing errors with ViewMDPErrors-Module, the according DGN-Files will displayed in MicroStation. Path to files will automatically find
from PDS. If DGN-Files are not reachable in this path (e.g. no user rights on all drives/directorys are set), you can replace it here.
Example:
MDP-Manager has find the following path to file test1.dgn:
[\\\\PDS-Server\\d\\pds\\project\\test1.dgn](file:///\\PDS-Server\d\pds\project\test1.dgn).
The host machine which runs MDP-Manager has a mapping called O:, which is connected to the following directory on PDS-Server:
\\\\PDS-Server\\d\\pds.
This means you can reach this file by two ways:
[\\\\PDS-Server\\d\\pds\\project\\test1.dgn](file:///\\PDS-Server\d\pds\project\test1.dgn)
O:\\project\\test1.dgn
In this case you can enter the following replace rule in MDP-Manager
configurations file:
\[ReplacePath\]
Path1=\\\\PDS-Server\\d\\pds\|O:
Now MDP-Manger has access to file test1.dgn over path
[\\\\PDS-Server\\d\\pds\\project\\test1.dgn](file:///\\PDS-Server\d\pds\project\test1.dgn)
.
Up to 100 entries can be defined in this chapter.
#### \[SchemasPass\]
Set schema passwords to access data by using Oracle-Client.
Format: Schemaname=Password
Write password in reverse order. Passwords are case-sensitive, so upper-
and lowercase are relevant to it, except in schema names.
If no password is defined to schema, password is set to schema name
automatically.
Example:
Schema pd_test1 gets password "pass1":
\[SchemasPass\]
PD_TEST1=1ssap
#### \[Export2Excel\]
Exportation data from Access database into MS Excel. The Excel-File will
generate automatically in same folder and with same name (Extension
\*.xls) as Access database file.
Format: Export\[1-100\]=table-/queryname
If you want to export all tables and querys, use the following syntax:
Export1=\*
Example:
\[Export2Excel\]
Export1=pdtable_12
Export2=pdtable_34
#### \[PartsListModule\]
After the MDP-Manager run, Parts-List Module will start. If no Access database is defined, MDP-Manager database will used. If no Access database for Ident-table is defined, a database will created automatically.
If no start number is defined, then start value for Ident-Number is 1.
If **UpdateIdentTable**=1, then ident_table will created/updated.
If **GenerateIdentNo**=1, then component parts without according number
gets a generated IdentNo.
If **WriteIdentNo**=1, then IdentNo will write back to Access database
in column size_dep_comm_code.
Example:
\[PartsListModule\]
UpdateIdentTable=1
GenerateIdentNo=1
WriteIdentNo=1
#### \[IdentAlloc\]
Chapter to store settings for PartsList-Module.
StartIdentNo=1
Start value for Ident-Number.
**MDBFile**= C:\\Temp\\Project.mdb
Path and name to database file in which Ident-Number will written.
**IdentMDBFile**= C:\\Temp\\Project_ident.mdb
Access database with ident_alloc-Table.
#### \[MatReq\]
Chapter to store settings for PartsList-Module.
**NewMDBFile**= C:\\Temp\\Project_new.mdb
New database file to compare.
**OldMDBFile**= C:\\Temp\\Project_old.mdb
Old database file to compare.
NoPDSMatColumnItem=item
Column name with key for Non-PDS-Material.
NoPDSMatColumnQuantity=quantity
Column name with values for Non-PDS-Material.
NoPDSMatTable=test
Table name, which contains Item- and Quantity-columns.
#### \[WriteToPDS\]
**OutputTable**=pdtable_12
PDS-Table name, to write back date.
InputTable=Abfrage1
Input Table or Query
Forced=0
If **Forced**=1 then all data will overwrite in PDS. If **Forced**=0
then only „NULL" values will change.
**InputMDBFile**=c:\\Beispiele\\demo.mdb
Input Access database.
If no Access database is defined, MDP-Manager database will used.
CreateLogFile=1
If **CreateLogFile**=1 then a Log-Access-File will create.
**LogMDBFile**=c:\\Beispiele\\demo_log.mdb
LOG Access database.
If no Log Access database is defined, one will build automatically.
#### \[WriteToPDSAllowUpdateTables\]
Define tables in this chapter, which can be changed by
WriteToPDS-Module.
Format: Tablename=1 or \*=1 (All tables might change)
Example:
\[WriteToPDSAllowUpdateTables\]
pdtable_12=1
#### \[WriteToPDSAllowUpdateColumns\]
Define columns in this chapter, which can be changed by
WriteToPDS-Module. Format: Columnname=1 or \*=1 (All columns might
change)
Example:
\[WriteToPDSAllowUpdateColumns\]
fluid_code=1
#### \[Abfrage1\]
In WriteToPDS-Module for each input table/query a separate chapter will
build which is named like input table/query. In this chapter columns
settings will storedIn diesem Abschnitt werden Spalte-Einstellungen
(condition column, output-column,column-key) in following format:
Columnname=\[0,1\]\|Decoding-key
If exist a Decoding-key then this columns will decoded by table
pdtable_250.
Example:
\[Abfrage1\]
fluid_code=0\|125
fluid_code-column from table/query is an output column, which must be
decoded by table pdtable_250 with key 125.
line_id=1\|
line_id-column from table/query isa condition column (input column).
piping_mater_class=0\|
piping_mater_class-column from table/query is an output column.
#### \[VerifyDataRules\]
Define and store rules for VerifyData-Module in this chapter.
Format:
Logic: „IN" or „NOT IN":
Rule\[1-100\]=Tablename.Columnname\|Logic\|Tablename.Columnname
For all other logic types:
Rule\[1-100\]=Tablename.Columnname\|Logic\|Value
Example:
\[VerifyDataRules\]
Rule1=pdtable_12.npd\|\<\>\|0
Rule2=...
Up to 100 entries can be defined in this chapter.