How To Fix 5A718 - Table PLOG must no longer be used for infotype &

5A718 - Overview

• Message type: E = Error

• Message class: 5A - Basis Personnel Management

• Message number: 718

• Message text: Table PLOG must no longer be used for infotype &

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

5A718 - Details

• The SAP error message 5A718, which states "Table PLOG must no longer be used for infotype &," typically occurs in the context of SAP HR (Human Resources) when there is an attempt to access or manipulate data in the PLOG table for a specific infotype. This error indicates that the PLOG table is deprecated for the specified infotype, and the system is enforcing this restriction.
  
  Cause:
  
  Deprecated Table: The PLOG table is no longer supported for the specific infotype you are trying to access. This could be due to changes in the data model or the introduction of new tables or structures that should be used instead.
  Custom Code: If there is custom ABAP code or enhancements that reference the PLOG table for the infotype, it may trigger this error.
  
  Configuration Issues: Incorrect configuration or settings in the HR module may lead to attempts to access deprecated tables.
  
  
  Solution:
  
  Identify the Infotype: Determine which infotype is