cancel
Showing results for 
Search instead for 
Did you mean: 

Multi-level Account Hierarchy in C4C

Former Member
0 Kudos

Dear Experts,

We would like to setup a multi-level Account Hierarchy in C4C.  The documentation and guides only provide clarity and guidance for a single level but the migration template lacks any documentation or assistance for multiple levels and how the data needs to be entered into the template.  We have tried a few different configurations for the data but they all seem to fail.

Please advise and provide some clarity around the structure of the data in the migration template.  An example template would be greatly appreciated.

Thanks,

Farasat

Accepted Solutions (0)

Answers (1)

Answers (1)

pushkar_ranjan
Employee
Employee
0 Kudos

Please read through the the following documentation and get back to us if you are unable to reach your end result of migrating a multilevel account hierarchy.

Thank you.

Activating Account Hierarchy Visibility

Prerequisites

You must decide whether your organization wants to activate the visibility of account hierarchies within SAP Cloud for Customer.

If this feature is activated, then users can choose the Account Hierarchy tab — for each account for which a parent account has been specified — to view the displayed accounts in a hierarchical structure. Users can expand and collapse the account hierarchy at any level to display as many or as few accounts as they like.

Overview

If your organization does want to activate account hierarchy visibility in its planned scope, then proceed as follows:

Procedure

  1. 1. Choose  Business Configuration  Implementation Projects .
  2. 2. Select the title of the appropriate implementation project.

The Project Overview screen appears.

  1. 3. Choose Edit Project Scope.

The Edit Project Scope screen appears.

  • Under Country and Type of Business, select Next.
  • Under Implementation Focus, select Next.
  • Under Scoping, select Next.
  1. 4. On the Questions screen, expand the Sales scoping element, then expand the Account and Activity Management scoping element, then select the Account Management scoping element.
  2. 5. On the adjacent screen, under Questions for Account Management, expand the Account Hierarchy selection.
  3. 6. Select Yes.
  4. 7. Choose Save Draft.
  5. 8. Close the Edit Project Scope screen.

Hide All

Migrating Account Hierarchies

Prerequisites

Configuration

Customer accounts have been created in the solution, or migrated into it.

If sales representatives are to see the migrated account hierarchies, then account hierarchy visibility must be active. For more information, see Activating Account Hierarchy Visibility.

Business Background

Master data for sales accounts is maintained under  Customers  Accounts . For information about creating and editing accounts, see Accounts.

Tasks

Downloading the Migration Template

To migrate account hierarchies into the solution, first download the predefined migration template that is provided for this purpose. To do so, proceed as follows:

  1. 1. Choose  Business Configuration  Implementation Projects .
  2. 2. Select the implementation project entitled First Implementation, then choose Open Activity List.

The Activity List appears. For more information, see Complete the Activity List.

  1. 3. In the Prepare phase, select the activity entitled Prepare for Data Migration.
  2. 4. On the subsequent screen, select Download Migration Templates.
  3. 5. On the resultant screen, find the migration object entitled Customer Hierarchies.
  4. 6. Click Download.
  5. 7. Save the migration template to your preferred directory.

Entering Legacy Data into the Template

Now enter data in each of the following columns:

  • Hierarchy ID, on the Hierarchies
  • Account ID, on the Accounts
  • Parent Account, on the Accounts

For additional instructions on how to enter legacy data into the template, review the Introduction and Field List worksheets.

As you enter data in the migration template, remember the following points:

  • The Hierarchy IDAccount HierarchyHierarchy ID
  • The Hierarchy ID
  • The Hierarchy ID
  • Each hierarchy must have exactly one top-level node.

If you enter multiple hierarchy top-level nodes or no top-level node at all, an error message will be displayed.

If you have not entered the data properly in the template, then you may encounter this error message. The following example therefore illustrates how to enter the data for two account hierarchies to be migrated:

  • On the Hierarchies

Hierarchy ID

A

B

  • .
  • On the Accounts worksheet, perform the following entries:

Hierarchy ID

Account ID

Parent Account

A

10001

A

10002

10001

A

10003

10001

A

10004

10001

