onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
Outside the atlasOutside the atlastypeA thing outside the atlas that something inside it depends on or talks to. It is named here so that the dependency or the connection can be an edge; it is not rated, not covered and never an artifact.See every one →

SAP BW/4HANA

SAP's data warehouse product for on-premise and private-cloud landscapes, optimised for the HANA database and installed rather than subscribed — the 2023 release is current, with its own master and upgrade guides. Outside the atlas because there is no adoption decision to model: you have a BW system or you do not, and what is entered here is the tooling that reaches one.

Open help.sap.comchecked

Where it sits

Kind
SAP solution

Used by3

bw-modeling-mcpindependently maintained

Dependency relationship. Every tool call reaches a live BW system through its modelling, ADT, manage and Push APIs; there is nothing to run against without one, on-premise, private cloud or BW Bridge.

Functional boundary

Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.

MBT Logical Object Listerindependently maintained

Optionally used: the object model being displayed is SAP BW/4HANA's; the README names SAP BW and SAP BPC as the alternatives The system whose object model metadata it displays, and the system it is itself deployed into with the MBT Installer.

Modernization Agents for SAP on AWSby a partner

Optionally used: The BW modernization use case runs against an SAP BW/4HANA system The warehouse whose objects the BW agent moves; the compatibility table names BW/4HANA 1.0 and 2.0, and SAP BW from 7.4 SP9.

Functional boundary

There is nothing to clone here: "Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation", and that repository answers 404 to anyone who has not registered, so neither the agent code nor the deployment guides can be read before the form is filled in. AWS states the agents are published as an unsupported solution, with customers responsible for testing and securing the code before deploying in production, and that they are intended for non-production SAP environments rather than production systems. The documentation link in the README is still a placeholder.

Details

Graph3
← POINTS HERE
dependency ofbw-modeling-mcp
optionally used byMBT Logical Object Lister
optionally used byModernization Agents for SAP on AWS
POINTS OUT →
nothing yet
For your agent
Ref
external:sap-bw4hana
JSON
/externals/sap-bw4hana.json
MCP
Connecting an agent