# 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.besmart.software/erpc/data-interface-reference-manual/data-interface/data-tables-relations/table-ecentity.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.