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

4.12.1.2.4.1.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

4.12.1.2.4.1.1.1.1.  CNSSEQ Table

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

PARTlinkManager -> Menu "Extras [Extras] " -> Database -> Edit additional tables -> CNSSEQ

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

4.12.1.2.4.1.1.2. Activating ERP Number Generator

Before you can use the ERP number generator, you must make the necessary settings in PARTadmin.

Open in PARTadmin in the dialog area Category under CADENAS_SETUP the configuration file erpcustom.cfg.

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.

The two keys ERP_NRGENERATOR and ERP_NRGENERATOR_CONDITIONS are now used.

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

The numbers are set consecutively, regardless of the setting 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 00001, 00002, 00005

Manufacturer catalog part: 00003, 00004

The parts with counters 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 generator names with the special generation pattern are defined in the ERP_NRGENERATOR block. Any number of variants can be created.

The associated catalog, directory or project path is defined for each generator in the EPR_NRGENERATOR_CONDITIONS block.

ERP_NRGENERATOR

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

The separator between the individual values is the colon.

Two generation modes (GENERATOR_1 and GENERATOR_2) are defined in the standard environment.

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 conditions.

The separator between the individual values is the colon.

Requirements depending on roles

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

The syntax is:

[ERP_NRGENERATOR_CONDITIONS(rolename)]

Call up the Add block command via the context menu. Then insert the required keys. You can find detailed information on this under Section 1.6.1.4, “Editing blocks and keys”.