The sample dataset

In order to make it easier to learn and practice Envision, we provide the following two sample datasets. These dataset are not real data, but we have made significant efforts to make sure it is similar to the data that can be found in a real-world supply chain. All the code snippets provided in the following are expected to work when applied to these dataset.

Dataset overview

The dataset represents the historical data of a small fictitious retailer. The dataset includes multiple tabular files formatted as flat text files.

The sample dataset contains the following files:

• Lokad_Items.tsv contains the list of products sold by the retailer.
• Lokad_Orders.tsv contains the list of historical client orders.
• Lokad_PurchaseOrders.tsv contains the list of historical purchase orders made to suppliers.
• Lokad_Suppliers.tsv contains the list of suppliers with their respective properties.
• Lokad_BOM.tsv contains the bills-of-material for bundles.

This dataset includes many interesting pieces of information such as product categories, stock levels, selling and purchasing prices, lead times, etc. It is also representative of the data that can typically be obtained from a company that uses a not-too-ancient ERP.

Using the dataset

You can use the links above to download the TSV files. Then, go to the Files tab of your Lokad account, create a folder named /sample – the path /sample is the convention that we follow in the rest of the documentation, and re-upload these files into this newly created folder. Your Lokad account should look like this:

Dataset details

In this section, we document all the fields contained in the sample datasets’ different files.

Lokad_Items.tsv

This file contains the list of products sold by the retailer along with relevant attributes at the product level.

• Id: the SKU identifier.

• Name: display name of the product.
• Category: top hierarchical level to organize the products.
• SubCategory: top hierarchical level to organize the products.
• Brand: brand name.
• ColorCode: color attribute.
• Supplier: primary supplier from whom the product is purchased.
• BuyPrice: per-unit purchase price, net of tax.
• SellPrice: per-unit selling price, net of tax.
• SellCurrency: currency of the selling price.

• SupplierLeadTime: default supplier delivery lead time, expressed in number of days.
• StockOnHand: the number of units readily available.
• StockOnOrder: the number of units already ordered from the suppliers but not yet received.

Lokad_Orders.tsv

This file contains the historical sales data disaggregated down to the transaction level, as the client identifiers are also provided.

• Id: a foreign key to the “Id” column in the Items file, the SKU identifier.

• Date: ordering date.
• Quantity: quantity ordered in units.
• Currency: a 3-letter code for the currency.
• NetAmount: amount paid for the order line, without taxes.

Lokad_PurchaseOrders.tsv

This file contains the historical purchase orders data disaggregated down to the transaction level of every shipment.

• Id: a foreign key to the Id column of the Items file.

• Date: date when the purchase order was placed.
• DeliveryDate: date when the goods were delivered, or blank if goods have not been delivered yet.
• Quantity: ordered quantity in units.
• Currency: a 3-letter code for the currency.
• Supplier: identifies the supplier who has received the purchase order.
• NetAmount: amount paid for the purchase order line, without taxes.

Lokad_Suppliers.tsv

This file contains the list of suppliers with their respective properties. On purpose, this file is not indexed by an Id column but by a Supplier column.

• Supplier: the index of the table. It acts as a foreign key toward PurchaseOrders.Supplier.
• MOQ: the minimal ordering quantity per product when ordering from the supplier.

Lokad_BOM.tsv

This file contains the list of bundles with their respective composition. The purpose of this file is to illustrate how Envision can cope with bills of materials.

• Bundle: a product identifier that identifies the bundle itself.
• Part: a product identifier that identifiers one element of the bundle.
• Quantity: the number of units for the part contained in the bundle.