Define M3 SCP Settings

This document explains how you define the basic settings for the integration from M3 BE to M3 Supply Chain Planner (M3 SCP). The procedure explains the basic settings for all M3 SCP versions within the company in question.

Outcome

The company is prepared for the integration with M3 Supply Chain Planner. M3 Supply Chain Planner settings control the M3 SCP versions within the company.

In M3, The system parameters file (CSYPAR) is updated.

Before you start

Your company must have a plan for how to use M3 SCP and what time fences to use in the supply chain optimization. You should also have decided upon what search keys to use for your sales nodes.

Follow These Steps

  1. Start 'Settings - Supply Chain Planner' (SPS701/E).

  2. Enter the U/M for weight and volume to be used for your M3 SCP item groups and node distribution relations.

  3. Enter the planning and sourcing time fences to be used for your company's supply chain planning versions.

  4. Enter the key fields that should be used when creating sales nodes. Press Enter.

Parameters to Set

Program ID/Panel Field The field indicates …
(SPS701/E) U/M weight … the U/M of weight for M3 SCP item groups and node distribution relations in M3 SCP. In M3 SCP, this U/M is only used for information.
  U/M volume … the U/M of volume for M3 SCP item groups and node distribution relations in M3 SCP. In M3 SCP, this U/M is only used for information.
  Planning time fence

… the point in the planning horizon outside which the optimization in M3 SCP should take place. When creating an M3 SCP version, the supply chain planning time fence is proposed as the start date for the optimization in M3 SCP.

Inside of this time fence, planning should be done in M3 SWB.

  Sourcing time fence … the point in the planning horizon after which the sourcing rules may be changed. M3 SCP will not permit any changes in sourcing rules within the M3 SCP sourcing time fence.
  Key 1, 2, 3

…the key fields to be used when creating sales nodes. A sales node may consist of up to three different key fields used in datasets, such as Country (UCCSCD) and Area/State (OKECAR).

Once these keys have been set, they may not be changed since this will cause incorrect data in existing sales nodes.

The keys control how demand in datasets is updated per node. For example, if you have created a sales node for Benelux (consisting of Belgium, the Netherlands and Luxembourg), the demand from all customers in these countries is summed up in the node.

Related topics