While this table does not have a field defined as a primary key, the ERPPAYFROMACCOUNTINGENTITYID field should be unique and considered a primary key.
Added in version 8.3.0.08
The ERPPAYFROMAccountingENTITY table supports master data consolidation of duplicate accounts when integrated with an ERP system.
|
|
While this table does not have a field defined as a primary key, the ERPPAYFROMACCOUNTINGENTITYID field should be unique and considered a primary key. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
ERPPAYFROM ACCOUNTINGENTITYID (PK) |
nchar(12) |
NOT NULL |
ERPPAYFROM ACCOUNTINGENTITY_PRIMARY(AK) |
|
|
| ERPPAYFROMID |
nchar(12) |
NOT NULL |
(One) to (Many) | ERPPAYFROM.ERPPAYFROMID | |
|
CREATEUSER(FK) |
nchar(12) |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime(8) |
NULLS |
|
|
|
|
MODIFYDATE |
datetime(8) |
NULLS |
|
|
|
|
MODIFYUSER (FK) |
nchar(12) |
NULLS |
|
(Many) to (One) |
|
| ISDEFAULT |
nchar(1) |
NULLS | |||
| BACKOFFICEACCTENTITYID |
nchar(12) |
NULLS |
(One) to (Many) | BACKOFFICEACCTENTITY.BACKOFFICEACCTENTITIYD | |
| BACKOFFICEID |
nchar(12) |
NULLS |
(One) to (Many) | BACKOFFICE.BACKOFFICEID |