Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Chris_Tam
Explorer
2,890

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




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

3 Comments
satya11719
Active Contributor
Thanks for the blog, it's really helpful.
hanish16
Explorer
0 Kudos
Thanks for the detailed blog, Chris.
Chris_Tam
Explorer
0 Kudos

Recently, my DSP system started to fail to connection to API Hub for these outbound Sustainability Metrics links. It turns out, some of the SSL certificates have changed on my DSP system and I had to reinstall them. To do the same:

- Go to: Import Certificates for SSL Connections to Remote Sources 

- Download the 2 DigiCert SSL certificates shown on that portion of the page

- Go to you DSP system and goto System | Configuration

- In the Security tab, you can add the new pem files that you've downloaded above. I named mine SAP HANA and SAP HANA Root as below.

Chris_Tam_0-1708490511362.png

That should be all, and you can try your Remote Table and Source as above.

 

 

Labels in this area