Hi all,
In the previous blog I described to you the weird behavior of our system (ERP - HCI - C4C), whenever a change was made in a customer.
In this blog I will explain the solution to overcome this deletion of ERP fields along with images.
In a more general approach, the are two reasons for that problem that have to be solved .
Regarding the first point, in C4C you must navigate to;
"APPLICATION AND USER MANAGEMENT", then "ID MAPPING FOR INTEGRATION".
You click on that, and then on the next screen, click on the "Edit ID Mapping for Integration"
In the upcoming screen, in the field "Mapping of:" select the "ERP Employees"
In the "System Instance ID:" field, insert the corresponding system ID of your ERP system, and click on "Go"
The following image shows a list of employees where "ID" is the C4C Internal ID number mapped with the External ID number (ERP).
In this blog you can see the way to do this mapping.
If the error persists, you have to move to the second solution, described in the next blog, part 3.
.CV
In the previous blog I described to you the weird behavior of our system (ERP - HCI - C4C), whenever a change was made in a customer.
In this blog I will explain the solution to overcome this deletion of ERP fields along with images.
In a more general approach, the are two reasons for that problem that have to be solved .
- ID mapping of the "Employee Responsible" (C4C side)
- Partner Function (HCI side)
Regarding the first point, in C4C you must navigate to;
"APPLICATION AND USER MANAGEMENT", then "ID MAPPING FOR INTEGRATION".
You click on that, and then on the next screen, click on the "Edit ID Mapping for Integration"
In the upcoming screen, in the field "Mapping of:" select the "ERP Employees"
In the "System Instance ID:" field, insert the corresponding system ID of your ERP system, and click on "Go"
The following image shows a list of employees where "ID" is the C4C Internal ID number mapped with the External ID number (ERP).
In this blog you can see the way to do this mapping.
If the error persists, you have to move to the second solution, described in the next blog, part 3.
.CV
- SAP Managed Tags:
