How To Fix G00070 - A few CGs were not processed: preceding task &1 is not blocked

G00070 - Overview

• Message type: E = Error

• Message class: G00 - SAP Consolidation

• Message number: 070

• Message text: A few CGs were not processed: preceding task &1 is not blocked

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 G00070 - A few CGs were not processed: preceding task &1 is not blocked ?

  The SAP error message G00070, which states "A few CGs were not processed: preceding task &1 is not blocked," typically occurs in the context of the SAP system's processing of change requests or tasks in a workflow. This error indicates that certain change requests (CGs) could not be processed because the preceding task is not in a blocked state, which is necessary for the current task to proceed.
  
  Cause:
  
  Workflow State: The preceding task in the workflow may not be in a state that allows the current task to proceed. This could be due to the task being completed, canceled, or not yet started.
  Task Dependencies: There may be dependencies between tasks that are not being met. If a task that needs to be completed before the current task is not completed, it can lead to this error.
  
  Configuration Issues: There may be issues with the configuration of the workflow or the change request