Data Migration Documentation

Post-Migration Tasks for Calyx RIM 5.1

Perform these tasks after you migrate to Calyx RIM 5.1.

EU 2.0 Manual Calyx RIM Data Administration Updates

To support EU M1 v2.0 implementation after the database upgrade from Calyx RIM 5.0 GA to 5.1, you must perform the procedure to update your Calyx RIM Data Administration configuration after executing the 5.1 migration.

If you have already performed these updates as part of Calyx RIM 5.0 CHF 6, you do not need to repeat these manual updates.

You must:
  • Update Country values
  • Add Filing Types
  • Update Region values
  • Update Procedure Types values
  • Update Event Plan values

For details, see the Calyx RIM 5.1 Data Migration Document.

US M1 3.3 Manual Calyx RIM Data Administration Updates

You must create:
  • Application Type eCTD Code values in Calyx RIM after migration for specific Application types. If the Application Type does not already exist, it must also be created. 
  • Filing Type eCTD Code values in Calyx RIM after migration for specific filing types. If the filing type does not already exist, it must be created. 

For details, see the Calyx RIM 5.1 Data Migration Document.

GCC 1.2 Manual Data Administration Updates

To support GCC M1 v1.2 implementation after the database upgrade from Calyx RIM 5.0 GA to 5.1, you must perform procedure to update your Calyx RIM Data Administration configuration after executing the 5.1 migration.

You must:
  • Update region values. For details, see the Calyx RIM 5.1 Data Migration Document.
  • Verify migration script updates

If you have already performed these updates as part of Calyx RIM 5.0 CHF 4, you do not need to repeat these manual updates.

For details, see the Calyx RIM 5.1 Data Migration Document.

Post-Migration Filing Type and Application Report

A post-migration report has been provided named “rpt_post_dtd_data.sql”. For details, see the Calyx RIM 5.1 Data Migration Document.

Calyx RIM Publisher Templates

All templates that are shipped with Calyx RIM 5.1 have been recreated based on the new Publishing Settings Library, however, the templates currently in the Calyx RIM 5.0 system will be available with the new Publishing Settings Library post migration as well. Templates were introduced in various Calyx RIM 5.0 Certified Hot Fixes and Hot Fixes. If the templates were not updated in Calyx RIM 5.0, they should be updated post migration to ensure the latest templates are being used. For details, see the Calyx RIM 5.1 Data Migration Document.

EVMPD Queries

The following OOTB EVMPD queries will not be available in Calyx RIM 5.1:
  • EVMPD Codes Query
  • EVMPD Analysis Query

If any of these queries have been saved as public or private queries they will not be migrated to Calyx RIM 5.1. For details, see the Calyx RIM 5.1 Data Migration Document.

Shelf Life Queries

In Calyx RIM 5.1 the shelf life and storage conditions fields on the package set detail will be migrated to the new shelf life details. As a result, some default queries have been updated to remove the shelf life and storage conditions fields associated with the package set detail.

Saved public and private queries created in releases prior to 5.1 that have the capability to report on shelf life and storage conditions from the package set detail will not be migrated to Calyx RIM 5.1. These queries will be deleted as a result of the migration to 5.1.

rpt_problematic_shelf_life_details.sql – Run this script post-migration to determine if there were shelf life details partially migrated. Partially migrated means that although the current shelf life detail was unmigratable, previous shelf life details were migrated and are now considered current.

rpt_pds_with_duplicates_removed.sql – This script can be run post-migration to identify any PDS with duplicate shelf life details where one of shelf life details was ignored, potentially causing a partial migration. Constraints in the new data model prevent duplicate details. In some cases, customers had the same modification under two different events, resulting in duplicate data. Post-migration, only one event will be associated with the detail as a result of the new constraints. Historical information will remain in the audit trail.

See the Calyx RIM 5.1 Data Migration Document.