OM infotypes not updated with relatioship.

[Former Member]

Hi Experts,

I made one LSMW to upload info types 0000 (Actions) and 0001 (Org Assignment) using batch input recording method and successfully updated PA infotypes and verified OM info types 1001 (Relationships) for those positions (S) which I assigned new holders (P).

But OM not got updated and is not showing the holder in those positions which I executed action.

Can any tell me why it has not updated OM.

With regards,

Chandrasekhar

Edited by: chandra sekhar on Mar 7, 2009 12:22 PM

[Former Member]

As to why OM is not updated, I believe the integration doesn't work for Batch Input. As said, RHINTE00 is meant to update OM with PA as master. Just one word of caution: If you have CostCenters sometimes assigned to positions in OM, you may get the follwoing problem:

- The integration (online) updates P0001 with the Cost Center from the position.

- Now if you run RHINTE00, this cost center is put to the org.unit.

So I would encourage that you check this out first. It caused problems in our system - as some costcenters were related to O and some to S.

/Kirsten

[sikindar_a]

means

run the RHINTE Reports once

before check all the records exists or not

u2022 RHINTE00 - Transfer PA Records To PD Positions. In another world, it creates the HRP1001 between P to S in the OM side of the world. When you view a record via IT0001, you see this person holds the position, however via HRP1001, that relationship isnu2019t so.

u2022 RHINTE10 - Generates the required relevant tables. (T513 - Jobs, T513S - Jobs, T528B - Positions, T528T - Work Center, T527X - Org Unit

u2022 RHINTE20 - checks for all objects for integration between PA and OM. This is a big one and will take awhile to run. What it does is look at table T513/T513T - Jobs, T528/T528T - Position, and T528X - Org Unit. It will then compare it against the HRPxxxx table to find missing objects. If there are any missing objects, it will create the record.

u2022 RHINTE30 - Transfer OM to PA. This will create infotype 0001. If the conversion strategy is to have SAP auto inherit factor to kick in for IT0001, often time jobs and org unit are missing via IT0001 during the inital conversion load. RHINTE30 will find the relationship and push it through IT0001.

Edited by: Sikindar on Mar 7, 2009 12:34 PM

[Former Member]

Hi,

In the relation with person, have u maintained the percentage 100%. Try to run the relationship with that once again it will update

Yogita