How To Fix RESCSU070 - SC key &1 is for directly posted costs: data exchange not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: RESCSU - Error Texts for Settlement Unit

• Message number: 070

• Message text: SC key &1 is for directly posted costs: data exchange not possible

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 RESCSU070 - SC key &1 is for directly posted costs: data exchange not possible ?

  The SAP error message RESCSU070 indicates that there is an issue with the cost object (in this case, a cost center or internal order) that is being used for a transaction. The specific message states that the SC (subcontracting) key is for directly posted costs, and therefore, data exchange is not possible. This typically occurs in the context of controlling (CO) and project systems (PS) when trying to transfer costs or perform postings that are not compatible with the settings of the cost object.
  Cause:
  
  Direct Posting Configuration: The cost object (e.g., cost center, internal order) is configured for direct postings, which means it cannot accept certain types of data exchanges or postings that are typically used for indirect costs.
  Incorrect Cost Element: The cost element being used may not be compatible with the type of posting you are trying to perform.
  Transaction Type: The transaction type being used may not be allowed for the specific cost object configuration.
  Master Data Issues: There may be issues with the master data of the cost object, such as missing or incorrect settings.
  
  Solution:
  
  Check Cost Object Configuration: Review the configuration of the cost object to ensure it is set up correctly for the type of postings you are trying to perform. If it is meant to handle indirect costs, consider changing its configuration.
  Review Cost Element: Ensure that the cost element being used is appropriate for the type of posting. If necessary, change the cost element to one that is compatible with the transaction.
  Transaction Type Validation: Verify that the transaction type you are using is allowed for the cost object. If not, you may need to use a different transaction type or adjust the configuration.
  Master Data Review: Check the master data for the cost object to ensure all necessary fields are filled out correctly and that there are no inconsistencies.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the error message and the configuration of cost objects.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to cost object configuration, such as KS01 (Create Cost Center), KO01 (Create Internal Order), and OKB9 (Define Cost Elements).
  User Authorization: Ensure that you have the necessary authorizations to perform the actions you are attempting, as lack of permissions can sometimes lead to errors.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in controlling and project systems.