SAP BTP
for LuumenAI
Gateways, jobs, and subaccounts operated from one governed chat.
SAP estates carry the most consequential operations work — and the least tolerance for guesswork. LuumenAI reads job status, interface queues, and subaccount configuration from SAP BTP alongside host sessions and tickets, then runs restarts and configuration changes only as previewed, approved steps that are written to the audit log and linked to the change.
The SAP BTP toolbox
14 tools: 11 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadList subaccounts & servicesInventory of subaccounts, service instances, and bindings.
- ReadCheck job & interface statusBatch jobs, queues, and interface health without the console.
- ReadRead application logsRecent log lines for a service instance or app.
- Readget_connector_infoGet trust attestation about how this connector reaches SAP: API source, authentication method, access mode, persistence policy and which SAP services are wired.
- Readget_posture_scoreGet the overall BTP security posture score (0-100) plus per-domain scores for Security, Access, Connectivity and Resilience, with a band of ok/review/atrisk/critical.
- Readlist_destinationsList destination configurations with their name, URL, authentication type, proxy type and level (subaccount or instance).
- Readlist_entitlementsList service plan entitlement assignments for the subaccount — service name, plan, amount and remaining quota.
- Readlist_findingsList governance findings from the Luumen posture engine — one row per rule check across the Security, Access, Connectivity and Resilience domains, sorted most-urgent-first.
- Readlist_role_collectionsList XSUAA role collections with their descriptions, role references and assigned user counts.
- Readlist_subaccountsList BTP subaccounts with their display name, subdomain, region and state.
- Readsearch_audit_logSearch BTP audit log records within an explicit time window.
- WriteRestart application or jobRestart a stuck job or app as an approved, audited action. Approval by default
- WriteReload gateway configurationApply a reviewed configuration reload on a gateway. Approval by default
- WriteUpdate destination or bindingChange a destination or service binding with the diff shown first. Approval by default
One prompt, start to finish
What a governed SAP BTP run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — restart application or job, reload gateway configuration, update destination or binding — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
SAP BTP is available on the enterprise plan. Talk to us about enabling it for your account — the rest of the catalogue is available on every plan.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to SAP BTP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put SAP BTP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.