How To Fix DT873 - Append & was activated with warnings => table & partially active

DT873 - Overview

• Message type: E = Error

• Message class: DT - Table activation (incl. indexes)

• Message number: 873

• Message text: Append & was activated with warnings => table & partially active

What causes this issue?

The <DS:TX.APPEND-STRUKTUR>append</> just created or edited was
activated with warnings by the system. The appending table, on the
other hand, is activated later by the mass activation program.
Therefore, the active version is temporarily given the status partially
active.

System Response

The table comparison is continued taking into account the activated
append.

How to fix this error?

Check whether you need to edit the append as a result of the warnings.
You will not need to do so if a warning is issued simply to inform you
that <DS:TX.DOKU_RADTBFDS_KUNDENFELD>customer fields</> are not in the
customer namespace (message no. DT221).
<LS>On no account should you activate the append yourself!</>
Carry out the adjustment as specified by the system.

Error message extract from SAP system. Copyright SAP SE.

DT873 - Details

• The SAP error message DT873 indicates that an append structure was activated with warnings, and as a result, the associated table is only partially active. This typically occurs when there are issues during the activation of an append structure, which can lead to inconsistencies in the data dictionary.
  
  Cause:
  
  Incompatible Data Types: The fields in the append structure may have incompatible data types with the existing fields in the base table.
  Field Length Issues: The length of the fields in the append structure may exceed the maximum allowed length for the base table.
  Missing Dependencies: There may be dependencies or references that are not properly defined or are missing.
  Existing Data: If there is existing data in the table that conflicts with the new structure being added, it can lead to warnings during activation.
  Database Constraints: Constraints at the database level (like primary keys, foreign keys, etc.) may not be satisfied.
  
  
  Solution:
  
  Check Activation Logs: Review the activation