This document explains how you create an SCP version and connect node networks and SCP groups or item numbers to it.
An SCP version with status 10 (deactivated) is created in the system.
The following tables are updated:
The SCP version is used to keep the data that will be exchanged between M3 BE and SCP together. Data is accumulated in the SCP version when you activate it (status 20).
Create SCP Version
Start 'SCP Version. Open' (SPS100/B).
Set the panel sequence to E12.
Enter the identity of the new SCP version and a blank version category.
Version categories other than blank, such as MDS, are used in simulations or when receiving data from SCP.
On the E panel, enter a name and description, and the user responsible for the SCP version.
Specify the aggregation level to be used.
Specify the currency and the exchange rate type that should be used.
Specify the dataset, budget version, quantity field, transaction type and MDS version to be used for demand data in the SCP version. These fields are optional.
Specify the SCP period type.
Check and, if needed, change the start and/or end date and the sourcing time fence proposed.
Connect Node Network to SCP Version
In 'SCP Version. Connect Node' (SPS110/B), connect one or several nodes to the SCP version.
You can display available nodes by pressing F4=Prompt.
For sales nodes, you can change the dataset, budget version, quantity and/or transaction type from which demand should be retrieved on the (SPS110/E) panel.
Connect Supplier and Warehouse to Nodes
Specify related option Nodes/SCP Version to start 'SCP Version-Node. Connect Object' (SPS111/B).
Sorting order B1 or B2 will be displayed, depending on whether the node is a purchase or a supply node.
For purchase nodes, enter one or several supplier(s). For supply nodes, enter a warehouse.
On the (SPS111/E2) panel, enter an MDS version; that is, whether you want to override the default MDS version set in (SPS100).
Define Supplier Constraints
Specify related option Supply capabil for the supplier(s) entered in (SPS111/B1). 'Supplier. Connect Assortment' (PPS012/B1) is started.
Select delivery group type 4 (SCP item group) or 5 (item number).
Specify the delivery groups to which the supplier is allowed to deliver.
Enter the delivery capacity and whether capacity should be considered on the (PPS012/E) panel. Press Enter.
Connect SCP Item Group or Items to SCP Version
Press F3=Close three times to start 'SCP version. Connect SCP Item Group/Item' (SPS112/B1).
Connect one or several item groups or items to the SCP version manually or select F14=Generate items to start 'SCP Version. Generate Items' (SPS113).
Make the desired selections of items on panel (SPS113/E). This works the same way as when you generate items to an SCP item group.
Select the Add/replace parameter if you want transactions to replace existing transactions.
Press Enter to start generating items.
Press F3=Close twice to return to 'SCP Version. Open' (SPS100/B).
|Program ID/Panel||Field||The field indicates …|
… the SCP version to be used when creating data for M3 SCP/M3 Yield Optimizer or receiving data from SCP/Yield Optimizer.
To be able to optimize/simulate a company's supply chain, you need a wide variety of data, such as nodes, SCP item groups and so on. The SCP versions are used to keep these data together.
|SCP version category||
… the category of an SCP version. A blank SCP version category means a standard SCP version; that is, data sent to M3 SCP.
Other SCP version categories are used when using simulations or receiving data from M3 SCP.
|(SPS100/E)||Responsible||… the user responsible for the SCP version.|
|Aggregation level||… the level on which data is aggregated in this SCP version. The two alternatives are SCP item group or item number.|
|SCP currency||… the currency to be used in the SCP version. All prices and costs are converted to this currency when you activate the SCP version.|
|Exchange rate type||… the exchange rate type to be used when converting into SCP currency.|
… the default dataset used in M3 SCP. Demand at sales nodes is stored in datasets. A dataset identifies the contents and search paths for a specific budget level and/or reporting level for key information from customer, service and/or maintenance orders and projects.
The dataset entered here may be overridden per sales node in 'SCP Version. Connect Node' (SPS110).
|Budget version||… the budget version stored in the dataset. The budget version entered here can be overridden per sales node in (SPS110).|
… the default field from which quantities for demand in M3 SCP are retrieved.
The valid alternatives are UCIVQT (Invoiced quantity - basic U/M), UCDEMA (Demand) and UCORQT (Ordered quantity - basic U/M).
This default field may be overridden per sales node in (SPS110).
… the default transaction type to be used in M3 SCP. Transaction types are used to classify the input to and content of a dataset.
The valid alternatives are 32=Sales statistics, 33=Sales budget, 34=Calculated sales forecast and 35=Lost sales.
The transaction type can be overridden per sales node in (SPS110).
|Master demand schedule version||
… the master demand schedule (MDS) version to be used in the SCP version.
The MDS version may be overridden per supply node in (SPS111).
|SCP period type||
… the period type used in the SCP version.
The valid alternatives are 1=MPM period (from (MNS100)) and 2=Daily buckets.
If you choose daily buckets, demand and capacity data will be stored on a daily level. If you choose MPM periods, the data will be stored on the first day of the period. The length of the MPM period is set per division.
|Start date||… the start date for the optimization or simulation in M3 SCP. This date is calculated as the date on which the SCP version is created plus the number of days entered in the SCP planning time fence field in (SPS701).|
|End date||… the optimization or simulation end date in M3 SCP. You enter this date manually.|
|(SPS110/B)||Node||… which node(s) to include in the SCP version.|
… a dataset that will be used for the selected sales node.
The default dataset from (SPS100) is overridden when you enter another dataset in this field.
|Budget version||… a budget version in the dataset selected. The default budget version from (SPS100) is overridden when you enter another budget version in this field.|
… from where the demand quantities for the sales node should be retrieved.
The valid alternatives are UCIVQT (invoiced quantity), UCORQT (ordered quantity) and UCDEMA (demand).
The default value from (SPS100) is overridden when you enter another quantity field in this field.
… the transaction type for the sales node selected. The valid alternatives are 32=Sales statistics, 33=Budget, 34=Calculated sales forecast and 35=Lost sales.
The default budget version from (SPS100) is overridden when you enter another transaction type in this field.
|(SPS111/B2)||Warehouse||… the warehouse(s) connected to the selected supply node. Only warehouses from the same facility may be connected.|
|(SPS111/E2)||MDS version||… which version of the master demand schedule is used in M3 SCP. The default MDS version is set in (SPS100), but may be overridden when you enter another MDS version in the field.|
|(SPS111/B1)||Supplier||… the supplier connected to the selected purchase node. Only one supplier may be connected per purchase node.|
|(PPS012/B1)||Group type||… the type of delivery group to which the supplier may deliver. The valid alternatives are 4=SCP item group or 5=Item number.|
|Delivery group||… the delivery group to which the supplier is allowed to deliver, in this case, an SCP item group or an item number.|
|(PPS012/E)||Delivery capacity||… the capacity a supplier can deliver of an SCP item group/item per working day, expressed in the basic U/M of the SCP item group/item.|
… whether the manually entered capacity in (PPS012/E) should be considered in the optimization/ simulation in M3 SCP. If this parameter is not selected, SCP uses infinite capacity.
Note that this setting can be overridden in SCP.
|(SPS112/B1)||SCP Item Group||… the SCP item group(s) that will be included in the SCP version.|
|(SPS113/B)||Add/replace||… whether transactions should be added to existing transactions or replace those already found.|