Siebel Database Upgrade Guide > Postupgrade Tasks for Siebel Applications >

Migrating Clinical Trip Report Data in Siebel Pharma

Upgrades from: Siebel 7.0.x, 7.5.x, 7.7.x, and 7.8.x.

Environments: Development, production test, production.

Platforms: Windows, UNIX, IBM z/OS.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

In Siebel 7.8.x and earlier releases, clinical trip report data are stored in S_EVT_ACT with joins to other tables including S_ORG_EXT, S_CONTACT for account name, contact name, and so on. Values in these joined fields can be changed, hence the trip data are dynamic. This is not compliant with government regulations that require all data in a clinical trip report to be static when the report record is locked.

In Siebel CRM 8.0, a new S_EVT_ACT extension table S_CL_TRP_RPT_LS stores the static data. Run the following script to populate S_CL_TRP_RPT_LS for existing trip report records in S_EVT_ACT:

Windows: DBSRVR_ROOT\common\ClinicalUpgrade.sql

UNIX: DBSRVR_ROOT/common/ClinicalUpgrade.sql

If you have already implemented a custom extension table or extension columns to store static data, modify the script to move the data to S_CL_TRP_RPT_LS.

Siebel Database Upgrade Guide Copyright © 2008, Oracle. All rights reserved.