Chapter 1. Controlled Use of Parts
1.7. Database Administration
Prev  Next

1.7. Database Administration

1.7.1. How do the datasets get into the LinkDB?
1.7.1.1. Data takeover from third party systems
1.7.1.2. Article assignment (initial filling of link database)
1.7.1.3. Background information
1.7.1.3.1. Link table and ERP table
1.7.1.3.2. Internal treatment of variants
1.7.2. Keep data up-to-date
1.7.3. Configure PARTsolutions
1.7.3.1. Add database columns
1.7.3.2. Configuration of the PARTdataManager view
1.7.3.3. Configuration of the entry dialog for the ERP number (erpcustom.cfg)
1.7.3.4. Naming rule for CAD file names
1.7.4. Ongoing data maintenance
1.7.4.1. Add new ERP numbers
1.7.4.1.1. Incorporate ERP number with PARTdataManager
1.7.4.1.1.1. Automatically generated timestamp number
1.7.4.1.1.2. Manual entry of ERP number
1.7.4.1.2. Enter ERP number with PARTlinkManager
1.7.4.2. Create variant in the PARTdataManager
1.7.4.3. Create variant in PARTlinkManager
1.7.4.4. Edit datasets in the PARTdataManager
1.7.4.5. Edit dataset in PARTlinkManager
1.7.4.5.1. Edit column
1.7.4.5.2. Edit row
1.7.4.6. Catalog update

The tool for administering the database (PLINKDB and/or PLDBDEMO) and the datasets, is PARTlinkManager.

Tools for so-called initial loadings and for running data comparison with third party systems, are the modules PARTident and PARTdataCenter.

The duties and responsibilities are divided into the following areas:

  1. Basically, one time requirements for initiating ERP/PDM integration

    • Column application for incorporating initial loading

    • Configuration of column display

    • Definition of a naming rule for file names

  2. Ongoing data management

    • Applying ERP numbers

    • Managing / editing the database entries

    • Applying variants

Prev Up Next
1.6.5.2.  plinkcommon.cfg -> Block [Common] -> Key "CADENAS_PRESELECT_LINKDB_GROUP" - Role selection by environment variable  Home 1.7.1. How do the datasets get into the LinkDB?