Different field groups in the different account groups

Question

Dear IT Experts,
I´m working on restructuring authorization in roles concerning the IC and TP customers.
The goal of this changes is be able to have different field groups in the different account groups (TP and IC), for give you some more detail a good example can be, the same AMS user should be able to change general data and sales views for TP customers  but for IC he should only be allowed to change the sales views, however when the changes are made in the roles they are being ignored because as far as I could check the system does not have as a rule that the field groups are or can be dependent from the account group...
I can give you a clear example:
Role A
F_KNA1_AEN -> VGRUP = 10-16
F_KNA1_GRP -> ACTVT = 01, 02, 03
F_KNA1_GRP -> KTOKD = INTR
Role B
F_KNA1_AEN -> VGRUP = 16
F_KNA1_GRP -> ACTVT = 01, 02, 03
F_KNA1_GRP -> KTOKD = THIR
Despite it looks fine, the system is not validating the account group with the correspondent field group in each role, so the field groups that the system use is unique, it means it the content of the object F_KNA1_AEN in total independently of used account group!
So my question is, can we apply any other object that makes the field group being directly depending of the account group, as we can see for example activities for each account group having something similar for field group and account group?
Can someone please explain me step-by-step how I can do this work even if by another method?
I´m quite new on this issues and I really need your wisdom to find a solution for this.
Many thanks
Katjia

Answer 1

Hi Manoj
The debate is each inidividual business unit has defined different account groups for the same vendor in their respective systems.
The question is : What is the best practice-- Should we keep Vendor account group as main table field and define Vendors with one unique account groups OR we maintain the account group in qualified table each pointing to different business unit.
In my opinion this is going to be very complex solution. Ideally we need to define all the Harmonization rules before syndicating data to different target systems.
Is this possibel that the same vendor record which is existing as vendor of different account groups in different systems have same set of attributes. If yes then enabling the remote key for Account group Lookup field is one option and defining a unique Account group 'AG" (which is mapped to say AG1 from remote system1, AG2 from remote system2 and so on..)..
Managing this via Qualified table will be very complex and not advisabel. As Rajesh also mentioned Account Group in MDM should be considered as Global attribute and all such harmonization rules should be defined in your project. AG1=AG2=AG in above exmaple.
Hope this clarifies.
Thanks-Ravi