1. Understanding Import and Export Management for Sales and Fusion Service
  2. Examples of Making Resource Role Related Updates

Examples of Making Resource Role Related Updates

You can make resource role related updates to a resource by changing the resource information such as resource role code.

The following scenarios illustrate the various resource role related updates you can make to a resource.

  • The resource is part of the hierarchy.

  • The resource isn't part of the hierarchy.

You can also add a standalone (non-manager or manager) resource to a hierarchy.

Resource is a part of the Hierarchy

Cox Parker is a Sales Representative reporting to Ross Hayes. The reporting hierarchy, organization, and role details of Cox Parker are displayed as shown in this image:

Sales Representative Role Changed to Different Non-Manager Role in the Same Organization

In this scenario, Cox's role is changed from Sales Representative to Sales Administrator within the same organization. To change the role of Cox Parker to Sales Administrator, you must create a source file (CSV) with the attributes and import it using import management as shown in this table.

Attribute Name

Value

ResourcePartyNumber

Conta504976

ResourceOrgRoleCode

SALES_ADMINISTRATOR
Note: You can obtain the ResourcePartyNumber either from the Resource Directory or through Data Export. For information about obtaining the ResourcePartyNumber either from the Resource Directory or through Data Export, see the topic "Obtaining the ResourcePartyNumber for a Resource".
Note: If you specify a value for the ResourceOrgRoleCode attribute, you don't need to specify a value for the IndividualRoleCode attribute.

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.

After your import runs successfully, send the pending LDAP user update requests:

  1. In the Navigator, click Scheduled Processes.

  2. In the Scheduled Processes page, click Schedule New Process.

  3. In the Schedule New Process dialog box, from the Name drop-down list, search for Send Pending LDAP Requests.

  4. From the search results, select Send Pending LDAP Requests and click OK.

  5. In the Process Details dialog box, click Submit.

  6. In the Confirmation dialog box, click OK.

  7. Click Close.

  8. In the Scheduled Processes page, click the Refresh icon.

  9. Verify if the status of the process has completed successfully.

You run the scheduled process Reporting Hierarchy Generation to re-generate 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.

The details of Cox Parker after the role change update from SALES_REPRESENTATIVE to SALES_ADMINISTRATOR are displayed as shown in this image:

Sales Representative Role Changed to Different Non-Manager Role in the Same Organization

Employee Resource isn't part of the Hierarchy

Pat Tyme is a Sales Manager who's not part of the hierarchy.

In this scenario, Pat's role is changed from Sales Manager to Sales Director. To change Pat's role to Sales Director, you must create a source file (CSV) with the attributes and import it using import management as shown in this table.

Attribute Name

Value

ResourcePartyNumber

Conta765976

IndividualRoleCode

SALES_DIRECTOR
Note: This scenario assumes that the user is assigned one IndividualRoleCode.

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.

After your import runs successfully, send the pending LDAP user update requests:

  1. In the Navigator, click Scheduled Processes.

  2. In the Scheduled Processes page, click Schedule New Process.

  3. In the Schedule New Process dialog box, from the Name drop-down list, search for Send Pending LDAP Requests.

  4. From the search results, select Send Pending LDAP Requests and click OK.

  5. In the Process Details dialog box, click Submit.

  6. In the Confirmation dialog box, click OK.

  7. Click Close.

  8. In the Scheduled Processes page, click the Refresh icon.

  9. Verify if the status of the process has completed successfully.

Adding a Standalone Resource to a Hierarchy

You can add a standalone resource (non-manager or manager) to a hierarchy. To add a resource to the hierarchy, you must create a source CSV file with the attributes and import it using import management, as shown in this table.

Attribute Name

Value

ResourcePartyNumber

Conta765976

ResourceOrgManagerEmail

charlotte.edwards@vision.com

ResourceParentOrganizationName

Global HQ

ResourceOrganizationName

JsmithOrg

(Optional)

You run the scheduled process Reporting Hierarchy Generation to re-generate 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.

Note: Provide values for the ResourcePartyNumber, ResourceOrgManagerEmail, and ResourceParentOrganizationName attributes when adding a non-manager resource to the hierarchy. Optionally, provide a value for the ResourceOrganizationName attribute when adding a manager resource to the hierarchy