User Tools

Site Tools


Sidebar

Go to GMDHsoftware.com

Video Tutorials

User Guide

1. General Information

2. Starting Up

3. Connecting data

4. Demand and Sales Forecasting

5. Inventory Planning

6. Reference

transactions-data

Demand forecasting data

  • Date – the transaction date.
  • Quantity sold – the item amount that was sold in the transaction.
  • Item code – the item identifier is also known as SKU.
  • Item description – a readable name for the item.
  • Item category – the category such as a product group. The number of categories is not limited - as soon as the category is selected, a new option appears as Item category 2, then Item category 3 and so on. The sequence of them forms a hierarchy of categories in Streamline. In other words, the Item category 2 is a subcategory of Item category, the Item category 3 is a subcategory of Item category 2, and so on. The sales history should be broken by these categories.
  • Location (such as a store, warehouse, or region) is used to forecast consumption of each Item code in each location.
  • Location category is used to create a hierarchy of locations, for example, Region > City > Store. The location category hierarchy is imported in Streamline the same way as for the item category hierarchy.
  • Channel represents a channel via which an item is distributed or sold. For example, e-commerce, direct sales, distributors, or a single customer. This column should be used when you need to plan your demand by channels or customers.
  • Sales price/unit – the price of one item in the sale transaction, used to forecast revenue and perform ABC analysis.
  • Transaction revenue – the price of the sale transaction. You should provide Streamline with either the Sales price/unit or Transaction revenue when importing.

Inventory data

  • On hand change – how much the On hand has changed. When this column comes into play the request must return not only the sales transactions but all the transactions impacting the On hand.
  • On hand – is the On hand remaining after the transaction. When both On hand and On hand change are given, the former is the Last on hand.
  • Qty to receive - the amount of the item currently in transition.
  • Delivery date – expected delivery date of the item from your supplier.
  • Lead time – is given in days and represents the interval of time between replenishment order placement and its receipt.
  • Lead time variance – the variance of the item lead time.
  • Order cycle represents how often the item is ordered from your supplier. It can be given in sales history periods (weeks or month), days, or lead times. For example, once per month, or once per item lead time. It must be an integer. For example, if inventory is replenished semimonthly, then enter number 2 and use weekly sales data. If order cycle column has empty cells or is not given at all, the default value is loaded from the inventory report settings.
  • Order rounding allows Streamline to take into account how many items come packed in a carton, allowing the application to suggest exactly the right amount of the item to order.
  • Min lot and Max lot represent optional constraints on how few or how many of this item can be purchased from your supplier.
  • Supplier code – the identifier of the supplier.
  • Supplier’s currency – the currency in which the purchase orders are placed.
  • Shelf life is given in the data aggregation periods (days, weeks or months) and is the desired shelf life time.
  • Item purchase price – the last purchase price of the item in the supplier's currency.
  • Inventory value/unit – the balance value of the item in stock.
  • Info field – any additional field that describes the characteristic of the item, e.g. purchasing preferences or comments.
transactions-data.txt · Last modified: 2019/07/11 08:32 (external edit)