Symptom
- Business wants to prevent employees from submitting a case in the Self-Service portal unless a specific document is attached.
- When an employee submits a case via Self-Service without attaching the required document, the case is created successfully with no validation error or submission block.
- No system message or enforcement mechanism prevents case creation when the required attachment is absent.
- Example 1: A "Change of Name" case type should only be created if the employee attaches proof of the new name document.
- Example 2: A "Jury Service" case type should only be created if the employee attaches a court letter.
Environment
- SAP Service Cloud Version 2
- SAP Enterprise Service Management
Reproducing the Issue
- Navigate to the Self-Service portal.
- Select a case type that is enabled with the Self-Service toggle (for example, "Change of Name" or "Jury Service").
- Complete the mandatory fields: Subject, Type, and Account.
- Do not attach any document.
- Click Submit.
- Observe that the case is created successfully with no error, warning, or submission block related to the missing attachment.
Cause
- SAP Enterprise Service Management (ESM) does not include a standard configuration option to enforce mandatory file attachment as a precondition for case submission in the Self-Service portal.
- The native required fields for case creation are Subject, Type, and Account only.
- Attachments are treated as optional in all documented Self-Service case creation flows.
Resolution
- There is currently no standard ESM configuration that blocks Self-Service case submission when a required file attachment is absent.
- The Forms feature provides the closest available enforcement mechanism via required form fields.
- For case types where a mandatory document is non-negotiable, the recommended best practice is to direct employees to the Self-Service portal rather than the email channel, where Forms-based enforcement can be applied.
- Four options are available, each addressing a different aspect of the requirement. .
- Option 1 — Use ESM Forms with a Required Acknowledgement Field
- ESM Forms allow administrators to create custom data entry forms per case type with conditional field enforcement.
- You can use a required checkbox or text field as a submission control that prompts the employee to confirm the document has been attached.
- Navigate to Settings → Cases → Case Types.
- Select the relevant case type (for example, "Change of Name").
- Confirm the case type has the Self-Service toggle enabled.
- Navigate to Settings → Forms and create a new form version for the case type.
- Add a required checkbox field with a label such as: "I confirm I have attached the required proof of name change document. Cases submitted without this document will not be processed."
- Set the field condition to Required so the employee cannot submit without checking it.
- Associate the form version with the case type.
- Repeat for each case type that requires a specific supporting document.
- Refer to KBA 3744700 - Case Subject Can Be Cleared After Creation Even When The Subject Is Mandatory
- Important limitation:
- This option creates a required acknowledgement control but does not technically enforce the presence of a file in the attachment upload area.
- An employee could select the checkbox without uploading a file.
- Agent-side validation (see below) is still required as a secondary control
- Option 2 — Configure Named Attachment Types per Case Type
- You can define specific attachment types and assign them to a case type. This makes the expected document type visible to the employee in the attachment area during Self-Service case creation and supports downstream agent processing.
- Navigate to your user profile menu → Settings.
- Under Cases, navigate to Attachment Types.
- Create the required attachment types (for example, Proof of Name Change, Court Letter).
- From Attachment Types, navigate to Attachment Types Assignment.
- In the Business Services section, search for Case.
- Select the desired types and click Save.
- For full configuration steps, refer to KBA 3317623 — How To Assign Attachment Types for Cases.
- Important limitation: Named attachment types guide the employee on what to upload but do not block submission if the file is absent.
- You can define specific attachment types and assign them to a case type. This makes the expected document type visible to the employee in the attachment area during Self-Service case creation and supports downstream agent processing.
- Option 3 — Attachment Instructions in Case Type Description
- You can embed a clear instruction in the case type description so the employee sees the attachment requirement before submitting.
- Navigate to Settings → Cases → Case Types.
- Select the relevant case type.
- Update the Description field to include explicit instructions — for example: "A court letter must be attached to this case. Cases submitted without this document will be returned and cannot be processed until the required document is provided."
- Limitation: This is an informational control only and does not technically prevent submission without an attachment.
- You can embed a clear instruction in the case type description so the employee sees the attachment requirement before submitting.
- Option 4 — Attachments in Forms (Delivered Q4 2025)
- SAP ESM delivered configurable attachment fields within forms, enabling employees and service agents to upload and manage documents in specific sections of a request.
- Create or edit a Form associated with the relevant case type (for example, "Jury Service").
- Within the form designer, add a configurable attachment field and mark it as Required.
- Associate the form version with the case type and ensure the Self-Service toggle is enabled.
- When the employee accesses Self-Service and selects that case type, the form is presented and the Submit button remains unavailable until all mandatory fields — including the attachment field — are filled.
- This is the most direct standard mechanism to enforce mandatory document capture at submission time, improving compliance and reducing back-and-forth processes.
- Note: This feature supports collecting supporting evidence at the right step of the process and ties it directly to the relevant workflow, improving audit readiness and accelerating case handling.
- SAP ESM delivered configurable attachment fields within forms, enabling employees and service agents to upload and manage documents in specific sections of a request.
- Option 1 — Use ESM Forms with a Required Acknowledgement Field
Additional remarks:
- Currently, pre-creation blocking is not possible via the email channel — cases are created automatically upon receipt of an inbound email, with no interactive submission step where an employee can be prompted or blocked.
- The following post-creation mitigations may apply (but please test and engage an expert consultant if required):
- Autoflow Rules:
- Configure an autoflow rule to automatically send a response email to the employee when a case is created without the required attachment, requesting the missing document.
- The Support for entity attachment in autoflow emails feature (available for SAP ESM from Q4 2023) supports attachment handling within autoflow rule execution.
- Business Documents:
- Business Document schemas can be configured per case type to capture data from email attachments using AI-driven extraction (generative AI with large language models).
- Conditions can be used to make specific Business Document fields required, read-only, or hidden, creating a process-level gate before the case progresses.
- Channel Redirection:
- For case types where a mandatory document is truly non-negotiable, the recommended approach is to direct employees to the Self-Service portal where Option 4 (Forms with mandatory attachment fields) can be enforced.
- An auto-acknowledgement email can include a link to the relevant Self-Service form.
- Autoflow Rules:
Product Enhancement Request: If enforcing mandatory document attachment at the point of Self-Service case submission is a business-critical requirement, submit a product enhancement request via the SAP Continuous Influence (Improvement Request).
See Also
- SAP Help — Self-Service — Overview of the Self-Service feature in SAP Enterprise Service Management
- SAP Help — Forms — Configure custom forms with required field conditions per case type
- SAP Help — Configure Case Types — Self-Service toggle and case type configuration
- SAP Community Blog — Introducing Forms for Self Service/Cases - SAP ESM — February 2026 Forms release announcement
- KBA 3317623 — How To Assign Attachment Types for Cases
- KBA 3595150 — ESM Frequently Asked Questions (FAQ)
- KBA 3744700 - Case Subject Can Be Cleared After Creation Even When The Subject Is Mandatory
Keywords
ESM Self-Service mandatory attachment, required document case creation, attachment validation Self-Service, block case submission missing document, compulsory document upload ESM, proof of identity attachment required, enterprise service management attachment enforcement, mandatory upload before submit, jury service change of name document required case , KBA , CEC-CRM-AD , Agent desktop - live channels , CEC-CRM-FORM , SCV2 and ESM support for Forms , CEC-CRM-CAS , Case Management for SAP Sales/Service Cloud , CEC-CRM-EML , Emails for SAP Sales/Service Cloud , CEC-CRM-SELF , ESM support for Self-Service module , CEC-CRM-BUSD , ESM Business Document Service , Problem
SAP Knowledge Base Article - Public