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

so

  • Last UpdatedNov 20, 2024
  • 1 minute read

The so table stores details for each sales order. The customer and their PO number are used for the primary key in case the organization does not use internal sales order "numbers".

Field

Datatype

PK

Nulls?

Description

cust_id

string40

Y

N

Identify customer placing order

po_id

string40

Y

N

Identify customer PO

date_received_utc

tdatetime

N

N

When SO received in UTC

date_received_local

tdatetime

N

N

When SO received in local time

purchaser_id

int32

N

Y

Reference to contact for purchasing

ship_from

int32

N

Y

From which entity this order is expected to ship (need not be an entity that can ship)

so_id

string40

N

Y

Internal sales order ID if any

state_cd

int32

N

N

Enumeration of the state of this sales order:

0 = open (default)

1 = partially complete

2 = complete

3 = closed

notes

nvarchar(max)

N

Y

Sales order notes

spare1

string80

N

Y

Use defined by language term 4339

spare2

string80

N

Y

Use defined by language term 4340

spare3

string80

N

Y

Use defined by language term 4341

spare4

string80

N

Y

Use defined by language term 4342

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 cust_id to cust. (Cascade delete)

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