1

Transaction Number

This is the transaction number, for example a delivery note number, receipt number or sales order number. Multiple SKUs can be part of this transaction.

Alpha

50

Y

Order Packingslip InventTransId

Space separated

2

Transaction Type

This is the type of the transaction and is a number. This type can be used to filter or exclude certain transaction types from the historical demand.

Alpha

50

Y

1 = Sales order

2 = Transfer order shipment

4 = Production BOM consumption

3

Transaction Type Name

Here, the name of the transaction type can be given. This is for clarifying the types given in the previous field.

Alpha

50

Sales order SalesId

Transfer order TransferId

Production line Production ID

4

Transaction Status

This is the status of the transaction. For example, is it an active transaction (the articles are already delivered, but no invoice is send) or a completely processes transaction (the articles are delivered and the invoice is send).

Alpha

50

Deducted = packing slip posted

Sold = Invoiced

5

Warehouse Code

This is the code of the location or warehouse where the demand transaction is realized. This code is used to analyse the demand from the different locations or warehouses. When no distinct locations or warehouses are in place, this field can be left empty.

Alpha

10

Y, when multiple Locations exist

Warehouse code with an underscore suffix

6

Article Code

The combination of the article code and the location or warehouse code is the unique combination we use in Slim4. If the location or warehouse code is not available, only the article code is used as the unique Slim4 SKU-number.

Alpha

25

Y

Standard items: Item number

Product masters: Product number 

7

Issue Date

This is the actual date of the physical goods movement. This date is used to set up the historical demand in time buckets. Date Format should be consistent (see technical requirements of files).

Date

Y

 Physical date YYYYMMDD

8

Confirmed Date

This is the delivery date confirmed to the customer. This can be used for delivery performance reporting. Date Format should be consistent (see technical requirements of files).

Date

Sales order: Confirmed date

YYYYMMDD

Transfer order: empty

Production BOM: raw material date

9

Requested Date

This is the date the customer requested for receiving the articles. This can be used for delivery performance reporting. Date Format should be consistent (see technical requirements of files).

Date

Sales order: Requested date

Sales line YYYYMMDD

Transfer order: Requested date

Transfer line YYYYMMDD

Production BOM: raw material date

10

Issue Quantity

This is the actual quantity delivered on the issue date.

Real

4 decimal points

Y

Delivered quantity in inventory unit.

Outgoing flow is positive.
Incoming flow is negative.

11

Line Number of Transaction

Line number of the transactions, often 1, but when item exists mulitple times on the same transactions then line number is required and needs to be unique for each Transaction, Warehouse, and Article.

Real

Integer

Y

Line number * 1000

12

Confirmed Quantity

This is the quantity confirmed to the customer, to be delivered on the confirmed date. This can be used for delivery performance reporting.

Real

4 decimal points

Sales order: Confirmed quantity on latest confirmation

Production: start up quantity

13

Requested Quantity

This is the quantity requested by the customer, to be delivered on the requested date. This can be used for delivery performance reporting.

Real

4 decimal points

Sales order: order line quantity 

Transfer order: order line quantity

Production: calculated quantity

14

Customer Number

This is the unique customer ID number.

Alpha

25

Sales order: Customer ID

Transfer order: To warehouse

Production Production ID

15

Customer Type

In this field, the type of customer is represented. It can be used to make a customer segmentation in historical demand.

For example: Business types (B2B, retail, or export) or Regions (EMEA, APAC, or America).

Alpha

50

Sales order: Customer group

Transfer order: empty

Production order: empty

16

Customer Name

This is the name of the customer belonging to the unique customer ID number.

Alpha

100

Sales order: Empty

Transfer order: To warehouse name

17

Sales Price

Here, the sales price on the demand transaction can be given.

Real

4 decimal points

Sales order: Sales price

Transfer order: empty

18

Delivery Location

This is the location where the articles of the demand transaction are delivered to.

Alpha

100

City Country

Space separated (no carriage return)

Production: empty

19

Supplier Number

This is the number of the supplying Supplier/Location.

Alpha

25

Empty

20

Supplier Type

This is the type of the supplying Supplier/Location.

Alpha

50

Empty

21

Supplier Name

This is the name of the supplying Supplier/Location.

Alpha

100

Empty

22

Buying Price

Actual buying price on the demand transaction.

Real

4 decimal points

Empty 

23

Supplying Location

Location of the supplying Supplier/Location.

Alpha

100

Empty

24

Conversion Factor

Conversion Factor of issue quantity. Slim4 Quantity = Issue Quantity * Conversion Factor

Real

4 decimal points

Slim4 conversion factor of the unit.

Required when IssueQuantity is not in same Unit of Measure as other files.

25

Free Field 1

 Customer specific

Alpha

255

26

Free Field 2

 Customer specific

Alpha

255

27

Free Field 3

 Customer specific

Alpha

255

28

Free Field 4

 Customer specific

Alpha

255