HR_INFOTYPE_OPERATION integration to PD/OM

[former_member622817]

Has anyone who has used FM HR_INFOTYPE_OPERATION had issues with integration to PD/OM?

After I use this FM to perform a termination for an EE (and create an IT0001 record with integration position 99999999) the validity period for the relationship (HRP1001) is not updated. If I terminate the EE manual using PA40 then the HRP1001 record is updated.

And yes, I do have PA/OM integration activated (PLOGI ORGA = 'X')

Thanks,-tom

[Former Member]

sorry for reopening this topic, but did anybody ever find a clever solution to this problem?

[ted_dinh]

Tom:

Check out OSS 874350 to see if it's relevant to your environment.

Rgds.

[former_member622817]

Note 874350 - Performance of idocs from F110 into IHC is not related to HR. So definitely not relevant.

[ted_dinh]

Note 874530 - Termination Org does not delimit Position relationship

[former_member622817]

Ted,

I imported this note using SNOTE but the system will not allow me to apply it. I think it is because the note is for component "PY-AU Australia" and since we do not have Australian payroll we cannot implement it.

But thanks for the suggestion.

cheers,-tom

[Former Member]

I dont think HR_INFOTYPE_OPERATION does that , run RHINTE reports to adjust the Relationships.

[former_member622817]

Balaji,

If you mean RHINTE00 then I can't really use this program since I'm using HR_INFOTYPE_OPERATION as part of an interface and this program creates a BDC session. I suppose I could submit RHINTE00 and then submit another report to execute the BDC from within the interface, but this would be far from a elegant fix.

Thanks,-tom

[Former Member]

In that Case , use the FM RH_PNNNN_MAINTAIN in the interface to adjust HRP1001 Relationships after the fm hr_infotype_operation

[former_member622817]

Yes, I'm aware that I can update HRP1001 myself but was hoping to avoid having to do this as it can get a bit complicated. I have both terminations and position reassignments to handle. I'll have to take make sure the relationship validity periods are correctly aligned with infotype 0001 as well.

I also tried doing a position change via a CALL TRANSACTION (so basically I coded a BDC to use PA40) and to my surprise I had the same problem! The HRP1001 records were not updated in this case as well.

Cheers,-tom