Migrating Sales Processes

This chapter describes how to migrate sales processes using the command-line interface of the Oracle Migration Tool On Demand client. It contains the following topics:

Sales Processes

A sales process is a series of steps that defines a sales methodology for your company. The following table describes the Oracle Migration Tool On Demand client commands used with sales processes. These commands are case sensitive.

Table Commands Used with Sales Processes in Oracle Migration Tool On Demand

Command	Description
`Read SalesProcess BaseName`	This command exports a single sales process. BaseName is the language-independent name of the sales process. If the language-independent name contains any spaces or special characters, such as brackets, then it must be enclosed with quotation marks.
`ReadAll SalesProcess`	This command exports all sales processes in the Oracle CRM On Demand tenant.
`Upsert SalesProcess SalesProcessXML`	This command updates or inserts the sales process specified in the XML file.

Privileges Required for Migrating Sales Processes

The following privileges are required for the user account running the Oracle Migration Tool On Demand client commands:

For the Read and ReadAll commands: Enable Web Services Access.
For the Upsert command: Enable Web Services Access, and Manage Data Rules - Manage Sales Stage Definition.

For information about setting and checking privileges, see Oracle CRM On Demand Online Help.

Elements and Sections in the Sales Process XML Output File

The following table describes the elements and sections in the sales process XML output file.

Note: When a sales process is created, sales stages named Closed/Lost and Closed/Won are automatically associated with the sales process. The Probability field on the Closed/Lost sales stage is set to zero (0), and the Probability field on the Closed/Won sales stage is set to 100. You cannot change these values. Do not set up any other sales stage with the Probability field equal to 0 or 100 percent. Modifying picklists that are used internally by the Oracle CRM On Demand application can have an adverse impact on standard functionality. You cannot remove the Closed/Lost and Closed/Won sales stages from a sales process.

Table Elements and Sections in the Sales Process XML File

Description	Element or Section
The <SalesProcess> section contains all of the information for a single sales process.	<data:SalesProcess> . . . </data:SalesProcess>
<Name> is the name of the sales process.	<data:SalesProcess> . . . <data:Name>High Potential</data:Name> . . . </data:SalesProcess>
<Translate> specifies whether the sales process is marked for translation.	<data:SalesProcess> . . . <data:Translate>N</data:Translate> . . . </data:SalesProcess>
<Default> specifies whether this is the default sales process.	<data:SalesProcess> . . . <data:Default>true</data:Default> . . . </data:SalesProcess>
<Description> contains a description of the sales process.	<data:SalesProcess> . . . <data:Description></data:Description> . . . </data:SalesProcess>
<TranslationLanguage> is the three-letter code for the language.	<data:SalesProcess> . . . <data:TranslationLanguage>ENU</data:TranslationLanguage> . . . </data:SalesProcess>
<BaseName> is the language-independent name of the sales process.	<data:SalesProcess> . . . <data:BaseName>[High Potential]</data:BaseName> . . . </data:SalesProcess>
The <ListOfOpportunityType> section contains the information for the opportunity types associated with the sales process.	<data:SalesProcess> . . . <data:ListOfOpportunityType> . . . </data:ListOfOpportunityType> . . . </data:SalesProcess>
The <Type> element in the <OpportunityType> section contains the name of an opportunity type associated with the sales process.	<data:SalesProcess> . . . <data:ListOfOpportunityType> <data:OpportunityType> <data:Type>Renewal</data:Type> </data:OpportunityType> </data:ListOfOpportunityType> . . . </data:SalesProcess>
The <ListOfSalesStage> section contains the information for the sales stages associated with the sales process.	<data:SalesProcess> . . . <data:ListOfSalesStage> . . . </data:ListOfSalesStage> . . . </data:SalesProcess>
The <SalesStage> section contains all of the information for a single sales stage associated with the sales process, as follows: <Name> is the name of the sales stage. <SalesCategoryName> is the category that the sales stage falls under. <Order> indicates the sequence of the sales stage as it appears in the picklist. <Probability> is the default probability for the sales stage. <Description> is the description of the sales stage. <TranslationLanguage> is the three-letter code for the language for the sales stage. <BaseName> is the language-independent name of the sales stage. <BaseCategoryName> is the language-independent name of the sales category that the sales stage falls under.	<data:SalesProcess> . . . <data:ListOfSalesStage> <data:SalesStage> . . . <data:Name>Short List<data:Name> <data:SalesCategoryName>Leads Category</data:SalesCategoryName> <data:Order>1</data:Order> <data:Probability>30</data:Probability> <data:Description>Looking for the Right Characteristics</data:Description> <data:TranslationLanguage>ENU</data:TranslationLanguage> <data:BaseName>Short List</data:BaseName> <data:BaseCategoryName>Leads Category</data:BaseCategoryName> </data:SalesStage> . . . </data:ListOfSalesStage> . . . </data:SalesProcess>
The <ListOfTranslation> section contains the translation values for the sales process.	<data:SalesProcess> . . . <data:ListOfTranslation> . . . </data:ListOfTranslation> . . . </data:SalesProcess>
The <Translation> section contains the translation values for one language: <LanguageId> contains the three-letter code for the translation language. For the list of language codes, see Language Codes and Their Corresponding Language and Country. <Name> contains the name for the sales process in the language identified by the language code. <Description> contains the description of the sales process in the language identified by the language code.	<data:SalesProcess> <data:ListOfTranslation> <data:Translation> <data:LanguageId>ENU</data:LanguageId> <data:Name>High Potential</data:Name> <data:Description>Looking for the Right Characteristics</data:Description> </data:Translation> . . . </data:ListOfTranslation> </data:SalesProcess>