B

10005

B

10006

10005

B

10007

10005

  • In short, for the top-level node of each account hierarchy to be migrated, you must enter a corresponding Account ID, and you must not enter a corresponding Parent Account.
  • Each Account ID
  • The Parent Account

Uploading the Completed Template into the Solution

Now upload into the solution the completed template containing your account hierarchy data. Proceed as follows:

  1. 1. In the Integrate and Extend phase, select the Migration of Customer Hierarchies activity.
  2. 2. On the subsequent screen, choose Migrate customer hierarchies using the migration tool.

A dialog box appears.

  1. 3. Choose Upload, then specify the location of the template file containing the customer data to be uploaded.
  2. 4. Choose Execute Migration.

A dialog box appears, enabling you to monitor the progress of data validation by the solution.

  1. 5. Validation steps are displayed, along with any errors, where applicable. If no errors are reported, choose Next.

The value conversions step appears.

  1. 6. Choose Convert to perform conversion for the Customer ID, if required.

Conversions for other values are not supported.

  1. 7. If no conversions are required, choose Next.

A simulation of the data import is performed, and a dialog box appears, enabling you to monitor the progress of the data import simulation. Any errors that occurred during the simulation are displayed.

  1. 8. If no errors are reported, choose Next.

A dialog box appears, prompting you to confirm that you want to import the data.

  1. 9. Confirm that you want to proceed with the data import.

A dialog box appears, enabling you to monitor the progress of the data import. When the data import is finished, any applicable errors are displayed.

  1. 10. To complete the process, choose  Finish  Close .

Entering Data Manually

After migration is complete, if account hierarchy visibility is active, account hierarchies can also be manually edited under  Customers  Accounts  Account Hierarchy .

Follow-On Activities

Once the data entered in the template is migrated into the solution, the hierarchical relationship between accounts and their parent accounts becomes visible. You can now verify migrated account hierarchy data under  Customers  Accounts  Account Hierarchy .

Compare the data in your legacy system with the data that you have migrated into SAP Cloud for Customer. Review various records to ensure that the values in each system are in agreement.

Top of Page

Former Member
0 Kudos

Hi Pushkar,

Thanks for posting the documentation.   Unfortunately this only provides a solution for multiple single level hierarchies.  There is an additional sheet in the migration template for which there is no clear guidance or example on achieving a multilevel hierarchy.

Thanks,

pushkar_ranjan
Employee
Employee
0 Kudos

Have you tried assigning a child account as the parent of another account lower in the hierarchy?

What is the behavior?

Please advise your observations.

Thank you.

chandansb
Active Contributor
0 Kudos

Hello Faraz,

Please refer the below screenshot.

Here this Hierarchy was brought into C4C via integration. And if it is possible via Integration it can be also done via Migration Template.

Below is how it was seen on C4C.

My suggestion will be to add the expected Parent account under Account. Ex. In above case, Lars Ulrich was Parent for James Hetfield which in turn is Parent for lower Accounts assigned under it.

So try to fill in the template by maintaining them as --

Parent Account for lower Account from above image- James Hetfield.

Parent Account for James Hetfield- Lars Ulrich.

And then migrate them.

Hope this helps.

Regards,

Chandan

Former Member
0 Kudos

Hi Pushkar,

Manual assignment of a Parent Account A1 to another account B1 with children C1, C2, and C3 results in a system dump.  I have checked this in both HTML 5 as well as Silverlight.

Anytime we try to manually create a multi-level hierarchy for more than one level in the UI we get a dump.  The errors have been attached.  If you know of anyone that uploaded the structure via the Migration template (multi-level) please provide an example.  There is no documentation in the guide nor in the actual template on how to layer the data (as compared to single level - for which there is an example).

Thanks,

Farasat

Former Member
0 Kudos

Chandan,

There are two templates.  Use of the main template - results in two parallel hierarchies being created at the same level.  Regarding the second template (the optional one which seems to support multi level hierarchies), SAP has provided no clarity on its usage nor layering of the data for upload if multi-level hierarchies are desired for "Organization/Corporate Accounts."

Thanks,

Farasat