Example of Creating a Sales Representative in a Resource Organization

You can use import management to create resources as a sales representative and add them to the resource hierarchy. You need to specify additional information such ResourceManagerEmail or ResourceParentOrganizationName to create a sales representative as a standalone resource.

Before You Begin

The scenario in this example assumes that the following prerequisites have already been set up.

1. Appropriate business units are set up using the Manage Business Unit task.

2. Appropriate legal entities are set up using the Manage Legal Entity task.

3. Email Ids and user names should be unique.

Scenario

In this scenario, Bob Frank is created as a resource with the role SALES_REPRESENTATIVE. You must create a source file (CSV) with the attributes and import it using import management as shown in this table.

Attribute Name	Value
FirstName	Bob
LastName	Frank
UserName	[e-mail]
ResourceEmail	[e-mail]
BusinessUnit	Vision Corporation Enterprise
LegalEntity	Vision Corporation
ResourceOrgRoleCode	SALES_REPRESENTATIVE
ResourceManagerEmail	[e-mail]
ResourceParentOrganizationName	Global HQ

Note: Providing the user name is optional. If you don't provide the user name, the application will generate the user name by default. Provide values either for the ResourceManagerEmail or the ResourceParentOrganizationName attribute. If neither of these is provided, then the resource is associated with the root resource organization as parent organization.

When you're creating a new resource user, the CreateUserAccountFlag controls the user account creation for the resource. The default value for CreateUserAccountFlag is Y. If you don't want the user account to be created, then you can set the attribute CreateUserAccountFlag to 'N'.

You can import the source data file.

1. Go to Navigator > Tools > Import Management > Import Queue.

2. Click Create Import Activity in the Manage Imports page.

3. In the Enter Import Options page, provide a name for the import activity, and select Resource from the Object drop-down list.

4. Select the CSV file in the File Name field, and click Next.

5. The source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

   Note: Validation errors, if any, are displayed on the Mapping Validation screen. If you get warnings about unmapped columns, then you can ignore these columns and proceed to submit the import job. Validations are for informational purposes and applicable only for low-volume imports.

7. Review the import details on the Review and Submit page, and click Submit when you're ready.

To enable or disable notifications for resources, see the section Set Up Event Notifications for Resources in the topic Import Data.

You must run the following scheduled processes after creating the sales representative in the resource organization:

1. Reporting Hierarchy Generation: This job re-generates the resource reporting hierarchy when there is a change in the organization hierarchy. For more information about the Reporting Hierarchy Generation scheduled process, see the section "Reporting Hierarchy Generation" in the Understanding Scheduled Processes guide.

2. Send Pending LDAP Requests: This job processes the pending LDAP requests to provision the user accounts and roles. You can specify the parameters User Type and Batch Size with this job. You must specify User Type (usually select All); if you leave it as blank, then this process won't process any requests. If you don't set Batch Size, the default will be A for automatic, which is 1/10th of the total requests number. You can specify a number for batch size to instruct the process to group that number of requests together for single batch process. If you want the process to pick up the FAULTED requests from previous run, you can set Batch Size as AF. Run this scheduled process when you create a new resource along with the user account.

3. Update Person Search Keywords: This job copies the keyword values automatically from the originating records to the PER_KEYWORDS table, where they are indexed to improve search performance.