How To Fix /ACCGO/CCK_SNP035 - Signature relevancy not set for the selected records,no signature allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CCK_SNP -

• Message number: 035

• Message text: Signature relevancy not set for the selected records,no signature allowed

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 /ACCGO/CCK_SNP035 - Signature relevancy not set for the selected records,no signature allowed ?

  The SAP error message /ACCGO/CCK_SNP035 Signature relevancy not set for the selected records, no signature allowed typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with cost center accounting or internal orders. This error indicates that the system has identified that the selected records do not have the necessary signature relevancy set, which is required for certain operations.
  Cause:
  
  Missing Signature Relevancy: The records you are trying to process do not have the signature relevancy defined. This means that the system does not recognize them as eligible for signature approval.
  Configuration Issues: There may be a configuration issue in the system where the signature relevancy settings have not been properly defined for the relevant cost centers, internal orders, or other objects.
  Data Entry Errors: The records may have been incorrectly entered or may not meet the criteria for signature relevancy.
  
  Solution:
  
  
  Check Signature Relevancy Settings:
  
  Navigate to the configuration settings for signature relevancy in your SAP system. This is usually found in the Controlling (CO) module settings.
  Ensure that the relevant cost centers or internal orders have the signature relevancy set correctly.
  
  
  
  Update Records:
  
  If the records are missing the signature relevancy, you may need to update them to include the necessary settings. This can often be done through transaction codes like KS01 (Create Cost Center) or KO01 (Create Internal Order), depending on the context.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to signature relevancy to understand the specific requirements and settings needed for your organization.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue through configuration changes, consider reaching out to SAP support for assistance. They can provide guidance based on your specific system setup.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KS02 (Change Cost Center), KO02 (Change Internal Order), and KSB1 (Cost Centers: Actual Line Items) to manage and review the records.
  Authorization: Ensure that you have the necessary authorizations to make changes to the configuration settings or to the records in question.
  Testing: After making changes, perform tests to ensure that the error does not reoccur and that the records can be processed as intended.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.