MM / P2Padvanced

MM Flexible Workflow Part 5: Agent Determination, Deadlines and Troubleshooting

Key takeaway

Make approvals reach the right people on time: agent determination via teams and responsibilities or rules, substitutes, deadlines and escalation, and troubleshooting when tasks disappear, go to no one, or workflows don't start — using workflow logs and admin tools.

Explanation

📌 KEY POINTS
✅ Agents are found by roles/rules (e.g. teams and responsibilities by purchasing group or cost center).
✅ Substitutions keep approvals moving during absence.
✅ Deadlines and escalations notify or reroute overdue tasks.
✅ Troubleshooting: no workflow started, no agent found, task not visible, workflow in error.
⚠️ "Approvals vanished" is usually an agent determination or substitution issue — not data loss.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered granularity. Now agents and troubleshooting.

━━━━━━━━━━━━━━━━━━━━
▶ 1. AGENT DETERMINATION

Teams and responsibilities (function + responsibility definitions).
Rules/BAdIs for special cases.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SUBSTITUTES

My Inbox substitution rules.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DEADLINES

Step deadlines, reminders, escalation to next level.

━━━━━━━━━━━━━━━━━━━━
▶ 4. TROUBLESHOOTING

Workflow status/log on document; admin monitoring; restart after fix.
Event linkage, runtime setup, activation per type.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PREVENTION

Team maintenance process with HR changes; fallback agents.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Maintain teams per purchasing group.
Create a PO; check agent in log.
Remove team member and observe error; fix and restart.

✅ CHECKPOINT: no workflow ends without an agent, and overdue tasks escalate.

Code example

ABAP Code

===== STEP 1: agents =====Manage Teams and Responsibilities: team "PG 001 approvers" → responsibility purchasing group 001 → function approver ===== STEP 2: troubleshooting checklist =====Workflow started? (document workflow status/log) | agent found? | task in My Inbox? (substitution, roles) | workflow error → fix → restart (admin tools, e.g. SWIA per release) ===== STEP 3: deadlines =====Step deadline 3 days → reminder → escalation to manager

Real project scenario

A buyer said PO approvals vanished from a manager's inbox. Logs showed the manager had been removed from the purchasing group team after a reorganization, and no fallback agent existed; tasks went to no one. Adding fallback agents, linking team maintenance to HR changes and a daily "no agent" report fixed it.

Common mistakes

No fallback agents.
Teams not maintained after reorganizations.
No deadlines.
Restarting without fixing cause.
Ignoring workflow logs.

Best practices

Maintain teams with HR changes.
Define fallback agents.
Set deadlines and escalations.
Monitor errors daily.
Document troubleshooting steps.

Interview angle

Questions: "How are approvers determined?", "Approvals disappeared — what do you check?", "How do deadlines work?"
Strong answer: teams and responsibilities, substitutes, deadlines/escalation, troubleshooting via logs and restart, prevention.

Practice this lesson

Quick check

1. PO approvals vanished from a manager's inbox after a reorganization. What is the likely cause?

2. A workflow started, but no approver received the task. What should be checked?

3. In a Flexible Workflow scenario, what determines the actual individuals (agents) who receive the approval task for a given step?

Interview questions

1. During hypercare after go-live, a Flexible Workflow for purchase requisition release is intermittently failing to trigger for requisitions created via MDG-driven mass changes, while manually created requisitions work fine. How would you diagnose and resolve this?

Answer it in your own words first, then compare.

2. Approvals sometimes go to no one or get stuck for days. How do you set up agent determination and deadlines?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.