Docs / Event Studio

Event Studio

ASAPIO Event Studio is a web-based SAPUI5 application for configuring, deploying, and monitoring ASAPIO integrations — without requiring SAP GUI or ABAP development skills.

Event Studio is available in two editions:

Release compatibility

Release numbers follow the pattern YYMM, e.g. 2607 = July 2026. – = not available in this release.

Both editions share the same core feature set.

Application Sections

Deployment

Backend Preparation (both editions)

Regardless of delivery type, the connected on-premise backend system must be configured before deployment.

Verify ASAPIO Integration Add-on Installation

At least version 9.32504 (SP11) is required for Event Studio. See the download page for details.

Verify Package Import

Use transaction SE80 to confirm that the packages /ASADEV/API_CONFIG and /ASADEV/API_EXT (required for the Explorer feature) have been successfully imported.

Activate Required OData Services

Event Studio relies on several OData services that must be active in the system:

• /ASADEV/GW_CONFIG_API_SRV — supports Event Studio's main functions
• /ASADEV/ODATA_EXTINT_1_SRV — required for the Explorer feature
• APS_EXT_CCV_SRV — required for CDS Payloads creation

For each service, open transaction /n/IWFND/MAINT_SERVICE, click Add Service, and fill in:

• System Alias: LOCAL (or your system alias)
• Technical Service Name: e.g. /ASADEV/GW_CONFIG_API_SRV

Click Get Services, select the service from the list, click Add Selected Services, and provide the package name and transport request when prompted.

Deploy ABAP Edition (via Transport Request)

Verify Package Import

Use transaction SE80 to confirm the package /ASADEV/APP_UI has been imported successfully.

Activate ICF Nodes

Open transaction SICF and locate the following nodes:

• /default_host/sap/bc/bsp/asadev/app_ui
• /default_host/sap/bc/ui5_ui5/asadev/app_ui

Right-click the app_ui node for each and select Activate Service. Confirm in the popup and ensure activation is performed in the correct client.

Test the Application

In SICF, select the /default_host/sap/bc/ui5_ui5/asadev/app_ui node and choose Test Service. Verify the application loads without errors. Confirm backend connectivity by checking that at least one page (Data Catalog, Interfaces, Events, or Connections) shows data.

Configure as Fiori Launchpad Tile (Optional)

1. Open /UI2/FLPD_CUST to access the Fiori Launchpad Designer.
2. Create a Semantic Object in /UI2/SEMOBJ (e.g., ZEVENTSTUDIO).
3. In the Launchpad Designer, create a Catalog (e.g., ID ZCAT_EVENTSTUDIO).
4. Inside the catalog, create a Target Mapping:
   • Semantic Object: ZEVENTSTUDIO, Action: display
   • Application Type: SAPUI5 Fiori App
   • URL: /sap/bc/ui5_ui5/sap/zeventstudio
5. Create a Tile (App Launcher – Static) using the semantic object and action above.
6. Create a Group and assign the tile to it.
7. In transaction PFCG, assign the catalog and group to a role, then assign the role to relevant users.

Deploy BTP Edition (via MTAR to SAP BTP)

The delivered package contains a prebuilt Multi-Target Application archive: eventstudiocap-<version>.mtar

Prerequisites

Install the MultiApps plugin if missing:

cf add-plugin-repo CF-Community https://plugins.cloudfoundry.org
cf install-plugin -f multiapps

Required SAP BTP services:

Deployment Steps

1. Open a terminal and navigate to the folder containing the .mtar file.
2. Log in to Cloud Foundry — obtain an SSO passcode from https://login.cf.<region>.hana.ondemand.com/passcode, then:

   cf login -a https://api.cf.eu10-004.hana.ondemand.com -u user@example.com --sso-passcode <SSO_PASSCODE>

3. Target the correct org and space if not selected during login:

   cf target -o <cf-org> -s <cf-space>

4. Deploy the archive:

   cf deploy eventstudiocap-2.2.0.mtar

Post-Deployment: Configure Destinations

In SAP BTP Cockpit, go to Connectivity → Destinations and create a destination for the on-premise backend:

The destination name is free — Event Studio identifies the relevant destination by the asapio.eventStudioDest=true additional property. If no such destination exists, users are prompted to select one on the start screen.

Post-Deployment: Configure AI Destination (optional)

Required only if AI features should be enabled. See Bring Your Own LLM below for the destination fields and supported providers.

