job_bom_default
- Last UpdatedNov 20, 2024
- 1 minute read
The job_bom_default table provides defaults for cases where BOM position and/or storage entities need to be assigned dynamically – BOM_pos when Job_BOM record is created (via SCC import without it) and storage entities when the job is started.
|
Field |
Datatype |
PK |
Nulls? |
Description |
|---|---|---|---|---|
|
item_id |
string40 |
Y |
N |
Identify item |
|
ent_id |
int32 |
Y |
N |
Identify entity to/on which job is scheduled or run |
|
BOM_pos |
int32 |
N |
N |
Identify BOM position to assign when importing a job_BOM record without it |
|
storage_ent_id |
int32 |
N |
Y |
Identify storage entity to use for good production when starting a job |
|
reject_ent_id |
int32 |
N |
Y |
Identify storage entity to use for reject production when starting a job |
|
last_edit_comment |
string254 |
N |
Y |
Reserved for internal use to indicate why this record was changed |
|
last_edit_by |
string40 |
N |
N |
Who last changed this record |
|
last_edit_at |
tdatetime |
N |
N |
When this data was entered or last edited. Used as a mod_id field for updates. |
|
row_id |
ID 1 |
Y |
N |
Unique identifier for row (a consumption transaction) |
FK from item_id to item. (Cascade delete)