powered by CADENAS

Manual

Manual

Chapter 4. Strategic Parts Management

Table of Contents

4.1. Introduction
4.1.1. Integration
4.1.2. Target groups
4.1.3. Entire workflow
4.1.4. Integrating LinkDB
4.1.4.1. Linkage
4.1.4.2. Data transfer and data link
4.1.4.2.1. Cyclical Replication
4.1.4.2.2. Online Replication
4.1.4.2.3. Direct Online linkage of LinkDB to ERP-DB
4.1.4.2.4. New installation of parts using an ERP Interface
4.1.5. User-role concept
4.1.6. Support of company-internal workflows
4.1.7. Modules
4.1.7.1. PARTsolutions/base module ERP linkdb
4.1.7.2. PARTsolutions/base module ERP
4.1.7.3. PARTsolutions/base module ERP CSV
4.2. Installation Link database
4.2.1. Hardware requirements
4.2.2. Installation von PARTsolutions parts management with PDM/ERP/PLM integration
4.2.3. Configuration of the database server connection (exemplified by MSSQL)
4.2.4. Create database scheme and users for ERP (exemplified by MSSQL)
4.2.4.1. Installations script
4.2.4.2. Base functionality
4.2.4.3. Additional functionalities
4.2.5. Configure the data-source for ODBC (exemplified by MSSQL)
4.2.5.1. Database connection via file DSN
4.2.6. JDBC driver
4.2.6.1. Installation
4.2.6.2. Configuration
4.2.6.3. Jar files for other databases
4.2.6.4. Configuration file jdbc.cfg
4.2.7. ERP connectivity from PARTsolutions via ODBC/JDBC and ERP activation
4.2.7.1. dbproxy.cfg
4.2.7.2. plinkcommon.cfg -> Block [Common] -> Key "DBName" - Determine ODBC data source name in PARTsolutions
4.2.7.3. plinkcommon.cfg -> Block [PARTdataManager] -> Keys "ERPenabled" and "ERPenabledPPrj" - Activate ERP
4.2.7.4. Starting PARTdataManager with ERP integration
4.3. Adding/removing database columns
4.3.1. Apply databases columns per SQL Scripting
4.3.2. Adding database column with PARTlinkManager
4.3.3. Set column visible in PARTdataManager
4.3.4. Removing database column
4.4. Save/restore database
4.5. PARTapplicationServer installation/configuration
4.5.1. General
4.5.2. Overview Multi Site Installation
4.5.3. Caching methods for data storage and operation
4.5.4. Licenses for the PARTapplicationServer
4.5.5. PARTapplicationServer - Installation
4.5.6. Set up PARTapplicationServer as service
4.5.7. PARTapplicationServer - Configuration
4.5.7.1. AppServer: Client configuration
4.5.7.1.1. The respective keys and values of the configuration file
4.5.7.1.2. Key combinations and values of the single GUI options
4.5.7.1.3. Global and local specification of the settings - Privileges for Admin
4.5.7.1.4. Caching on client side or at secondary locations
4.5.7.2. PARTapplicationServer: Server configuration
4.5.7.2.1. Site-Setup-Sync
4.5.7.2.2. Caching index files of $CADENAS_DATA on PARTapplicationServer
4.5.7.2.3. LinkDB queries
4.5.7.2.4. Updates of ERP search index
4.5.7.2.4.1. Logging of LinkDB changes
4.5.7.2.4.2. Manual update and initial creation of LinkDB search index
4.5.7.3. SSL encryption
4.5.8. PARTapplicationServer Dashboard
4.5.9. Set up ERP on PARTapplicationServer
4.5.9.1. Overview on client connection mode to link database and login mode in PARTdataManager
4.5.9.2. Example 1: Database connection via AppServer and manual user login
4.5.9.3. Example 2: Database connection via AppServer and automatic user login
4.5.9.4. Example 3: Direct database connection and manual user login
4.5.9.5. Example 4: Direct database connection and automatic user login
4.5.9.6. Troubleshooting
4.5.10. AppServer Service: Authentication - Assign rights - Rights
4.5.11. More information
4.6. Name rule for the CAD file name
4.7. ERP toolbar and menu
4.8. Table layout for PARTdataManager and (PARTlinkManager)
4.8.1. Adjust table values -> Adjust text / plinkcommon.cfg -> Block [MAPPING_<COLUMN_NAME>] - Key for visible text
4.8.2. Adjust table values -> Adjust color / plinkcommon.cfg -> Block [COLMAPPING_<variable name>] - Key COLORCODE<number>
4.8.3. Adjust table values -> Adjust text and color / plinkcommon.cfg -> Block [MAPPING_<variable name>] -> Key for visible text
4.8.4. Adjust table values -> Adjust color with condition / plinkcommon.cfg -> Block [COLMAPPING_<column name>] -> Key "COLORCOND<number>"
4.8.5. Adjust table values > Set bitmap / plinkcommon.cfg -> Block [BMPMAPPING_<column name>] -> Key "BMPCODE<number>"
4.8.6. Adjust table values -> Set bitmap with condition / plinkcommon.cfg -> Block [BMPMAPPING_<column name>] -> Key "BMPCOND<number>"
4.8.7. Background color for ERP/PDM columns / plinkcommon.cfg -> Block [GROUP_COLORS] -> Key GROUP<number>
4.8.8. Determine column color by indicator in ERP column (very special) / plinkgroups.cfg -> Block [<Role_name>] -> Key "COLORNUMBERTREE"
4.9. Modify column display - plinkcommon.cfg -> Block [LINKDBFIELDS] -
4.10. Basic design of "new ident-no." dialog box - erpcustom.cfg -> Block [USERDIALOG]
4.10.1. material_assign.cfg (with ERP integration)
4.10.2. Ignore custom set values for the combobox - Key "USERDIALOG_SKIPDBLOAD"
4.10.3. Change default description text for ERP_PDM_NUMBER - erpcustom.cfg -> Block [VARS] -> Key "USERDIALOG_ERPNR"
4.11. Timestamp number on/off
4.11.1. Automatically generated ERP_PDM_NUMBER at new creation of parts (on/off) - erpcustom.cfg -> Block [VARS] -> Key "TIMESTAMPNR"
4.11.2. erpcustom.cfg -> Block [dialogOnExport] - Automatic generation of ERP number: Export dialog for material and other fields yes/no
4.11.3. ERP Number Generator - erpcustom.cfg -> Blocks [ERP_NRGENERATOR] und [ERP_NRGENERATOR_CONDITIONS]
4.11.3.1. Prerequisites
4.11.3.1.1. SQL commands for applying the "Sequencer" table in the LinkDB
4.11.3.1.1.1. CNSSEQ Table
4.11.3.1.2. Activating ERP Number Generator
4.11.3.2. Incorporate ERP number into the PARTdataManager
4.11.3.3. Further number generations based on the example of the default setting
4.11.3.4. Adjust conditions for number generation
4.12. User-role concept
4.12.1. Create users
4.12.1.1. Create database user by database internal administration
4.12.1.2. Create database users in database via access from PARTadmin
4.12.1.3. Create users on the side of PARTsolutions via PARTadmin (dialog User-Role assignment) / plinkusers.cfg -> Block <user name>
4.12.1.4. Create database user on the side of PARTsolutions via PARTadmin (dialog "Database user")
4.12.1.5. Role sequence in the dialog box "Select role" / plinkusers.cfg -> Block [<role_name>] -> Key "GROUPORDER"
4.12.2. Create and configure roles
4.12.2.1. Tabbed page "General"
4.12.2.1.1. Dialog box for role selection - plinkgroups.cfg -> Block [Role name] -> Keys "DESC" and "IMAGE"
4.12.2.1.2. Preferred ranges - plinkgroups.cfg -> Block [Role_name] -> Key "PREFRANGE"
4.12.2.1.3. Display condition for parts selection - Colored catalog index - plinkgroups.cfg -> Block [Role_name] -> Key "CONDITIONTREE"
4.12.2.1.4. Viewing condition for table rows - plinkgroups.cfg -> Block [Role_name] -> Key "TABRESTRICTION"
4.12.2.1.5. Show table row but hide LinkDB content - plinkgroups.cfg -> [Role_name] -> Key "CONDITION"
4.12.2.1.6. Columns to be displayed - plinkgroups.cfg -> Block [Role_name] -> Key "VARSUSED / VARSHIDDEN"
4.12.2.1.7. Export condition - plinkgroups.cfg -> Block [Role_name] -> Key "EXPORTRESTRICTION"
4.12.2.1.8. Export information (tooltip) at status lights - plinkgroups.cfg -> Block [Role_name] -> Key "TOOLTIPTEXTEXPORTON" / "TOOLTIPTEXTEXPORTOFF"
4.12.2.1.9. Release certain directories for export - plinkgroups.cfg -> Block [Role_name] -> Key "EXPPRJTAB" / plinktemplates.cfg
4.12.2.1.10. Hide catalogs - plinkgroups.cfg -> Block [Role name] -> Key "HIDELIST"
4.12.2.2. Tabbed page "PDM"
4.12.2.3. Tabbed page "Display"
4.12.2.3.1. Status indicating icons in table - plinkgroups.cfg -> Block [<Role_name>] - Key "BMPCONDITION0"
4.12.2.3.2. Status colors for catalog index - plinkgroups.cfg -> Block [Role_name] -> Key "COLORCONDITIONTREE<number>"
4.12.2.4. Request ERP number per e-mail
4.12.2.5. Tabbed page "Translations"
4.12.3. User-Role assignment
4.12.3.1. User-Role assignment / plinkusers.cfg -> [<role name>] -> Key "GROUPS"
4.12.3.2. plinkcommon.cfg -> Block [Common] -> Key "CADENAS_PRESELECT_LINKDB_GROUP" - Role selection by environment variable
4.13. Manual data administration
4.13.1. Creation of ERP numbers
4.13.1.1. Using PARTdataManager
4.13.1.1.1. Without direct linkage to the ERP system
4.13.1.1.1.1. Manual entry of ERP number
4.13.1.1.2. Applying ERP numbers using an online gateway to the SAP system
4.13.1.2. Using PARTlinkManager
4.13.1.2.1. Enter ERP number with PARTlinkManager
4.13.1.2.2. Import a project into LINKDB – Assign ERP number
4.13.1.3. PARTdataCenter
4.13.2. Edit variant / Create variant in PARTlinkManager
4.13.3. Create variants in PARTdataManager
4.13.4. Editing LinkDB in PARTlinkManager
4.13.4.1. Editing columns
4.13.4.2. Edit row
4.13.5. Delete datasets
4.13.6. Edit/delete dataset using PARTdataManager
4.14. Complex workflows for data maintenance
4.14.1. Overview
4.14.2. Initial filling of the LinkDB / Article assignment
4.14.2.1. Data export per CSV with an example from SAP
4.14.2.1.1. Manual export
4.14.2.1.2. Automated Export
4.14.2.2. Complexity assessment
4.14.3. Updating data
4.14.3.1. Online replication
4.14.3.2. Cyclic replication
4.14.3.3. Automated and cyclical update of data
4.14.3.4. Direct online linkage of the LinkDB to the ERP-DB
4.14.3.5. Configuration file nightupdate.cfg
4.14.3.5.1. Block [LOG]
4.14.3.5.2. Block [MISC]
4.14.3.5.3. Block [LOAD]
4.14.3.5.4. Block [ERPTABLE-IDENTIFY-COLUMNS]
4.14.3.5.5. Block [ERPTABLE-UPDATE-COLUMNS]
4.14.4. New application of parts with ERP Gateway
4.14.5. Distributed Locations - LinkDB Replication
4.15. Index update
4.16. Catalog update with ERP integration
4.16.1. Catalog update Standard information
4.16.2. Standard check on problems with mapping LinkDB entries
4.16.3. Catalog update with ERP integration - Fix mapping problems with the Update manager
4.16.3.1. Catalog update (Tutorial) - Example 1
4.16.3.1.1. Preparations
4.16.3.1.2. Catalog update - Download
4.16.3.1.3. Assignment / release – Overview on the best approaches
4.16.3.1.4. PARTadmin - Check | Compare | Install
4.16.3.1.5. PARTlinkManager - Important notes on procedure
4.16.3.1.6. Update manager - Project assignment to LinkDB datasets
4.16.3.1.6.1. Update manager - Assign projects after mapping automatically processed before
4.16.3.1.6.1.1. Assign project.prj (Standard name adjusted)
4.16.3.1.6.1.2. Assign project2.prj (Adjusted directory)
4.16.3.1.6.1.3. Assign project4.prj (directory relocated and Standard name adjusted)
4.16.3.1.6.2. Update manager - Assign projects without preceding mapping
4.16.3.1.6.2.1. Assign project3.prj (project and Standard number renamed)
4.16.3.1.6.2.2. Assign project5.prj (project and Standard number renamed and Standard name adjusted)
4.16.3.1.6.2.3. Assign project6.prj and project7.prj
4.16.3.1.6.3. Final check
4.16.3.2. Catalog update (Tutorial) - Example 2
4.16.3.2.1. Preparation
4.16.3.2.2. Status after update installation to Bikecompany V2 and before editing with Update Manager
4.16.3.2.3. Editing in Update manager
4.16.3.3. Install update version
4.16.3.3.1. Update without connection to the LinkDB
4.16.3.3.2. Correct version numbers
4.16.3.3.3. Update structure table
4.16.3.4. User interface of Update Manager
4.16.3.4.1. Symbols in the Catalogs section
4.16.3.4.2. Symbols in the Line mapping section
4.16.3.5. Functions
4.16.3.5.1. Active State and Requested State
4.16.3.5.2. Changed standard name
4.16.3.5.3. Moved dataset
4.16.3.5.4. No correlation to the old dataset found
4.16.3.5.5. Conduct assignments across lines
4.16.3.6. Background information
4.16.3.7. Configuration file plinkupdatemgr.cfg
4.16.3.7.1. Block [WORKFLOW]
4.16.3.7.1.1. Key "CUSTOMUPDATESCRIPT"
4.16.4. Catalog update with ERP integration - Check LinkDB mapping problems BEFORE installation (table and 3D view)
4.16.5. PARTsolutions with LinkDB - Troubleshooting at catalog updates
4.16.5.1. Revising / Updating the LinkDB
4.16.5.2. Manual revision via parameter calls
4.17. Further settings in plinkcommon.cfg
4.17.1. Enable automatic login / plinkcommon.cfg -> Block [Login] -> Key "AUTOLOGIN"
4.17.2. Try NT user authentication / plinkcommon.cfg -> Block [Login] -> Key "NTUSERAUTH"
4.17.3. Pinning Dimension attribute OnOff / plinkcommon.cfg -> Block [PARTdataManager] -> Key "LockDimRange"
4.17.3.1. Background information
4.17.4. Login options / plinkcommon.cfg -> Block [PARTdataManager] -> Key "LoginMode"
4.17.5. PARTlinkManager: Line color at missing ERP_PDM_NUMBER / plinkcommon.cfg -> Block [COLORS]
4.17.6. E-mail settings / plinkcommon.cfg -> Block [MAIL]
4.17.7. Own template for Request ERP number per e-mail / plinkcommon.cfg -> Block [MAIL] -> Key "TEMPLATE"
4.17.8. ERP for single parts in assembly tables / plinkcommon.cfg -> Block [PARTdataManager] -> Key "UseErpForAssPart"
4.17.8.1. Preparations in order to put the functionality into practice
4.17.8.2. Loading the assembly in the PARTdataManager
4.17.8.2.1. Assembly without ERP number
4.17.8.2.2. Assembly with ERP numbers
4.17.8.3. Scripting - further possibilities
4.17.9. Update full-text search index / plinkcommon.cfg -> Block [Common] -> Key "UPDATESEARCHINDEX"
4.17.10. Adjust Standard name - Standard name (short) - BOM name / plinkcommon.cfg -> Block [PARTdataManager] -> Keys "NB" "ShortNB" "LINA"
4.18. Translation file "plinkcommon.def"
4.19. Further settings in "plinkgroups.cfg"
4.19.1. E-mail settings for "new ident-no." dialog / plinkgroups.cfg -> Block [<Role_name>] -> Keys "SENDTO" "SUBJECT" "SERVER" "ISHTML"
4.19.2. Own template for Request ERP number per e-mail / plinkgroups.cfg -> Block [<Role_name>] -> Key "TEMPLATE"
4.19.3. Adjust Standard name - Standard name (short) - BOM name / plinkcommon.cfg -> Block [PARTdataManager] -> Keys "NB" "ShortNB" "LINA"
4.20. Translation file "plinkgroups.def"
4.21. Further settings in erpcustom.cfg
4.21.1. Load additional scripts - erpcustom.cfg -> Block [LOAD]
4.21.2. Default value for new "ACATIVE_STATE" values - erpcustom.cfg -> Block [VARS] -> Key "NEWASTATE"
4.22. Getting started - Demo database
4.22.1. Features
4.22.2. Subsequent installation of PLDBDEMO instance
4.22.3. ERP activation / deactivation
4.23. Troubleshooting
4.23.1. Link database troubleshooting
4.23.1.1. Disabling Journaling on DB2/400
4.23.1.2. Database login - Error message
4.24. PARTadmin Reference
4.24.1. Menus
4.24.1.1. File
4.24.1.2. ? (Help)
4.24.2. Icons
4.24.3. ERP environment settings
4.24.3.1. Idle time - Connect LinkDB
4.24.3.2. Try NT user authentication
4.24.3.3. Enable automatic login
4.24.3.4. Define Database interface
4.24.4. "Roles" dialog - Buttons
4.24.5. "Roles" dialog - Tabbed pages
4.24.5.1. Tabbed page "General"
4.24.5.2. Tabbed page "PDM"
4.24.5.3. Tabbed page "Display"
4.24.5.4. Tabbed page "Mail"
4.24.5.5. Tabbed page "Translations"
4.24.5.6. Tabbed pages Standard name , Standard name (short) , BOM name
4.24.5.6.1. Syntax
4.24.5.6.2. Examples
4.24.5.6.3. Change NB according to project
4.24.5.6.4. Change NB via vbs scripting
4.25. PARTlinkManager reference
4.25.1. PARTlinkManager: Launch from Start menu
4.25.1.1. License selection dialog box at Floating licensing
4.25.2. Launch PARTlinkManager from PARTdataManager
4.25.3. Authorization rights
4.25.4. Menus
4.25.4.1. File
4.25.4.1.1. Connect
4.25.4.1.2. Connect as...
4.25.4.1.3. Switch role
4.25.4.1.4. Disconnect
4.25.4.1.5. Export as -> CSV table
4.25.4.1.6. Import
4.25.4.1.7. Execute Script
4.25.4.1.8. Exit
4.25.4.2. View
4.25.4.2.1. Show tree
4.25.4.2.2. Display filtered tree
4.25.4.2.3. Hide old versions of parts
4.25.4.3. Extras
4.25.4.3.1. Database
4.25.4.3.1.1. Adding/removing database columns
4.25.4.3.1.1.1. Apply databases columns per SQL Scripting
4.25.4.3.1.1.2. Adding database column with PARTlinkManager
4.25.4.3.1.1.3. Set column visible in PARTdataManager
4.25.4.3.1.1.4. Removing database column
4.25.4.3.1.2. Show database columns
4.25.4.3.1.3. Save/restore database
4.25.4.3.1.4. Editing additional tables in the PARTlinkManager
4.25.4.3.2. Configure ERP environment
4.25.4.3.2.1. Tabbed page "PARTlinkManager preferences"
4.25.4.3.2.1.1. Set row color
4.25.4.3.2.1.2. Group definitions / Set column color
4.25.4.3.2.1.3. Adjust table values
4.25.4.3.2.1.4. Modify column display
4.25.4.3.2.1.5. Column position in PARTlinkManager
4.25.4.3.2.2. Tabbed page "PARTdataManager preferences"
4.25.4.3.2.2.1. Login mode
4.25.4.3.2.2.2. e-mail notification
4.25.4.3.2.3. Tabbed page "Database"
4.25.4.3.2.4. Tabbed page "Export tables"
4.25.4.3.2.5. Tabbed page "Translations"
4.25.4.3.2.6. Tabbed pages "Standard name", "Standard name (short)", "BOM name"
4.25.4.3.3. Preferences
4.25.4.3.3.1. PARTlinkManager - Search fields
4.25.4.3.3.2. Network
4.25.4.3.3.3. Logging settings
4.25.4.3.4. Catalog update - Update manager
4.25.4.3.5. PARTadmin
4.25.4.4. ? (Help)
4.25.5. Menu buttons
4.25.6. Buttons
4.25.7. Context menu
4.25.7.1. Set fields
4.25.7.2. Duplicate
4.25.7.3. Edit variant
4.25.7.4. Create variant
4.25.7.5. Assign ERP numbers / delete
4.25.7.6. Import project into database
4.25.7.7. Edit project table
4.25.7.7.1. Change standard descriptions according to project
4.25.7.7.2. Explicitly specify sorting order of variants for PARTdataManager table
4.25.7.7.3. Column sorting of geometry columns in PARTdataManager
4.25.7.7.4. Update structure table
4.25.8. Filtering display