LOT DETAILS Data Columns¶
Lot detail record entries are divided into the following sections:
- Keys – A combination of values which uniquely identify a product
- Descriptors – Alternate textual product identification and categorization
- Dimension – The measures of packing for a product
- Transactions – keys, Posting, Lot Identification, and quantitative entries.
Detail Lot Header Columns¶
REQ | SM | COLUMN NAME | TYPE | UC | VALIDATE | DEFAULT | JUST | NOTE |
---|---|---|---|---|---|---|---|---|
– – – – – – – – – – – – Keys | ||||||||
M | S | ACCOUNT | A | U | VT=ACCOUNTS | L10 | ||
M | S | PRODUCT | A | U | VT=PRODUCTS, key1 | L20 | ||
M | S | VARIETY | A | U | VT=PRODUCTS, key2 | null | L10 | |
M | S | CONTROL | A | U | paired: CONTROLCODE | L20 | [A] | |
– – – – – – – – – – – – Descriptive Entries | ||||||||
M | S | POSTDATE | A | U | DATE | TODAY | R10 | [A] |
M | S | CONTROLCODE | LC | U | Lot Control Codes | NA | L4 | [A] |
O | T | DESCRIPTION | A | T40 | ||||
[B] – – – – – – – – – – Dimensional Entries | ||||||||
M | S | UNITUOM | A | U | Units of Measure | PL | L4 | |
O | S | UNITNET | N.2 | (MD2) | R9 | |||
O | S | UNITTARE | N.2 | (MD2) | R9 | |||
O | S | UNITSIZE | N.2 | (MD4) | R9 | |||
O | S | UNITSTACK | N.0 | (MD0) | R1 | |||
O | S | PACKAGEUOM | A | U | Units of Measure | CA | L4 | |
O | S | PACKAGECOUNT | N.0 | (MD0) | R6 | |||
O | S | PACKAGENET | N.4 | (MD4) | R9 | |||
O | S | PACKAGETARE | N.4 | (MD4) | R9 | |||
O | S | PACKAGESIZE | N.4 | (MD4) | R9 | |||
O | S | INNERUOM | A | U | Units of Measure | EA | L4 | |
O | S | INNERCOUNT | N.0 | (MD0) | R6 | |||
O | S | INNERWEIGHT | N.4 | (MD4) | R8 | |||
O | S | INNERSIZE | N.4 | (MD4) | R8 |
[A] | (1, 2, 3) CONTROLCODE may be assigned automatically based on the associated product record. Control codes may determine the default values of control, such as rotation dates or warehouse sequential lot numbers. |
[B] | When a document is entered, defaults for lot dimensional values are copied from the current values of the product master. These values may be changed during document entry. |
LEGEND:
REQ | O = optional
M = mandatory
P = pair required
C = conditional
|
SM | S = single valued
M = multiple values
A = associated (array member)
|
COLUMN NAME | (not case specific) |
TYPE | A = alpha
N.n = numeric with decimals
B = boolean
D = datetime
U = UUID
LC = list of codes
SK = key sequence
S = sequence
|
U | Key values and codes are uppercase |
VALIDATE | links refer to code validation lists
Tablenames (uppercase) refer to verifiles
(‘values’) list allowed entries
|
DEFAULT | a value default |
JUST | Justify (L)eft, (C)enter, (R)ight, (T)ext
n = characters to show
|
Note
- Entries of type list code (TYPE=LC) are validated against the associated linked code option list.
- Entries with a paired requirement (REQ=P) are required when the associated paired entry or code is specified.