How To Fix SO570 - Read the long text before editing the table

SO570 - Overview

• Message type: E = Error

• Message class: SO - SAPoffice: message texts

• Message number: 570

• Message text: Read the long text before editing the table

What causes this issue?

Many errors can occur in the maintenance of this table. Please note
the following points:
New tables must have the exact same structure with the same field
names as in SOC3.
The database has to be informed of the new tables.
The first two points are important as a check is only made for the
existence of the new tables. No comparison is made between SOC3 and the
new tables. The system also does not test to see if the new tables
exist in the database.

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

It may be a good idea to move all PC documents to another database
table. PC documents have the type EXT.
A conversion is necessary when specifying years. You can only enter a
two-digit number, beginning with 00 for the year 1975. This means the
value 21 has to be specified for the year 1996. Only values in the
future may be used. This is checked along with the area.
The number area in which the new table should be included must lie in
the future if the same year is referred to. It can begin with a 0 for
a new year. You can check the current status of numbers for each
document type with transaction SNRO. You simply enter SO_OBJ_<xxx>,
where <xxx> stands for the document type, and call the range display.
Please note that only future areas can be entered. Existing dates
cannot be adopted in a new file.

System Response

How to fix this error?

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SO570 - Read the long text before editing the table ?

  The SAP error message SO570 ("Read the long text before editing the table") typically occurs when a user attempts to edit a table or a configuration setting in SAP without first reviewing the associated long text documentation. This long text often contains important information, guidelines, or warnings that are crucial for making informed changes.
  
  Cause:
  
  Lack of Documentation Review: The primary cause of this error is that the user has not read the long text associated with the table or configuration they are trying to edit. This long text usually contains critical information about the implications of the changes.
  System Configuration: The system is configured to enforce this check to prevent unintentional errors or misconfigurations that could arise from editing without understanding the context.
  
  
  Solution:
  
  
  Read the Long Text: The immediate solution is to read the long text associated with the table or configuration. You can usually access this by:
  
  Navigating to the relevant transaction or