Scenario Data Changes

This page is accessed via Logistics Network Modeling > Modeling Scenario. On a modeling scenario, select Scenario Data Changes. Then, select New Object.

When adding a new modeling scenario, the Scenario Data Changes tab is available only when adding from the Modeling Scenario screen. It is not available when added from the Modeling Project screen.

Note: Changes that you make on this screen are only temporary and are not persisted to the actual objects in the database. This includes new order releases and copied order releases.

Use scenario data changes to "set" a specific field on a specific object. Or, for order release only insert or delete orders, as well as update data on existing orders. These changes override the changes made by data rules.

Defining Scenario Data Changes

1. Select the Object Type to specify the object where you will change some of the existing data. Depending on the object type selected, the fields on the page will change.
   • If you select an object type of ORDER_RELEASE, you a different drop-down lists titled Change Type. See details below.
   • If you select the object type of EQUIPMENT GROUP, LOCATION, RATE GEO, or RATE OFFERING, you also see the Child Object Data Changes grid. See details below.
   • If you select any other object type than those mentioned above, you continue to the step below.
2. Select the Object ID to specify the object for which you would like to change some fields.
3. Optionally, enter a Description.
4. Enter the Data Changes:
   1. In the Column Name drop-down list, select an editable column for a given object type.
   2. View the Original Value of that field selected in the database. This is the original value of the field.
   3. Enter the New Value is a free-form text field that accepts input in accurate format. If the input is not provided in the correct format, the changes may not be applied correctly.
   4. Select Save for each data change.
5. Select Save.

Object Type of ORDER_RELEASE

If you select an Object Type of ORDER_RELEASE, you see the Change Type drop-down list with the options of:

• Update: Updates the specified order release with the data changes entered.
  
  Update is also used (behind the scenes) when changing data on other objects.
• Insert: Inserts the order release ID. You can also specify the Number of New Objects which controls how many new order releases are inserted. For example, if you select Insert, enter an existing order release of ABC, and enter 20 for Number of New Objects, then 20 copies of the order release ABC are added to the scenario. You can use the change type of Insert on the same object multiple times.
• Delete: Exclude the specified order release from the scenario planning.

Adding Child Object Data Changes

For the object types of EQUIPMENT GROUP, LOCATION, RATE GEO, and RATE OFFERING, you can add data changes to child objects.

For the object types, you can specify data changes for the following child objects:

• The object type of EQUIPMENT GROUP has the following child objects:
  • EQUIP_GROUP_EQUIP_REF_UNIT
  • EQUIPMENT_GROUP_COMPARTMENT
• The object type of LOCATION has the following child object:
  • LOCATION_ROLE_PROFILE
• The object type of RATE GEO has the following child objects:
  • RATE_GEO_COST
  • RATE_GEO_STOPS
• The object type of RATE OFFERING has the following child object:
  • RATE_OFFERING_STOPS

If you selected one of the four object types, you see a grid Child Object Data Changes.

1. Select a Child Object. The drop-down lists child tables of the object type and object ID selected previously. 
2. Select a Primary Key. This drop-down displays record identifiers (primary keys) for the selected child object. This allows you to select a specific record for modification.
3. Select a Column Name: This drop-down displays the list of columns/fields available for update for the selected child object. Only relevant/applicable columns are shown.
4. The Original Value is automatically populated once Child Object, Primary Key, and Column Name are selected and contains the current value from the OTM database. This field is non-editable and serves as a reference.
5. Enter a New Value an updated value to replace the Original Value. This value is used when running Scenario Bulk Plan.