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

std_oper_ent_spec

  • Last UpdatedNov 20, 2024
  • 2 minute read

The std_oper_ent_spec table contains setup parameters specific to a standard operation being done on a specific entity, independent of which item is being consumed or produced. 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 standard operation as a whole and not any specific step.

Field

Datatype

PK

Nulls?

Description

oper_id

string40

Y

N

Identify operation

step_no

int32

Y

N

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

ent_id

int32

Y

N

Identify entity

ver_id

string40

Y

N

Identify spec version

spec_id

string40

Y

N

Identify spec for operation

spec_value

string1700

N

N

Value for this spec

assoc_file

string254

N

Y

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

assoc_file_type

string254

N

Y

The file type of the file that is associated with the 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

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

FK from ent_id to ent. (Cascade delete implemented by SP)

FK from oper_id, ver_id to std_oper_spec_ver. (Cascade delete)

FK from spec_id to spec. (Cascade delete)

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