on 01-14-2011 4:00 AM
Hi All,
In the HR Org structure in ECC, a position (S) can have more than one A012 relation with different organization units (O).
For example:
S 123 has a A012 relation with Org unit A; validity date: 04/04/2006 to 12/31/9999
S 123 has a A012 relation with Org unit B; validity date: 06/01/2006 to 12/31/9999
org unit B falls under Org unit A in the Org unit hierarchy structure.
But, in SRM I find that only one relation A012 linking S to O can be maintained, which is:
S 123 has a A012 relation with Org unit B; validity date: 06/01/2006 to 12/31/9999
I tried passing the data again through PFAL transaction (update mode), but the data in SRM does not change.
Is this standard behaviour? Can't a person manage more than one org unit in SRM?
I am currently working on SRM 5.0 with ECC 6.0 as backend.
Regards,
Ancy
Hi,
This functionality only relates to users who are professional
purchasers. It means that they can be responsible for more than one
purchasing group. In past releases, they were responsible for the
purchasing group that they hung from in the org structure. Since some
customers wanted that they could be responsible for more than one
purchasing group, but the system would not allow the purchaser to belong
to more than one org unit. Hence they introduced the new functionality
that I described above. However it is not technically possible for a
user to belong to more than one org unit since this would lead to
inconsistencies in the way that the attributes work.
I hope this helps.
Kind Regards,
Edel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.