SAP ABAP Message Class SO Message Number 570 (Note: Before maintaining this table, please refer to the description)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
     ⤷ SO (Package) SAPoffice

Attribute

Message class	SO
Short Description	SAPoffice: message texts
Message Number	570
Documentation status		Space: object requires documentation
Authorization check Error Message	☐
Changed On	20130531

Message Text

Note: Before maintaining this table, please refer to the description

Help Document

Diagnosis

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.

• 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

Procedure

History

Last changed on/by	20130531	SAP
SAP Release Created in