Large Purchasing Group Responsibilities
Fellow SRM Users,
We currently had to restructure our org in SRM, we went from a number of small purchasing groups to one large purchasing group with 2000+ members in it's responsibility tab. Unfortunately it looks like this is causing slow down whenever our org administrator makes updates to that p.group. It gets worse with more users added to the responsibility tab, to the point actions such as save times out or abap dump.
Does any other company have large purchasing groups? Did you experience this issue? If so, what is a work around? Does it make sense to have this many users in the responsibility tab of a p. group?
Laurent Burtaire replied
Why do not you use object O (Organizational Unit) instead of object US (User) in the Purchasing Group responsability tab ?
If all your concerned users are assigned to Units being hirerarchically linked to same Unit, insert only its ID.
In this way all puchasings done by users belonging to this Unit or lower ones will have this Puchasing Group as responsible.
If it is not possible with your current Organizational plan, put all Org. Units ID of concerned users: you will have fewer entries than with users ID.