Post-Deployment: Assign Role Collections

After assigning role collections, ask users to log out and back in to refresh their authorization token.

Validation Checklist

After deployment and configuration are complete, open the application URL and validate the following:

General Navigation

After the application loads, select the desired SAP system from the dropdown and click OK. To switch systems later, use the dropdown in the top-right corner. Use the left sidebar menu to navigate between pages — the default landing page is the Data Catalog.

Data Catalog

The Data Catalog page lists all available data objects with a filter bar at the top and interactive tiles for each object. The filter bar supports keyword search, Data Layer selection, and Data Objects Type filter (all, standard, or custom).

Each tile shows: title, Data Layer type, payload, package, version, data source name, and status (active/inactive). The Payload link on each tile opens either the Payload Designer in SAP GUI for HTML or the Custom CDS application in the Fiori Launchpad, depending on the source type.

Data Catalog — Details Page

The details page contains:

• Breadcrumb Navigation — navigate back to previously visited pages
• Data Object Header — key attributes summary
• Available Standard Events Table — predefined events with a Deploy button per row and a Create Event button
• Active Instances Table — active deployments with navigation to each instance and update functionality
• Payload Details Table — full payload structure for in-depth review
• AsyncAPI Section — load, copy, or download the AsyncAPI specification for a selected Interface ID

Data Catalog — Deployment Page

Accessible via the Deploy button in the Events table or by navigating to an entry in the Active Instances table. Configure:

• Interface Name — auto-generated from the data object properties
• Connection — dropdown; selecting one auto-populates the Header Fields table
• Header Fields Table — add, edit, or delete entries; all mandatory fields must be filled
• Load Type — dropdown selection
• Activation Flag — checkbox to activate immediately on deploy

Click Deploy (top right) to create or update the deployment. Invalid or incomplete fields are highlighted; errors show a corresponding message.

Interfaces

The Interfaces page shows a filter bar and a table (or tile grid) of configured interfaces. Two action buttons sit above the table: Create Interface and Transport Interface Configuration.

The filter bar includes a keyword search field, a Connection ID dropdown, and a Display Mode toggle (table view / grid view).

Create Interface

Click Create Interface to open the creation screen. Fill in:

• Interface Name — free-text input
• Connection — dropdown
• Header Fields Table — auto-populated from Connection and Load Type; entries can be added, modified, or deleted
• Load Type — dropdown
• Extraction Type — dropdown

Click Create (top right) to submit.

Transport Interface Configuration

Select one or more interfaces in Table View, then click Transport Interface Configuration. A dialog lists available Workbench and Customizing transport requests assigned to the current user. Select the appropriate transports and click OK to add the interface configuration to them.

Note: This action is only available in Table View mode and requires at least one interface to be selected.

Interface Details

Click any table row or tile to open the details screen, which contains:

• Breadcrumb Navigation
• Interface Tile — key attributes summary
• AsyncAPI Section — load, copy, or download the AsyncAPI schema
• Active Instances Table — navigate to instances and update deployments

Interface Deployment Page

Accessible from the Active Instances table row. All fields are pre-filled from the selected entry. Adjust as needed and click Deploy to update the existing instance.

Dynamic Topic (Solace / SAP Advanced Event Mesh)

Dynamic topic is a path of segments that can be defined on the Deployment or Create Interface screen, for example: sap/s4/sales-orders/EMEA/1000/CHANGED

How to set it up

1. Choose a connection of type Solace or AEM. The Solace Dynamic Topic section appears.
2. Click add. A new segment opens in the editor.
3. Pick the segment type with the three-way toggle:
   • Default value: type the text.
   • Structure field: enter the source structure (for example MARA) and the field (for example MATNR).
   • Conversion: choose the class and method with the value help. The method list is filtered by the class you chose.
4. Click Save. Cancel drops a segment that is still empty, and Save refuses an incomplete one.
5. Repeat for each topic level. Each segment shows as a coloured chip, one colour per type, separated by /.
6. Click a chip to edit it. The arrow buttons move it left or right, which changes the topic order. The bin button deletes it.
7. Click Deploy (or Create) to store the segments.

What happens at runtime

Whenever an event fires, the add-on reads the segments in order. It takes the fixed text, the document field value, or the conversion result, and joins them with / into the topic. For example, one order with VKORG = 1000 and a region method returning EMEA is published to sap/s4/sales-orders/EMEA/1000/CHANGED. A different order can be published to a different topic. Subscribers on Solace or AEM can then subscribe to just the part they care about, for example sap/s4/sales-orders/EMEA/>.

