Forecasting Migration

This chapter discusses how to migrate from Siebel Sales 6.x to Siebel Forecasting 8.1. It includes the following topics:

About Forecasting Migration

If you are migrating data from a 6.x version of Siebel Sales, you need to determine whether:

To use the automatic upgrade feature, or,
To use the data migration utility.

Note: Forecasting migration only applies when you are upgrading your Siebel application from 6.x versions to 7.x or later versions.

The following topics describe the Automatic Upgrade feature and the data migration utility. Read both sections carefully before upgrading to Siebel 8.1.

About the Automatic Upgrade Feature

The automatic upgrade feature of Siebel Sales migrates opportunities, opportunity product information, and select opportunity sales team information from older versions. The automatic upgrade does not, however, migrate old forecasting information. For many Siebel customers, there is sufficient information in the opportunity and opportunity product tables in Siebel Sales to begin the forecasting process without the old forecasts.

The automatic upgrade feature is sufficient if your organization:

Does not use Siebel Forecasting yet
Uses revenue forecasting for simple opportunities with one close date and one revenue amount
Uses the Opportunities list or the Opportunities Products list to enter most forecast information
Uses the New button when forecasting, rather than the Copy button

About the Data Migration Utility

Some Siebel customers need to also run the data migration utility provided with the Siebel installation. This utility migrates information from old forecasting tables into new revenue tables. You must use the data migration utility if your organization:

Uses Siebel Forecasting
Uses revenue forecasting with more complex opportunities that include recurring revenues over many months
Uses the Forecasts screen to enter most forecast information (instead of the Opportunities list or Opportunities Products list)
Uses the Copy button when forecasting, rather than the New button

Upgrading Forecasting Automatically

In previous versions of Siebel Business Applications, the opportunity close date, win probability, commit status, and revenue amount were stored on the intersection table between the opportunity and its sales team members. In newer versions of Siebel Business Applications, each opportunity has only one close date, win probability, commit status, and revenue amount. This information is stored in the Revenue table, on a special primary revenue record for that opportunity. This portion of the upgrade is automatic.

In older versions of Siebel Business Applications, opportunity products were stored in the opportunity product intersection table. Since Siebel 7.0, opportunity products are stored in the Revenue table, along with the primary revenue record. For each opportunity product migrated from a previous version, a revenue record is created. The product name, part number, quantity, price, and extended revenue is copied from the old opportunity product record to the new revenue record. Other attributes, such as the win probability, the primary sales representative’s name, and the opportunity name, are copied in from the opportunity record.

Before you upgrade from a previous version of Siebel Business Applications, decide whether the revenues for nonprimary sales team members must be upgraded. Consider upgrading nonprimary sales team members’ revenues if your organization:

Uses nonprimary forecasting and wants to continue using a similar nonprimary forecasting approach. (Running queries on the Revenue table is not always adequate to meet this need.)
Wants each sales team member to have a different opinion on the close date and revenue amount for each opportunity
Wants to assign some portion of each opportunity that is not related to a specific product or some percentage of the overall opportunity value to each sales team member

For each opportunity migrated from a previous version, the automatic upgrade evaluates the opportunity sales team records for nonprimary sales team members. Each sales team member record is used to create a revenue record in Siebel 8.1, if:

The primary flag is not checked
The revenue amount is nonzero
The commit flag is checked

Before you upgrade, make sure that your opportunity sales team records are appropriately marked as committed (to upgrade them) or not committed (to ignore them during the automatic upgrade process). Most customers do not need to upgrade these uncommitted sales team records.

Upgrading Forecasting Using the Data Migration Utility

The data migration utility is designed for customers with recurring revenues entered directly into the Forecasts screen.

Note: Because of the data model changes in forecasting, it is recommended that you print out your old forecasts before upgrading. Those forecasts are no longer visible in this version of the Siebel application. Although the data migration described here moves your data, double-check the results when the migration is finished.

To use the Data Migration Utility

