How To Fix RP785 - Record with key & & appears for select, but not for IMPORT

SAP Error Message - Details

• Message type: E = Error

• Message class: RP - Error Messages for Infotype Module Pools

• Message number: 785

• Message text: Record with key & & appears for select, but not for IMPORT

What causes this issue?

The displayed record was imported from a database table in <LS>cluster
format</> using the ABAP command IMPORT. However, the system has
detected an error and terminated the import. The record now probably
has a corrupt data format. The system cannot interpret the record, and
it therefore cannot be repaired.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Please delete the record from the database table <LS>before production
startup</>. Most HR cluster records can be restored by HR application
programs once the relevant recalculations have been performed.
A database record of this type usually affects only one personnel
number. In critical situations, call the Hotline.
You can use the utilities RPUPxD00 and RPUPxD10 to delete records from
HR cluster databases. The 'x' stands for the number of the PCLx
database (1, 2, 3, or 4).
<LS>Records should only be deleted by an experienced and authorized HR
system administrator. If you have any questions, please call the HR
Hotline.</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RP785 - Record with key & & appears for select, but not for IMPORT ?

  The SAP error message RP785 typically indicates that there is a problem with the data being processed in the context of a payroll operation. Specifically, the message "Record with key & & appears for select, but not for IMPORT" suggests that the system is trying to access a record that exists in the database for selection purposes but cannot find it when attempting to import it into the payroll processing.
  Causes:
  
  Data Inconsistency: The record may exist in the database but is not available for import due to inconsistencies or missing data in related tables.
  Incorrect Configuration: There may be configuration issues in the payroll schema or in the infotype records that prevent the system from importing the necessary data.
  Missing Authorizations: The user executing the payroll run may not have the necessary authorizations to access certain records.
  Timing Issues: The record may have been created or modified after the payroll selection was made, leading to a mismatch.
  
  Solutions:
  
  Check Data Consistency: Verify that the records in the relevant infotypes (e.g., IT0000, IT0001, etc.) are complete and consistent. Ensure that all required fields are filled out correctly.
  Review Payroll Configuration: Check the payroll schema and rules to ensure that they are correctly set up to handle the records in question. Look for any custom logic that might be affecting the import process.
  Authorization Check: Ensure that the user has the necessary authorizations to access the records being processed. This can be done by checking the user roles and authorizations in the SAP system.
  Re-run Payroll Selection: If the issue is related to timing, re-running the payroll selection after ensuring that all records are in place may resolve the issue.
  Debugging: If the problem persists, consider using the SAP debugging tools to trace the execution of the payroll program and identify where the mismatch occurs.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE16 or SE11 to view the relevant database tables and check the records.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide patches or updates.
  Documentation: Review the SAP documentation related to payroll processing and the specific infotypes involved to ensure compliance with best practices.
  
  If the issue continues after trying the above solutions, it may be beneficial to consult with an SAP expert or reach out to SAP support for further assistance.