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

SAP Error Message - Details

• 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 assigned or modified.
  User Error: The user may have selected the wrong object type or number in the transaction.
  
  Solution:
  To resolve the KR335 error, you can take the following steps:
  
  Check Object Number Set: Verify the object number set specified in the error message. Ensure that it contains the correct object types as expected by the transaction.
  Review Configuration: Check the configuration settings related to the object types in the controlling or financial accounting modules. Ensure that they are set up correctly.
  Data Validation: Validate the data associated with the object numbers. Ensure that the object numbers are correctly assigned and that there are no inconsistencies.
  Transaction Review: Review the transaction or report that triggered the error. Ensure that the correct object type is being used and that it aligns with the expected input for the transaction.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to the object types and their expected configurations.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may want to check transaction codes related to cost accounting (e.g., KSB1, KOB1) or financial accounting (e.g., FB50, FBL1N).
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the KR335 error and implement a suitable solution.