CRM and CX Blogs by SAP
Stay up-to-date on the latest developments and product news about intelligent customer experience and CRM technologies through blog posts from SAP experts.
Showing results for 
Search instead for 
Did you mean: 

Mapping ECC Account Groups and Partner Functions in C4C

C4C Party Roles are used to define the Account team roles and Relationships with other business Partners. These are maintained in the PARTY ROLE DEFINITION activity in Fine Tuning, and are mapped in Code list mapping (CLM) under the mapping group PartyRoleCode to Partner Functions in ERP (Field TPAR – PARVW).

The concept of PartyRoleCode is often confused with the BusinessPartnerRoleCode, where we map ECC Account Groups.

But please pay attention to the following chart to get the concepts right:

If you create a Z Party Role, you will be able to see it in the PartyRoleCode  Mapping group, but not in BusinessPartnerRoleCode.

If what you need is to map ECC ACCOUNT GROUPS to C4C, please consider that C4C was not designed with a correspondent

Accounts cannot be distinguished using an Account Group assignment in C4C. Only 2 types of Account Characters
(Accounts and Prospects) are assigned to Account Groups for classification in ERP. This is a 1 to N relationship.

It is not possible to create these Business Partner Role Codes in Fine Tuning, the Local Codes you see under this group are the only
ones you can map, and you can do it in the following way:


  1. ECC Account Group  (KNNV – KTOKD) --> Sold to Party KUNA is mapped to Local code CRM000 (Account)
  2. ECC Account Group  (KNNV – KTOKD) --> Goods Recipient Z0002  is mapped to Local code CRM000 (Account)

This means that regardless of what is the Account group used in ERP, it will always create a “generic” account in C4C.

If the Account is generated in C4C it will always create An Account in ECC that belongs to the “outbound default Account
group” defined in the CLM. (check the Outbound default column)

This limitation has been addressed by SAP product Management and it is currently in backlog to be improved in a future
release. Please stay tuned for updates!!

For the time being, depending on your business case you may want to explore some possible workarounds:

Assign Correct  Account Group in ECC TRX XD07:

Let the Standard C4C solution create the account in ERP, using a single default Account Group, and then let sales ops change the Account Group in ERP using transaction XD07, once they decide on the correct Account Group.


The Account number in ERP does not change to match the number range of the new Account Group, when you change the Account Group via XD07.This results in Account Ids belonging to different number ranges for Accounts with the same Account Group.

If the Account Group is changed in ERP, all future integration from C4C to ERP will fail, since the Account Group C4C is sending
by default, does not match any more. This can easily be corrected applying OSS note, which then ignores the Account Group coming from C4C

Use a Field Extension to map Acc. Groups 1 to 1:

There is an option to create a field extension for the Account Group in C4C and to map it to KTOKD field in ECC, but that would only work for the initial account creation. Once the Account is replicated to ECC no further changes should be done to the field, since the same IDOC cannot be used
to change Account Groups. An Approach could be to Integrate that extension field  also in the inbound, that way, in case the Account Group is for some reason changed in ECC, the inbound message would take care of changing the Extension field in C4C.


It is necessary to set the Account Group Extension field as Mandatory and also Read only once saved, via PDI.