What to Do Before Importing Channel Sales Users

After you create several channel sales users in the UI to test your setup, you are ready to import the rest of the users from a text file.

The import creates the resource organizations for each manager, creates the channel sales organization hierarchy, and provisions the channel sales users with the job roles and abstract roles they need. To speed up your import, you can download a template provided by Oracle.

You can open the different import tasks directly from the Create Sales Users folder in the implementation project or by searching for the tasks by name from the Setup and Maintenance work area.

The following table provides the steps for importing channel sales users, including downloading the import template, replacing the sample data with your data, adding columns to the template for additional data and mapping the new data, importing the data, and testing the import results. This table also lists the task name for each step (where applicable).

Step	Description	Task Name
1	Download the template from the Employee Resource Seeded Mapping - Comprehensive mapping. To display the mapping, search for the seeded mappings for the Employee Resource object.	Manage File Import Mappings
2	Replace the sample data in the template with your data, preserving the order of the columns. You must obtain some of the values for your import from the application itself. For example, you must include the names of the business unit and the legal entity as it appears in the application and you must include the codes for the resource roles you are using.	This is a task you perform in your import file.
3	Append to the last column in your import file any additional attributes you want to import. For example, to control which user records send you the emails with user credentials, append a column with the heading WorkerProfile_SendCredentialsEmail. By importing a value of Y or N for each user, you can specify which user records generate the email. Make sure that you obtain the sign-in information for a representative sample of users, so that you can use those users for testing. For example, to test opportunity assignment and forecasting, you can sign in as a salesperson and manager in each regional sales organization. To test forecasting and quotas, you must be able to sign in as the sales administrator. If you are importing the users, then you can indicate in your import file if you want to receive the credentials emails.	This is a task you perform in your import file.
4	If you added any additional columns to the original template, you must create a new mapping for your import. To do this, you copy the predefined mapping and add the additional import column to the copy.	Manage File Import Mappings
5	Import the file using the mapping you copied and modified.	Manage File Import Activities
6	Enable searching of the imported users.	Manage HCM Configuration for Coexistence
7	Sign in as one of the sales users you created, and review the resource organization by navigating to the Resource Directory. The directory displays a graphical representation of the resource hierarchy. You can correct any minor errors that you find and upload user photos by signing in as a setup user again. You search for and edit the user records in the Manage Users work area.	This task is not available in the implementation project. Instead, select Resource Directory in the Navigator.

Employee Resource Import Template

The following table describes the columns contained in the Employee Resource Seeded Mapping - Comprehensive import template and the values these columns expect.

The template file includes a header row with the key attributes for your import, including all the required fields. The attribute name in each column consists of two parts separated by a period. These correspond to selections you make for mapping the import file to the attributes in the application.

The file columns are arranged in the same order as a mapping Oracle provides for you. If you do want to add additional columns, then add them after the last column.

The following table lists the columns in the order they are included in the template and provides instructions for the values each attribute expects. You can get more detailed information about these attributes from the File Based Data Import guide available for sales applications on docs.oracle.com.

