How To Fix SIG504 - Indirect predecessors added

SAP Error Message - Details

• Message type: E = Error

• Message class: SIG - Digital Signature

• Message number: 504

• Message text: Indirect predecessors added

What causes this issue?

When defining the signature sequence, you marked the direct
predecessors of each individual signature.

System Response

To correctly check signature strategies for loops, the system
automatically adds the indirect predecessors of each signature, which
means that it marks all signatures that are executed before a signature
some time during the course of the signature process.
<ZH>Example</>
You define the following signature sequence:
,, ,,Predecessor signatures
,,<ZH>Signat.to be executed</> ,,<ZH>S1</> ,,<ZH>S2</> ,,<ZH>S3</>
,,<ZH>S4</>
,, <ZH>S1</>
,, <ZH>S2</>,,X
,, <ZH>S3</>,,X
,, <ZH>S4</>,, ,, ,,X
The system adds the indirect predecessors. Therefore, the sequence
matrix looks as follows:
,, ,,Predecessor signatures
,,<ZH>Signat.to be executed</> ,,<ZH>S1</> ,,<ZH>S2</> ,,<ZH>S3</>
,,<ZH>S4</>
,, <ZH>S1</>
,, <ZH>S2</>,,X
,, <ZH>S3</>,,X
,, <ZH>S4</>,,X ,, ,,X

How to fix this error?

When you acces the sequence matrix once again and change it, you must
also correct the indirect predecessors.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SIG504 - Indirect predecessors added ?

  The SAP error message SIG504, which states "Indirect predecessors added," typically occurs in the context of project management within SAP, particularly when dealing with network planning and scheduling. This message indicates that there are indirect dependencies or relationships between tasks in a project that have been automatically added by the system.
  
  Cause:
  The error is usually triggered when:
  
  Task Dependencies: You have defined tasks in such a way that they have indirect dependencies. For example, if Task A is dependent on Task B, and Task B is dependent on Task C, then Task A indirectly depends on Task C.
  Scheduling Conflicts: The system may automatically add these indirect predecessors to ensure that the scheduling logic is maintained, which can lead to conflicts or unexpected behavior in the project timeline.
  Changes in Task Relationships: If you modify the relationships between tasks (e.g., changing start or finish dates), the system may add indirect predecessors to maintain the