Limitations of HR Org Structure in EBP?

[Former Member]

Hi Friends

What are the limitations of HR Org structure in EBP?

Regards

Raahul

Edited by: N.Raahul on Aug 19, 2009 3:50 PM

Edited by: N.Raahul on Aug 20, 2009 3:48 PM

[Former Member]

Hi Raul,

a few things have to be checked:

1. Very important for the transfer from HR-System is NOT to use the insert mode, but the update mode . Otherwise all attributes, extended attributes and flags are killed within SRM.

2. For the problem with the not usable SU01 users, "force" the HR department to maintain the info type 0105 (communication) subtype 0001 (SAP-User), and you´ll get the connection between person and SAP-User automatically.

3. Check whether the must have adress fields within HR are maintained ORT01 and LAND1

4. The position sharing within HR causes problems within SRM, because only one person (the earlier one) can be found for e.g. approval.

5. Obsolete orgunits, positions etc. should not be deleted, but to be set invalid with "valid until", because the update of deleted orgunits to SRM doesn´t work.

That´s it - maybe the comes more.

Kind regards,

Tilman

[Former Member]

Hi Rahul,

There are many ..... one of the important which SAP recommend is that performance problems can be encountered in transaction PPOMA_BBP if too many users are assigned to the same organizational unit. You should therefore make sure that you do not assign more than 200 users to the same organizational unit.

Hope this helps

Thanks, Sachin

[Former Member]

SU01 users will not be created in the EBP system.

Org Strucuture Attributes have to be maintained manually.

Regards,

Satya.

[Former Member]

Also, refer note 934372 and 1345913.

Edited by: sachindubey on Apr 8, 2010 11:23 AM