How To Fix S#070 - Responsibility &1 of type &2 in client &3: Assignments not copied

SAP Error Message - Details

• Message type: E = Error

• Message class: S# -

• Message number: 070

• Message text: Responsibility &1 of type &2 in client &3: Assignments not copied

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 S#070 - Responsibility &1 of type &2 in client &3: Assignments not copied ?

  The SAP error message S#070 indicates that there is an issue with the assignment of responsibilities in a specific client. This error typically arises when there is an attempt to copy or transfer responsibilities (such as roles or authorizations) from one client to another, and the system encounters a problem with the assignments.
  Cause:
  The error message "Responsibility &1 of type &2 in client &3: Assignments not copied" can be caused by several factors, including:
  
  Missing Authorizations: The user attempting to perform the copy operation may not have the necessary authorizations to copy the responsibilities.
  Inconsistent Data: There may be inconsistencies in the data related to the responsibilities being copied, such as missing or invalid entries.
  Client-Specific Settings: The target client may have specific settings or configurations that prevent the copying of certain responsibilities.
  Transport Issues: If the responsibilities are being transported from one client to another, there may be issues with the transport request or the transport directory.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the copy operation. You may need to consult with your SAP security team to verify this.
  
  
  Review Data Consistency: Check the data related to the responsibilities being copied. Ensure that all necessary entries exist and are valid in both the source and target clients.
  
  
  Client Settings: Review the settings of the target client to ensure that there are no restrictions or configurations that would prevent the copying of responsibilities.
  
  
  Transport Request: If the issue is related to a transport request, check the transport logs for any errors or warnings. You may need to re-import the transport request or resolve any issues identified in the logs.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
  
  
  Consult Documentation: Review the SAP documentation related to the specific transaction or process you are using to copy responsibilities. There may be additional steps or considerations outlined in the documentation.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PFCG (Profile Generator) for managing roles and authorizations.
  SAP Support: If the issue persists, consider reaching out to SAP Support for further assistance, providing them with the error message details and any relevant logs or screenshots.
  Testing in Development: If possible, replicate the issue in a development or test environment to troubleshoot without affecting production data.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.