Message type: E = Error
Message class: DRD - Messages for Delivery Relationships
Message number: 220
Message text: No specific check set for the level (see long text).
You have set a more detailed level than plant (that is to say
<DS:GLOS.3528EA7BE8AA5570E10000009B38F983>material group</> or
<DS:GLOS.3526BF19AFAB52B9E10000009B38F974>material</>) for determining
the receiving <DS:GLOS.3526BF3BAFAB52B9E10000009B38F974>plants</> or
<DS:GLOS.3526C729AFAB52B9E10000009B38F974>customers</>. You have not,
however, activated a check specifically for this level.
If no other check specific to the level set is carried out using an
exit (BAdI), the system will carry out
<DS:GLOS.8F1666FFD6F0DB468B7643C63EECC977>delivery relationship</>
determination unnecessarily often with the same data, which is stored
redundantly in the database.
Example
You set the determination of receiving plants to the level "material"
according to the method "Recipient Determination". You select the
supplying plant check and activate additional checks. As the
<DS:GLOS.3526C111AFAB52B9E10000009B38F974>supplying plant</> check is
only specific for plants and material groups (data retention level for
maintaining the supplying plants), the same check is carried out for
all the materials in a material group, with the same result. This
causes an unnecessarily long runtime and unnecessarily high data volume
in the database.
You should therefore select the level "material group" or "plant" for
this check (if you use the "plant" level, the system does not check
supplying plants at material group level).
However, if you want to use an exit to carry out other checks that are
specific to the material on the receiving plants that were determined
by the supplying plants check, use the level "material".
You can still save the profile as set.
If you do not use a BAdI to carry out a customer-specific check that
justifies the level set, change the level or the scope of the check so
that no redundant checks take place.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
DRD220
- No specific check set for the level (see long text). ?The SAP error message DRD220, which states "No specific check set for the level (see long text)," typically occurs in the context of the Data Retention and Deletion (DRD) process. This error indicates that the system is unable to find a specific check set for the level of data being processed, which can hinder the execution of data retention or deletion tasks.
Cause: Missing Configuration: The most common cause of this error is that the necessary configuration for the check set at the specified level is missing. This could be due to incomplete setup in the Data Retention Management (DRM) configuration. Incorrect Level Specification: The level specified in the process may not correspond to any defined check set in the system. Transport Issues: If the configuration was recently transported from another system, it may not have been fully or correctly transported.
Solution: Check Configuration: Navigate to the Data Retention Management configuration in your SAP system. Ensure that
Get instant SAP help. Sign up for our Free Essentials Plan.
DRD213
Invalid value for method; select a value using input help
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DRD212
Incorrect/missing value for document category to determine receiving &1.
What causes this issue? When you use the method "Documents Available" to determine the receiving &V1&, you must enter a document ty...
DRD221
Neither delivery plant check nor source list check are maintained.
What causes this issue? You must at least set the <DS:GLOS.3526C111AFAB52B9E10000009B38F974>supplying plants</> check or the <DS:GLOS....
DRD222
Invalid value for delivery plant check.
What causes this issue? An invalid value is set for the <DS:GLOS.3526C111AFAB52B9E10000009B38F974>supplying plants</> check. Use valid va...
Click on this link to search all SAP messages.