Events

The Events page displays predefined events in a table. Use the Create button to add a new event definition or the Delete button to remove a selected entry. Click any table row to open the details screen, where event information can be viewed or edited.

Some events ship with Event Studio, but you can also add definitions for other events in your system or link standard events to custom data catalog objects.

Connections

The Connections page displays a table of all configured connections. Use the Edit button to navigate to SAP GUI for HTML, where connection details can be viewed or modified.

Explorer

The Landscape Explorer (currently in beta) is a built-in visualization tool that renders the entire ASAPIO integration landscape as an interactive network graph. The page is split into two areas:

• Integration Network (upper area) — an animated canvas graph. Each node represents a connection endpoint; interfaces are drawn as directed flow chips between the SAP system node and the target connector node. Nodes are color-coded by business category (Business Partner, Sales & Orders, Material/MDM, etc.).
• Lower panel — a tabbed list with three tabs: Interfaces, Connections, and Connectors. Use the Hide panels button to maximize the network view.

Network Controls

Clicking a node or interface chip in the network highlights it and cross-selects the corresponding row in the lower panel.

Interfaces Tab

Shows all configured interfaces with a summary bar of clickable filter chips (total, active/inactive, real-time/batch, outbound/inbound, per-connection counts). Chips act as quick filters — click once to apply, again to clear. The toolbar provides full-text search, Status, Direction, Load Type, Connection, and Category filters, a Cards/Table view toggle, and CSV export. Each interface card shows: Interface ID, direction and load-type badges, data-flow arrow, payload name, connection ID, and last-run timestamp.

Detail Panel

Clicking any interface, connection, or connector card opens a slide-in detail panel containing: a Data Flow diagram, an inferred Business Purpose description, Interface Details (all fields), Connection Details, Related Interfaces, a Mini Network Map, and a Copy as JSON button.

Connections and Connectors Tabs

The Connections tab shows a card per configured connector instance (Connection ID, connector type, RFC Destination, SSL, Hostname, Port, and interface count). The Connectors tab shows a card per available connector type (Connector ID, active/inactive status, installed flag, and counts of connections and interfaces).

AI Assistant

BTP Edition only

The BTP Edition of Event Studio includes a built-in AI Assistant sidebar that helps users navigate the application and configure integrations. The assistant can answer questions about interface setup, explain payload structures, and guide users through deployment steps — all in context of the currently open page.

What the Assistant Supports

The assistant is scoped to three kinds of questions:

• Navigation — where a page is and how to get there (e.g. "take me to the catalog", "where can I create a new event?"). It can give a direct in-app link to the page or record.
• Current screen — questions about the data you are actually looking at (e.g. "what events does this interface have?", "which connections are active?", "explain these data objects"). It reads what is on your current page to answer.
• Documentation — how features work and how to configure them.

Documentation Topics It Can Answer

• Getting started & concepts — quick start, key terms/glossary, general FAQ.
• Core features — Payload Designer, message sequencing, inbound and outbound messaging.
• Event formats & sources — CloudEvents, AsyncAPI export, IDoc-to-JSON, RAP events, CDS View / CDS Entity data sources.
• Setup & operations — installation prerequisites and roles, Monitoring, release history, transport, GDPR functions, SAP Cloud ALM connectivity, ATP.
• Supported connectors — AWS, Azure (including Azure Service Bus), Google Pub/Sub, Microsoft Fabric, Apache Kafka, Confluent, Solace, StreamSets, SAP AEM (Advanced Event Mesh), and SAP Event Mesh.

Connectors Excluded from AI Support

The following connectors are not supported by the assistant in this edition, and it will not provide configuration detail for them: SAP Ariba, SAP Fieldglass, mysupply, and AI Vergabemanager. When a question names any of these connectors, the assistant replies with a fixed notice:

"This connector type is not supported currently."

It does not attempt a partial answer or reveal any related documentation for these connectors.

Questions Outside the Assistant's Capabilities

The assistant is not a general-purpose chatbot. It cannot answer questions that have no connection to Event Studio — general ABAP or software development questions, non-ASAPIO SAP transactions or unrelated SAP functionality, or general knowledge and other products. When a question is completely unrelated to Event Studio, the assistant does not guess: it replies with a short message stating the question is outside its area of expertise and lists what it can help with (current-screen, documentation, and navigation) with examples of each. Questions that Event Studio's pages or documentation can partly answer are still answered rather than rejected.

