Symptom
- A RAP validation adds an error to REPORTED for a child/grandchild entity, but the message does not appear in the UI.
- Records can be saved even when a field is initial because the validation does not block save.
- After adding FAILED, an exception occurs but the UI still does not show the message.
Environment
SAP S/4HANA Cloud Public Edition 2502
Reproducing the Issue
- Implement a RAP validation on a child or grandchild entity that adds an error to REPORTED when a field is initial.
- Do not set the REPORTED-%PATH (and optionally do not set FAILED).
- Create or edit a record so that the field remains initial and attempt to save.
- Observe that no error message is displayed on the UI; save may proceed or be blocked without a visible message.
Cause
- The REPORTED message for the child/grandchild entity does not have the %PATH component populated, so the framework cannot locate the instance and display the message on the UI.
- FAILED was not initially populated, so the save was not prevented.
Resolution
- In the validation implementation for the affected child/grandchild entity, add the message to REPORTED with the appropriate severity and target.
- Populate REPORTED-%PATH with the full path from the root to the affected child instance (e.g. root entity → intermediate child → target child), including technical components such as %IS_DRAFT and %PID when applicable.
- If the save must be prevented, also add the same instance to FAILED.
- Activate the changes and test by performing the validation scenario, confirming that the message appears in the UI at the correct context and that save behavior matches expectations.
See Also
Keywords
rap validation, reported, failed, %path, state messages, child entity, grandchild entity, message not shown, ui message, abap cloud, rap messages, draft validation, save blocked, ui error display, entity path , KBA , BC-ESI-ESF-BSA , Business Service Adaptation , Problem
Product
SAP S/4HANA Cloud Public Edition 2502
SAP Knowledge Base Article - Public