How To Fix 5G217 - Entries in the old NI Data Take-on table not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: 5G - HR: Messages for Britain

• Message number: 217

• Message text: Entries in the old NI Data Take-on table not allowed

What causes this issue?

The NI Data Take-on table T5G_NIDTO has been replaced by table
T5G_DTONI.

System Response

It is no longer possible to maintain table T5G_NIDTO with the view
maintenance transactions /SM30 or /SM31. However, it may be the case
that there are still entries in the table that were entered before the
table was replaced.
NI Adjustments
In payroll, only entries in the new table T5G_DTONI will be considered
by the payroll function <LS>National Insurance Great Britain User
Adjustments</> (GBNIA) for NI adjustments. To make sure that all data
is considered, any entries for the current personnel number in the
current period in the old table T5G_NIDTO lead to a rejection in
payroll.
NI Data Take-on (Schema GLK0)
Data Take-on for the National Insurance tables can only be carried out
using the new NI data take on table T5G_DTONI.

How to fix this error?

Run the report <LS>Migration report for NI Data Take-on table</>
(RPUMNIG0), which moves all existing entries from the table T5G_NIDTO
to T5G_DTONI.
Re-run payroll for those employees affected.

Procedure for System Administrators

See also the Note 528186 for additional information.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5G217 - Entries in the old NI Data Take-on table not allowed ?

  The SAP error message 5G217, which states "Entries in the old NI Data Take-on table not allowed," typically occurs in the context of the National Insurance (NI) data take-on process in the SAP system. This error indicates that there are entries in the old NI Data Take-on table that are not permitted, likely due to a configuration or data integrity issue.
  Cause:
  
  Data Integrity Issues: The error may arise if there are inconsistencies or invalid entries in the NI Data Take-on table. This could be due to incorrect data being entered or legacy data that is no longer valid.
  Configuration Settings: The system may be configured to prevent the use of old data entries, especially if the data has been migrated or if there are new rules governing how NI data should be handled.
  Versioning Issues: If the system has been upgraded or if there are changes in the NI data handling processes, older entries may not be compatible with the current system requirements.
  
  Solution:
  
  Data Review: Review the entries in the NI Data Take-on table to identify any outdated or incorrect records. This may involve checking for duplicates, invalid formats, or entries that do not meet current criteria.
  Data Cleanup: If invalid entries are found, they should be corrected or removed. This may involve working with your data management team to ensure that the data is accurate and compliant with current regulations.
  Configuration Check: Verify the configuration settings related to the NI Data Take-on process. Ensure that the system is set up correctly to handle the data as intended.
  Consult Documentation: Refer to SAP documentation or support notes related to the NI Data Take-on process for any specific guidelines or updates that may address this error.
  SAP Support: If the issue persists after reviewing and cleaning the data, consider reaching out to SAP support for further assistance. They may provide insights or patches that can resolve the issue.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on handling NI data take-on issues.
  Transaction Codes: Familiarize yourself with transaction codes related to NI data management, such as those used for data entry, reporting, and configuration.
  User Roles: Ensure that users have the appropriate roles and permissions to access and modify the NI Data Take-on table, as restrictions may also lead to errors.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.