SAP® BTP Build Work Zone End-to-End | Create SAP® Fiori® LaunchPad in SAP® BTP | SAP® BAS BTP App

[@kirthikaselvaraj7347]

Good explanation.. really helped me

[@ui5cn]

Thank you!

[@Sonu-gm8yi]

Hello, The video is really helpful, but I am more interested in the next part, like creating the destination in SAP BTP connecting your API, and then having your application deployed to SAP BTP and then to SAP Fiori Launchpad. I am following SAP CPI -> SAP BAS -> SAP BTP -> SAP Fiori Launchpad. While performing I can see the application created in the instances field of SAP BTP, but I cannot see it in the HTML5 applications field, and also my application is not visible in Content-Manager/Content-Explorer/HTML5 Apps.

[@biswa141]

What is the difference between standard instance and standard subscription.?

[@ui5cn]

In BTP, a Standard Instance is a pay-as-you-go model where you provision and manage specific services, paying based on actual usage, like CPU or memory consumption, offering flexibility in scaling resources. On the other hand, a Standard Subscription provides fixed-term access to a service for a set fee, regardless of usage, offering predictable costs but less control over resources. While instances are ideal for variable or dynamic usage needs, subscriptions are best for regular, consistent access to services with stable pricing.

[@karthikdakdar6623]

Hello, Thanks for sharing this, really helps! I have a scenario where I have created the destination and consumed it in the UI5 application. These destinations work fine locally as well as when viewed on HTML5 application post deployment. But when configured in Build Work Zone, the destination is unreachable and I am receiving 404 not found error. Could you please suggest an approach here?? Thanks in advance!

[@ui5cn]

It sounds like you're encountering an issue where the destination that works locally and in your HTML5 app isn't working when accessed through SAP® Build Work Zone, resulting in a 404 error. This is a common issue when destinations are not properly configured for specific environments. Here are some steps you can try to resolve this: 1. Check Destination Configuration in SAP® BTP: Make sure the destination is correctly configured in the SAP® BTP cockpit for the Build Work Zone environment. The destination might need additional configurations, such as proper authentication settings (OAuth, BasicAuth, etc.) or updating the URL paths. 2. Authorization and Trust Settings: Ensure that the destination is set up with the right authorization settings. Sometimes, the issue might be due to incorrect user roles or authorization missing for accessing the destination from SAP® Build Work Zone. 3. Cross-Origin Resource Sharing (CORS): If you're working with external services, ensure that CORS policies are set up correctly for the destination, allowing access from SAP® Build Work Zone. 4. Route Matching: Double-check the routing configuration in your UI5 app. When deployed to Build Work Zone, the routes and paths could differ from local testing, and you may need to adjust them. 5. Proxy Settings: In some cases, Build Work Zone might require additional proxy configurations. Verify that the destination is correctly routed through any necessary proxy settings. 6. Logs and Debugging: Check the browser console and network logs in the developer tools when loading the app through Work Zone. This can give you more insights into what might be causing the 404 error. You can try these approaches to solve the issue.