Historical deliveries

date is marked as Must have in the RELEX interface definition. This value is carried on the RELEX transactions interface and must remain semantically intact during migration.

Inventory location code (i.e. code for affected store, warehouse, etc.)

Item code (code for finished product or stock keeping unit)

Type of the transaction: DELIVERY = Goods received into stock (or goods returned to supplier) SPECIAL_DELIVERY = To separate fast, special deliveries from normal deliveries

Physical balance quantity in the location in base unit of measure (e.g. SKU, stock unit, piece, smallest possible unit). Quantity sign defines the transaction direction as seen by the warehouse, e.g. outgoing sales is sent as negative quantity. See more detailed instructions in Info tab.

Stores the RELEX transactions.transaction_uid value used by the interface workbook for downstream planning, validation, and migration load execution.

Value of the whole transaction in the location's currency (e.g. €, £, $). Value should always be positive, since transaction quantity determines the direction of the transaction. Negative values are automatically converted to the positive absolute value of the inserted value, if Transaction: Quantity is not 0 or null. If Transaction: Quantity is 0 or null, the absolute value conversion is not done, and the negative value is kept.

Defines the partner related to the transaction, usually: - Sales transactions: Customer - Incoming deliveries: Supplier - Stock transfers: Sending/receiving warehouse

Sales or purchase order number related to sale or goods receival transaction.

Sales or purchase order row number related to sale or goods receival transaction.

Additional transaction type. E.g. delivery channel for deliveries (from supplier, from DC)

Stores the RELEX transactions.time value used by the interface workbook for downstream planning, validation, and migration load execution.

Stores the RELEX transactions.expiration_date value used by the interface workbook for downstream planning, validation, and migration load execution.