Enabling M3 BE Integrated M3 SCP Model

This document explains how you enable the integration between M3 Business Engine (BE) and M3 Supply Chain Planner (M3 SCP).

Basic data from M3 BE is accumulated in M3 SCP versions and imported into M3 SCP. M3 SCP is a client planning tool that optimizes the supply chain and exports data back to BE in the form of sourcing rules, master demand schedules and/or inventory buildup proposals.

Outcome

The process results in an integrated Supply Chain Planning (SCP) Model.

The M3 SCP model is used for supply chain optimization in M3 SCP.

During this process, a large number of tables are updated. These tables are listed in the individual documents in the See also section.

Before you start

  • The basic settings for supply chain planning must have been defined.
  • You must have sufficient knowledge about the company's supply chain to be able to create your node network.
  • Demand data, such as sales forecasts, must exist.
  • Other planning data must exist.

Workflow

  1. Define M3 SCP Settings

    Some general settings must be defined before you can start building your Supply Chain Planning version. You define the basic parameters, such as units of measurement and time fences, for supply chain integration in 'Settings - Supply Chain Planner' (SPS701). These settings are defined on a company level.

  2. Define and Build M3 SCP Node Network

    By defining nodes and node distribution relations (NDR), you build the network that will be connected to your SCP version. Refer to See Also section for related documents.

    Market demand is connected to the sales nodes, which represent the end customers. Demand at the different sales nodes in the supply chain is retrieved from datasets in M3 BE. Demand may come from sales statistics, sales budgets or sales forecasts.

    When defining the NDRs, you specify the transportation lead time and the capacity and cost for distributing goods between two nodes. You can also control whether an item number or M3 SCP item group should be included in or excluded from an NDR.

  3. Define M3 SCP Item Group

    Items to be included in the supply chain planning are connected to the M3 SCP version. You may run M3 SCP on an aggregated or stockkeeping unit (SKU) level (item numbers). SCP Item Group provide an aggregated level aimed at reducing the amount of data. M3 SCP item groups may be created on different levels; that is, one group may be included in another.

    Item numbers are either connected manually or generated to an M3 SCP item group. Note that an item number can only be connected to one M3 SCP item group per company.

  4. Defining Manufacturing Resource Constraints

    The M3 SCP model needs information about the resources available for manufacturing and distribution. You use the functionality for rough-cut capacity planning (RCCP) to create resource profiles per item or M3 SCP item group.

    Distribution resources are set on the node distribution relations when you create your node network.

  5. Creating M3 SCP Version

    You create M3 SCP versions in 'M3 SCP Version. Open' (SPS100). The M3 SCP versions keep the data that is to be exported to or imported from M3 SCP together. You connect the physical network (nodes and node distribution relations) and its contents (M3 SCP item groups or items and warehouse, supplier and market demand information) to the M3 SCP version.

Related topics