While this table does not have a field defined as a primary key, the BACKOFFICEACCTENTITYID field should be unique and considered a primary key.
Added in version 8.3.0.08
The BACKOFFICEACCTENTITY table supports master data consildation of duplicate accounts when integrated with an ERP system.
|
|
While this table does not have a field defined as a primary key, the BACKOFFICEACCTENTITYID field should be unique and considered a primary key. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
BACKOFFICEACCTENTITYID |
nchar(12) |
NOT NULL |
BACKOFFICEACCTENTITY_PRIMARY (AK) |
(One) to (Many) | |
| (One) to (Many) | CONTACTACCOUNTINGENTITY.BACKOFFICEACCTENTITYID | ||||
| (One) to (Many) | ERPBILLTOACCOUNTINGENTITY.BACKOFFICEACCTENTITYID | ||||
| (One) to (Many) | ERPPAYFROMACCOUNTINGENTITY.BACKOFFICEACCTENTITYID | ||||
| (One) to (Many) | ERPSHIPTOACCOUNTINGENTITY.BACKOFFICEACCTENTITYID | ||||
| BACKOFFICEID | nchar(12) | NOT NULL | BACKOFFICEACCTENTITY_BACKOFFID (IE | (One) to (Many) | BACKOFFICE.BACKOFFICEID |
|
CREATEUSER (FK) |
nchar(12) |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime |
NULLS |
|
||
|
MODIFYUSER (FK) |
nchar(12) |
NULLS |
|
(Many) to (One) |
|
|
MODIFYDATE |
datetime |
NULLS |
|
||
|
NAME |
varchar(128) |
NULLS |
|
||
|
ACCTENTITYEXTID |
varchar(64) |
NULLS |
|
|
|
| LOCATION |
nvarchar(22) |
NULLS |