cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Clarification on Storing Rejection Reasons for Activities

aziz96
Participant

Accepted Solutions (0)

Answers (1)

Answers (1)

MOHAMMED_BASER
Participant

Hello Aziz, Reasons of rejection in Crowd Workforce (SAP Field Service Management) are typically stored within the activity logs or backend database, but their visibility depends on system configuration and role permissions. In SAP Field Service Management’s Crowd Workforce module, when an activity is rejected, the system prompts for a rejection reason. However, where this reason is stored and how it's accessed can vary depending on your setup

You will find the rejection reasons in below areas as explain.

Activity History Logs: Rejection reasons are often recorded in the activity’s audit trail or history log. This allows managers and admins to trace decisions made during the assignment lifecycle.

Backend Database: The reason may be stored in a specific field tied to the activity object in the database. Accessing this typically requires backend or API-level permissions.

Partner Portal or Technician View: Depending on your configuration, crowd partners or technicians may see rejection reasons in their assignment dashboard or notification panel.

Reporting Tools: If your organization uses reporting or analytics tools integrated with SAP FSM, rejection reasons can be extracted and analyzed from those datasets.

Hope the above explanation helps you.

Ask a Question
Top Q&A Solution Author