3798123 - Error G00056 when saving task group in Define Task Group - SD1 last task S1180 cannot have successor tasks

Symptom

When creating or saving a task group in configuration activity Define Task Group (104737), the system raises error G00056:

"Task group SD1: The last task S1180 cannot have successor tasks"

The long text may identify task S1010 as a successor task. The following warnings may also be displayed:

"Task group SD1 cannot contain both data tasks and consolidation tasks"

The error can prevent a newly created customer task group from being saved even when the new task group itself is not SD1.

Additionally, when opening Define Reclassification Tasks, the message "Fill out all required entry fields" may occur if mandatory fields such as Short Text are missing for existing reclassification tasks.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

Open configuration activity Define Task Group (104737).
Create or modify a task group.
Save the configuration.
Error G00056 is raised for task group SD1:
"The last task S1180 cannot have successor tasks."
The system may identify S1010 as a successor and may also report that SD1 contains both data and consolidation tasks.

Cause

Reclassification task S1010 Sign Based Reclassification, which is used in the Data Monitor task group SD1, is assigned to a document type with posting level 30.

For example, document type 3X has posting level 30.

Posting level 30 is intended for group-dependent consolidation entries. Therefore, assigning such a document type to S1010 causes the task to be treated as consolidation-level processing although S1010 is included in a Data Monitor task group.

This creates an inconsistent task group configuration and can lead to error G00056 and the warning that the task group contains both data tasks and consolidation tasks.

Posting level 10, in contrast, is intended for standardizing entries at consolidation-unit level and is suitable for Data Monitor reclassification processing.

SAP-delivered document types 1D and 1F are examples of posting level 10 document types intended for automatic sign-based reclassification.

Resolution

Open Define Reclassification Tasks.
Select reclassification task S1010 Sign Based Reclassification.
Open Assign Method, Document Type.
Check the document type assigned to S1010.
If the assigned document type uses posting level 30, replace it with an appropriate posting level 10 document type suitable for the intended sign-based reclassification process.
Do not change the posting level of an existing posting level 30 document type solely to resolve this issue.
Save the configuration.
Retry creating or saving the required Data Monitor or Consolidation Monitor task group.

If Define Reclassification Tasks raises "Fill out all required entry fields", review the existing reclassification tasks and complete any missing mandatory fields, such as Short Text, before saving.

After correcting the S1010 document type assignment to an appropriate posting level 10 document type, the task group configuration can be saved successfully and error G00056 no longer occurs.

Additional Information:

SAP defines posting level 10 for standardizing entries that adjust local reported data from the perspective of the group close. These entries are commonly created through reclassifications.

Posting level 30 is defined for consolidation entries that are explicitly dependent on consolidation groups.

SAP-delivered document type 3X is a posting level 30 document type used for group-dependent consolidation processing, specifically for the method-change divestiture scenario.

Keywords

group reporting, data monitor, task group sd1, s1180, last task cannot have successor tasks, g00056, s1010, reclassification, document type, posting level 30, posting level 10, sign based rcl, sscui 104737, save error, consistency check , KBA , FIN-CS-COR-DT-2CL , Data Transfer (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions