Importing model scenarios from the Supply Chain platform

The Platform Scenarios Import action allows you to download and import the model scenarios from a Supply Chain Guru model on the Supply Chain platform to a local database. Before using this action, you must create a Supply Chain Guru Cloud connection to Supply Chain.

Scenarios are complex structures made up of dependent components:

  • A model can have one or more scenarios.

  • Each scenario can have one or more individual scenario items.

  • Each scenario item can be used in one or more scenarios.

  • Scenario items can optionally include a filter to limit the data they affect. Filters may have criteria for more than one column in the table.

When importing model scenarios, you provide:

  • Platform Connection - Select the connection to the Supply Chain platform.

  • Platform Model - This is the name of the model on the platform.

  • Database Connection - Select the connection to the local database to which the options are imported.

  • Table Names for the scenario components:

    • Scenario Table Name - This is the table in the local database to which the scenarios are imported.

    • Scenario Items Table Name - This is the table in the local database to which the scenario items are imported.

    • Filters Table Name - This is the table in the local database to which the optional filters for scenario items are imported.

For example, if you are importing model scenarios:

  1. Enter a name and description.

  2. Specify connection to Supply Chain platform.

  3. Select platform model.

  4. Select database connection, local table names, and options.

    By default, only filters associated with tables that are used in Scenario Items are imported. Select the Download all model filters checkbox to import filters from all model tables.

    The model scenario definitions are imported into the local tables.

The most common application is to download data from the cloud to a local database for additional processing and to populate additional platform models.

This action imports only standard Scenarios from the platform. Rapid Solve Scenarios are not imported to the local database.

Scenario definition local tables

When you import scenario definitions, the scenario data is populated in 3 separate local tables.

  • Scenario Table Name - This is the table in the local database to which the scenarios are imported. It is used to map scenario items to the scenario. There will be one record per Scenario Item Name per Scenario Name. The Baseline scenario is not included in the import. This table includes the following columns:

    Name Description
    Scenario Name The name of the scenario. This value should be the same for all records with the same Scenario Id value.
    Scenario Item Name The name of the scenario item as defined in the table specified by the Scenario Items Table Name (see below).
    Scenario Item Order

    This is the order in which scenario items are processed when the scenario is run. For example, assume there are two scenario items affecting Sites:

    • Exclude All Sites (1)

    • Include Mexico Sites (2)

    In this order, the scenario will run using the sites in Mexico (first excludes all sites, then includes those from Mexico). If the order is reversed, no sites will be included when the scenario is run.
    Notes

    Optional notes for the scenario.

    Do not include new lines (multiple paragraphs) in the Notes value.

  • Scenario Items Table Name - This is the table in the local database to which the scenario items are imported. There will be one record per Value per Scenario Item Name. This table includes the following columns:

    Name Description
    Scenario Item Name The name of the scenario item.
    Target Table Name This is the table for which you are defining the scenario item. This is typically an input table such as Customer Demand, but can also be one of the solver options, such as Network Optimization Options. The solver options are set using Options on the Modeler Launch Pad. Use the table display name for this value.
    Target Type For all input tables, the value is "Table". When using one of the sets of solver or model options, the value is "Option".
    Filter Name The name of the table filter as defined in the table specified by the Filters Table Name (see below). For the filter to be valid, it must be defined for the table specified by Target Table Name.
    Target Field The field in the Target Table Name that is affected by the scenario item.
    Target Operator The operator that is used when applying the Values to the Target Field. This is one of Equals, Add, Subtract, Multiply, Divide.
    Values The value that is applied to the Target Field. If you have multiple values for a single scenario item, each value results in a unique row in this table.

  • Filters Table Name - This is the table in the local database to which the optional filters for scenario items are imported. There will be one record per Column Name per Filter Name. This table includes the following columns:

    Name Description
    Filter Name The name of the filter. Must be unique for a specific table.
    Table Name The table to which the filter is applied.
    Column Name The column name with filter criteria applied. Additional records in the table are populated if multiple columns in a table have criteria applied.
    Filter Value The criteria applied to the column.
If a Scenario Item uses a filter from an input table, all tables filters from that input table are imported into the local table. For example, if you have a scenario filter for the Customers table, all filters for the Customer table are imported.
By default, only filters associated with tables that are used in Scenario Items are imported. Select the Download all model filters checkbox in the action configuration to import filters from all model tables.

See Populating the local scenario tables for detailed information about successfully structuring scenario definitions.

Last modified: Thursday December 19, 2024

Is this useful?