How To Fix RJ117 - Was not able to delete InfoSource & successfully

RJ117 - Overview

• Message type: E = Error

• Message class: RJ - BW Extractor Handling Message Class

• Message number: 117

• Message text: Was not able to delete InfoSource & successfully

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RJ117 - Was not able to delete InfoSource & successfully ?

  The SAP error message RJ117 indicates that the system was unable to delete an InfoSource successfully. This can occur for various reasons, and understanding the cause is essential for resolving the issue. Here are some common causes, potential solutions, and related information:
  Causes:
  
  Dependencies: The InfoSource may have dependencies, such as being used in existing data flows, transformations, or other objects in the SAP BW system.
  Data Locks: There may be data locks on the InfoSource, preventing its deletion.
  Authorization Issues: The user attempting to delete the InfoSource may not have the necessary authorizations to perform this action.
  Technical Issues: There could be technical issues or inconsistencies in the system that prevent the deletion.
  
  Solutions:
  
  
  Check Dependencies:
  
  Review the InfoSource to see if it is being used in any data flows, transformations, or other objects. If it is, you will need to remove those dependencies before attempting to delete the InfoSource again.
  
  
  
  Release Data Locks:
  
  Ensure that there are no