Template Header Column Name	Value to Import
WorkerProfile_BusinessUnit	Enter the name of the business unit created for you when you signed up for the service. You can obtain this value from the Business Unit field in the Employee Information region of Create User page, as described in this topic.
WorkerProfile_LegalEntity	Enter the legal entity created for you. You can obtain this value from the Legal Employer field in the Employee Information region of Create User page, as described in this topic.
WorkerProfile_FirstName	Enter the first name as you want it to appear in the sales application.
WorkerProfile_LastName	Enter the last name as you want it to appear in the sales application.
WorkerProfile_EmailAddress	You must enter a unique email address. The application sends the initial sign-in credentials to this address unless you: Redirect the email to an alternate user Delay the sending of the email. These options are described in related topics.
WorkerProfile_ManagerEmail	Enter the manager's email address. The application uses this address to build the management hierarchy.
WorkerProfile_PersonType	Indicates the type of worker you are importing. Because you are creating users who are employees, you can either enter EMP (for employee) or leave this column blank. The application supplies the EMP value by default. You can use other values, such as CWK (contingent worker), but doing so is useful only if you are building an integration with the Oracle HCM Cloud.
ResourceProfile_RoleCode	Enter the internal code for each resource role. For sales, the codes for the sales resource roles provided by Oracle include: SALES_VP CHANNEL_SALES_MANAGER CHANNEL_OPERATIONS_MANAGER CHANNEL_ACCOUNT_MANAGER Follow the procedure in this topic to obtain additional codes.
ResourceProfile_RoleTypeCode	Always enter CHANNEL_SALES (uppercase) in all rows for sales resource roles. For other types of resource roles this value is different. For example, for the customer data management role, the code is CUSTOMER_DATA_MANAGEMENT.
ResourceProfile_CreateUserAccount	Always enter a Y.
ResourceOrganizationMembership_TreeCode	Always enter GLOBAL_CHANNEL_SALES_MARKETING.
ResourceOrganizationMembership_ParentTreeCode	Always enter GLOBAL_CHANNEL_SALES_MARKETING.
ResourceOrganizationMembership_OrganizationUsage	Always enter CHANNEL_SALES_RESOURCE_ORG
ResourceOrganizationMembership_OrganizationName	For each manager, enter the name of his or her resource organization. Leave this column blank for the individual contributors. The organization names you enter here appear in the resource directory and elsewhere in the UI.
ResourceOrganizationMembership_ParentOrganizationName	Enter the organization name of the person's manager. You must make this entry both for the managers and individual contributors. The names must precisely match the names you entered for OrganizationName, so watch for capitalization and spaces.

Add Channel Sales to Vision Corp.

To support the business use cases mentioned previously, we must create a channel sales branch of Vision Corp.

The channel sales team consists of the following:

• Beth Howard - VP Global Channel Sales

• Daniel Grayson - VP US Channel Sales

• Terry Smith - Channel Sales Manager

• Bill Cross - Channel Operations Manager

• Colby Morris - Channel Account Manager

• Bonnie Vickers - Channel Account Manager

• Ellis Gibson - Channel Account Manager

The following table shows the ResourceOrganizationMembership_OrganizationName and ResourceOrganizationMembership_ParentOrganizationName entries for each member of the channel sales branch of Vision Corp. listed above.

WorkerProfile_FirstName	WorkerProfile_LastName	ResourceOrganizationMembership_OrganizationName	ResourceOrganizationMembership_ParentOrganizationName
Beth	Howard	Global Channel Sales	Global High Tech
Daniel	Grayson	US Channel Sales	Global Channel Sales
Bill	Cross	US Channel Sales	US Channel Sales
Terry	Smith	US Channel Sales	US Channel Sales
Colby	Morris	US Channel Sales - East	US Channel Sales
Bonnie	Vickers	US Channel Sales - Central	US Channel Sales
Ellis	Gibson	US Channel Sales - West	US Channel Sales

Obtain the Names of the Business Unit and Legal Entity

1. Sign in as a setup user.

2. Open the task Users and Roles from the implementation project or search for the task by name in the Setup and Maintenance work area.

3. Click Create.

   The Create User page appears.

4. In the Employment Information region, select Employee as the Person Type.

5. You can obtain the business unit and legal entity values for your file from the Business Unit and Legal Entity lists.

6. Click Cancel.

Obtain the Resource Role Codes

1. Sign in as a setup user.

2. Open the task Manage Resource Roles task from the implementation project. Alternately, search for the task by name in the Setup and Maintenance Work area.

   The Manage Resource Roles page appears.

3. To obtain a list of resource roles for sales, select Sales from the Role Type list and click Search.

4. Click Edit for each resource role that you want to import. The value in the Role Code field is the value you must include in your file.