Example upgrade scenario

In an example upgrade scenario, Sterling Order Management System Software introduces a feature that recognizes the various attributes for order types.

For example, an Order_type "URGENT" implies that the order should be displayed in the user interface with a specific icon that enables you to distinguish it from other orders. However, in previous releases, you may have been using the Order_type field to classify orders into other types because this field was designed for order classification.

When Sterling Order Management System Software provides an upgrade toolkit, one component of the toolkit handles upgrades to the Order_type field.

The upgrade logic may flow as follows:

  1. Read all the distinct values of the Order_type field from the YFS_ORDER table.
  2. For each different Order_type in the your system, create entries in the Order_Type_Master configuration table and assign a default icon to it.

If this data upgrade is run on the staging system, it will not find any orders, so the Order_Type_Master table will only contain "URGENT" which is provided by default.

However, when the same data upgrade is run in production, the Order_Type_Master table will contain multiple entries, one for each type of order that is in the transaction database.

Then, when the Configuration Deployment Tool is run again, it marks all of these new records for deletion because the source is assumed to be the most up-to-date configuration.

As a result, you should design upgrade kits or service packs for transaction dependent configuration data as follows:

  1. The upgrade kit (or service pack) should have one script to prepare input for upgrade of transaction-dependent configuration data (for example, prepared list of distinct order types). Then you can run this script on the production database. You can also run this script in the test database and can take the union of the two.
  2. The next step in the upgrade should use this as input and upgrade the configuration data accordingly. For example, inserting into ORDER_TYPE_MASTER table.

If you have identified any changes in the configuration data, please contact IBM® Technical Support.