attributes gone mising after HR sync

[Former Member]

Hi guys,

We're receiving the SRM org model via the ECC org model.

We have a daily night job (RHALEINI) that's in update mode. First we run this on org units and after this one has ended we run it for positions.

Every now and then we miss the values of several attributes at position level. The values we miss are usually extra values. For example, there's been added an additional BUK value besides tha default one.

You can think of the attributes CAT and BUK. We also miss several custom attributes.

Any idea why we have this issue? Is it because we run the job for positions and org units seperated? Or is there another reason?

Regards,

Timo

[Former Member]

Hi guys,

I faced the same while running RHALEINI in update mode.

Can anyone confirm the updates work with evaluation path SBESX? Or RHALEINIas to be run separately for O, S, P using evaluation path O-S-P.

Many thanks in advance.

Regards

Message was edited by: Muhammad Ali Mahmood

[Former Member]

Evaluation path wasn't succesfull. Any other ideas?

Timo

[Former Member]

Hi

Thumb rule for HR-SRM Replication.

1. Except Initial Upload or a post upgrade activity, changes from HR should flow via Change Pointers and not via PFAL in Update mode

2. In case if there are manual updates to be carried out , then carefully analyze what needs to be repaired in SRM. Pick up the evaluation path carefully as per the mentioned OSS note and trasfer that data in update mode. Update will work this way - if an object already exist, it will get updated in SRM. If not, it will be created afresh.

3. In update mode, the attributes should not be overwritten.... for any org unit or position.

Virender Singh

[manikanda_sundararajan]

Thanks for your reply . But change pointers are not picking all the information like employee details. how it will work for new employees added in a org. Any feedback on this is much appreciated.

Thanks, Mani

[Former Member]

Thank you both for your answers.

I've updated rhaleini with evaluation path SBESX and the evaluation path of today.

We'll now keep a closer look at the updates for the next few days.

Evaluation path wasn't succesfull. Any other ideas?

[Former Member]

For distributing organizational units, positions and employees please

refer to note 363187. If you don't want to distribute all employees,

but only the positions and employees that are assigned to a special

root you may procede as described below: You can distribute all of the

positions and employees of a root node, including all of the sub nodes,

in the same way as you distribute the organizational units. To do so,

you must make the following settings in the RHALEINI report:

Since the organizational units are distributed again with this selection

you must select the UPDATE mode; otherwise all of the attributes maintai

-ned previously will be deleted.

Object type O

Object ID Root organizational unit number

Evaluation path SBESX

Status vector 1

Rec. partner system Logical system name of the EBP system

Message type HRMD_A or HRMD_ABA

For distributing

Also please refer note 550055 it is a collective note which deals all

the problems related to HR replication and organizational structure

synchonization.

[manikanda_sundararajan]

The information regarding the selection parameters in "RHALEINI" is very useful . What should be parameter in Reporting Period. Whether this has to be " Today " or "All"

Thanks , Mani