The attached excel file contains a list of tables with columns description for each function block data load. It also highlights required and optional tables/fields that are only used when certain features are enabled.

All tables are separated into blocks, just like in the user interface.

1 Overview
- 1.1 Data types
- 1.2 ETL process example
  - 1.2.1 Master data
  - 1.2.2 General data
  - 1.2.3 Sales and stock data
2 Forecast Tables
- 2.1 Master data
  - 2.1.1 PRICELINES - Price lines (price lists)
  - 2.1.2 REGIONS - Regions
  - 2.1.3 STORES - Stores (and warehouses)
  - 2.1.4 GROUPS - Product groups
  - 2.1.5 PRODUCTS - Products (SKU - Stock Keeping Units)
- 2.2 General data
  - 2.2.1 PRICES - Retail prices
    - 2.2.1.1 PRICES_CURRENT - Current retail prices
  - 2.2.2 PRODUCTS_EAN - Barcodes (EAN codes) of products
- 2.3 Assortment matrices
  - 2.3.1 SKU_RANGE - Assortment matrices, history and future data
    - 2.3.1.1 SKU_RANGE_CURRENT - Current state of the assortment matrix
- 2.4 Sales and stock data
3 Replenishment Tables
4 Reorder point tables
- 4.1 UOM_CLASSES - UOM (Unit Of Measure) classes
- 4.2 PRODUCTS_UOM - Product units conversion
5 Master forecast tables
- 5.1 MASTER_FCST - Master forecast data table at the SKU level
- 5.2 MASTER_FCST_STORES _ List of Stores for master forecast
6 Promotion tables
7 Data completion flag
- 7.1 SEMAPHORE - Data loading completion flag
8 Loading Orders from MySales

Overview

The MySales system works with a wide range of databases (Oracle, Microsoft SQL Server, MySQL, PostgreeSQL, Oracle Teradata and etc.).
We recommend that you choose the database that matches the database of your ERP or similar system where you already have data on sales, stock balances and which is used to register purchase orders and goods receipts.
You can use the following options to create a database:
1. Database instance on separate server
2. Separate database instance on the same server as the ERP database instance.
3. Separate database on ERP server database instance (recommended).
4. Separate database schema on same database on ERP server database instance.
The main workload usually occurs at night, when sales and stock balance data are exchanged between MySales and ERP system and forecasts and orders calculated.

If you are tackle with difficulties when preparing data for loading or with performance issues, you can always contact us, but you must know the data structure of your ERP system.

We may change the data structure, lengths and types of some fields for data storage optimization and compatibility purposes.

Not all tables are required for integration. The list of tables is determined by the capabilities of the ERP system used and the customer's processes.

Data types

The following data types are used in the MySales system:

Data type	MSSQL	ORACLE

Customer support

Specification of Integration

Overview

Data types