Bring Your Own LLM

The AI Assistant is model-agnostic. LLM provider selection and API key provisioning are managed entirely through SAP BTP Destination Manager — no credentials are stored in the application itself. Currently supported providers: SAP AI Core, Groq, OpenAI, Anthropic (Claude), and Google (Gemini).

Supported Models

Set asapio.modelName to any model identifier below, matched to the provider used in the destination's URL.

To configure the AI backend, create a destination in SAP BTP Cockpit (Connectivity → Destinations) with the following properties:

Then add the following additional properties:

Users with the eventstudiocap_aiviewer role collection can access the AI sidebar. See Deploy BTP Edition above.

AI Core Setup

1. Book entitlement (Global Account)
   • BTP Cockpit → Global Account → Entitlements
   • Add the "SAP AI Core" service
   • Plan: extended (only this plan allows the use of foundation models such as Claude)
   • Assign quota to the target subaccount
2. Create Service Instance & Service Key (Subaccount)
   • Instances and Subscriptions → Create → Service: SAP AI Core, Plan: extended
   • Create the instance (name of your choice)
   • Create a Service Key: Instance → Actions (…) → Create Service Key

   The Service Key provides the values needed for all following steps:

   • clientid → Client ID for OAuth2ClientCredentials
   • clientsecret → Client Secret for OAuth2ClientCredentials
   • url → Token Service URL (append /oauth/token)
   • serviceurls.AI_API_URL → AI_API_URL (inference endpoint / Destination URL)
3. Obtain an OAuth Token (manual verification only)

   This step is only needed to manually verify the setup via PowerShell/curl before wiring it into the app. The app itself never fetches this token manually (see Step 9).

   $authUrl='<AUTH_URL>/oauth/token'
   $clientId='<clientid>'
   $clientSecret='<clientsecret>' # single quotes!
   $aiApiUrl='<AI_API_URL>'

   $tokenResponse = Invoke-RestMethod -Uri $authUrl -Method Post   -ContentType 'application/x-www-form-urlencoded'
     -Body @{grant_type='client_credentials';client_id=$clientId;client_secret=$clientSecret}
   $accessToken = $tokenResponse.access_token

