BetishOps
Observation platform

Context for your SAP ecosystem.

SAP Classic and BTP services, connected through context. Without confusing an SAP client with a cloud service identity.

SAP CLASSIC

System and client, without losing identity.

Observation of processes, errors, jobs and resources belongs to a precise technical context. Not all system data has client-level semantics; its scope must be stated.

Context hierarchy

Demo organizationDEMO-ERPClient 100
SAP BTP / INTEGRATION SUITE

Cloud services, explicit context.

Subaccount, service and connection identify cloud observations. An OAuth credential is not a business customer or an SAP client.

Cloud hierarchy

Organization›BTP›Subaccount›Service

Connecting SAP and BTP contexts requires explicit relationships. Similar names or coincident timing do not justify mixing identities or claiming causation.

Observation domains

Each source answers a question.

12 source groups

ST22

ABAP errors

Timestamp, program, error class and system context.

Which error appeared, and when?

SM37

Background jobs

Status, start, end and job duration.

Which jobs stopped or changed duration?

SM13

Update requests

Update-request status and context.

Are update requests pending or interrupted?

SM58

tRFC communication

Destination, status and age of pending units.

Where is pending work accumulating?

SMQ1 / SMQ2

qRFC queues

Direction, queue name, status and observed volume.

Is an inbound or outbound queue growing?

SM66

Work processes

Process activity and state by context.

How is processing activity changing?

SMLG

Logon groups

Groups, instances and distribution observations.

How is the observed load distributed?

ST06

Host resources

CPU, memory and available host measurements.

Which resource changed before degradation?

AL08

Sessions

Sessions and instances with observation scope and time.

Which activity pattern coincides with the event?

DBACOCKPIT

Database

Inventory and metrics according to the available interface and permissions.

What changed in database capacity or behavior?

SAP BTP

Subaccounts and services

Identity, resources and observations for authorized services.

Which cloud service and context need attention?

Integration Suite

Integration flows

Message status, time and technical identifiers.

Which messages fail, and how do they evolve?

This catalog presents observation domains. Available fields and history depend on the source interface, version, retention and authorization. A transaction name does not imply universal availability or authorize writes.

From your question to a demonstration

Let’s explore your operational context.

Let’s discuss your sources, your questions and the outcome you need. No credentials or sensitive data required.

Request a demonstration