ALE ISSUE HRMD_A

[Former Member]

HI Experts,

We have a issue where we are sending the data from one HR system to another HR system using ALE message type HRMD_A07. So in sending system if we create a record which has a validity date of 01/01/2011 to 12/31/9999. The change pointers take that record and update it in the receiving system which is fine but instead of delimiting the record on the receiving end it inserts the record. So in the receiving end we have two records with 12/31/9999 end dates which we dont want.

Is there a BAPI or Setting in the t77s0 table which will prevent this from happening and instead of directly updating the table it delimits the old record and create a new one. Any help would be much appreciated. Thanks

[Former Member]

HI Experts,

We have a issue where we are sending the data from one HR system to another HR system using ALE message type HRMD_A07. So in sending system if we create a record which has a validity date of 01/01/2011 to 12/31/9999. The change pointers take that record and update it in the receiving system which is fine but instead of delimiting the record on the receiving end it inserts the record. So in the receiving end we have two records with 12/31/9999 end dates which we dont want.

Is there a BAPI or Setting in the t77s0 table which will prevent this from happening and instead of directly updating the table it delimits the old record and create a new one. Any help would be much appreciated. Thanks

[gokul_radhakrishnan3]

Check whether there is any indicator flag or something is there in the IDOC. something like E1PLOGI-OPERA flag.

Regards,

Gokul

[Former Member]

Hi Gokul,

I checked the IDOC there is no such indicator, the only indicator is opera which is set to U. Which is the update.

Any other thoughts. ?

[Former Member]

Hi,

I guess this is due to your destination infotype time constraints... Have you check this? What infotype is it? a standard one or a custom?

Kr,

Manu.

[Former Member]

Its a standard one Infotype 7.

[SuhaSaha]

Hello Hasan,

Last year we had faced the same problem As per our investigation std. HRMD i/b idoc processing doesn't provide data delimition.(We were using an ECC6.0 system)

If you check the i/b processing FM IDOC_INPUT_HRMD, there is a BAdI HRALE00INBOUND_IDOC. You can use the method PROCESS_IDOC( ) for user-defined IDoc processing.

Inside the method you can call an FM (for e.g., HR_INFOTYPE_OPERATION ) which can delimit the infotype.

BR,

Suhas

PS: Alternatively you can use the function-exit 'EXIT_SAPLRHA0_003'.

[Former Member]

Check SAP Note 134085