How To Fix RSM368 - Discrepancy - This InfoPackage has been deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 368

• Message text: Discrepancy - This InfoPackage has been deleted

What causes this issue?

This InfoPackage no longer exists.
It was deleted but the blank entry in the hierarchy list still exists.

How to fix this error?

Remove the Package from the group.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM368 - Discrepancy - This InfoPackage has been deleted ?

  The SAP error message RSM368 indicates that there is a discrepancy because the InfoPackage you are trying to use has been deleted. This typically occurs in the context of data extraction processes in SAP BW (Business Warehouse) when the system cannot find the InfoPackage that is referenced in a process chain or a data load request.
  Cause:
  
  Deletion of InfoPackage: The most common cause is that the InfoPackage has been deleted from the system, either intentionally or accidentally.
  Transport Issues: If the InfoPackage was transported from one system to another (e.g., from development to production), it may not have been included in the transport request.
  System Migration: If there has been a system migration or upgrade, some objects may not have been migrated correctly.
  Data Load Request: The data load request may still reference the deleted InfoPackage, leading to this error.
  
  Solution:
  
  Recreate the InfoPackage: If the InfoPackage was deleted, you can recreate it with the same settings as before. This can be done by going to the Data Warehousing Workbench and creating a new InfoPackage for the relevant data source.
  Check Process Chains: If the InfoPackage is referenced in a process chain, you may need to update the process chain to remove or replace the reference to the deleted InfoPackage.
  Review Transport Requests: If the InfoPackage was supposed to be transported, check the transport requests to ensure that it was included. If not, you may need to create a new transport request that includes the InfoPackage.
  Check for Dependencies: Ensure that there are no other dependencies or objects that rely on the deleted InfoPackage. You may need to adjust those as well.
  Consult Logs: Review the logs for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to manage InfoPackages and process chains.
  Documentation: Refer to SAP Help documentation for detailed steps on creating and managing InfoPackages.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to resolve the RSM368 error and restore the functionality of your data extraction processes.