powered by CADENAS

Manual

Manual

5.8. Data administration

5.8.1. Launch PARTlinkManager using PARTdataManager
5.8.2. Display filtered datasets
5.8.3. Catalog update
5.8.4. Catalog update with ERP integration - Update manager
5.8.4.1. Catalog update - Example 1
5.8.4.1.1. Preparations
5.8.4.1.2. Catalog update - Download
5.8.4.1.3. Assignment / release – Overview on the best approaches
5.8.4.1.4. PARTadmin - Check | Compare | Install
5.8.4.1.5. PARTlinkManager - Important notes on procedure
5.8.4.1.6. Update manager - Project assignment to LinkDB datasets
5.8.4.1.6.1. Update manager - Assign projects after mapping automatically processed before
5.8.4.1.6.1.1. Assign project.prj (Standard name adjusted)
5.8.4.1.6.1.2. Assign project2.prj (Adjusted directory)
5.8.4.1.6.1.3. Assign project4.prj (directory relocated and Standard name adjusted)
5.8.4.1.6.2. Update manager - Assign projects without preceding mapping
5.8.4.1.6.2.1. Assign project3.prj (project and Standard number renamed)
5.8.4.1.6.2.2. Assign project5.prj (project and Standard number renamed and Standard name adjusted)
5.8.4.1.6.2.3. Assign project6.prj and project7.prj
5.8.4.1.6.3. Final check
5.8.4.2. Catalog update - Example 2
5.8.4.2.1. Preparation
5.8.4.2.2. Status after update installation to Bikecompany V2 and before editing with Update Manager
5.8.4.2.3. Editing in Update manager
5.8.4.3. Install update version
5.8.4.3.1. Update without connection to the LinkDB
5.8.4.3.2. Correct version numbers
5.8.4.3.3. Update structure table
5.8.4.4. User interface of Update Manager
5.8.4.4.1. Symbols in the Catalogs section
5.8.4.4.2. Symbols in the Line mapping section
5.8.4.5. Functions
5.8.4.5.1. Active State and Requested State
5.8.4.5.2. Changed standard name
5.8.4.5.3. Moved dataset
5.8.4.5.4. No correlation to the old dataset found
5.8.4.5.5. Conduct assignments across lines
5.8.4.6. Background information
5.8.5. PARTadmin - Index administration
5.8.6. PARTadmin - Catalog update
5.8.7. Creation of ERP numbers
5.8.7.1. Using PARTdataManager
5.8.7.1.1. Without direct linkage to the ERP system
5.8.7.1.1.1. Manually enter ERP number
5.8.7.1.1.2. Automatically generated timestamp number
5.8.7.1.1.3. ERP Number Generator
5.8.7.1.1.3.1. Prerequisites
5.8.7.1.1.3.1.1. SQL commands for applying the "Sequencer" table in the LinkDB
5.8.7.1.1.3.1.2. Activating ERP Number Generator
5.8.7.1.1.3.2. Incorporate ERP number into the PARTdataManager
5.8.7.1.1.3.3. Further number generations based on the example of the default setting
5.8.7.1.1.3.4. Adjust conditions for number generation
5.8.7.1.2. Applying ERP numbers with direct linkage to the SAP system
5.8.7.2. Using PARTlinkManager
5.8.7.2.1. Enter ERP number with PARTlinkManager
5.8.7.2.2. Import a project into LINKDB – Assign ERP number
5.8.7.3. PARTdataCenter
5.8.8. Edit variant / Create variant in PARTlinkManager
5.8.9. Create variants in PARTdataManager
5.8.10. Editing LinkDB in PARTlinkManager
5.8.10.1. Editing columns
5.8.10.2. Edit row
5.8.11. Delete datasets
5.8.12. Edit/delete dataset using PARTdataManager
5.8.13. Automated and cyclical update of data

In the application flows of some companies, it may be useful to apply ERP numbers into the link database via PARTsolutions. Some important processes can be launched directly from the PARTdataManager.

With a complete ERP/PDM integration some possibilities described here may be omitted. For example, the creating of ERP numbers. This occurs only in the ERP system whereby the applied numbers are carried over into the link database in the sequence direct, cyclical or with online linkings.

Below you will find some important points about "data administration".

An overall depiction of the function of the module PARTlinkManager can be found under Section 5.9.1, “ PARTlinkManager reference ”.