Reviewing Obsolete Tables

The upgrade process generates a report that you can review for information about obsolete tables that will help you decide whether or not you have to reapply schema customizations. This report, xtndobstbl.txt, lists the following:

Obsolete tables in the current release
Custom columns in obsolete tables
Custom foreign key columns pointing to obsolete tables
EIM mappings for custom foreign key columns to obsolete tables
Workflow columns by custom foreign key to obsolete tables
Custom denormalized columns to Siebel base tables that might be obsolete

Each obsolete table is listed with one of three codes:

Not Used. These tables are not required in the current release but, if you are already using them, for example, with docking or EIM, you can continue to do so and they will be supported.
EOL (end of life). These tables are not used in the current release, and they are not supported in future releases.
Inactive. These tables have been discontinued, and are not supported in the current release. You can choose to move extension columns and foreign key columns that reside on inactive tables to alternate tables.

If no tables are listed in xtndobstbl.txt, no action is required. If this file lists any tables, you can reapply their custom extensions and foreign key columns to tables in the current release using Siebel Tools. For further information on this task, see Configuring Siebel Business Applications.

The following table shows examples of previously used tables that are inactive in the current release (you can no longer use these tables) and the suggested new tables to which custom extensions can be reapplied. The new tables are recommendations only; the tables that you choose to apply the extensions to might vary depending on their type and use. For help with validating the reapplication of extension columns, and reviewing the steps necessary to migrate any extension column data to the new tables, create a service request (SR) on My Oracle Support. You can log service requests by accessing My Oracle Support (Service Request tab), or by using your existing phone support numbers to contact Oracle Global Customer Support.

This data must be migrated during both the development and production environment upgrades.

Inactive Table	Suggested New Table
`S_EMPLOYEE`	`S_CONTACT, S_USER, S_EMP_PER`
`S_EMP_POSTN`	`S_PARTY_PER`
`S_ORG_INT`	`S_ORG_EXT, S_BU`
`S_POSTN_RPT_REL`	`S_PARTY_RPT_REL`

If you have created many custom extension columns on the tables S_EMPLOYEE or S_ORG_INT, neither of which are used in Siebel CRM 16.0 or later, the joins between the tables will not be accurate. This can result in SQL errors when you launch the Siebel client.

In such cases, using Siebel Tools, you can manually create corresponding extension columns in the new target tables, and manually move the data to the new extension column on the new table before you continue migration of the application. Then review the business component configuration to make sure that the client will operate properly. You might have to do this in one of the following instances:

Fields based on custom extension columns in S_EMPLOYEE or S_ORG_EXT
Fields based on custom extension tables from S_EMPLOYEE or S_ORG_INT with or without join
Custom joins to custom extension tables from S_EMPLOYEE or S_ORG_INT

If you review the xtndobstbl.txt file after you run the business component migration utility, you will find a list of fields that require your attention.

The following table lists examples of previously used tables that are no longer used in the current release of Siebel CRM.

Previous Table	Suggested New Table
`S_CRSE`	`S_SRC, S_SRC_EVT`
`S_CRSE_OFFR`	`S_SRC, S_SRC_EVT`
`S_CRSE_REG`	`S_SRC_REG`
`S_CTLG_CAT_REL`	`S_CTLG_CAT`
`S_OPTY_PROD`	`S_REVN`
`S_TMSHT_LINE`	`S_TMSHT_ITEM, S_TMSHT_LN`

The following table lists examples of tables which were unused in previous releases of Siebel Business Applications, but are used in the current release.

Current Table	Previous Table
`S_ACT_EMP`	`S_EVT_ACT`
`S_ACT_CON`	`S_EVT_ACT`