Skip to Content

Hoeffding Tree Overview – Creating a Scoring Project (Part 4)

Welcome to the final installment of the Hoeffding Tree machine learning series, where you build a streaming project in SAP HANA studio that can execute a scoring model. The fourth video is now available:

To see how we got here, check out the previous content:

  • Creating a Training Model (Part 1) – video and blog
  • Creating a Training Project (Part 2) – video and blog
  • Creating a Scoring Model (Part 3) – video and blog

Here’s a summary of part 4, and then a quick review of the series.


Part 4 involves creating and building a project that uses the scoring model you created earlier to predict if financial claims are likely to be fraudulent. The scoring model stream applies what it learned from the training data to make these predictions.

Like before, you’ll build the project using a CCL code snippet, and you’ll upload the financial claims data from a CSV file. You can download these from As mentioned in a previous blog post, the code in GitHub is not official SAP code, it is sample code that you’ll use for this tutorial series.

You can get your scoring data from the CLAIMS_SCORE.csv file. This file contains data from the input stream, ‘in1’, which includes:

  • ID,
  • policy type,
  • age of the claimant, and
  • department of the claimant.

Here’s a look at the data:

Before uploading this data, you need to create and build a project.

Creating and building a project

In studio or Web IDE, create a new project. Then, copy the CCL from the sha_hoeffding_score.ccl file and replace the default CCL in your project with the CCL you just copied.

The CCL structure is the same as what we saw in the training phase:

  1. Create the input and output schemas.
  2. Declare the model.
  3. Set the schemas and data service connection.
  4. Create any number of input and output streams you require. Again, one input stream needs to gather the data, and one output stream needs to execute the model.

Here’s what the CCL looks like:

CREATE SCHEMA schema_in (ID integer, POLICY string, AGE integer, AMOUNT integer, OCCUPATION string);
CREATE SCHEMA schema_out (ID integer, FRAUD string, PROBABILITY double);

DECLARE MODEL hoeffdingscore
 INPUT SCHEMA schema_in
 OUTPUT SCHEMA schema_out
 PROPERTIES dataservice = 'hanaservice' 

 SCHEMA schema_in 

 EXECUTE MODEL hoeffdingscore
 FROM in1 

 SELECT * FROM model_stream 

These input and output schemas mirror the schemas you used in the previous blog, where you created your scoring model. The ‘DECLARE MODEL’ statement sets the name of the model, the input and output schemas, and the data service. The input stream, ‘in1’, collects the scoring data, and the output stream, ‘model_stream’, collects this data from ‘in1’ and executes the scoring model. Another output stream, ‘out1’, collects all results. You can write ‘out1’ to a HANA table, or stream it to wherever you want.

Note: The names of the scoring model and data service must match the names in your landscape. For us, the model name is ‘hoeffdingscore’ and the data service name is ‘hanaservice’.

The project’s built, so now you can compile and run it on your workspace.

Once running, open the input and output streams so you can see the data when it uploads.

Uploading data and viewing the output

Via the File Upload view, browse for the CLAIMS_SCORE.csv file. Choose which project you want your input stream to be sent to by hitting the Select Project  button:

With the scoring file selected, hit Upload.

The input tab shows 5 rows:

The output tab shows the results. As seen below, none of the transactions are identified as being potentially fraudulent:

Thankfully, there’s nearly an 80 percent probability that the scoring model stream is correct with its predictions. But, if there were a fraudulent claim and you needed to know about it, then you could set up an alert system. All you’d have to do is filter fraudulent claims into a derived window and then use an adapter to output that info somewhere, like to a dashboard or email account. For details on generating alerts using a derived window, check out this tutorial.


To sum up this series, we began with the training phase where you created a training model and executed it in a project. This model is continually updated as new data arrives in the input stream. Next was the scoring phase, where you built a scoring model to score new data in a project. You used the training data to identify whether transactions are likely to be fraudulent or legitimate.

For more on machine learning models, check out the Model Management section of the Streaming Analytics Developer Guide. If you’re interested in creating machine learning models in Web IDE, then check out this blog post.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.