How To Fix KR312 - No sub-object types to be archived were found


SAP Error Message - Details

  • Message type: E = Error

  • Message class: KR - Archiving Reports and Utilities

  • Message number: 312

  • Message text: No sub-object types to be archived were found

  • Show details Hide details
  • What causes this issue?

    You have entered sub-object types. There are indeed sub-object types
    that are suitable for your selection, but none that are to be archived
    according to Customizing.

    System Response

    The system rejects the entry since nothing would be archived anyway.

    How to fix this error?

    Check your entries. If need be, select the sub-object types using F4.
    If you want to archive line items for all sub-object types, leave the
    sub-object type empty.
    Check the settings for CO line item archiving. In case of doubt, an
    entry should exist in Customizing for each sub-object type. If no entry
    exists, the entry with the empty sub-object type is used if it exists.
    If this entry does not exist, no line item is archived for this
    sub-object type.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message KR312 - No sub-object types to be archived were found ?

    The SAP error message KR312 ("No sub-object types to be archived were found") typically occurs during the archiving process in SAP, particularly when dealing with controlling (CO) objects. This message indicates that the archiving program did not find any sub-object types that meet the criteria for archiving.

    Causes:

    1. No Data Available: There may simply be no data available for the specified sub-object types that can be archived. This could be due to the data already being archived or there being no data that meets the archiving criteria.

    2. Incorrect Selection Criteria: The selection criteria defined for the archiving run may not match any existing data. This could include date ranges, object types, or other filters that are too restrictive.

    3. Archiving Object Configuration: The archiving object may not be properly configured, or the necessary settings for the sub-object types may not be defined in the system.

    4. Authorization Issues: The user executing the archiving process may not have the necessary authorizations to access the data that is supposed to be archived.

    Solutions:

    1. Check Data Availability: Verify if there are any records available for archiving. You can do this by checking the relevant tables or using transaction codes that display the data.

    2. Review Selection Criteria: Reassess the selection criteria used in the archiving run. Ensure that the criteria are broad enough to include records that can be archived.

    3. Configuration Review: Check the configuration of the archiving object in transaction SARA. Ensure that the sub-object types are correctly defined and that the archiving settings are appropriate.

    4. Authorization Check: Ensure that the user has the necessary authorizations to perform the archiving. This can be checked in transaction SU53 or by consulting with your security team.

    5. Consult Documentation: Review the SAP documentation related to the specific archiving object you are working with. This can provide insights into the expected configuration and usage.

    6. Run Archiving Object Test: Use the test functionality in transaction SARA to simulate the archiving process without actually archiving data. This can help identify issues without affecting the database.

    Related Information:

    • Transaction Codes:

      • SARA: For archiving administration.
      • SARI: For archiving information.
      • SE11: To check the data model and tables related to the archiving object.
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues or bugs related to the archiving process for your version of SAP.

    • SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.

    By following these steps, you should be able to diagnose and resolve the KR312 error message effectively.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker