Scenario Tables
These are used to insert actions, selections, and updates into the back end of the process compared to the standard process of building scenarios through Gains Architect. Both processes work, however, we would recommend that this should only be used for advanced users in the Supply Chain Management field.
dbo.Scenarios
Field | Data Type | Description |
BaseScenario | Text | Base scenario name |
OutputScenario | Text | Output scenario name |
Action | Text | Action name, for example “Turn on Atlanta Shipments” |
ActionNum | Int | Ordinal action number within the scenario. Action order matters because actions are applied to the base scenario in the order specified by the ActionNum |
Solver | Text | Solver to be used for this scenario. Choose one of the following: NEO – Network Optimization COG – Center of Gravity VRO – Vehicle Route Optimization |
dbo.ScenarioActions
Field | Data Type | Description |
Action | Text | Action name, for example “Turn on Atlanta Shipments” |
Selection | Text | Selection name, which defines the BaseScenario rows to be updated by this action. For example, “Atlanta Shipments” |
Update | Text | Update name, which defines the update to be applied to the rows selected by Selection. For example, “Turn ON” |
dbo.ScenarioSelections
Field | Data Type | Description |
Selection | Text | Selection name, e.g. “Atlanta Shipments” |
SelectionTable | Text | Table that selection applies to, e.g. “Shipments” |
SelectionSQL | Text | SQL WHERE clause defining the rows to be selected for update, e.g. originsite like 'DC_Atlanta_GA' |
dbo.ScenarioUpdates
Field | Data Type | Description |
Update | Text | Update name, e.g. “Turn ON” |
UpdateSQL | Text | SQL Update clause, e.g. [SolverInclude]='Yes' |