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

job_spec

  • Last UpdatedNov 13, 2024
  • 2 minute read

The job_spec table provides the ability to override operation specifications for job instances (MTO applications). If there is no record in this table for a particular job, the process’s specifications are used, if they exist.

There is an extra act_param_value field in this table which can be configured to capture actual ‘as built’ values for specific job instances. The trigger to capture actual data would need to be driven by a button on a UI screen.

This data is instantiated from both the oper_ent_spec and bom_item_oper_spec tables when a job is instantiated from a process.

The ‘step_no’ field is used to allow a spec to optionally be linked to a step. This field is set = -1 for specs that apply to the operation as a whole and not any specific step.

Field

Datatype

PK

Nulls?

Description

wo_id

string40

Y

N

Identify work order

oper_id

string40

Y

N

Identify operation

seq_no

int32

Y

N

Identify row in job table

step_no

int32

Y

N

Identify step no. Default = -1 (not associated with a step)

spec_id

string40

Y

N

Identify spec for operation

spec_value

string1700

N

N

Planned value for this spec

act_spec_value

string1700

N

Y

As built value for this spec; initially null

assoc_file

string254

N

Y

The path and file name of the file associated with the job spec.

assoc_file_type

string254

N

Y

The file type of the file that is associated with the job spec. This value is entered internally, based on the file extension of the file specified in the assoc_file field.

comments

string1700

N

Y

Comments/instructions to operator

min_value

string80

N

Y

Minimum acceptable value for the spec. Default = null which means no minimum value defined.

max_value

string80

N

Y

Maximum acceptable value for the spec. Default = null which means no maximum value defined.

access_level

int32

N

Y

Required security access level for modifying this spec. Default = null which means no extra security defined (null has same meaning as value = 0).

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

mod_id

timestamp

N

N

A binary number that increments each time the row is modified.

row_id

bigint64

N

N

Unique row identifier, for audit trail

FK from wo_id, oper_id, seq_no to job. (Cascade delete)

FK from spec_id to spec. (Cascade delete)

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