Symptom
- An Adapt UI Personas flavor created in development works as designed, but after transport to quality or production it does not render as expected (misaligned layout or wrong fields shown);
- The issue might only occur in the screens or sections that include Custom Fields, and generally there's no issue with other screens or flavors;
- Comparing the original (unflavored) screen between DEV and target systems, additional or missing fields are visible in the target;
- Key User Extensibility is being used to edit the custom fields in the affected application;
Environment
- SAP S/4HANA Cloud Public Edition
- Adapt UI Public Cloud
- SAP Screen Personas Public Cloud
Reproducing the Issue
- In the quality or production system, open the application;
- Activate the transported Adapt UI flavor for the user;
- Certain fields are not rendered with the wanted customizing design;
- Check the same flavor in DEV, it works fine without issue;
Cause
- The original (unflavored) screen is not identical across systems. There are some custom fields generated by Key User Extensibility which are activated or deactivated only on DEV system;
- The customization of Key User Extensibility is on the top of WebGUI application, then Personas (Adapt UI) Flavor is applied on the top of it;
- Personas changes rely on unique control IDs. While the control IDs are generated automatically from the rendered screen, differing originals lead to different control IDs among different systems. Therefore, the customizing script in the flavor cannot match the correct field after transport, finally causing those unexpected behaviors;
- If even one custom field control is forgotten, then this will affect control IDs of other custom fields because of such specific implementation of Custom Fields;
Resolution
From Personas (Adapt UI) perspective, the original screen among every systems must be ensured to be completely the same.
- If there is Customer Field configured in the screen, all Custom Fields key user extensibility configurations must be exported/imported to all systems to be completely the same before transporting the flavor, which ensures the flavor identifies the correct control ID and functions well among all systems;
- Re-transport the Screen Personas flavor again and test if consistencies persists;
See Also
Keywords
CO11N, screen personas, flavor, transport, different layout, not showing properly, webgui, control id, original screen mismatch, custom fields, key user extensibility, adapt ui, assignment category, publish flavor, s/4hana cloud , KBA , BC-PER , SAP Screen Personas , BC-SRV-APS-EXT-FLD , Custom Fields , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public