2711961 - Change before earliest retro. date xx.xx.xxxx acc. to control rec. to py area ##

• The field Earliest MD change (RRDAT) in infotype 0003 is wrongly updated when replicate infotype 0001 data from SF to ERP system.
  For example:
  Original Infotype 0001 record is in 2018.07.01 ~ 9999.12.31, and you change some data on 2018.10.17 SF EC.
  Payroll is already accounted to 2018.10.30.
  After replication to ERP system, the Earliest MD change date is wrongly updated as 2018.07.01(the begin date of original record). It should be 2018.10.17 (the change date in SF).
• Error 'Change before earliest retro. date xx.xx.xxxx acc. to control rec. to py area xx' happens in SLG1 log during replication.
• No EC data is changed in a period, but system detects there is data difference between SF EC and SAP ERP system and tries to replicate the data into SAP ERP.

SAP ERP 6.0
SAP enhancement package 1 for SAP ERP 6.0
SAP enhancement package 2 for SAP ERP 6.0
SAP enhancement package 3 for SAP ERP 6.0
SAP enhancement package 4 for SAP ERP 6.0
SAP enhancement package 5 for SAP ERP 6.0
SAP enhancement package 6 for SAP ERP 6.0
SAP enhancement package 7 for SAP ERP 6.0
SAP enhancement package 8 for SAP ERP 6.0
PA_SE_IN Addon (all releases)

Correction Note 2654487 is missing in SAP ERP system.

This is a known issue in Software Component SAP_HRRXX.

To correct this issue, apply Note 2654487 - Infotype 0001 triggers erroneously the error message RP456 ('Change before earliest retro. date &1 acc. to control rec. to py area &2').

This is also an issue in PA_SE_IN.

Please apply Note 2775750 - IT 0001 is updated although there has been no change

Message No. SFIOM_PROCESSING042, Database could not be updated, SFIOM_PROCESSING240, CL_HRPA_RETROCALC ~ CALCULATE_RETRO_DATES , KBA , LOD-SF-INT-SAP , Please use LOD-EC-INT* , Problem