3753695 - Troubleshooting Spaces layout failures in hybrid landscapes: SAP Build Work Zone Federation vs. Local S/4HANA Launchpad Shell (SAP_UI 816)

When custom Launchpad Spaces and Pages layouts (e.g., Z<YourSpace> ) are transported or assigned to user roles, they fail to render for end users. The behavior is split across two distinct system layers: 

• Symptom Channel 1 (SAP Build Work Zone Cloud Portal): The federated content catalogs do not appear in the cloud portal's Content Explorer or user interface dashboard, despite a clean transport import into the landscape.
  
  • Real Word Example:  A user created a custom tile for the extended version of the "Find Technical Object" app
    • When the custom tile configured with a start Target Mapping was launched, it ignored the extension entirely and launched the standard version of the app instead.
      • The issue: The "Related App" navigation link did correctly trigger the extended version of the application using that exact same Target Mapping setup.
      • The Landscape Setup: Both the standard app and the custom extended app were placed into separate, dedicated Fiori catalogs, and the end users had explicit PFCG authorization to access to both catalogs simultaneously
    • ----Summary-----
      This issue frequently surfaces when attempting to isolate custom extensions. For example, a customer creates a custom tile for an extended version of the "Find Technical Object" app. When launched via a standard Target Mapping, the custom tile ignores the extension and launches the standard version of the app instead—even though the "Related Apps" link correctly triggers the extended version. To fix this, the standard and custom apps are isolated into separate, dedicated Fiori catalogs with dual PFCG role assignments, and the new layout structure is transported. Post-transport, these newly separated catalogs disappear entirely from the Work Zone dashboard. 
      ----end-------------

• Symptom Channel 2 (Local S/4HANA On-Premise Launchpad): Navigating directly to the local on-premise launchpad shell triggers a generic front-end navigation error: "Navigation target could not be resolved." Inspecting the browser developer console reveals a hard network layer crash during the launchpad boot sequence:

  HTTP 404 (Not Found): /sap/opu/odata/sap/SUI_FLP_EXT_BLD_PLUGIN/$metadata

S/4HANA Cloud and On-Prem

Keywords: SUI_FLP_EXT_BLD_PLUGIN, LAUNCHPAD_PLUGIN_ID, /UI2/FLP_CUS_PICONF, SOTR_EDIT, EP-WZ-SM, CA-FLP-ABA, Fiori launchpad 404 metadata, SUI_USER_INTERFACE/LAUNCHPAD_PLUGIN_ID, Work Zone federation blank spaces, target mapping navigation target could not be resolved, Fiori spaces missing after transport, SAP_UI 816 launchpad error, Launchpad App Descriptor Item plug-in error. , KBA , EP-WZ-SM , Site Management (non selectable) , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , Problem