LOT Lines Data Table Columns

REQ	SM	COLUMN NAME	TYPE	UC	VALIDATE	DEFAULT	JUST	NOTE
– – – – – – – – – – – – Keys
M	S	SEQUENCEKEY	A	U			R12	[1]
– – – – – – – – – – – – Transaction Entries
O	S	UNITIDENTIFIER	A	U			L20	[2]
M	S	TRANSACTIONTYPE	A	U			R2
M	S	TRANSACTION	A	U			R10
M	S	LINEKEY	A	U			R10
– – – – – – – – – – – – Posting Control Entries
M	S	STATUS	A	U			R2
M	S	POSTDATE	A	U	DATE	TODAY	R10
M	S	LOCATION	A	U	VT=LOCATIONS	WH	L12
– – – – – – – – – – – – Lot Identification Entries
M	S	ACCOUNT	A	U	VT=ACCOUNTS		L10
M	S	PRODUCT	A	U	VT=PRODUCTS key1		L12
M	S	VARIETY	A	U	VT=PRODUCTS key2	null
C	S	CONTROL	A	U		[3]	L16	[4]
O	S	CONDITION	LC	U	Unit Condition Codes	G	L2	[5]
– – – – – – – – – – – – Other Entries
O	T	DESCRIPTION	A				T40
– – – – – – – – – – – – Quantitative Entries
M	S	UNITUOM	LC	U	Units of Measure	PL	L4
O	S	UNITNET	N.2		(MD2)		R8
O	S	UNITTARE	N.2		(MD2)		R8
O	S	UNITSIZE	N.2		(MD4)		R8
O	S	UNITSTACK	N.0		(MD0)		R1
M	S	PACKAGEUOM	LC	U	Units of Measure	CA	L4
M	S	PACKAGECOUNT	N.0		(MD0)		R8
O	S	PACKAGEONHAND	N.0		(MD0)		R8
O	S	PACKAGERESERVE	N.0		(MD0)		R8
O	S	PACKAGENET	N.4		(MD4)		R8
O	S	PACKAGETARE	N.4		(MD4)		R8
O	S	PACKAGESIZE	N.4		(MD4)		R8
O	S	OVERSHORT	N.0		(MD0)		R8	[6]
O	S	INNERUOM	LC	U	Units of Measure	EA	L4
O	S	INNERONHAND	N.0		(MD0)		R8
O	S	INNERRESERVE	N.0		(MD0)		R8
O	S	INNERWEIGHT	N.4		(MD4)		R8
O	S	INNERSIZE	N.4		(MD4)		R8

[1]	Transaction lines are directly written from transaction documents in receipts, shipments, and adjustments.

[2]	UNITIDENTIFIER is required when tracking is by (U)nit; it is optional when tracking by (C)ontrol.

[3]	A CONTROLCODE (on the product master) may determine default values for lot control, such as a rotation date or a warehouse lot sequence.

[4]	CONTROL may be entered optionally when tracking is by (P)roduct.

[5]

Inventory control allows a single primary condition code which is used with balance identifiers, where only lot balances which are (G)ood are considered available. Additional conditions which may apply to units in a lot: quality check, inspection hold, freezer hold, and so forth, are considered descriptive and are ignored for posting purposes.

[6]	OVERSHORT quantity applies to content of receipts only. Hidden quantity shortage within sealed cartons cannot be detected when receiving.

Note

• Tracking requirements are set by product and are not reflected in the transaction line data.
• When multiple fungible units are received on a line, the number of units is determined from QUANTITY divided by PACKAGECOUNT, plus 1 for a remainder.
• Unit counts may not make sense for some bulk products, such as a piled sand or liquid in a storage tank. Such products should have a null PACKAGECOUNT entry.
• When products or lots are fungible then storage units must be uniform. This is a necessary consequence of not tracking individual units. Non-uniform units require separate lot control values or unit identifiers to manage inventory.

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

1. Entries of type list code (TYPE=LC) are validated against the associated linked code option list.
2. Entries with a paired requirement (REQ=P) are required when the associated paired entry or code is specified.