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

wo

  • Last UpdatedNov 20, 2024
  • 3 minute read

The wo table contains header data for released work orders, which includes data such as which parent item is required, what quantity and by when. This data is common to all jobs (operations) within the work order. It thus defines what work orders are scheduled to run at the facility at various times. It also records data for work orders that are currently running or have been completed or suspended.

The status of a work order is different than the status of its constituent jobs, though it is somewhat dependent on their statuses. It is coded differently and has a different meaning.

The ‘not_deletable’ field is used to specify that this wo or any of its dependent data may not be deleted. The dependent data includes any data in the following tables for the specified wo_id: wo, wo_attr, job, job_attr, job_route, job_bom, job_step, job_step_grp, job_step_file, job_bom_step, job_step_data, job_spec, wo_file, item_prod, item_cons. This is useful in some cases for maintaining audit trails.

Field

Datatype

PK

Nulls?

Description

wo_id

string40

Y

N

Identify work order

wo_desc

string80

N

Y

Work order description

process_id

string40

N

Y

Identify process unless created on-the-fly

bom_ver_id

string40

N

Y

BOM version of the original item this work order makes specified at the time it was created, unless created on-the-fly

spec_ver_id

string40

N

Y

Specification version selected for all operations (if any) at the time this work order was created, unless created on-the-fly

item_id

string40

N

N

Final item being made, unless all its jobs are disassembly, in which case this is initial item

req_qty

float

N

N

Qty of item required, default value for final operation’s jobs to total

release_time_utc

tdatetime

N

Y

When work order was/will be released in UTC

release_time_local

tdatetime

N

Y

When work order was/will be released in local time

req_finish_time_utc

tdatetime

N

Y

Required completion datetime in UTC

req_finish_time_local

tdatetime

N

Y

Required completion datetime in local time

state_cd

int32

N

N

0 = Released (default)

1 = Started

2 = Completed

3 = Closed

When closed nothing else for this work order is editable

wo_priority

int32

N

Y

Work order priority; default value for job_priority in job table (0- 2147483647)

cust_info

string80

N

Y

Customer info for this work order

mo_id

string40

N

Y

Manufacturing order, for grouping different final parts

production_schedule_
id

string80

N

Y

Production schedule to which work order (Production Request ID) belongs

notes

nvarchar(max)

N

Y

Notes about this work order

not_deletable

logical

N

N

Disallow deletes of any work order dependent data for this work order. Default = No, except if work order was created from a ‘Certified’ process.

disassembly

logical

N

N

If Yes, this work order is disassembling something (BOM_pos = 0) into its components (BOM_pos > 0). Default = No.

may_override_route

logical

N

N

If Yes, certain methods would include operations other than those immediately upstream or downstream from the current one. Default No.

override_
serialization

logical

N

N

If Yes and any item the work order produces is normally serialized, it is treated as not serialized. Default = No.

input_wo_id

string40

N

Y

Identifies the job that initiated this work order (used for rework/dynamic routing work orders)

input_oper_id

string40

N

Y

input_seq_no

int32

N

Y

target_sched_line_id

int32

N

Y

The line to which this work order is assigned.

queue_seq_no

int32

N

Y

If a work order is queued to a line, its relative position in the queue.

Will be null if target_sched_line_id is null.

Note: This field is currently not used.

spare1

string80

N

Y

Use defined by language term 5157

spare2

string80

N

Y

Use defined by language term 5158

spare3

string80

N

Y

Use defined by language term 5159

spare4

string80

N

Y

Use defined by language term 5160

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

ID 1

N

N

Unique row identifier, for audit trail.

FK from process_id to process. (Inhibit delete)

FK from item_id to item. (Cascade delete)

FK from target_sched_line_id to line. (Set null)

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