Bookshelf v7.5: Reapplying Custom Extensions and FK Columns on Obsolete Tables

Upgrade Guide for UNIX > Postupgrade Tasks > Postupgrade Tasks for All Environments >

Reapplying Custom Extensions and FK Columns on Obsolete Tables

This procedure only applies to development environment upgrades. For production environment upgrades, skip this procedure and proceed to Generating Reporting Relationships.

NOTE: Skip this procedure if you are performing an upgrade from Release 7.x to Release 7.5.

Several tables used in prior versions of Siebel eBusiness Applications are no longer used, or have been replaced by new tables in Release 7.x. The new configuration uses the new tables. You need to reapply the extensions and foreign key (FK) columns that you added to previous versions of the tables to the new tables.

The upgrade process generates a report that you must review for information about tables that are either obsolete or no longer in use for Release 7.x. This report, xtndobstbl.txt, lists the following:

Custom columns in obsolete tables
Custom foreign key columns pointing to obsolete tables
EIM mappings for custom foreign key columns to access-control related obsolete tables
Workflow columns by custom foreign key to obsolete tables
Customer denormalized columns on obsolete tables
Obsolete tables in Release 7.x. Each obsolete table is listed with one of three codes:

Not Used. These tables are not used in Release 7.x, but you may continue to use them; for example, S_ORG_PROD, S_PERIOD BU. These tables are supported as is (for instance, with docking or EIM).
EOL (end of life). These tables are not used in Release 7.x, and they are not supported in future releases; for example, old S_*_IF tables.
Inactive. These tables have been discontinued, and are not supported in Release 7.x. Extension columns and foreign key columns that reside on inactive tables must be moved to alternate tables. For example, custom extension columns on S_EMPLOYEE should be moved to S_CONTACT, S_USER, or S_EMP_PER. Likewise, if you are upgrading from a pre-7.x version of Siebel Industry Applications, custom extension columns on S_PER_ORG_UNIT need to be moved manually to S_PARTY_PER, and custom extension columns on S_CONTACT REL need to be moved manually to S_PARTY_REL.

You need to review this report for extension columns and foreign key columns that reside on obsolete tables, and therefore need to be moved to alternate tables. If no tables are listed in xtndobstbl.txt, no action is required. If this file lists any tables, their custom extensions and foreign key columns must be reapplied to Siebel eBusiness Applications Release 7.x tables using Siebel Tools. See Siebel Tools Reference.

Table 20 lists examples of previously used tables which are inactive in Release 7.x (you can no longer use these tables) and lists the suggested new tables to which custom extensions need to be reapplied. The new tables are recommendations only; the tables that you need to apply the extensions to might vary depending on their type and use. Contact Siebel Technical Services to validate the reapplication of extension columns and to review the steps necessary to migrate any extension column data to the new tables.

Table 20.  Examples of Tables That Are Obsolete in Release 7.x

Previous 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 created many custom extension columns on the tables S_EMPLOYEE or S_ORG_INT, both of which are no longer used in Release 7.x, the joins between the tables are not accurate. This may result in SQL errors when you launch the Siebel client.

In such cases, using Siebel Tools, you must 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. You must then review the business component configuration to make sure that the client operates properly.

You may need 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

Review the xtndobstbl.txt file after you run the upgrade to locate a list of fields that require your attention.

Table 21 lists examples of previously used tables that are no longer used in Release 7.x, but that you may want to continue to use.

Table 21.  Examples of Tables That Are Not Used in Release 7.x

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_EVT_REG

S_CTLG_CAT_REL

S_CTLG_CAT

S_DNB_CONTACT

S_PRSP_CONTACT

S_OPTY_PROD

S_REVN

S_TMSHT_LINE

S_TMSHT_ITEM, S_TMSHT_LN

Table 22 lists examples of tables which were unused in previous releases of Siebel eBusiness Applications, but are now used in Release 7.x.

Table 22.  Examples of Previously Unused Tables That Are Used in Release 7.x

Now Used Table

Used to be...

S_ACT_EMP

S_EVT_ACT

S_ACT_CON

S_EVT_ACT

Table 20. Examples of Tables That Are Obsolete in Release 7.x
Previous 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

Table 21. Examples of Tables That Are Not Used in Release 7.x
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_EVT_REG
S_CTLG_CAT_REL	S_CTLG_CAT
S_DNB_CONTACT	S_PRSP_CONTACT
S_OPTY_PROD	S_REVN
S_TMSHT_LINE	S_TMSHT_ITEM, S_TMSHT_LN

Table 22. Examples of Previously Unused Tables That Are Used in Release 7.x
Now Used Table	Used to be...
S_ACT_EMP	S_EVT_ACT
S_ACT_CON	S_EVT_ACT

Upgrade Guide for UNIX
Published: 20 October 2003