Technology Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 

With Datasphere, AIs tend to use the full HANA functionality, but only a limited set of HANA functions is available in Datasphere.

With SAC it is even more difficult, as AIs tend to use a standard JavaScript approach, whereas SAC uses its own APIs and coding. But now we have built-in AI-assisted generation of SQL in Datasphere and JavaScript in SAC. The SAC feature has been available since June 2026, while the Datasphere feature came out just before TechEd.

So how does it work? Activate it for free and use it :). As with SAC’s assisted JavaScript generation, no AI Units are consumed.

In Datasphere, just drag and drop the objects you would like to use in the new SQL. Then write down what you need. The difference from J4C or Claude is that you no longer need to feed in the metadata (burning input tokens to provide the context), because Joule is already grounded.

Made a mistake while dragging and dropping? No problem. Remember, Joule is already grounded and automatically fetches the correct source object.

Don’t know which keys to use? No problem. Joule has access to the metadata and is a fully trained LLM for SQL, so just tell it to join whatever it sees fit.

Of course, as with any AI, a human needs to stay in the loop!

This feature makes ETL development fun. I can concentrate on delivering the solution instead of wasting time on missing commas, misspellings, incorrect joins, ...

 

Martin_Kuma_1-1793786572109.png

Martin_Kuma_3-1793786718180.png

 

https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/1b3fe45f38df4db1a9cda97a5a...

https://help.sap.com/docs/SAP_DATASPHERE/c8a54ee704e94e15926551293243fd1d/d1530656d42f44f68b6265666e...

https://www.sap.com/norway/products/technology-platform/datasphere-sql-generation.html?tab=technical...

Martin_Kuma_0-1793786512387.png

 

 

 

4 Comments
appel_solar_dk
Active Participant

Hi Martin

Yes, but no. I have only tried a few times, and it is not working out for me. If you know your SQL then it will typically be faster to simply write it all on your own, as describing what you need is more wordy than the select statement. Also if your data model is a bit out of the ordinary then Joule don't understand and will suggest weird things (e.g. joining af customer number on a adress ID as they both have length 10). Additional small details like WEEK versus ISOWEEK is apparently missed. Have you tried to see if Joule "understands" the semantics of a table like VBFA (the document flow) with custom document types or the table with business partners on sales documents?

The day where Joule know my data model then it will be better, when it tells me that I'm missing a table to make it work or it's asking me if we should handle null values in the output. But at the moment it's just not ready for really helping out, unless you already have a pretty good idea about what it is you want and then there is no point.

Kristian

Martin_Kuma
Active Contributor

Hi Kristian, 

yes as with any AI. The same applies to Joule. I am more comparing Joule to Claude. What I observed on project via vibe-coding from the very same developers (I mean different approaches). I feel Joule would provide a more coherent overall approach for all developers, not just for the one. 

No, I did not try with VBFA, nor WEEK vs. ISOWEEK. Thanks for the info. 

Martin

 

MKreitlein
Active Contributor

Hello @Martin_Kuma 

thanks for your Blog 🙂 ... only one question: Are these "embedded AI features" in SAP Datasphere (and SAC) really "Joule" or is it just an "embedded AI feature"?

I mean, in 2025 I saw Partner Webinars where those features have really been shown in a Joule window... but this year, especially from the Discovery Center e.g. for SAC: https://discovery-center.cloud.sap/serviceCatalog/sap-analytics-cloud/?region=all&tab=relatedaioffer... it seems it is no longer related to Joule, since you als find here Smart Predict, Smart Predict etc. which have never been a Joule function, plus, Joule in S4 Public for example will (I guess) never be able to execute those DSP and SAC tasks.

For me, it is definitely not Joule or Joule related since, like you said, we can just activate it.

BR, Martin

Martin_Kuma
Active Contributor

@MKreitlein You are correct Martin! Seems that the underlying engine is not Joule, but Generative AI Hub... 

Martin_Kuma_0-1794391892290.png

Joule is inactive as it needs AI Units. Even in Joule and J4C news, nothing about AI Assisted SQL for Datasphere exists.

https://help.sap.com/whats-new/762ba6531c9948ab9785aa76c8e9c21d

 

 

Labels in this area