Hello Everyone,
We are currently migrating our Enterprise Portal to SAP BTP – Build Work Zone (Standard Edition). During this migration, we encountered a few challenges. One of the key issues—and its resolution—is described in this blog to help others facing a similar situation.
Please note we created Local Artifact in the Work Zone and connected the S/4HANA system through Cloud Connector Tunnled access.
Issue Description
We have several ESS Web Dynpro ABAP (WDA) applications running on the S/4HANA system that need to be accessed through SAP Build Work Zone.
After completing all the required configurations, we encountered an error while accessing nested WDA applications through Work Zone.
What do we mean by “Nested WDA”?
For example, we have a Working Time application exposed in Work Zone. When users access it, they see sub-applications such as:
-
Create Leave Request
-
Leave Overview
-
View Time Account Balances
When attempting to open any of these sub-applications, the following error occurs:
Configuration Overview
Build Work Zone Application Configuration
Run Destination Configuration
Note: As mentioned earlier the content is not federated so Design Time destination not required in this case.
Additional Property of Destinaiton
Despite correct configuration on the Work Zone side, the issue persisted.
Analysis
After extensive analysis, we identified a relevant SAP Knowledge Base Article that describes the same issue:
SAP KBA 3385676
“Getting Failed to resolve navigation target Shell-startWDA error in Work Zone”
This KBA pointed us in the right direction.
Resolution
As per the KBA, the fix needs to be applied on the S/4HANA side only.
No changes are required in SAP BTP Build Work Zone.
Steps to Resolve the Issue
-
Open transaction SM30
-
Enter the view name:
/UI2/NWBC_CFGCV -
Add the following parameter:
-
Parameter Name:
MAP_LEGACY_TO_IBN -
Value: (leave it empty — this disables the setting)
-
Before the Change
The view is empty, as shown below:
After the Change
The parameter is added with an empty value:
-
Save the changes.
Result
After maintaining this parameter, the nested WDA applications were successfully accessible through SAP Build Work Zone without any navigation errors.
As per the above screen shot, the application is accessible. There is no HR data maintian for my id so the message is coming.
Conclusion
If you are facing navigation issues with nested WDA applications while migrating to SAP Build Work Zone, disabling IBN navigation for inner WDA navigation on the S/4HANA side can resolve the issue.
I hope this blog helps others save time during their migration journey.
Regards,
Rohit Gera
#abap