Routing and navigation
Full lesson currently free to read · AI practice limits apply separately
In-app routes map application state to targets; launchpad intents navigate between applications. Encode parameters and bind the target to the resolved business key. A deep link must reconstruct the screen after a reload without depending on a previous list selection.
Visual overview
Explanation
Tutorial outcome
In-app routes map application state to targets; launchpad intents navigate between applications. Encode parameters and bind the target to the resolved business key. A deep link must reconstruct the screen after a reload without depending on a previous list selection.
Prerequisites
Complete chapters 1–5 in this module. Use synthetic fixtures or an authorized sandbox.
Worked case — fictional
A mock order detail route works after clicking a row but fails when the same URL is opened directly.
Step-by-step investigation
1. Route
Declare an order-key parameter and its detail target in the app descriptor.
Expected evidence: Route order/PO101 matches the detail target.
2. Match
Read the matched parameter and bind the detail view independently of list-controller state.
Expected evidence: Direct navigation resolves PO101 without a prior selection.
3. Missing
Handle an unknown key as a missing object rather than showing cached data.
Expected evidence: PO999 displays a not-found state.
4. Back
Check reload, back navigation and intent navigation without duplicate history entries.
Expected evidence: Back returns to the expected list state.
Try it yourself
Reproduce the synthetic input from the example below in a local fixture or authorized sandbox. Follow each step, record the observed result, and explain any mismatch before continuing. Do not treat the expected evidence as a result observed in your SAP tenant.
Acceptance check
Reloading PO101 opens the correct record; PO999 cannot display the previously viewed order.
Common failure to avoid
Avoid using a global selected-object variable as the only source of detail-page state.
Self-check
What is the essential deep-link test?
Expected reasoning: Open the detail URL in a fresh application session.
Edition and release scope
Check the linked SAP documentation for your product, runtime, region and enabled service plan. The worked case is a simulation; these steps were not executed in a customer SAP tenant.
SAP references
References checked 2026-10-30. SAP material supports the named concepts; the case, fixture and acceptance checks are original ERPClimb teaching material. No SAP tenant execution or certification is claimed.
[SAP Help — Routing configuration](https://help.sap.com/docs/SAPUI5/3f47ec0c79a547aeaa23090b74c9520c/902313063d6f45aeaa3388cc4c13c34e.html) — Targets, asynchronous loading and component routing
Code example
{"route":"order/{orderId}","target":"OrderDetail","testKeys":["PO101","PO999"]}Loading guided workshop…
Real project scenario
A mock order detail route works after clicking a row but fails when the same URL is opened directly.
Common mistakes
Avoid using a global selected-object variable as the only source of detail-page state.
Best practices
Reloading PO101 opens the correct record; PO999 cannot display the previously viewed order. Check the linked SAP documentation for your product, runtime, region and enabled service plan. The worked case is a simulation; these steps were not executed in a customer SAP tenant.
Interview angle
What is the essential deep-link test? Open the detail URL in a fresh application session.
Practice this lesson
Original educational case studies for SAP consultants, not official SAP certification exam questions. Verify product edition and implementation details against the current SAP documentation.
Quick check
0 of 3 questions attempted
1. Where is in-app routing configured in a UI5 app?
2. How do Fiori apps navigate to other apps in the launchpad?
3. A deep link to an object page shows an empty page. What should the controller do?
Interview questions
1. Explain routing and cross-app navigation in SAPUI5.
Answer it in your own words first, then compare.
2. Users can't navigate from your app to another app. What do you check?
Answer it in your own words first, then compare.
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.