4. Check the Model Catalog

   $models = Invoke-RestMethod -Uri "$aiApiUrl/v2/lm/scenarios/foundation-models/models" `
     -Method Get -Headers @{Authorization="Bearer $accessToken";"AI-ResourceGroup"="default"}

   $models.resources | Where-Object { $_.model -like 'anthropic--*' } | Select-Object model, executableId

5. Create the Configuration

   $configBody = @{
     name = 'Claude_Haiku_4_5'
     executableId = 'aws-bedrock'
     scenarioId = 'foundation-models'
     parameterBindings = @(
       @{key='modelName'; value='anthropic--claude-4.5-haiku'},
       @{key='modelVersion'; value='1'}
     )
   } | ConvertTo-Json

   $configResponse = Invoke-RestMethod -Uri "$aiApiUrl/v2/lm/configurations" -Method Post   -Headers @{Authorization="Bearer $accessToken";"AI-ResourceGroup"="default";"Content-Type"="application/json"}
     -Body $configBody

   The response returns an id. This is the Configuration ID needed in the next step.

6. Create the Deployment

   $deployBody = @{ configurationId = '<CONFIGURATION_ID_FROM_STEP_5>' } | ConvertTo-Json

   $deployResponse = Invoke-RestMethod -Uri "$aiApiUrl/v2/lm/deployments" -Method Post   -Headers @{Authorization="Bearer $accessToken";"AI-ResourceGroup"="default";"Content-Type"="application/json"}
     -Body $deployBody

   Returns the Deployment ID, status initially UNKNOWN/PENDING, reaches RUNNING after ~3-5 minutes.

   Note down this Deployment ID – you'll need it for Step 7a and later for the asapio.aiCoreDeploymentId Additional Property on the Destination (Step 9.1).

7. Check the Deployment Status

   $statusResponse = Invoke-RestMethod -Uri "$aiApiUrl/v2/lm/deployments/<DEPLOYMENT_ID>" -Method Get `
     -Headers @{Authorization="Bearer $accessToken";"AI-Resource-Group"="default"}
   $statusResponse.status

   7.1 Determine Which Model Is Actually Running Behind a Deployment

   Use this when you already have a Deployment ID (e.g. taken from an existing Destination's asapio.aiCoreDeploymentId) and need to confirm which model is actually deployed behind it – for example before filling in asapio.modelName on a Destination, or when auditing an unfamiliar deployment.

   Prerequisite: AUTH_URL, clientid, clientsecret, AI_API_URL from the AI Core Service Key (Step 2).

   $authUrl='<AUTH_URL>/oauth/token'
   $clientId='<clientid>'
   $clientSecret='<clientsecret>'   # single quotes, in case the secret contains a $
   $aiApiUrl='<AI_API_URL>'

   1. Get OAuth token

      $tokenResponse = Invoke-RestMethod -Uri $authUrl -Method Post   -ContentType 'application/x-www-form-urlencoded'
        -Body @{grant_type='client_credentials';client_id=$clientId;client_secret=$clientSecret}
      $accessToken = $tokenResponse.access_token

   2. Query the deployment

      $deployment = Invoke-RestMethod -Uri "$aiApiUrl/v2/lm/deployments/<DEPLOYMENT_ID>" -Method Get `
        -Headers @{Authorization="Bearer $accessToken";"AI-Resource-Group"="default"}
      $deployment.status

   3. Query the Configuration to see the model name that is actually deployed

      $config = Invoke-RestMethod -Uri "$aiApiUrl/v2/lm/configurations/$($deployment.configurationId)" -Method Get `
        -Headers @{Authorization="Bearer $accessToken";"AI-Resource-Group"="default"}
      $config.parameterBindings

   Result: $config.parameterBindings lists the deployed modelName (e.g. anthropic--claude-4.5-sonnet) and modelVersion. Enter this value in the asapio.modelName Additional Property on the corresponding AI Core Destination (see Step 9.1), that's the only place it needs to be set.

8. Call Claude (manual verification only)

   $invokeBody = @{
     anthropic_version = 'bedrock-2023-05-31'
     max_tokens = 100
     temperature = 0.2
     messages = @(@{role='user'; content='Your message here'})
   } | ConvertTo-Json -Depth 5

   $invokeResponse = Invoke-RestMethod -Uri "$aiApiUrl/v2/inference/deployments/<DEPLOYMENT_ID>/invoke" -Method Post   -Headers @{Authorization="Bearer $accessToken";"AI-ResourceGroup"="default";"Content-Type"="application/json"}
     -Body $invokeBody

9. Integration into the App (eventstudiocap – Destination-based)

   Adding, changing, or removing an AI Core or Langchain AI model like Claude requires only a Destination edit.

   9.1 Create the Destination

   Destination Details:

   Field	Value
   Name	e.g. AICoreDestination
   Type	HTTP
   URL	<AI_API_URL> (from step 2)
   Proxy Type	Internet
   Authentication	OAuth2ClientCredentials
   Token Service URL	<AUTH_URL> (/oauth/token from step 2)
   Client ID	<clientid> (from step 2)
   Client Secret	<clientsecret> (from Step 2)

   Additional Properties:

   Key	Value	Purpose
   asapio.aiDest	true	Flags this destination as an AI model, makes it appear in the chat model dropdown
   asapio.provider	aicore	Routes this destination through the AI Core invocation path instead of a direct-fetch provider
   asapio.modelName	e.g. claude-sonnet-aicore	Display name shown in the model dropdown (Destination → modelName). Determine the underlying deployed model with Step 7a before setting this.
   asapio.aiCoreDeploymentId	String deployment id	ID of the AI Core deployment created in step 6.
   asapio.aiCoreBackend	anthropic-bedrock	Only these values are valid: anthropic-bedrock (Claude), openai (OpenAI models), gemini (Gemini models) – depending on the deployed model.
   asapio.aiCoreResourceGroup	default	Sent as the AI-Resource-Group header on every /invoke call
   asapio.tokenDayLimit	e.g. 60000	App-internal daily token budget for this destination. Default value is always 60000 unless changed.

10. Check Function of AI Sidebar

    Check if the AI Sidebar is working.

11. Error Messages

    asapio.aiCoreResourceGroup property is not set:
    Error: AI destination 'AICoreDestination' is missing the asapio.aiCoreResourceGroup property. Please contact your BTP administrator to configure it.

    asapio.aiCoreDeploymentId property is not set:
    Error: AI destination 'AICoreDestination' is missing the asapio.aiCoreDeploymentId property. Please contact your BTP administrator to configure it.

    asapio.modelName property is not set:
    Error: AI destination 'AICoreDestination' is missing the asapio.modelName property. Please contact your BTP administrator to configure it.

Event Studio MCP Server

The ASAPIO Event Studio MCP server exposes Event Studio's core functionality — SAP outbound event/interface configuration, CDS view generation, and deployment — as tools an MCP-compatible AI client (Claude Desktop, Claude Code) can call directly. Instead of clicking through the Event Studio UI, a developer can describe what they want in natural language and have Claude create, inspect, filter, or deploy the underlying objects on their behalf.

Role collections

The following role collections must be assigned to the user in relevant BTP subaccount.

Example: Connect from Claude Desktop

How to connect it in Claude Desktop:

1. Open Claude Desktop and go to Customize > Connectors (or Settings > Connectors, depending on your version).
2. Find "ASAPIO Event Studio MCP", press the Connect button and follow the prompts to authenticate/connect (use your IAS tenant).
3. If the MCP is not in the list, click the "+" button, then "Add custom connector."
4. Enter a name (e.g. "ASAPIO Event Studio MCP") and the server URL for your instance – this is your own Event Studio deployment URL from your BTP tenant, not a URL provided by ASAPIO.
5. Click "Add," then follow the prompts to authenticate/connect.
6. Once connected, you can enable it per-conversation from the same Connectors menu, and Claude will be able to call its tools directly in chat.

Monitoring

The Monitoring page tracks system activity for a specified time range. Use the From and To timestamp fields and click Go to refresh results. Select any entry in the results table to show the corresponding request and response traces at the bottom of the page. Traces can be downloaded for further analysis.

Help

The Help page displays the current Event Studio release version along with links to documentation and user guidelines.

Troubleshooting

If the application is running but data is missing on one or more pages, follow these steps:

Backend System

• Check packages: In SE80, verify that /ASADEV/API_CONFIG and /ASADEV/API_EXT are present. If missing, re-import the transports.
• Confirm table data: In SE11, verify that tables /ASADEV/CTLG, /ASADEV/CTLG_LOG, and /ASADEV/CTLG_EVE exist and contain entries.
• ABAP dumps: Check ST22 for dumps related to /ASADEV/GW_CONFIG_API_SRV or /ASADEV/* classes.
• Authorization failures: Use SU53 to identify missing roles or permissions for the current user.
• OData service activation: In /IWFND/MAINT_SERVICE, confirm /ASADEV/GW_CONFIG_API_SRV is listed, activated, and has a system alias. Test the metadata endpoint in /IWFND/GW_CLIENT: /sap/opu/odata/asadev/GW_CONFIG_API_SRV/$metadata should return HTTP 200.
• OData error log: Check /IWFND/ERROR_LOG for service call errors.

If connected to multiple SAP systems, perform these checks for each system — a problem in one system can affect data visibility across the application.

Browser

• Open browser developer tools (F12), go to the Console tab, and look for errors with status codes 400, 403, or 500. Errors for Component.js or marked [FUTURE FATAL] can be ignored.
• Clear the browser cache or use Incognito/Private Mode after updating the application.

Cloud Foundry / BTP Specific

• MultiApps plugin missing: Symptom: 'deploy' is not a registered command. Install with cf install-plugin -f multiapps.
• Wrong org/space: Run cf target to verify, then cf target -o <org> -s <space> to correct.
• Backend data not loading: Verify the destination exists, has Proxy Type = OnPremise, Authentication = PrincipalPropagation, and asapio.eventStudioDest = true. Confirm Cloud Connector is connected to the same subaccount and the backend OData service is reachable.
• AI panel not available: Check that the user has the eventstudiocap_aiviewer role collection and that the AI destination has asapio.aiDest = true, a valid asapio.modelName, and the correct URL.headers.Authorization value.
• Principal propagation issues: Temporarily switch the destination authentication to Basic Authentication to confirm principal propagation is the root cause. Review authentication logs in SAP BTP and Cloud Identity Authentication (IDP) for failed SSO or JWT token exchanges.

If the issue persists, contact the ASAPIO support team with: a description of the issue, screenshots of error messages from the browser console or SAP GUI, steps already taken, and details about the system configuration or recent changes.