Migrating Sales Categories

This chapter describes how to migrate your sales categories using the Oracle Migration Tool On Demand client. It contains the following topics:

Sales Categories

Sales categories are used to organize sales stages from different sales processes into groups. You can run analyses against the sales categories.

The following table describes the Oracle Migration Tool On Demand client commands used with sales categories. These commands are case sensitive.

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

Command	Description
`Read SalesCategory Order`	This command extracts a sales category. The Order parameter specifies the order number of the sales category.
`ReadAll SalesCategory`	This command extracts all sales categories.
`Upsert SaleCategory SalesCategoryXML`	This command updates or inserts the sales categories specified in the XML file.

Privileges Required for Migrating Sales Categories

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 and Manage Data Rules - Manage Sales Stage Definition.
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 Categories XML Output File

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

Table Elements and Sections in the Sales Categories XML File

Description	Element or Section
<SalesCategory> contains the details of the sales category, as follows: <StageCategory> is the name of the sales category. <Description> is a description of the sales category. <Order> is the order number of the sales category. <MarkForTranslation> corresponds to the Mark for Translation check box in the UI. For more information, see Considerations for the Mark for Translation Setting.	<data:SalesCategory> <data:StageCategory>[Test Sales Category] </data:StageCategory> <data:Description>This is a test sales category</data:Description> <data:Order>1</data:Order> <data:MarkForTranslation>false </data:MarkForTranslation> . . . </data:SalesCategory>
The <ListofSalesCategoryTranslations> section contains the translation values for the sales category.	<data:SalesCategory> . . . <data:ListOfSalesCategoryTranslations> . . . </data:ListOfSalesCategoryTranslations> </data:SalesCategory>
The <SalesCategoryTranslation> section contains the translation values for one language: <LanguageCode> contains the three-letter language code for the language. For the list of language codes, see Language Codes and Their Corresponding Language and Country. <StageCategory> contains the sales category name in the language identified by the language code. <Description> contains the description in the language identified by the language code.	<data:SalesCategory> . . . <data:ListOfSalesCategoryTranslations> <data:SalesCategoryTranslation> <data:LanguageCode>ENU</data:LanguageCode> <data:StageCategory>My Test Sales Category 2</data:StageCategory> <data:Description></data:Description> </data:SalesCategoryTranslation> . . . </data:ListOfSalesCategoryTranslations> </data:SalesCategory>

Description

Element or Section

<SalesCategory> contains the details of the sales category, as follows:

<StageCategory> is the name of the sales category.
<Description> is a description of the sales category.
<Order> is the order number of the sales category.
<MarkForTranslation> corresponds to the Mark for Translation check box in the UI. For more information, see Considerations for the Mark for Translation Setting.

<data:SalesCategory>
  <data:StageCategory>[Test Sales Category]
  </data:StageCategory>
  <data:Description>This is a test sales 
   category</data:Description>
  <data:Order>1</data:Order>
  <data:MarkForTranslation>false
  </data:MarkForTranslation>
. . .
</data:SalesCategory>

The <ListofSalesCategoryTranslations> section contains the translation values for the sales category.

<data:SalesCategory>
. . .
  <data:ListOfSalesCategoryTranslations>
. . .
  </data:ListOfSalesCategoryTranslations>
</data:SalesCategory>

The <SalesCategoryTranslation> section contains the translation values for one language:

<LanguageCode> contains the three-letter language code for the language. For the list of language codes, see Language Codes and Their Corresponding Language and Country.
<StageCategory> contains the sales category name in the language identified by the language code.
<Description> contains the description in the language identified by the language code.

<data:SalesCategory>
. . .
  <data:ListOfSalesCategoryTranslations>
    <data:SalesCategoryTranslation>
      <data:LanguageCode>ENU</data:LanguageCode>
      <data:StageCategory>My Test Sales 
       Category 2</data:StageCategory>
      <data:Description></data:Description>
    </data:SalesCategoryTranslation>
. . .
  </data:ListOfSalesCategoryTranslations>
</data:SalesCategory>

Migrating Sales Categories

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

Extracting a Single Sales Category

This topic describes how to extract a single sales category 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 category:

migrationtool -u UserID -s ServerURL Read SalesCategory Order

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.
Order is the order number of the sales category.

The output XML file is named with the order number of the sales category that is extracted. For example, if you extract the sales category that has the order number 2, then the XML file is named 2.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 Extracting a Single Sales Category

The following is an example of extracting a sales category that has the order number 2:

migrationtool -u UserID -s ServerURL Read SalesCategory 2

Extracting All Sales Categories

This topic describes how to extract all of the sales categories 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 categories:

migrationtool -u UserID -s ServerURL ReadAll SalesCategory

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.

The output XML file is named with the order number of the first sales category in the file. For example, if the first sales category has the order number 1, then the XML file is named 1.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.

Updating or Inserting Sales Categories (Upsert)

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

Syntax

The following is the syntax for using the Oracle Migration Tool On Demand client to update a sales category (if it exists) or insert a sales category (if it does not exist):

migrationtool -u UserID -s ServerURL Upsert SalesCategory SalesCategoryXML

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.
SalesCategoryXML is the fully qualified path name of the sales categories XML file, for example:
```
C:\MyFiles\1.xml
```
If the fully qualified path name contains any spaces, then it must be enclosed with quotation marks, for example:
```
migrationtool -u UserID -s ServerURL Upsert SalesCategory "C:\My Files\1.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.