Understanding SAP Sustainability Control Tower Architecture

Objective

After completing this lesson, you will be able to identify SAP Sustainability Control Tower Architecture.

SAP Sustainability Control Tower Architecture

SAP Sustainability Control Tower supports both systems-based and file-based integrations with various SAP and non-SAP data sources. The architecture of SAP Sustainability Control Tower supports inbound and outbound interfaces.

Inbound Interface

The inbound interface supports the following use cases:

  • Local CSV file upload via the Manage Quantitative ESG Data application.Qualitative data is entered manually in SAP Sustainability Control Tower.
  • Central replication service using SAP BTP destinations and authentication features.
  • Standard integrations of SAP S/4HANA Finance, SAP Datasphere, SAP EHS Management, and SAP Sustainability Footprint Management through OData interface/BTP destinations.
  • SAP BW integration through SAP Datasphere or OData interface.
  • Inbound API as OData interface for non-SAP source systems.
Inbound APIs allow external data sources, including both SAP and non-SAP systems, to send information directly into the SAP Sustainability Control Tower.

Outbound Interface

Utilizing an outbound API allows you to access and retrieve information about measures or metrics from the SAP Sustainability Control Tower database. This capability enables the design of customized displays and facilitates the integration of acquired data into your custom systems. SAP Sustainability Control Tower has predefined outbound APIs for:

Navigating through SAP Sustainability Control Tower Fiori launchpad

The video provides a walk through of SAP Sustainability Control Tower Fiori launchpad.

SAP Sustainability Control Tower is undergoing ongoing enhancements. Therefore, you may observe updated screens in the video in the next iteration of this training.

You can see an overview of these apps here. Overview of applications