Employee Data Replication issues

Error:

1)Pers.number already flagged for xx/xx/xxxx

• Position assignment in PA and OM are different and the object is flagged for master data integration. Called as open processes
• To Check , navigate to table T77INT , give the Employee Number number , you should get an entry for that PERNR  in T77INT and a  error message for same person in RHINTECHECK report.
• To resolve the error run the RHINTE* reports

2) Prebooking exists for personnel number

This error is coming from the activation of switch PLOGI EVENB and PLOGI EVEGC. here is the functionality Setting the 'PLOGI EVENB' switch to 'X' enables you to move a person, position or organizational unit within an organizational structure, when these changes lead to a change in company code for the person(s) concerned.

The personnel numbers of the persons concerned are locked in PA. The only personnel action you can now carry out these personnel numbers is Organizational change. You must carry out this action before you can make further changes to the Infotypes for the persons concerned .

Technically the lock what we are getting was caused by entry in the table T77INT.

 .

Workaround : Run the program RPLEVENT to create the action what it demands.

SuccessFactors - Payslip Issue  

- Suresh Kalimahanthi's NOTEs

Symptom

-> Customer is using Standard EC Payroll Pre-packaged Content for Employee Replication.

-> Login to SFSF Instance and navigate to Employee Files -> Payroll Information -> Pay Statement.

-> Now while trying to view their Pay Statement in Successfactors, employees are receiving an error message that says-

There’s a problem with the Employee ID. Check if the employee information was added to the system & try again. If it continues, please contact your Admin.

-> Employee access has already been verified and the employee has all the necessary roles and privileges in order to access the system, and so the issue is not with permissioning.

-> Also checked that the data for this employee was successfully replicated to the SAP ERP System from SFSF via the Standard Employee Replication Content delivered by SAP.

-> And also verified that there is an entry correctly maintained in the key mapping table PAOCFEC_EEKEYMAP. (If not, this can be a potential root cause for the erro

Cause

Go to transaction SFW5 and search for business function 'HCM_SFEC_MDEC2HR' and verify that this business function should not be activated, which in this case is the reason for the error.

Resolution

-> The function HCM_SFEC_MDEC2HR decides what mapping table for the employee is used to access the payslip.

-> If it is activated then the mapping table HRSFEC_D_EEKEYMP of the EA-HR-XX codeline is used for the employee. And if it is deactivated then the table PAOCFEC_EEKEY_MAP of the AddOn is used.

-> So in case you are using the AddOn implementation, you need to check that what was the reason for which this function was activated?

->Because to ensure that the correct mapping table is used for the payslip it needs to be deactivated.

-> And so in order to resolve this issue, if there is no specific reason why it was activated, you can directly go and change the settings for this in your system.

OSS NOTE:  2224933 - Unable to access/view the Pay Statement in Successfactors System