Migrating Sales Processes

The following topics describe how to use the Oracle Migration Tool On Demand client to migrate sales processes:

Note: Back up your configuration data and all other relevant data before running the Oracle Migration Tool On Demand client.

Extracting a Single Sales Process

This topic describes how to extract a single sales process from your Oracle CRM On Demand environment.

Syntax

The following is the syntax for using the Oracle Migration Tool On Demand client to extract a sales process:

migrationtool -u UserID -s ServerURL Read SalesProcess BaseName

where:

UserID is the user sign-in ID that has the appropriate privileges to run the Oracle Migration Tool On Demand client commands.
ServerURL is the URL for the Oracle CRM On Demand server where your company resides.
BaseName is the language-independent name of the sales process.

If the language-independent name of the sales process contains any spaces or special characters, such as brackets, then it must be enclosed with quotation marks.

The output XML file is named with the language-independent name of the sales process.

Note: The Oracle Migration Tool On Demand client requests your Oracle CRM On Demand password, which can be redirected (using the pipe command) to the client program from standard input; that is, from a file, from the command line, or from another program.

Example of Extracting a Single Sales Process

The following is an example of extracting a sales process named High Potential:

migrationtool -u UserID -s ServerURL Read SalesProcess "[High Potential]"

Extracting All Sales Processes

This topic describes how to extract all of the sales processes from your Oracle CRM On Demand environment.

Syntax

The following is the syntax for using the Oracle Migration Tool On Demand client to extract all of the sales proceses:

migrationtool -u UserID -s ServerURL ReadAll SalesProcess

where:

UserID is the user sign-in ID that has the appropriate privileges to run the Oracle Migration Tool On Demand client commands.
ServerURL is the URL for the Oracle CRM On Demand server where your company resides.

Note: The Oracle Migration Tool On Demand client requests your Oracle CRM On Demand password, which can be redirected (using the pipe command) to the client program from standard input; that is, from a file, from the command line, or from another program.

Updating or Inserting a Sales Process

This topic describes how to update a sales process (if it exists) or insert a sales process (if it does not exist) on your Oracle CRM On Demand environment (customer test environment or production).

About the Upsert Operation

The Upsert command inserts or updates sales processes based on the user key: BaseName, which is the language-independent name of the sales process.

Oracle CRM On Demand attempts to locate the sales process specified in the input file based on the user key. If a match is located, then the sales process is updated. If Oracle CRM On Demand cannot locate a sales process based on the user key, then a new sales process is created.

Syntax

The following is the syntax for using the Oracle Migration Tool On Demand client to insert or update a sales process:

migrationtool -u UserID -s ServerURL Upsert SalesProcess SalesProcessXML

where:

UserID is the user sign-in ID that has the appropriate privileges to run the Oracle Migration Tool On Demand client commands.
ServerURL is the URL for the Oracle CRM On Demand server where your company resides.
SalesProcessXML is the fully qualified path name of the sales process XML file, for example:
```
C:\My Files\[High Potential].xml
```
If the fully qualified path name contains any spaces or special characters, such as brackets, then it must be enclosed with quotation marks, for example:
```
migrationtool -u UserID -s ServerURL Upsert SalesProcess "C:\My Files\[High Potential].xml"
```

Note: The Oracle Migration Tool On Demand client requests your Oracle CRM On Demand password, which can be redirected (using the pipe command) to the client program from standard input; that is, from a file, from the command line, or from another program.

Example of Updating or Inserting a Sales Process

The following is an example of updating a sales process (if it exists) or inserting the sales process (if it does not exist) in your Oracle CRM On Demand server:

migrationtool -u UserID -s ServerURL Upsert SalesProcess "C:\Oracle Migration Tool On Demand\windows\repository\SalesProcess\[High Potential].xml"