Tables for Data Logging
- Last UpdatedApr 13, 2021
- 2 minute read
The following changes were made to the data log tables.
New Data_Log Table
Stores logged data values when a logging sample is triggered. Currently this table is accessible only from the MES Web API V3.
|
Field |
Datatype |
PK |
Nulls? |
Description |
|---|---|---|---|---|
|
grp_id |
int32 |
N |
N |
Identify logging group |
|
ent_id |
int32 |
N |
Y |
Entity from which data came |
|
sample_time_utc |
tdatetime |
N |
N |
When sample was first taken in UTC (GMT) |
|
sample_time_local |
tdatetime |
N |
N |
When sample was first taken in local time |
|
wo_id |
string40 |
N |
Y |
Identify work order |
|
oper_id |
string40 |
N |
Y |
Identify operation |
|
seq_no |
int32 |
N |
Y |
Identify row in job table |
|
step_no |
int32 |
N |
Y |
Identify step within job |
|
item_id |
string40 |
N |
Y |
To which item data applied |
|
lot_no |
string40 |
N |
Y |
To which lot data applied |
|
sublot_no |
string40 |
N |
Y |
To which sublot data applied |
|
shift_id |
int32 |
N |
N |
Identify Shift |
|
shift_start_utc |
tdatetime |
N |
N |
When shift started in UTC (GMT) |
|
shift_start_local |
tdatetime |
N |
N |
When shift started in local time |
|
genealogy_id |
string254 |
N |
Y |
PEM intra-segment genealogy ID |
|
segment_requirement_ |
string80 |
N |
Y |
S95 segment requirement ID |
|
segment_response_id |
string80 |
N |
Y |
S95 segment response ID |
|
value1 |
string80 |
N |
Y |
1st value to be logged |
|
value2 |
string80 |
N |
Y |
2nd value to be logged |
|
value3 to value63 |
string80 |
N |
Y |
3rd to 63rd values to be logged |
|
value64 |
string80 |
N |
Y |
64th value to be logged |
|
last_edit_comment |
string254 |
N |
Y |
Reserved for internal use to indicate why this record was changed |
|
last_edit_by |
string40 |
N |
Y |
Who last changed this record |
|
last_edit_at |
tdatetime |
N |
N |
When this record was last changed |
|
created_at_utc |
tdatetime |
N |
N |
When this record was created, in UTC |
|
created_at_local |
tdatetime |
N |
N |
When this record was created, in the local time of the entity |
|
row_id |
bigint64 |
Y |
N |
Unique row identifier, for audit trail. |
FK from grp_id to data_log_grp. (Cascade delete)
Note that there is no FK from wo_id, oper_id, seq_no to job, or from item_id to item in case logging is independent of them.
Data_Log_Group Table
-
For the trigger_type field, only the manual trigger type (0) is supported by the system.
-
The trigger_detail field is not used by the system.