FLP Chat Communication Channel Setup
The Fiori Launchpad Chat Plugin enhances the SAP Fiori Launchpad with an integrated AI-powered chat assistant.
Key Features
Section titled “Key Features”1. Custom UI Control
The plugin is built using a custom SAPUI5 control called AiDialog, located in the controls directory. This control is responsible for managing the chat interface and handling user interactions.
2. Dynamic Messaging
The chat supports both user-generated and AI-generated messages with flexible formatting options. It allows multiple message types, with text messages rendered via Markdown-to-HTML conversion and displayed using sap.m.FormattedText (htmlText).
Supported Markdown elements include headings, bold and italic text, links, inline code and code blocks, ordered and unordered lists, and line breaks.
Note: Markdown tables are not rendered as HTML tables—they appear as list items instead.
3. Cross-Application Navigation
The plugin enables navigation across SAP Fiori applications. URLs starting with # trigger internal navigation within the Launchpad (e.g. #SalesOrder-display?ObjectKey=123), while external URLs (without #) open in a new browser tab.
4. Adaptive Cards Support
The plugin supports Microsoft Adaptive Cards for rendering rich, structured messages. Cards are processed using the formatAdaptiveCard function and rendered via widgets:Card. This enables advanced UI elements such as forms, layouts, and interactive components. After the user submits a card, it keeps the entered values and hides its submit buttons; see Submitted cards in the FLP Chat.
Supported Message Types
Section titled “Supported Message Types”The plugin currently supports the following message types:
- Text – Markdown-rendered messages displayed via sap.m.FormattedText
- Buttons – Supports multiple interaction types:
- web_url: internal navigation (URLs starting with #) or external links (open in a new tab)
- postback: sends predefined responses to the chatbot
- trigger_skill: triggers specific chatbot skills or workflows
- Media & Structured Content:
- picture: displays images
- quickReplies: provides selectable quick response options
- card: displays structured card content
- carousel: displays multiple cards in a scrollable view
- list: displays structured lists
- Client Data:
- client_data (adaptive_card): enables Adaptive Card rendering
- Adaptive Card – native support for Microsoft Adaptive Cards
Incomplete Message Type Support
Section titled “Incomplete Message Type Support”The following message types are not yet implemented:
client_data: calendar, client_data: close_chat
Channel Creation
Section titled “Channel Creation”Step 1. Open the _AI Agent Configurato_r application in the AI Agent group.

Step 2. After opening the application, you will see a screen displaying all available AI Agents. Each tile represents one Agent, including its name, description, and deployment status. Click on the Agent you want to work with to proceed.

Step 3. Open the Channel management application- Communication Channels.

Step 4. Channel creation.
You can create a new Channel from scratch or Copy the Existing Channel.
To create a new Channel, click the Create button:

Step 5. Initial Parameters
Fill in the initial parameters for the new Channel. The form includes:
- Channel Name — follow your organization’s naming convention.
- Channel ID — this field is auto-generated.
- Channel Type — select from a list of available types (e.g., Webchat, Microsoft, Telegram).


Step 6. Channel Settings.
To configure additional Channel Settings for your FLP Chat Channel, click the Edit button.

Survey
Section titled “Survey”Survey ID — select a previously created survey form from the drop-down menu.
Send Survey Automatically — choose either Off or When chat ended.
Identity Provider
Section titled “Identity Provider”Identity Provider Application: choose the Identity Provider application from the list. This must be configured beforehand in the Identity Providers Application (see: Identity Providers)
Memory Retention Policy
Section titled “Memory Retention Policy”Retention time — specify the number of days for which chat data will be stored. After this period, the system automatically deletes stored conversation data according to your retention rules.
Communication Protocol
Section titled “Communication Protocol”FLP Chat uses WebSocket as its communication protocol to support real-time, bidirectional messaging between the Fiori Launchpad and the backend services.
Step 7. Tools Activation
Once your Channel is created, you can activate or deactivate tools defined within your AI Agent.
For more information, visit: Tools Activation.
Step 8. Destination Assignment
This setting allows you to assign destinations to tools that have backend-connected actions.
For more information, visit: Destination Assignment.
Step 9. Access Your FLP Chat
To access your FLP Chat, access your Fiori Launchpad.
After logging in, click the chat icon in the Fiori Launchpad to open the chat interface.
Only the users you choose in Choose Who Sees the FLP Chat see the chat icon.


The chat icon is the Skybuffer AI logo. How it looks depends on the launchpad header of your SAPUI5 version:
- In the classic launchpad header, as in the pictures above, the logo is in color.
- In the newer launchpad header of recent SAPUI5 versions, the logo is in one color and matches the other header icons, as in the picture below.
- If the launchpad cannot show the logo, the chat icon is the standard SAP AI icon. The chat works the same. See Troubleshooting.
![]()
Setting Up the Connection to the AI Model
Section titled “Setting Up the Connection to the AI Model”To enable the FLP Chat channel on the backend, you must maintain its configuration in the SAP Object Navigator.
Step 1. Open Object Navigator (SE80)

Step 2. Navigate to the configuration table: /SKYBFR/YAIC_LVL

Step 3. Locate the row corresponding to your Channel ID

Maintain the following fields:
CHANNEL_ID — the identifier of the FLP Chat channel that you configured in the UI.
WSS_URL — the WebSocket Secure endpoint used for real-time communication.
This URL must point to the active WebSocket server instance.
The backend uses this entry to link the FLP chat front-end configuration with the WebSocket messaging infrastructure.
External API Integration
Section titled “External API Integration”The plugin provides a public API that allows other Fiori applications to interact with the chat.
Key capabilities:
- Send messages to the chat from external applications
- Open or control the chat dialog programmatically
- React to chat lifecycle events via EventBus
The API is exposed via the global object: window.SkybufferAiChat
This enables integration of chat-driven workflows across applications.
Post-Installation Activities
Section titled “Post-Installation Activities”After transporting and configuring the Fiori Launchpad Chat Plugin and ABAP Push Channel, the following steps must be completed to ensure proper functionality.
Step 1. Activate Required Services
Section titled “Step 1. Activate Required Services”To enable the plugin and ensure correct backend communication, you must activate the necessary services in transaction SICF.
Activate the following services:
/sap/bc/ui5_ui5/skybfr/yai_lc
(UI5 application service)
/sap/bc/bsp/skybfr/yai_lc
(BSP application service)
/sap/bc/apc/skybfr/yai_lc_flp
(ABAP Push Channel WebSocket service)
Any additional services within the /skybfr namespace, depending on your specific implementation scenario.
Step 2. Choose Who Sees the FLP Chat
Section titled “Step 2. Choose Who Sees the FLP Chat”Use a role to choose which users see the FLP Chat in the Fiori Launchpad, for example when only some organizations or user groups in a shared system use it. Skybuffer delivers the launchpad catalog /SKYBFR/YAI_BC_LC, which adds the FLP Chat to the launchpad, and the role template /SKYBFR/YAI_BR_LC, which contains this catalog. You copy the template to a new role in your own namespace and assign the new role to the users who should see the chat.
An SAP administrator does these steps in the system where your Fiori Launchpad runs.
Step 1. Start transaction PFCG, enter the role /SKYBFR/YAI_BR_LC and click Copy role. Enter a name for the new role in your own namespace and click Copy all.
Step 2. Open the new role in change mode. On the Menu tab, check that the role contains the launchpad catalog /SKYBFR/YAI_BC_LC, Skybuffer AI - Launchpad Chat Plugin.

Step 3. On the Authorizations tab, click Change Authorization Data. Adjust the authorization values to your security rules, click Generate, and save the role.
Step 4. On the User tab, enter the users who should see the FLP Chat, and save the role. Then run the user master comparison with transaction PFUD.
Step 5. Start transaction /UI2/FLP_SYS_CONF and open Launchpad Plug-Ins. If the list contains the plug-in ZSKYBFRYAILC, set its Activity State to Disabled and save. An active entry loads the FLP Chat for every launchpad user, and the role has no effect.

/UI2/FLP_SYS_CONF applies to the whole system. The client settings in /UI2/FLP_CUS_CONF and the user settings in /UI2/FLP_USER_CONF override it, so check them for the same entry.
Step 6. Run transactions /UI2/INVALIDATE_GLOBAL_CACHES and /UI2/INVALIDATE_CLIENT_CACHES so that the launchpad uses the new settings.
Step 7. Check the result in a private browser window. A normal window can keep showing the chat icon from its cache.
Log on to the Fiori Launchpad as a user with the new role. The chat icon is in the launchpad header, next to the search icon.
![]()
Log on as a user without the role. The chat icon is not there.
![]()
If the result is different, see Troubleshooting.
Troubleshooting
Section titled “Troubleshooting”After each change described below, run /UI2/INVALIDATE_GLOBAL_CACHES and /UI2/INVALIDATE_CLIENT_CACHES, and test again in a private browser window.
The chat icon is shown to users without the role
Section titled “The chat icon is shown to users without the role”Test again in a private browser window: a normal window can show the icon from its cache. If the icon is still there, find out how the chat is loaded for the user. Log on as the user, open the browser console (F12) and run:
console.log(Object.keys((window["sap-ushell-config"] || {}).bootstrapPlugins || {}), "| loaded:", !!window.SkybufferAiChat);ZSKYBFRYAILCin the output: the launchpad configuration loads the chat for all users. SetZSKYBFRYAILCto Disabled in/UI2/FLP_SYS_CONF, and check/UI2/FLP_CUS_CONFand/UI2/FLP_USER_CONFfor the same entry.X-SAP-UI2-CATALOGPAGE:<catalog>:<id>in the output: one of the user’s roles contains a launchpad catalog that loads the chat. If it is not/SKYBFR/YAI_BC_LC, the user gets the chat through another role. Run transaction/UI2/FLCfor the user to identify the catalog.
The chat icon is missing for a user with the role
Section titled “The chat icon is missing for a user with the role”Check that:
- the profile of the role is generated;
PFUDran after you assigned the user to the role;- the service
/sap/bc/ui5_ui5/skybfr/yai_lc, which the launchpad catalog points to, is active inSICF. See Step 1. Activate Required Services.
The chat icon shows the SAP AI icon instead of the Skybuffer AI logo
Section titled “The chat icon shows the SAP AI icon instead of the Skybuffer AI logo”The chat works the same with this icon. In the newer launchpad header, the plugin shows the SAP AI icon when it could not load the Skybuffer AI logo within a second, for example on a slow connection. It also shows it when your SAPUI5 version does not let the plugin use its own icon in the header.
Reload the launchpad page to load the logo again. If the SAP AI icon is still there, your SAPUI5 version is the cause, and the chat icon stays the SAP AI icon.