In the default bin directory on the server, there is a file called fcstcnvrt.exe. This is the program that is used to migrate information from old Siebel forecasting tables to the new Siebel Revenue table. Also in this directory is a set of DLL files used by the data migration utility:
```
sslcshar.dll
sslcfom.dll
sscfdm.dll
sscfcmn.dll
sscacmbc.dll
sslcsym.dll
sslcosd.dll
```
When you have located these files and made sure that they are available for data migration, clean up your existing data.
If necessary, perform some data cleanup on your old Siebel database. Specifically, check for and remove duplicate periods from the Periods table, if they exist.
To check for duplicate periods, manually review the Periods view in your Siebel application, or run the following SQL statement:
```
select t1.row_id || ' CONFLICTS WITH ' || t2.row_id || 
    ' (' || t1.period_cd || ',' || t1.start_dt || ')'
    from s_period t1, s_period t2
    where t1.period_cd = t2.period_cd
    and t1.start_dt = t2.start_dt
    and t1.row_id <> t2.row_id 
```
If you do have duplicate periods, and you find that they have been used in creating old Siebel forecasts, work with Oracle to address this issue before proceeding to the next step.
At the command prompt, enable logging using the following commands:
```
set SIEBEL_LOG_EVENTS=errors
set ForecastUpgdEvent=errors
```
To log all events instead of just errors, set each of the preceding variables to All instead of errors.

To run the data migration, use fcstcnvrt.exe. The syntax for this command is:

fcstcnvrt/u username /p password /d datasource /m masterForecast /date date [/c 
cfgFile] [/l language] [/postn postn] [/login login] [/sspec searchSpec] [/r 
revision] [/submitted [/Opportunity [/OpportunityProduct [/OpptyProduct [/NP] [/
Period period] [/UseStartDate] [/Desc description]

or

fcstcnvrt[/help]

The following table describes this syntax:

Switch	Description	Notes
`/u username /p password`	Required. System Administrator’s username and password.	These are the same username and password that you use to log on to the Siebel server database.
`/d datasource`	Required. The name of the datasource.
`/c cfgFile`	The name of the configuration file.
`/l language`	The language being used.
`/m masterForecast /date date`	Required. Specify which forecasts to upgrade, using masterForecast and date as search specifications.	1. masterForeast must be the name of a valid master forecast. 2.date must be a valid date. The format for the date field is: MM/DD/YYYY. For example, 01/05/2007.
`/postn postn`	Specifies a position to upgrade.	To specify more than one position, use `/sspec` `/postn` takes priority over /login
`/login login`	Specifies a login to upgrade.	Applied in conjunction with other search specifications.
`/sspec searchSpec`	Limits the forecast records by search specification.	searchSpec must be a valid search specification for a personal forecast.
`/r revision`	Limits the forecast records by revision.	revision can be a valid number, or one of `{Earliest\|Latest}`.
`/submitted`	Limits the forecast records to those that have been submitted.
`/Opportunity /OpportunityProduct /OpptyProduct`	Specifies the business component to upgrade.	1. Only the specified business components are upgraded. 2. You can upgrade a child business component without upgrading its parent. For example, Opportunity Product without Opportunity.
`/NP`	Indicates whether to upgrade the nonprimary counterpart of the specified business component (for example, opportunity personal forecast).	The primary business component must be specified for the nonprimary business component to be upgraded.
`/Period period /UseStartDate /Desc Description`	Specify how to create Revenues.	1. period must be a valid period type, for example, Month or Year. 2. If `/UseStartDate` is specified, the revenues are created using the start date of the period in which they fall. Otherwise, the default is the end date. 3. If `/Desc` is specified, the revenues are created with description as their description.
`/help`	Lists the parameters described here.

The data migration utility takes a few minutes to run. Some messages can appear while the upgrade is running. For example, sometimes messages similar to the following appear:

   -> "Upgrading forecast for CCONWAY Revision 1.. Success".
   -> "Upgrading forecast for CCONWAY Revision 2.. Failure".
   -> "*******Upgrade complete**************"
   -> "Errors were encountered. Please see the logfile in d:\log\siebel.log for
         more details"