Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

data_entry_sched

  • Last UpdatedNov 20, 2024
  • 2 minute read

This table allows for a data collection schedule to be specified for any category of data for a specified entity or user group.

Field

Datatype

PK

Nulls?

Description

key_id

int32

Y

N

Primary key or row_id value of row on which this data collection schedule is based (ent_id if linked to an entity, grp_id if linked to a user group, row_id for tables with non-integer primary keys, possibly others in future).

key_type

int32

Y

N

Enumeration of the basis for this data collection:

0=entity

1=user group

2=std. operation

3=std. operation step

4=operation

5=operation step

6=job

7=job step

category

string40

Y

N

Category of this data collection group, e.g., "Yield KPIs", "Defect Data", "Datalog Group"

value_name

string40

Y

N

Specific data value or set of values to be collected within this category, e.g., "KPI 123", "Line 3 Defect Data", "Datalog Group ABC"

trigger_type

int32

N

N

Enumeration of what triggers this data collection activity:

0=shift start

1=shift end

2=hourly (future)

3=daily

4=weekly

5 = minutes

9=SCC trigger (future)

trigger_period

int32

N

N

If trigger = 2 or 5, the number of hours or minutes between data collection triggers. Greater than or equal to 1, default = 1.

entries_reqd

int32

N

N

Number of entries required each time this data collection activity is triggered, e.g., 8 per shift. Default = 1.

display_seq

int32

N

Y

Optional display sequence for this data entry requirement to facilitate sorting

last_trigger_at

datetime

N

Y

When the last trigger occurred for this data entry requirement, in UTC

last_trigger_desc

string40

N

Y

Description for last trigger, e.g., "Shift 2" or "Daily", "100 items produced"

string_spare1

string40

N

Y

Spare string field copied to data_entry_log when triggered

Note: This field is currently not used.

string_spare2

string40

N

Y

Spare string field copied to data_entry_log when triggered

Note: This field is currently not used.

string_spare3

string40

N

Y

Spare string field copied to data_entry_log when triggered

Note: This field is currently not used.

string_spare4

string40

N

Y

Spare string field copied to data_entry_log when triggered

Note: This field is currently not used.

number_spare1

tfloat

N

Y

Spare numeric field copied to data_entry_log when triggered

Note: This field is currently not used.

number_spare2

tfloat

N

Y

Spare numeric field copied to data_entry_log when triggered

Note: This field is currently not used.

number_spare3

tfloat

N

Y

Spare numeric field copied to data_entry_log when triggered

Note: This field is currently not used.

number_spare4

tfloat

N

Y

Spare numeric field copied to data_entry_log when triggered

Note: This field is currently not used.

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 record was last changed

row_id

ID 1

N

N

Unique row identifier, for audit trail

TitleResults for “How to create a CRG?”Also Available in