After migrating to SAP S/4HANA 2020 cloud edition, purchase order approval workflows are stuck in the Fiori My Inbox app. PO approvals show up in the inbox but clicking them displays ‘Workitem cannot be executed - Agent determination failed’. The workflow was working perfectly in our on-premise 1909 system. Transaction SWDD shows the workflow definition is active and agents are assigned in SWFVISU. When I check SWI1, the workitems have status ‘Ready’ but no processor assigned. Is there a specific agent determination configuration needed for Fiori My Inbox in cloud deployments that differs from the classic SAP GUI workflow inbox?
This sounds like a Fiori launchpad role assignment issue rather than workflow configuration. In Fiori My Inbox, users need specific catalog assignments to execute workitems. Check that your approvers have the SAP_FIORI_MY_INBOX catalog assigned in transaction PFCG. Also verify the Fiori app tile is properly configured with the correct semantic object and action. Sometimes the workitem type mapping to Fiori app is missing after migration. Check table SWF_FLA_APP for your PO approval task mapping.
In cloud migrations, I’ve seen agent determination fail when the user master data format changed. Check transaction SU01 for your approvers - ensure the ‘User ID’ format matches what the workflow expects. Cloud editions sometimes enforce different user ID patterns (like I-numbers or P-numbers). Also verify in SWDD that your agent determination uses the correct user reference field. If your workflow uses employee number for agent lookup, ensure those are maintained in cloud user records.
The empty ‘Actual Agent’ in SWI1 is the key symptom. This typically happens when the workflow container elements aren’t properly populated for agent determination. In SWDD, check your task definition - specifically the ‘Agents’ tab. If you’re using rule resolution (AC container element), verify that the rule is being evaluated correctly. Run transaction SWF_RULE_SIMULATION with your PO number to test rule evaluation. Also check the workflow log in SLG1 with object ‘SWF’ - it should show why agent determination is failing.
Running SWF_RULE_SIMULATION revealed the issue! The rule evaluation returns the correct users but with a warning ‘User assignment to position incomplete’. Checking PPOME, I can see the users are assigned to positions, but the relationship dates might be wrong. In our on-premise system, we had open-ended position assignments (no end date). Could cloud edition require specific validity periods for org assignments to work with workflow agent determination?