Hey everyone,
Following my last blog post (SAPPHIRE 2024 – My impressions and vision on what is ahead for us), I want to dive into something crucial that SAP needs to address ASAP: Groundings. Let me explain why this is so important.
What Are Groundings?
In the world of Generative AI (GenAI), one of the key building blocks is Groundings, also known as knowledge bases. Groundings enable a technique called RAG (Retrieval Augmented Generation) to expand the knowledge of a Large Language Model (LLM). Here’s why this matters:
- LLM Data Cutoff: LLMs have a cutoff date for the data they can access. They know a lot up to a certain date, but not beyond.
- Limited Knowledge on Private Data: LLMs might lack information on personal or company-specific data.
- Specific Application Data: Sometimes, you need to add very specific application data that LLMs don’t know.
With RAG, we query vector databases to pre-select semantically related information and pass it to the LLM for additional context. This process is hugely beneficial.
The Need for SAP to Build Groundings
While we’re all working on building our own groundings, there are some that SAP should create and publish. Here are the most pressing ones I can think of:
- HELP.SAP.COM: Groundings on help.sap would allow us to create chatbots that can easily answer user queries. This is likely a foundation grounding of Joule, but we all need this. Handling different versions and products is a challenge, but it’s workable. Groundings should be created by product/version.
- SAP Training Documentation: This is more complex due to the variety of data types, but incredibly valuable. It extends far beyond what HELP.SAP covers.
- ABAP (or Other Technical) Documentation: While SAP has mentioned working on a fine-tuned LLM version, a grounding with numerous referenceable examples would greatly improve quality. Current LLM-generated ABAP examples often display questionable examples.
- SAP API Documentation: Detailed explanations on the function and usage of all SAP APIs would be an incredible addition for functional, ABAP, and integration developers. "Is there an API to perform X?" "How do I call this particular API?"
- S/4 Data Model: Though more complex to structure, a grounding with all SAP tables, their descriptions, and relations to supporting tables would be beneficial. Utilizing the CDS views repository could be a starting point. "How do I determine delivery status for sales order items?"
- COMMUNITY.SAP.COM: There’s a wealth of great content in blogs and forum conversations that could be turned into groundings.
- SAP Support Tickets: While sensitive, anonymized support tickets could be made available to customers and partners, significantly reducing support costs across the ecosystem. I’d be willing to pay for that.
How SAP Can Make Groundings Available
SAP could build and offer these groundings in several ways:
- For Free: Some of it could be offered for free. 🙂
- GenAI Hub: Groundings could be integrated into the GenAI Hub, increasing the platform’s value.
- Licensed Access: Groundings could be licensed and charged based on access, allowing consumption anywhere.
Conclusion
These are just a few examples of the groundings SAP could develop to enhance our tools and workflows. It’s time for SAP to step up and help us all achieve more with GenAI.
Tchau for now!
Leo
