Skip to Content
Technical Articles
Author's profile photo Chris Tam

Getting ESG metrics from SAP Sustainability Control Tower

Extending my sustainability metrics

I’ve been anxiously waiting on the API Integration feature from SAP Sustainability Control Tower  (SCT) and with their 2023/04 release, I can finally start blending those sustainability metrics within SCT with the eGRID emissions factor data I have already stored in my SAP Datasphere.

However, there were a few hoops that I needed to jump through to get these systems connected.

Setting up my new entitlement

First up, I had to ensure that the new sct-service-api entitlement was allocated to my BTP subaccount. (This is also referred to later as the Instance as opposed to the Application that I already had installed).

I added this to the subaccount where I had SCT installed, but I also had to enable Cloud Foundry.


Subaccount entitlement

Creating a Cloud Foundry space to install the SCT Instance

Next, from that same subaccount, I had to create a cloud foundry space that would run this new instance.


Create a Cloud Foundry Space


With that complete, I created a new SCT instance from the Service Marketplace and set the Runtime Environment to the Cloud Foundry space above.


Create Service Instance in Cloud Foundry space


Once I saw the instance created in the subscriptions portion of my subaccount, it was simply a matter of creating a Service Key for that instance. (You can add Binding Parameters here as well, but I did not.)

From this newly created service key, I grabbed the clientID, clientsecret as well as the url which I would be using later in my SAP Datasphere connection.


Create Service Key for SCT Instance

Onward to SAP Datasphere connections

Finally, I turned my attention to SAP Datasphere where I created a connection in the same space as my eGRID emission factors data. Using the Generic OData connection type, I created this connection using the information available on SAP Business Accelerator Hub and the SCT instance above.


Creating a connection from SAP Datasphere

  • For the SCT systems in the Netherland’s datacenter, the URL for the Connection Detail was:
  • For the SCT systems in the US’ datacenter, the URL for the Connection Detail was:
  • The OAuth Token Endpoint is just the url from the service key with /oauth/token added to the end; the Client ID, and Client Secret are directly as copied

Time to explore!

Now within my SAP Datasphere data builder, I had access to all of the exposed metrics from the SCT package so I could start creating remote tables.


Data builder connecting to SCT

This OData connection can also be made directly within SAP Analytics Cloud but for me, it’s time to make some creative views on SAP Datasphere! For one, it’s a great staging area to blend and curate the data, and two, I can use the persistency feature that is native to Datasphere views to reduce the latency between my model’s data center and SCT’s data center.

Happy Exploring!


Datasphere model with SAC visualizations

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Satyanarayana Reddy Dondapati
      Satyanarayana Reddy Dondapati

      Thanks for the blog, it's really helpful.

      Author's profile photo Hanish Shan S
      Hanish Shan S

      Thanks for the detailed blog, Chris.