Hello Experts,
I am facing an issue with federated content from an on‑premise S/4HANA system to SAP Build Work Zone (Standard Edition).
Our authorization team has removed the old tile and assigned a new tile to the correct custom role, custom catalog, and custom group in S/4HANA.
To ensure a clean setup, I deleted the previous exposure configuration and re‑created the full setup from scratch in:
/UI2/CDM3_EXP_SCOPE (content exposure)SAP BTP → Build Work Zone → Content Provider → Synchronize Content
Despite repeating the full process multiple times, the old tile continues to appear in Build Work Zone instead of the new one.
The authorization consultant has verified both the new role and the tile assignments several times on the S/4HANA side, and everything looks correct there — but Build Work Zone keeps federating only the old tile.
Has anyone experienced something similar?
I am trying to understand:
Why outdated tile information is still being federatedWhether additional cleanup is required on the CDM or content provider sideIf there are any cache layers (S/4HANA, BTP, or Build Work Zone) that must be explicitly clearedWhether Exposure Version 2 requires specific steps to refresh or replace previously published app IDs
Any advice, known issues, or guidance on how to force Build Work Zone to pick up the updated tile would be greatly appreciated.
Thank you!
Hello Experts,I am facing an issue with federated content from an on‑premise S/4HANA system to SAP Build Work Zone (Standard Edition).Our authorization team has removed the old tile and assigned a new tile to the correct custom role, custom catalog, and custom group in S/4HANA.To ensure a clean setup, I deleted the previous exposure configuration and re‑created the full setup from scratch in:/UI2/CDM3_EXP_SCOPE (content exposure)SAP BTP → Build Work Zone → Content Provider → Synchronize ContentDespite repeating the full process multiple times, the old tile continues to appear in Build Work Zone instead of the new one.The authorization consultant has verified both the new role and the tile assignments several times on the S/4HANA side, and everything looks correct there — but Build Work Zone keeps federating only the old tile.Has anyone experienced something similar?I am trying to understand:Why outdated tile information is still being federatedWhether additional cleanup is required on the CDM or content provider sideIf there are any cache layers (S/4HANA, BTP, or Build Work Zone) that must be explicitly clearedWhether Exposure Version 2 requires specific steps to refresh or replace previously published app IDsAny advice, known issues, or guidance on how to force Build Work Zone to pick up the updated tile would be greatly appreciated.Thank you! Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
