Since it's been awhile - I figured I give you an update on the SAP integration with the retirement aggregator.
At a high level - this integration prioritizes real time carbon retirements made in fiat. This is to avoid the complexities of large companies having to track digital asset price movements in their general ledger.
For the very technically inclined - the SAP ABAP source code of the MVP that was showcased in the Carbonmark webinar last August is made available here:
https://github.com/fleischr/carbonmark-sapabap-demo
This is ABAP source code developed from an on-premise SAP system - however given there was an earlier consideration to develop the SAP integration MVP using the RESTful ABAP Programming Model (RAP) this repo should largely be compatible also with the cloud-based / clean-core Steampunk ABAP environments. Getting a proper SAP environment to run this example in can be tricky. On-premise SAP systems are pretty costly to self-administer - so for most solo builders/tinkerers I recommend setting up access to an ABAP steampunk trial account. I have a guide that includes instructions on for that here: https://github.com/fleischr/abap-eclipse-guide.
I'd be thrilled to get more help with people familiarish enough with ABAP and abapGit to try pulling the repo so we can smooth out onboarding to this resource in any remaining ways necessary.
ABAP is a COBOL-ish language with some object oriented features. While ABAP is entirely unfamiliar to most in web3 - the reality is that the majority of the world's b2b and b2g commerce happens between companies using SAP systems to track the finances and supply chain. And that means from that place you are pretty close data and system wise where to calculate emissions. And it didn't surprise me at all when earlier in 2023 when we saw SAP announce
the "Green ledger" for tracking emissions to the same precision as financial units of account. That's a product/capability still emerging. But still - its pretty neat we have to the power to get KlimaDAO in the mix there!
This application in particular extends on a popular developer test scenario known as SFLIGHT. A rudimentary set of emissions calculations are performed on the sample flight data - and from that those emissions can be offset via KlimaDAO.
This repo presently requires usage of the provide-abap SDK and Provide APIs. However - there are incoming changes for the Carbonmark API generally that will mitigate those technical dependencies. There will be changes to this repo that instead use a more straightforward client id / client secret configured into 'communication arrangements' as Carbonmark API shifts into a more vendor-neutral standard model here in the near future
Regardless who you are - I'm always happy to help you get started with ABAP with this or other resources. It's a great skill to have if you've been looking for a good big boy/big girl IRL job. ABAP is not the only way to integrate / extend SAP in scenarios like this though. The latest trends have been to develop using Node.js and Java in the SAP Business Technology Platform (BTP) which supports several kinds of cloud environments (AWS, Azure, GCP, Alibaba Cloud, etc). There are other unique considerations for building deploying apps to SAP BTP which I don't have time to get into here - but overall any node.js /API examples produced by the Carbonmark team should be feasible for use in SAP BTP.
A big thank you again to the KlimaDAO / Carbonmark folks that supported me in the past year with this. Anytime you need some insight on enterprise like this, hmu!