How To Fix KR335 - Object number set &1 contains the object type &2 (instead of &3)

KR335 - Overview

• Message type: E = Error

• Message class: KR - Archiving Reports and Utilities

• Message number: 335

• Message text: Object number set &1 contains the object type &2 (instead of &3)

What causes this issue?

You entered <DS:GLOS.3552CF13CEA7323BE10000009B38F984>object type
</> &V3& to be archived. To limit the line items to be archived you
entered the general object number set &V1&. This object number set,
however, contains at least one object number with object type &V2&.

System Response

During the selection the system ignores all the lines in the set where
the object type differs from the object type &V3& entered on the
selection screen.

How to fix this error?

If possible, you should avoid using a general object number set. For
further information on the input possibilities, see the F1 help for
field <DS:DE.COOM_ARC_SETNAME>"Group or set"</>.
Enter object number sets that contain only those entries that match the
chosen object type. Note that the line items for some object types are
archived with other object types. This applies to the object types NWA
(network activity), ORI (order item) and ATY (activity type). Objects
of these object types are archived automatically with the superior
objects of object types NWK (network), ORD (order) or CTR (cost
center).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KR335 - Object number set &1 contains the object type &2 (instead of &3) ?

  The SAP error message KR335 indicates that there is a mismatch between the expected object type and the actual object type found in the specified object number set. Specifically, the message states that the object number set contains an object type that is not what was expected.
  
  Cause:
  The error typically arises in the context of controlling (CO) or financial accounting (FI) modules when the system is trying to process a transaction or report that involves object numbers (like cost centers, internal orders, etc.). The mismatch can occur due to several reasons:
  
  Incorrect Object Type: The object number set may have been defined or populated incorrectly, leading to the presence of an unexpected object type.
  
  Configuration Issues: There may be configuration settings in the system that are not aligned with the expected object types for the transaction being processed.
  Data Integrity Issues: There could be data integrity issues where the object numbers have been incorrectly