Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

An application router sends incoming web requests to the right service. Its route rules are matched in order, so a broad early rule can catch a request intended for a later rule.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Business Technology Platform, or BTP, provides cloud services for applications, data and integration. A connection needs a route, an identity and permission to perform the intended task.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for BTP application router routes: Check matching order and destination rewrites
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP BTP application-router xs-app.json routing. Managed-router services and deployed router versions can add configuration and destination-resolution differences.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Route the plant app's API request correctly

The first match wins

Incoming path: /api/orders. Rule 1: Broad catch-all pattern. Rule 2: Specific API pattern. Review: Which rule matches first?
What to notice: A later specific rule may never handle a request already caught by an earlier rule.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Incoming path
/api/orders
Rule 1
Broad catch-all pattern
Rule 2
Specific API pattern
Review
Which rule matches first?
Words you’ll meet in this guide
Backend
The service or system doing the work behind an interface.
Destination
Named connection settings for another service.
Credential
Access information used to prove an identity.
Subaccount
A BTP scope for applications, services and access settings.
BTP
SAP Business Technology Platform: cloud services for applications, data and integration.
API
A defined interface through which programs exchange data or request actions.
HTTP
The request-and-response protocol used by web applications and APIs.
CSRF
Cross-Site Request Forgery. A CSRF token helps a service reject unwanted cross-site write requests.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Incoming URL → First matching route → Selected backend. Conceptual diagram for BTP application router routes: Check matching order and destination rewrites.
Apply the idea: A manufacturer's BTP application sends an operational API request that is intercepted by a broader application route.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Route the plant app's API request correctly

    A manufacturer's BTP application sends an operational API request that is intercepted by a broader application route.

  2. Start with the request that was actually routed

    When an SAP BTP application router sends a request to the wrong backend, evaluate the deployed routes in their declared order, including any HTTP-method restrictions, and then calculate the selected route’s target rewrite.

  3. Separate browser navigation, router matching and backend addressing

    A browser may show a long URL containing an application prefix, query parameters and a fragment.

  4. Worked case: an orders request is swallowed by a generic route

    Use this fictional request: GET /api/orders/4711.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.