SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

teched2025-DA266

SAP TechEd 2025 session material for two SAP Databricks scenarios in SAP Business Data Cloud: cashflow forecasting and payment-delay prediction with SHAP explanations.

Guided Exercise notebooks with matching Solution notebooks, numbered to be followed in order, for two scenarios run inside SAP Databricks in SAP Business Data Cloud. The cashflow scenario shares a cashflow data product from S/4HANA into the workspace, prepares the data, trains a time-series forecast and applies it, then re-shares the enriched data product to the BDC data catalogue with sap-bdc-connect-sdk, with MLflow listed for monitoring query performance. The payment-delay scenario determines the key drivers of a delay through SHAP values, optimises hyperparameters with xgboost, configures SAP AI Core orchestration services to turn the drivers into a human-readable explanation, and wraps the model as an MLflow PyFunc model for monitoring and logging. The prerequisites are an administrator's: two Unity Catalog catalogs with write access, the two shared data products, an SAP AI Core service instance with its key, two Python packages and a secret scope.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Predictive modelsBTPPredictive modelscapabilityTraining, deploying and calling a model that predicts a value from tabular business data: a classification, a regression, a forecast. Distinct from [LLM integration](capability:llm-integration), where a language model generates text, even where both run on the same service.LLM integrationBTPLLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.
Requires
DatabricksDatabricksoutside the atlasthe workspace the notebooks are imported into and run in, reached from the Business Data Cloud cockpit's system landscape page.SAP Business Data CloudSAP Business Data Cloudartifactwhere the two data products are shared from and the enriched one is published back to; its cockpit is the way into the workspace.SAP AI CoreSAP AI Coreartifactthe orchestration services the payment-delay scenario calls for the human-readable explanation; a service instance and its key have to exist.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222
@SAP-samples
maintainerAjay SorengPersonContributes to this
In the atlas: contributes to 36
@ajaysoreng
Ajinkya PatilPersonContributes to this
In the atlas: contributes to 112
@ajinkyapatil8190
chantakkuenPersonContributes to this
In the atlas: contributes to 1
@chantakkuen
San TranPersonContributes to this
In the atlas: contributes to 1
@d031182
Neetha PucknatPersonContributes to this
In the atlas: contributes to 2
@neethapucknat
5 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
Workshop or CodeJam material

Connections5

README

quoted from SAP-samples/teched2025-DA266 under Apache-2.0, read
SAP-samples/teched2025-DA266/README.mdOn GitHub

REUSE status

DA266 - Operationalizing AI with SAP Databricks in SAP Business Data Cloud

Description

This repository contains the material for the SAP TechEd 2025 session called DA266-Operationalizing AI with SAP Databricks in SAP Business Data Cloud. It covers end-to-end workflows and scripts for two main user case scenarios Cashflow Prediction and Payment Delay Prediction. The repository is organized to support both learning (Exercise) and reference (Solution) use cases, with each scenario broken down into modular notebooks that guide you through the data science lifecycle.

Tip

  1. Download this github repository, you will need to upload the files into your SAP Databricks workspace
  2. Login the SAP Databricks instance, and apply the setups steps
  3. Start with the Exercise notebooks to follow the guided workflow and implement each step yourself.
  4. Refer to the Solution notebooks for completed code and best practices.
  5. Follow the notebook order (as indicated by the numbering) for a logical progression from data understanding to publishing a data product.

Loging SAP Databricks instance and first setups

  1. Users and Password for SAP Databricks

  2. Access to SAP Business Data Cloud Cockpit: https://trial-bdc-core-3.eu10.hcs.cloud.sap/

  3. In the System Landscape page click on the SAP Databricks link to access the instance. The url link for that should be: https://accounts.cloud.databricks.com/select-workspace?account_id=779c1dfb-54a0-4c0b-ab10-657b3ea0e70b

  4. Login with the provided user creditials.

  5. Before running the exercises, navigate to the Unity Catalog and check in the My organization for the following catalogs:

    • uc_cash_liquidity_forecast
    • uc_delayed_payments

    Furthermore, you will find in the Received Deltas Shares the shared data products from SAP Business Data Cloud:

    • Cashflow
    • Entry View Journal Entry
    • python_environment
  6. Download this github repository into your local PC.

  7. To import the notebook, navigate to your own folder (same as the user email assigned to you) under the Workspace> Users tab. In the whitespace, right-click or use the context menu and select Import. Then import the file in question from your system's File Explorer.

    • import_notebook
  8. For the Python environment the exercises have been run with the python v5 which is the latest version. Note: Please check for each notebook if you have the environment set properly!

    • python_environment
  9. Please note, that in the exercises you will be asked to create in the catalog a <SCHEMA>, to have a clear separation of the exercise artefacts. The <SCHEMA> will follow the pattern <catalog_name>.dsag+<last_2_digits_of_user>.

    • e.g. user ac285809u01 will create correspondingly the schemas

      • uc_cash_liquidity_forecast.dsag01
      • uc_delayed_payments.dsag01

      unity_catalog_schema

Requirements

Following pre-requisites should have been already prepared by the system administrator:

  • Unity Catalog with 2 predefined catalogs with read and write access for all users:
    • uc_cash_liquidity_forecast
    • uc_delayed_payments
  • The following SAP Data Products are shared and accessible by all users:
    • Cashflow
    • Entry View Journal Entry
  • Appropriate permissions for all users to create schema within the above mentioned catalogs
  • Access to a configured SAP AI Core Service intance with corresponding service key
  • Access to required Python packages
    • sap-bdc-connect-sdk
    • sap-ai-sdk-gen
  • Configured SECRET SCOPE
    • This step has already been done by the administrator to facilitate the sharing process. However, if you need to do it on you own you can follow the steps described here to create a secret scope: To create a secret scope you can either use the following URL https://<databricks-instance>#secrets/createScope. Replace <databricks-instance> with the workspace URL of your Databricks deployment.
    • Alternatively, you can run the following command in the terminal by clicking on the terminal icon on the lower right corner: databricks secrets create-scope sap-bdc-connect-sdk.
    • The secret scope only has to be created once and can be made accessible to all workspace users by either toggling manage principal to all workspace users or via the terminal using the following command databricks secrets put-acl sap-bdc-connect-sdk users READ. To check whether the assignment worked, you can then use the command databricks secrets list-acls sap-bdc-connect-sdk.
    • A full explanation can be found here https://docs.databricks.com/aws/en/security/secrets/example-secret-workflow

Exercises

Contributing

Please read the CONTRIBUTING.md to understand the contribution guidelines.

Code of Conduct

Please read the SAP Open Source Code of Conduct.

How to obtain support

Support for the content in this repository is available during the actual time of the online session for which this content has been designed. Otherwise, you may request support via the Issues tab.

License

Copyright (c) 2024 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/teched2025-DA266tree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, ai-and-agents
Contributors5

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-teched2025-da266
JSON
/artifacts/sap-samples-teched2025-da266.json
MCP
Connecting an agent