The following prerequisites must be met in order to use the ERP Number Generator:

5.8.7.1.1.3.1.1. SQL commands for applying the "Sequencer" table in the LinkDB

Make sure your PARTsolutions version contains the "Sequencer" table "CNSSEQ". If needed, use the following corresponding command lines.

• MSSQL

  CREATE TABLE CNSSEQ (
    TOPIC VARCHAR(50) NOT NULL,
    PREFIX VARCHAR(50) NOT NULL,
    COUNTER INTEGER NOT NULL,
  PRIMARY KEY(TOPIC,PREFIX,COUNTER)
  );
  grant all on dbo.CNSSEQ to public;

• MySQL

  CREATE TABLE CNSSEQ (
    TOPIC VARCHAR(50) NOT NULL,
    PREFIX VARCHAR(50) NOT NULL,
    COUNTER INTEGER NOT NULL,
  PRIMARY KEY(TOPIC,PREFIX,COUNTER)
  );
  grant all on dbo.CNSSEQ to public;

• Oracle

  CREATE TABLE CNSSEQ (
    TOPIC VARCHAR(50) NOT NULL,
    PREFIX VARCHAR(50) NOT NULL,
    COUNTER INTEGER NOT NULL,
    PRIMARY KEY(TOPIC,PREFIX,COUNTER)
  );
  CREATE PUBLIC SYNONYM CNSSEQ FOR SYSTEM.CNSSEQ;
  GRANT ALL ON CNSSEQ

5.8.7.1.1.3.1.1.1.  CNSSEQ Table

In the LinkDB, the respectively next counter for the generation is saved in the "CNSSEQ" table.

If needed, as many counter names (GEN1, GEN2,...) as possible may be used in order to differentiate between the counters in the LínkDB.

5.8.7.1.1.3.1.2. Activating ERP Number Generator

Before you can use the ERP Number Generator you must make the appropriate settings in PARTadmin.

In PARTadmin, under CADENAS_SETUP open the configuration file erpcustom.cfg in the dialog area Category.

Set the settings as follows:

• TIMESTAMPNR=0

• ERPNR_ENABLED=0 (Activate the key - if needed - per right-click on the key name)

• erp_nrgenerator (Activate the key per right-click on the key name)

Save changes.

Now both keys ERP_NRGENERATOR and ERP_NRGENERATOR_CONDITIONS are used.

With both these keys you define the pattern after which the ERP numbers are to be generated.

Choose a part which does not yet have a number.

Click on Add dataset to link database .

Choose the Material.

Please note: The entry field ERPNo is deactivated since the ERP number is automatically generated.

Click on OK.

The number is inserted into the LinkDB according to the defined key and displayed in the attribute table.

The numbers are set consecutively, independent of settings for special catalogs or directories.

Prefix and postfix are set specifically according to the setting in PARTadmin in the configuration file erpcustom.cfg.

Standard part: Number 00000, 00001, 00002, 00005

Supplier catalog part: 00003, 00004

The parts with counters 00000, 00001 and 00002 were set consecutively in the standard parts catalog.

Afterwards, the counters 00003 and 00004 were set in the supplier catalog.

Then the counter 00005 is again inserted into the standard parts catalog.

The following figure shows the default setting.

The ERP_NRGENERATOR key, defines the generator names with the special generating pattern. You can attach as many variables as needed.

The EPR_NRGENERATOR_CONDITIONS key defines the related catalog, directory and project path for every generator.

ERP_NRGENERATOR

The following table shows the syntax for the entry of the generating pattern and explains the meaning of the individual values.

Separators between individual values are colons.

In the standard environment two generating patterns (GENERATOR_1 and GENERATOR_2) are defined.

Example value for GENERATOR_1: STD:0:0:5:-std:GEN1

Example value for GENERATOR_2: CAT:0:100:5:-cat:GEN1

ERP_NRGENERATOR_CONDITIONS

The following table shows how to configure the requirements.

Separators between individual values are colons.

Requirements depending on roles

You can also define requirements based on user-role dependencies.

The syntax is:

[ERP_NRGENERATOR_CONDITIONS(rolename)]

Via the context menu, launch Insert block. Insert the necessary key. Detailed information can be found under Section 1.1.7.3.5, “Edit blocks and keys”.