Table EcENTITY

entity data (item, change order, purchase request, etc)

field

data type

description

id

bigint not null PK

record number

bulk_id

int not null

bulk number – unique number for a set of rows that are referenced by EcASSOC ent_id_parent/ent_id_child fields (BOM, Change order items,

…)

ent_class_id

nvarchar 10 not null

entity type (FILE; ITEM; CUSTENT; CO; FLDR)

guid

nvarchar 36

entity guid (only for ent_class_id=CUSTENT)

name

nvarchar 100 not null

entity name (folder name, CustEnt name, item number, CO number)

master_id

bigint

Vault MasterId – remains the same during the whole Vault entity life

iter_id

bigint

iteration number – changes each time the entity is updated/changed

revision

nvarchar 12

entity revision

version

int

entity version

modified

datetime

last time the entity was changed in a Vault/ERP

category

nvarchar 60

entity category (or routing name for CO)

lfcycst_id

int

entity lifecycle state id

lfcycst_name

nvarchar 60

entity lifecycle state display name

base_qty

float

BOM component base quantity

base_uom

nvarchar 10

for ent_class_id = ITEM: unit of measure (Vault UOM abbreviation)

default = ‘’

for ent_class_id = FLDR: ‘LIBRARY’ for Library Folder Type

requested_by

nvarchar 60

communication requested by user name

comm_dir

int not null

bit not null

target system specification: ERP = 0, Vault = 1, FLC = 10

transfer direction: Vault to DI = 0, DI to Vault = 1 changed 2021-02

comm_status

smallint not null default = -1

transfer status:

PreparingData = -1, Pending = 0,

Stage1Finished = 1, Stage2Finished = 2, Success = 7, Ignore=8, Error = 9,

SuccessReportRequest = 70, SuccessReported = 71,

ErrorReportRequest = 90, ErrorReported = 91,

MockMode = -7; PendingPublication = -2

thumbnail

varbinary

thumbnail (export from Vault; only for FILE or ITEM)

created

datetime not null

default = GetDate()

time of creation of the transfer request

processed1

datetime

stage 1 finished timestamp

processed2

datetime

stage 2 finished timestamp

Remarks:

  • entity type is fully specified by two fields: “ent_class_id” + “guid”

however “guid” field is used only when ent_class_id=’CUSTENT’

  • each EcENTITY table record is considered as a data transfer request

  • records are grouped by “bulk_id”,

bulk is data describing one transfer batch, e.g. : BOM structure, CO with linked items, …

bulk is data having relations that must be respected during processing

  • bulk_id value:

    • ERP Connector creates/generates only positive bulk_id value by incrementing the MAX existing value

    • In case external system (ERP) is not able to reliably create/generate such number, it can use its own unique negative numbers;

in other words: external system uses its own negative bulk_id values and guarantees its uniqueness

  • MockMode = for testing purposes only; data should be ignored by the target system

  • field length can be modified

  • comm_dir field data type can be BIT