1. User Guide
  2. Business Rules Administration
  3. Application Specific Rules
  4. Lookup Table
  5. Navigation in the Detail Screen
  6. Migration of Lookup Tables

5.3.6.1.5 Migration of Lookup Tables

  • SaaS version to SaaS version migration:

    The scope of migration of lookup tables is limited to tables present with status='Table Created' and the utility does not migrate lookup tables present with ('Creation in Progress', 'Deletion in Progress', 'Failed') status.

    If the migration process is successful, the migrating table arrives at the target environment with status='Table Created' if the table creation in the target environment database is successful. If the table creation process has failed, the migrating table arrives at the target environment with status=’Failed’.

    If the migration process has failed, there appears no entry in the target environment Lookup Table Summary for the migrating lookup table rule.

    Once the lookup tables are migrated, the user can proceed to migrate the Lookup Table Drivers and the Lookup Driver Table allocation rules and the Allocation Models containing any Lookup Driver allocation rule, in the same sequential order of object types.

  • Legacy (on-premise) version to SaaS version migration:

    Lookup Tables are physical tables and not objects in the on-prem version and thus Lookup Tables are not in the scope of Legacy Object Migration into SaaS.

    Similarly, the Legacy Migration Export utility installed in on-premise version is configured to exclude the Lookup Table Driver and the Allocation Rules of the Lookup Driver Table allocation type from the list of object types available for migration.

    The SaaS users are expected to create from scratch, the Lookup Tables, the Lookup Table Drivers and the Lookup Driver Table allocation rules, in the same sequential order of object types in the target environment before proceeding to migrate the allocation models.

    The Allocation Models containing Lookup Driver allocation rules are in the scope for On-prem to SaaS Migration. An allocation model will only be migrated successfully if all the rules present in the model meta data is successfully migrated into Target. An allocation model will not be migrated if any of the rules present in the model meta data are not migrated successfully into Target.