Scenarios and scenario items

In general scenarios and the scenario items themselves will convert successfully when opening a Supply Chain Guru 8.x model in Supply Chain Guru X. This includes table names, filters, columns and values. In cases where tables referenced by scenario items need to be updated, you will need to redefine the scenario item.

Table splits

Various tables are split when converting from SCG 8.4.x to Supply Chain Guru X:

Sites

Sites is now two tables:

1. Sites - all facilities are populated in this table.
2. Customers - all customers are populated in this table.

   The original Scenario Items will refer to the Sites table after the conversion. A second Scenario Item is created on upgrade that refers to the Customers table. This item is called <ItemName>_Cust.

Sourcing Policies

Sourcing Policies is now three tables:

1. Production Policies – all Make policies are populated in this table.
2. Site Sourcing Policies – sourcing policies between facilities are populated in this table.
3. Customer Sourcing Policies – sourcing policies from facilities to customers are populated in this table.

The original Scenario Items will refer to the Site Sourcing Policies table after the conversion. A set of additional Scenario Items is created on upgrade that refers to the other tables that are part of this split:

• <ItemName>_Cust – This item uses the Customer Sourcing Policies table.
• <ItemName>_Prod – This item uses the Production Policies table.
• <ItemName>_Proc – This item uses the Production Process Assignments table.
• <ItemName>_Bom – This item uses the Bill of Material Assignments table.

Multi-Period Tables

There are now also three Multi-Period tables associated with Sourcing Policies:

1. Production Policies Multi-Period
2. Sourcing Policies Multi-Period
3. Customer Sourcing Policies Multi-Period

Similar to the single period tables, the original Scenario Items will refer to Sourcing Policies Multi-Period after the conversion. Two additional Scenario Items are created on upgrade that refer to the other tables that are part of this split:

• <ItemName>_Cust – This item uses the Customer Sourcing Policies table.
• <ItemName>_Prod – This item uses the Production Policies table.

Processes

Processes are now populated across these tables:

1. Production Processes – defines the process name and type.
2. Production Process Steps – defines process steps, associated work centers and resources, and time, cost and lot parameters.
3. Production Process Assignments – defines the Period – Site – Product – Process relationship.

Scenario Items will refer to Production Process Steps after the conversion.

Multi-Period Tables

Processes Multi-Period is now Process Steps Multi-Period. Scenario items will refer to the Process Steps Multi-Period table after the conversion.

Bills of Material

Bills of Material are now populated in two tables:

1. Bills of Material – this is the definition with BOM Name, Product Name, Type and Quantity.
2. Bill of Material Assignments - defines the Period – Site – Product – BOM relationship.

   Scenario Items will refer to Bill of Materials after the conversion, so no changes are required.

Relating policies, processes and BOMs

If your original model had “Make” Sourcing Policies where Process and BOM Name were populated, you will see the following:

• Production Policies – The actual policies are defined here. If the original used “Make (Process – Probability” or “Make (Split by Ratio)” as the Sourcing Policy, these will be grouped by Site-Product into a single “Make” policy in the Production Policies table.
• Production Processes – This table will have Processes, defined as “Run Production”.
• Production Process Steps – Detailed Process steps are defined in this table.
• Production Process Assignments – These will be defined as “Split By Probability” based on the values in the original policies.
• Bills of Material – These remain consistent with original records.
• Bill of Materials Assignments – These are grouped by BOM-Site-Product.

Process to evaluate scenario items

Coupa recommends the following process:

1. Review Scenario Items to determine if the table is any of those listed in the table splits section above.
2. Determine if the field and field value are appropriate for the currently selected table. For example, if the value for policy is “Make”, ensure that the table is now Production Policies and the field is Production Policy.
3. In the Scenario Item, click Edit Filter to assess whether or not the current filter definition is valid after the conversion. For example, if the filter on Sites selects Type = Customer, the scenario item should reference the Customer table instead. Note that there may be cases where you need to adjust which column is used for the filter.