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_step_data

  • Last UpdatedNov 20, 2024
  • 2 minute read

The job_step_data table captures data as each step is executed for each step/lot combination such as the start and end times, the user performing the work, and any data associated with the step for each lot (or serial) number. The step_data and 6 spare fields allow for specific data to be captured by step and lot if required.

These rows are only created when a step is started on a specified lot.

Field

Datatype

PK

Nulls?

Description

wo_id

string40

N

N

Identify work order

oper_id

string40

N

N

Identify operation

seq_no

int32

N

N

Identify row in job table

step_no

int32

N

N

Identify step

lot_no

string40

N

Y

Lot or serial number of specific piece or batch

sublot_no

string40

N

Y

Sublot or serial number of specific piece or batch

state_cd

int32

N

N

Step state – only NEW, READY, RUNNING, COMPLETE, BYPASSED, or SUPERSEDED allowed

act_start_time_UTC

tdatetime

N

Y

Time the step was started in UTC

act_start_time_local

tdatetime

N

Y

Time the step was started in local time

act_finish_time_UTC

tdatetime

N

Y

Time the step was finished in UTC

act_finish_time_local

tdatetime

N

Y

Time the step was finished in local time

step_data

string254

N

Y

Data for specific piece or batch

step_data_time_UTC

tdatetime

N

Y

Time the step data was entered in UTC

step_data_time_local

tdatetime

N

Y

Time the step data was entered in local time

start_user_id

string40

N

Y

User that started the step

finish_user_id

string40

N

Y

User that finished the step

data_user_id

string40

N

Y

User that entered the step data

form_done

logical

N

N

Has form data entry been performed at this step? Default = No.

spare1

string80

N

Y

Use defined by language term 5329

spare2

string80

N

Y

Use defined by language term 5330

spare3

string80

N

Y

Use defined by language term 5331

spare4

string80

N

Y

Use defined by language term 5332

spare5

string80

N

Y

Use defined by language term 5333

spare6

string80

N

Y

Use defined by language term 5334

last_edit_comment

notes

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

Last time this row was edited – use as mod_id field

row_id

ID 1

Y

N

Unique identifier for row for audit trail purposes

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

FK from state_cd to job_state. (Inhibit delete)

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