SAP Community - SAP Business Technology Platform

Building multitenant SaaS solutions with SAP Build: A partner's guide to innovate for scale

2026-02-18T09:00:00.017000+01:00

Building a SaaS solution is exciting. Building one that scales cleanly across customers without breaking the core? That’s where things get interesting.

In our upcoming webinar, “Building multitenant SaaS solutions with SAP Build: A partner's guide to innovate for scale,” we’ll walk through how you can design, deploy, and commercialize multitenant applications on SAP Business Technology Platform while staying true to clean core principles with SAP Build.

We’ll cover the real journey, from architecture and ERP-agnostic design to pricing models, provisioning, and cost structures for dev, test, demo, and production. Plus, we’ll connect the dots between technical decisions and commercial impact.

Honestly, multitenancy isn’t just a technical choice. It’s a business multiplier. One code line. Multiple customers. Controlled extensions. Stronger margins.

Whether you’re in the SAP PartnerEdge Open Ecosystem or a Build partner refining your portfolio, this session is designed to give you clarity and confidence.

Register now and start building for scale, the smart way. https://partneredge.sap.com/en/library/education/psd/2026/feb/e_oe_te_w_PSD_WEB_00013076.html

#SAP #SAPBTP #SAPBuild #SaaS #SAPPartners #CleanCore

SAP Commodity Management: Driving the Bottom Line with Precision Expense Control

2026-02-18T11:54:47.782000+01:00

In commodity trading, third-party expenses are not merely overheads; they are critical factors that significantly influence the profitability of trading activities. Costs such as demurrage, brokerage, throughput charges, insurance, and tank cleaning, when not managed precisely, can lead to margin and revenue leakage. While SAP’s native capabilities offer robust expense management, the unique and dynamic requirements of commodity supply chains, including the need to track costs throughout the entire deal and contract lifecycle, necessitate a specialized approach.

To address these industry-specific challenges, we are thrilled to have launched SAP Commodity Expense Management, as part of S/4HANA 2025. This new product is purpose-built as an application on SAP Business Technology Platform (BTP), designed specifically for commodity organizations to provide focused, industry-relevant expense management, all supported by dedicated and intuitive Fiori Apps delivering enhanced usability.

The solution delivers several key benefits:

Increased Automation: Leverages automation rules defined in Expense Master Data, automatic defaulting of expenses during planning and automated accrual reversals and adjustments.
Enhanced Integration and Visibility: Provides cross-company visibility of expenses across multiple document types from capture to settlement.
Improved Data Accuracy: Reduces the risk of margin and revenue leakage through better expense planning and integrated reporting.

SAP Commodity Expense Management offers a comprehensive suite of capabilities, ensuring granular control and enhanced visibility over commodity-related costs across both Energy and Agri industries:

Expense Setup & Configuration: This feature provides tools to define the fundamental structure of your expenses. It allows for the setup of various expense types, units of measure (UoMs), currencies, and account mapping. Users can configure automation rules, mass update expense rates, and maintain essential posting assignments for both accrual and settlement processes. Furthermore, the solution offers extensibility with flexibility to define attributes for determining templates and expense rates, along with APIs for mass upload of these rates.
Expense Planning: Essential for proactive cost management, this capability supports both automatic and manual expense planning. Expenses can be planned during deal capture, contract creation, nomination, and Agricultural Contract Management Application Document items, allowing for iterative expense updates throughout the process. The system facilitates defaulting of expenses based on predefined automation rules and allows tracking of overrides and manual additions at various stages. It offers the ability to determine expenses using customer-specific attributes during Deal Capture.
Expense Accrual: This function handles the recognition of liabilities for services received. Accruals can be created and adjusted based on key events such as Deal Publish, Contract Approval, Nomination Confirmation, and ACM Application Documents/Ticketing. It includes features for automatic accrual reversals, automatic accrual on ticket corrections, and the ability to split and collate accruals for complex scenarios. Accrual postings are integrated during delivery execution.
Expense Settlement: Designed to streamline the payment process, this feature supports invoice verification and the settlement of both planned and unplanned expenses, distinct from core commodity contract settlements. It allows for correction of service provider and invoice amounts and provides for the recovery of expenses from contract or deal counterparties. An API is available to capture Expense Settlement, and it includes tax code determination for accurate financial postings. Settlement postings are integrated into the accounting process.

By bringing precision, automation, and comprehensive visibility to third-party costs, SAP Commodity Expense Management empowers organizations to transform expenses from a potential liability into a strategic advantage. Don’t let unmanaged costs erode your profitability; embrace the future of commodity expense control. We invite you to explore the capabilities further by visiting the SAP Help Portal and Roadmap Explorer (links below).

Visit SAP Help Portal for more an Administration Guide: https://help.sap.com/docs/CCS/7b6b503b6ae0446fb3d6801c98f56b1e/2fe3a2ae04e74a598c8c39f73b4710e3.html?locale=en-US&version=LATEST

Stay tuned for future innovations by following SAP Roadmap Explorer for Commodity Management: https://roadmaps.sap.com/board?PRODUCT=42F2E964F4E71EDAA6A3587248CD40E5&range=CURRENT-LAST

Unlocking the business value of SAP Business Data Cloud - BDC value framework

2026-02-18T16:00:00.023000+01:00

Features are easy. Value wins deals.

In “Unlocking the business value of SAP Business Data Cloud – BDC value framework,” we go straight to what matters: turning SAP Business Data Cloud into a quantified, strategic business case.

You’ll get:
✔ A structured Value Framework linking capabilities to real business drivers
✔ A Value Calculator to put numbers behind the story
✔ A maturity assessment that exposes process gaps and sparks opportunity

No fluff. Just practical tools you can use in your very next customer conversation.

The difference between “interesting” and “compelling” often comes down to one thing: clarity around impact. Let’s sharpen that edge together.

#SAP #SAPBTP #SAPEcosystem #SAPBDC #PartnerSuccess #ValueSelling #BusinessTransformation

Harnessing SAP BW data product generator for BW modernization with SAP Business Data Cloud

2026-02-19T09:00:00.014000+01:00

Many of our customers have invested years in building robust SAP BW landscapes. The question we keep hearing is: how do we modernize without starting from scratch?

In our upcoming webinar, Harnessing SAP BW data product generator for BW modernization with SAP Business Data Cloud, we’ll explore how the SAP BW data product generator, part of SAP Business Data Cloud, helps you transform existing BW assets into reusable data products, quickly and intelligently.

Think of it as turning well-organized shelves in BW into ready-to-serve data packages for cloud innovation. No heavy lifting. No wasted value.

We’ll walk through prerequisites, roles, system requirements, plus a live demo showing exactly how to create and activate data products step by step. And yes, we’ll leave space for real questions in an open Q&A.

If you’re in pre-sales, delivery, or architecture, this session will help you accelerate BW modernization conversations with confidence.

Register now and secure your spot. https://partneredge.sap.com/en/library/education/psd/2025/jun/e_oe_te_w_PSD_WEB_00010566.html

#SAP #SAPPartners #SAPBusinessDataCloud #SAPBW #DataModernization #SAPBTP

Master Blog: B2B Integration with SAP Integration Suite

2026-02-19T10:22:28.687000+01:00

Introduction

B2B integration plays a critical role in enabling seamless and reliable data exchange between enterprises and their business partners. As integration landscapes grow in scale and complexity, standardized B2B capabilities become essential to ensure secure connectivity, partner onboarding, message validation, monitoring, and operational resilience.

This master blog serves as a technical reference hub for B2B Integration Factory, consolidating all related blog posts in one place to support integration architects and developers in designing, implementing, and operating scalable and governed B2B integration scenarios with SAP Integration Suite.

If you are interested in deepening your knowledge of B2B integration using SAP Integration Suite, we recommend our free learning course. This comprehensive course offers detailed explanations of each B2B capability and includes hands-on exercises with an example end-to-end B2B scenario. You can access it here: SAP Learning: Manage B2B Scenarios Effectively with SAP Integration Suite.

B2B Integration Factory

B2B integration Factory’s services & integration packages

B2B Integration Factory services to unlock the power of SAP Integration Suite's B2B capabilities

B2B Integration Factory – B2B related Integration Packages with your Custom Extensions

B2B Integration Factory: What is Pre-packaged B2B Integration Content, and what is this used for?

B2B Integration Factory's Role and Value Adds in t... - SAP Community

B2B Integration Factory Q4/2024 Release highlights - SAP Community

First release of B2B Integration Factory – Integration Packages and their Extensions

SAP Migration Factory for Integration Suite – FAQ - SAP Community

The importance of B2B Monitoring in customer's day... - SAP Community

VDA Automotive Flat File Processing with B2B Integ... - SAP Community

B2B integration scenarios

Blog posts describing end-to-end B2B integration scenarios using IA, TPM and CPI

B2B data exchange using Trading Partner Management... - SAP Community

B2B Scenario Sender EDI to IDOC - SAP Community

Bridging EDI and SAP S/4HANA Cloud: Seamless EDI-t... - SAP Community

Completing the B2B migration into SAP Integration ... - SAP Community

Creating MIGs and MAGs Using Integration Advisor i... - SAP Community

How to build custom B2B Interface using Integratio... - SAP Community

Inbound Interface: EDI → SAP BTP (Integration Suit... - SAP Community

Real-Time XML to EDI Conversion: A Step-by-Step CP... - SAP Community

SAP BTP - Integration Advisor - (MIG & MAG) from a... - SAP Community

SAP Integration Suite - TPM - B2B PassThrough Scen... - SAP Community

Streamlining B2B Integration with AI-Powered SAP C... - SAP Community

Use TPM, IA, CI to Efficiently Manage and Run Comp... - SAP Community

Integration Advisor

Blog posts focusing only on IA

Beginner's Guide to Integration Advisor - SAP Community

Base-/Overlay Mappings for Integration Advisor - SAP Community

Creating MIGs and MAGs Using Integration Advisor i... - SAP Community

Integration Advisor – Automotive EDIFACT Subsets (... - SAP Community

Integration Advisor – change in namespace handling... - SAP Community

Integration Advisor: complex mapping code for dime... - SAP Community

Integration Advisor – Create 1:1 Mapping Elements ... - SAP Community

Integration Advisor – Download MAG Simulation Resu... - SAP Community

Integration Advisor – GS1 XML Messages and Namespa... - SAP Community

Integration Advisor – GS1 XML Messages of the vers... - SAP Community

Integration Advisor – direct support of EDI payloa... - SAP Community

Integration Advisor: Early UN/EDIFACT Versions wit... - SAP Community

Integration Advisor – extended support for Custom ... - SAP Community

Integration Advisor – Extended semantic validation... - SAP Community

Integration Advisor: Functions at target side - Or... - SAP Community

Integration Advisor - List of supported XSLT eleme... - SAP Community

Integration Advisor – Mapping element functions, t... - SAP Community

Integration Advisor – Mapping element functions fo... - SAP Community

Integration Advisor – MAG: How to create If-Then-E... - SAP Community

Integration Advisor – MIG Qualification based on m... - SAP Community

Integration Advisor – multi-payload support for MI... - SAP Community

Integration Advisor – new B2B Library content for ... - SAP Community

Integration Advisor – Now GS1 EANCOM Library avail... - SAP Community

Integration Advisor – Odette Message Standard - SAP Community

Integration Advisor: Overview of components for bu... - SAP Community

Integration Advisor – payload-based qualification ... - SAP Community

Integration Advisor - Quickly create your individu... - SAP Community

Integration Advisor - support for multi-value Qual... - SAP Community

Integration Advisor – Support of xCBL Messages - SAP Community

Integration Advisor – Tradacoms Message Standard - SAP Community

Integration Advisor – Use Custom XSLT as MAG - SAP Community

Integration Advisor: Using the Pre-Transformation ... - SAP Community

integration content advisor: Create a customized i... - SAP Community

integration content advisor: Create a mapping usin... - SAP Community

integration content advisor: The importance of cus... - SAP Community

How to Provide Read-only Access to Integration Adv... - SAP Community

Restoring the hierarchical order of a flattened so... - SAP Community

SAP BTP - IS - ( IA | CPI ) - The Commander's Blue... - SAP Community

Support for ASC X12 Subsets (VICS etc.) in Integra... - SAP Community

Streamlining B2B Integration with AI-Powered SAP C... - SAP Community

Taming the X12 856 message in SAP Integration Advi... - SAP Community

Using EDI Envelopes in Integration Advisor - SAP Community

Trading Partner Management

Blog posts focusing only on TPM

Archiving B2B Messages from SAP Integration Suite ... - SAP Community

B2B data exchange using Trading Partner Management... - SAP Community

Custom Message Mapping - TPM - B2B - SAP Integrati... - SAP Community

Custom Search Attributes in SAP B2B - SAP Community

Integrating Cloud Application Lifecyle Management ... - SAP Community

Guide for migrating PI/PO B2B mappings to Integrat... - SAP Community

Reusing SAP PI/PO B2B mapping content in Cloud Int... - SAP Community

SAP Cloud Integration : B2B - Restart/Retry Messag... - SAP Community

SAP Trading Partner Management - Part I: TPM overv... - SAP Community

SAP Trading Partner Management - Part II: Data - SAP Community

SAP Trading Partner Management - Part III: Partner... - SAP Community

SAP Trading Partner Management - Part IV: Agreemen... - SAP Community

SAP Cloud Integration - Trading Partner Management... - SAP Community

Troubleshooting SAP BTP TPM: Debugging Step 1b and... - SAP Community

Using Trading Partner Management with AI - SAP Community

Summary

This collection brings together key insights, best practices, and technical deep dives on B2B integration using SAP Integration Factory, helping you design, implement, and optimize your B2B integration landscape. If you feel a relevant topic or blog post is missing, please let us know in the comments—we’re happy to expand the list and keep this collection current and comprehensive.

SAP BTP ABAP Environment - Release 2602

2026-02-19T10:47:10.350000+01:00

SAP BTP ABAP Environment - Release 2602

On February 14, the new 2602 release was delivered as the successor to the 2511 release. In this blog post, we provide a detailed overview of the new features and enhancements included in this release, highlighting the key improvements and innovations introduced with 2602. Some highlights in the new release include the My Home as your new personalized entry page in SAP Fiori Launchpad, the CDS Embedded Analytics Star Schema Generator and the RAP recommendations for input assistance based on the user input and interaction history.

The list of all new features including more information can be found on the What's New for SAP BTP ABAP environment page. The new AI-related features are listed separately on the What's New for ABAP Generative AI in ABAP Cloud.

ABAP Development Tools (ADT)

New Grouping Option Effect on transports in ATC Problems View
ABAP Testability: Enhancements to Test Double Frameworks (details)
Global User ID for ATC Exemptions
Displaying the Used Objects of CDS Service Definitions in the Relation Explorer

ABAP RESTful Application Programming Model (RAP)

Collaborative Draft, now also works in cross-business object scenarios if both business objects are collaborative draft-enabled, and if the cross-business object scenario is fully draft scope-enabled (details)
Recommendations, previously, business users had to fill out input fields manually and choose the right values. The new RAP recommendations standardize and ease this process: In RAP applications on an SAP Fiori user interface, RAP recommendations provide input assistance by proposing field values for input fields based on the user input and interaction history. RAP recommendations can be implemented using deterministic rules or using generative AI, which predicts the most likely values for each input field based on the context of the data. By integrating the ABAP AI SDK powered by Intelligent Scenario Lifecycle Management, you can embed AI capabilities into the application, enriching traditional value help with context-aware suggestions (details)
Embedded Analytics Star Schema Generator, the Star Schema Generator Wizard streamlines the creation of star schema models using ABAP Core Data Services. It empowers you to build comprehensive analytical models with ease. This tool guides you through the entire generation process, ensuring a consistent and efficient workflow. The wizard supports the following key components: Transactional Scenario, Analytical Cube and Dimension Views (details)

Identity and Access Management

IAM App Assignment: So far, it was only possible to assign access to Fiori apps to business users indirectly via business catalogs. Now, it's also possible to directly create business roles based on IAM apps for SAP-delivered business catalogs
Maintain Business Roles, you can now directly assign IAM apps in the Maintain Business Roles app. This supports you in handling authorizations more flexibly. You can also use the Mass Change Wizard if you need to add or remove multiple IAM apps at once (details)
App References, the following apps now contain references to IAM apps: Maintain Business Roles, Manage Business Role, Changes After Upgrade, Display Restriction Types, Business Catalogs, Business Role Templates, IAM Information System (details)
Information System, the main entity Application is now deprecated. The successor will be the IAM app, which is now contained in the Main Entity dropdown list (details)
App Authorization Variant, you can now use the IAM app of the App Authorization Variant type. This gives you more flexibility in managing restrictions because it allows you to activate or deactivate app authorization variants to define different access rights per business role (details)

Manage API Snapshots

As a provider for released APIs, you can now download and upload API snapshots using the Manage API Snapshots app. This way, you can download API snapshots from the test system and upload them in the development system, thus preventing incompatible changes to your released objects early in the development process (details)

SAP Fiori Launchpad

My Home in SAP BTP ABAP environment
Launching an App with a Transaction Code (details)
Download and Upload of Spaces
Removal of Business Groups

Landscape Portal

Publish Product: Publish up to Two Product Versions (details)
Deploy Product: System multi-select supported and performance improved (details)

Infrastructure

Optional Integration with SAP Key Management Service, SAP BTP ABAP environment provides an optional integration with the SAP Key Management Service (KMS). With this integration, it's possible to manage the SAP HANA Cloud database of an ABAP environment instance via SAP KMS (details)

Best practices and guidelines in SAP Integration Suite

2026-02-19T16:00:00.019000+01:00

Let’s be real. Integration can either feel like elegant orchestration… or controlled chaos.

That’s why we’re hosting “Best practices and guidelines in SAP Integration Suite”. This session goes beyond theory. We’ll explore how SAP Cloud Integration (CPI) fits into modern enterprise architecture and how to apply recommended integration patterns across SAP-to-SAP, SAP-to-non-SAP, and hybrid scenarios.

Plus, we’ll dive into the details that actually matter in projects: secure connectivity, smart scripting, message processing, monitoring, and alerting. The stuff that keeps your integrations stable at 2 a.m. when no one wants surprises.

Think of it like designing highways between systems. Good design means smooth traffic. Poor design? Bottlenecks everywhere.

If you’re building or optimizing integrations for customers, this session will give you clarity and confidence.

Register now and let’s build integrations that scale with purpose. https://partneredge.sap.com/en/library/education/psd/2026/feb/e_oe_te_w_PSD_WEB_00013114.html

#SAP #SAPBTP #SAPIntegrationSuite #SAPCloudIntegration #SAPPartners #DigitalTransformation #HybridIntegration

Where Your Ideas Shape SAP BTP: Become Part of the SAP Customer Engagement Initiative 2026-1

2026-02-19T16:02:40.549000+01:00

SAP Business Technology Platform is reshaping how organizations innovate. By unifying application development, automation, data and analytics, integration, and AI, it empowers businesses to build smarter, more efficient, and more adaptable solutions.

Now, you can help shape what comes next.

Cycle 1 of the SAP Customer Engagement Initiative for 2026 is now open, giving you as SAP customers and partners the opportunity to directly influence the future of SAP BTP. Collaborate with SAP product teams and developers, share feedback early, and help guide upcoming capabilities and improvements.

This isn’t just early insight - it’s your chance to impact the direction of enterprise technology.

Registration is open until March 13, 2026.

Check out the full list here or follow the links below to discover the exciting opportunities:

Let’s shape the future together!

Innovation happens through collaboration. By participating in the SAP Customer Engagement Initiative projects, you help SAP create better, more relevant solutions for businesses like yours. This is your chance to influence what comes next.

Don’t miss out – sign up today at influence.sap.com and be a part of the SAP Customer Engagement Initiative Cycle 1 in 2026!

Warm regards,
Your SAP Customer Engagement Initiative Team

Follow-up after registration: When you register for a project, you will be invited to an introductory call with the SAP project lead. At this point further participation is optional. Typically, all activities are governed by the Feedback Agreement with SAP.

SAP Developer News, February 19th, 2026

2026-02-19T21:10:00.016000+01:00

DESCRIPTION

SAP Developer Insights Survey

The 2026 SAP Developer Insights Survey is live now: https://sapinsights.eu.qualtrics.com/jfe/form/SV_9prRAJk5ccYPMMe
2025 Survey Report: https://community.sap.com/t5/technology-blog-posts-by-sap/the-2025-developer-insights-survey-the-report/ba-p/14323198

SAP RPT-1 Beta Available in the SAP Cloud SDK for AI

SAP RPT-1 (Beta): https://sap.github.io/ai-sdk/docs/js/rpt

SAP CodeJams in Australia and New Zealand

SAP CodeJam Group: https://groups.community.sap.com/t5/sap-codejam/gh-p/code-jam

SAP BTP, ABAP Environment Customer and Partner Roundtable

Event Details: https://community.sap.com/t5/technology-blog-posts-by-sap/live-demos-at-the-sap-btp-abap-environment-customer-amp-partner-roundtable/ba-p/14328427

Did You Know #4: Released Object in ABAP Development Tools

More Details: https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/7e27832a2d494e0b98359a7f1c6edefe.html?locale=en-US

CHAPTER TITLES

0:00 Intro

0:10 SAP Developer Insights Survey

0:44 SAP RPT-1 Beta available in the SAP Cloud SDK for AI

1:17 SAP CodeJams in Australia and New Zealand

3:15 SAP BTP, ABAP Environment Customer and Partner Roundtable

4:07 DYK 4 Released Object in ADT

Transcription

00;00;00;00 - 00;00;05;06
Announcer Guy
This is the SAP Developer News for February 19th, 2026.

00;00;05;09 - 00;00;09;22
Riley Rainey
Developers and SAP's annual Developer Insight survey has started live this

00;00;09;26 - 00;00;35;28
Riley Rainey
past Monday. You can get warmed up for it by reviewing Mamikee's blog posts in community. It's a complete report of the 2025 survey, contains all the data and also some key findings. There's tidbits on AI, popular frameworks help learning. It's all there. Have a look. This year we also have questions diving even deeper into those AI topics, we're keen to understand how you and your colleagues have been using AI for development in the past year.

00;00;36;01 - 00;00;44;26
Riley Rainey
We have links to the blog post and the survey in the section below. As always, your participation is key, so go check it all out. Thank you very much.

00;00;44;29 - 00;01;11;04
Kevin Riedelsheimer
The team behind the SAP cloud SDK for AI, released a new package to support the SAP Rapid-1 model. This package allows you to create a client to interface with the relational pre-trained transformer model. The package can simply be installed via npm, and is also currently only available for JavaScript. In case you haven't heard yet, but the Rapid-1 delivers accurate predictive insights from structured business data.

00;01;11;06 - 00;01;17;24
Kevin Riedelsheimer
This feature is currently in beta, but what are you waiting for? Try it out today.

00;01;17;27 - 00;01;19;02
Shilpa Shankar
We are live from

00;01;19;04 - 00;01;20;05
Rekha D R
Sydney.

00;01;20;07 - 00;01;21;04
Shilpa Shankar
Melbourne.

00;01;21;06 - 00;01;22;13
Rekha D R
Brisbane.

00;01;22;16 - 00;01;23;19
Shilpa Shankar
Auckland.

00;01;23;22 - 00;01;49;03
Shilpa Shankar
Hello SAP Community. We are in the second week of Australia New Zealand Roadshow and we just wrapped up ABAP Cloud CodeJam in this beautiful city of Auckland in New Zealand. We had lots of fun and lots of, technical discussions and ABAP Cloud topic because as many customers are moving to S/4 HANA and the feedback was tremendous.

00;01;49;05 - 00;01;57;07
Shilpa Shankar
Tomorrow we have another CodeJam related to Joule Studio in Auckland itself. Rekha can you highlight, what happened in Australia?

00;01;57;10 - 00;02;28;06
Rekha D R
Yeah, sure. So we started our week one in Australia, and we did, three CodeJams on Joule Studio topic. We started with Sydney and then we moved to Melbourne and then to Brisbane. There is a beautiful community, like all very technical people there. And we got to, try hands on with the customers and partners. And there is a very good response for Joule studio, product there.

00;02;28;09 - 00;02;54;28
Rekha D R
The community is very much excited for the, Joule and Joule Studio product and, yeah. And, in Brisbane we wrapped up, our, Australia trip with, SAP Stamtish (Meetup) with, wonderful SAP community, local community. So this way we had, lots of learning, lots of engagements with customers and partners. It was great, Shilpa.

00;02;55;01 - 00;03;14;09
Shilpa Shankar
Yeah, the local community meetup was good to meet, many local developers, in Brisbane. And, in case if you are interested to host, this CodeJam, you know what to do. Go to community.sap.com, go to SAP CodeJam group and then leave a discussion. We will get back to you. Thank you.

00;03;14;10 - 00;03;16;28
Rekha D R
Thank you. See Ya!

00;03;17;00 - 00;03;44;08
Mamikee Kanneh
Hi, everyone. Quick heads up. If you're working with SAP BTP, ABAP environment, the next Customer and partner roundtable is happening on March 3rd, 2026, from 10 a.m. to 11 a.m. CET. This roundtable is a part of a monthly series that takes place on the first Tuesday of every month, and it's a great opportunity to stay up to date with the latest products, insights, updates, and live demos directly from the SAP team.

00;03;44;10 - 00;04;09;11
Mamikee Kanneh
They also publish everything centrally on SAP community, including the agendas, the slides, the recordings and updates from the past and current sessions. So it's a great resource even if you can't attend live now. If you want the full details and the link to join. Check out the blog post in the link below to learn more.

00;04;09;13 - 00;04;37;28
Shilpa Shankar
Did you know that released objects that are available for developer extensibility are displayed in the Project Explorer of ABAP Development Tools under Released Objects in ADT. Open the context menu of an ABAP project and choose new ABAP Repository Tree. This allows you to create a new tree and filter for released objects. You can expand the tree by various options such as application component, package, API state and so on.

00;04;38;00 - 00;04;44;21
Shilpa Shankar
All the released development objects will be grouped accordingly. Under the properties tab you can check the release contract.

How to Integrate ABAP Composite Roles in SAP Build Work Zone

2026-02-20T10:22:56.337000+01:00

When you're integrating launchpad content from SAP S/4HANA or SAP S/4HANA Cloud Private Edition to SAP Build Work Zone and have an existing role model built on composite roles in your ABAP system, you've likely encountered the challenge of efficiently exposing these roles. The good news is there are two ways to expose composite roles from your ABAP backend to Work Zone, using the Common Data Model (CDM) content exposure. In this post we will break down what your options are, each with distinct technical implications.

Option 1: Direct Exposure of Composite Roles

With this approach, you select the composite role itself for exposure in the ABAP transaction /UI2/CDM3_EXP_SCOPE (Launchpad Content Exposure to SAP BTP). The content of all underlying single roles is aggregated into the selected composite role, which is then exposed as single role to SAP BTP.

Key points

The consumer (Work Zone) sees the composite role as a single, unified role containing all the launchpad content of its component single roles.
The individual single roles inside the composite are not exposed separately.
Should you require separate access to the single roles beyond the unified composite role, you'll need to manually include each single role in the exposure selection.
Exposed roles are available in the BTP cockpit and can be assigned to users. However, IPS can optionally be used to automate role collection assignments and reduce administrative effort.
Direct exposure is available since SAP S/4HANA and SAP S/4HANA Cloud Private Edition release 2023 or release 2022 with note 3325870

Option 2: Indirect Exposure via Single Roles (with IPS)

The second approach keeps your original role structure and the IPS ensures correct user to role assignment between the ABAP system and BTP.
You select only the single roles which contain launchpad content for exposure in /UI2/CDM3_EXP_SCOPE (not the composite role itself).
During content calculation, the system checks whether these single roles belong to any composite roles. If they do, it includes a reference to this relation in the exposed CDM content. The composite role itself is not exposed to Work Zone.

IPS handles the role assignment logic, ensuring users with composite roles get the correct roles assigned on BTP side.

Key points

Each exposed single role includes information about its composite role relationships, but those composite roles are not directly available in the Content Manager on BTP.
The Identity Provisioning Service (IPS) ensures that when an user is assigned to a composite role in ABAP, all required single roles (now exposed) are assigned in Work Zone/BTP. For further information see Configure Integration with the Identity Provisioning Service and Exploring Role Assignments

If you expose only some single roles from a composite role, any other single roles within that composite are not automatically included. Users will only see apps from the exposed single roles in Work Zone not the full composite role content.

Indirect exposure is available since SAP S/4HANA and SAP S/4HANA Cloud Private Edition release 2022.

Next Steps

Both approaches are technically valid and work with CDM exposure version 1 and version 2.

If you're invested in IPS-driven provisioning the indirect approach gives you flexibility for Work Zone integration by keeping the existing role structure and automated user to role provisioning. Without IPS you have the option to directly expose composite roles and maintain user to role assignment on BTP side.

In any case avoid creating dedicated roles solely for exposure purposes. Instead, use the same roles that are actively used by your local entry point (SAP Fiori Launchpad). This ensures consistency between your on-premise and cloud experiences, reduces administrative overhead, and maintains a single source of truth for your role-based content model.

How SAP ESM + Document AI + S/4HANA Work Together to Automate Invoice Processing End‑to‑End

2026-02-20T18:58:48.723000+01:00

One of the most powerful capabilities in SAP Enterprise Service Management (ESM) is its ability to automate invoice processing the moment a customer or vendor sends an email. With SAP Document Information Extraction (Document AI) integrated into ESM, the journey from a raw invoice PDF to a validated posting in SAP S/4HANA Private or Public Edition becomes almost fully automated.

Click on Image to view High Quality

Step 1: The User Sends an Email with an Invoice

A customer or vendor sends an email to the SAP ESM dedicated email address configured for automatic case creation.

The invoice may be:

Attached as a PDF, JPEG, PNG, or
Embedded in the email body itself

SAP ESM picks up both.

Step 2: SAP ESM Automatically Creates a Case

Once the email reaches the ESM mailbox:

A new case is created automatically
The email body and all attachments are stored within the case
The attachments (PDFs, images) trigger SAP Document AI processing immediately

This eliminates manual case creation entirely.

Step 3: SAP Document AI Processes the Invoice

SAP Document AI retrieves the attachment from the case and begins extraction using OCR and machine learning.

It identifies:

Invoice number
Customer or vendor name
Address
Line items
Totals & taxes
Payment terms
Contract or PO references

Document AI also calculates a confidence score for each extracted field.
These scores help determine whether the data is reliable enough to auto‑post or requires user intervention.

Step 4: Validation Using Business Rules & Customer Framework

Once extraction is complete, SAP ESM applies:

Business rules
Customer validation frameworks
Mapping logic
Master data checks

These validations are essential before communicating with S/4HANA.

Examples:

Is the customer known in S/4?
Is the invoice number valid and not duplicated?
Does the PO exist?
Do line item totals match?

Only when the validations pass does ESM proceed to the next step.

Step 5: Invoice Number & Customer Auto‑Identification

If Document AI finds the invoice number, SAP ESM updates the line items and case fields:

invoiceNumber → updated
customerNumber → auto‑identified
isClearing → set according to logic (e.g., invoice found, ready to post)

This gives the ESM user immediate visibility:

Has the system recognized the invoice?
Has the customer been identified?
Is the invoice ready for posting?

Step 6: ESM Sends the Validated Invoice to S/4HANA via OData APIs

Once the case has all mandatory and validated data, the ESM user can trigger the next action:

“Post Invoice to S/4”

At this point:

ESM calls S/4HANA OData APIs
A draft or final FI invoice is created
Additional steps like clearing, matching, or workflow approvals occur inside S/4

This hands-off process ensures:

No manual entry in S/4
No data inconsistencies
Full auditability from source → document → posting

Step 7: ESM User Monitors and Completes the Process

Inside the ESM case, the user can now see:

Status of the posting
Document number returned from S/4
Any errors (e.g., master data inconsistencies)
New actions available for follow-up

They can then:

Update the customer
Add missing reference information
Re-trigger the posting
Close the case once processing is complete

Result: A Fully Streamlined, AI‑Driven Invoice Workflow

By integrating SAP ESM, Document AI, and S/4HANA, organizations benefit from:

✔ Zero manual invoice entry

✔ Auto-identification of customers and invoice data

✔ Early error detection using business rules

✔ Faster posting to S/4HANA

✔ End-to-end transparency in one central case

✔ Higher accuracy and reduced effort

This modernizes invoice handling from a traditionally manual process into an intelligent, automated workflow.

Learning Journey : Business Documents in ESM

When Business Asks for a Bicycle, Don't Build a Spaceship

2026-02-21T19:02:14.003000+01:00

When Business Asks for a Bicycle, Don't Build a Spaceship

I have developed a comprehensive playbook demonstrating how modern SAP tools and AI can deliver solutions in DAYS instead of MONTHS.

The shocking math:
- Traditional approach: 6 months, $650K in delayed value
- SAP tools + AI: 1 week, $25K in delayed value

This isn't just theory—it's a practical guide that covers:
- CDS Views for data modeling
- CAP for service generation
- Fiori Elements for instant UIs
- Integration Suite for connectivity
- AI to accelerate everything

https://www.linkedin.com/posts/rajesh-putumbaka-456267101_sap-btp-ai-development-playbook-ugcPost-7431029390173696001-y7Yn?utm_source=share&utm_medium=member_desktop&rcm=ACoAABnYP8IBvlY4GDRmR8utVFLHXZ61gUvSa-0
Download the full playbook (PDF attached) and share your thoughts: Have you encountered the "perfect is the enemy of good" trap in your SAP projects?
#SAP #DigitalTransformation #AI #SAPCommunity

Action Required: Update your certificate trust stores for enhanced SAP HANA Cloud security

2026-02-23T10:10:00.017000+01:00

To enhance the security of our cloud services, SAP is updating the root certificate authority (CA) for various services, including the SAP BTP, Cloud Foundry environment, SAP BTP, ABAP environment, and SAP HANA Cloud. We are transitioning our server certificates signed by DigiCert Global Root G2 and G1/G5 cross-signed CAs to the newer and more secure "DigiCert TLS RSA4096 Root G5" CA, as DigiCert will stop signing new server certificates with the old root certificate.

This change is necessary to align with the latest industry security standards and recommendations, which call for stronger cryptographic keys. The new G5 certificate chain uses RSA-4096, providing a higher level of security for your connections.

What Does This Mean for You?

If you have client applications or services that connect to SAP HANA Cloud, you may need to take action to ensure a seamless transition and avoid connection failures.

Call to Action: Review the official notes and update your Trust Stores as needed

To prevent any disruption to your services, it is crucial that you update the trust stores for your client applications and services, as needed. Please review the officially provided SAP notes, giving more guidance:

SAP Note 3397584: HANA Cloud Connections will switch from "DigiCert Global Root CA" to "DigiCert TLS RSA4096 Root G5"
SAP Note 3399573: HANA Cloud Switch of DigiCert Root Certificate

Rollout Timeline

The switch to the G5 root CA for existing SAP HANA Cloud regions is planned for the second quarter of this year. The timeline for your landscape will be communicated via established communication channels begin of March. This blog post will also be updated with further information once available.

Further Information and References

As the root certificate change is not only impacting SAP HANA Cloud usage, but also other SAP BTP services, we highly recommend reviewing the below mentioned references/notes, to ensure the highest degree of business continuity:

SAP Note 3566727: Root Certificate Replacement in the SAP BTP, Cloud Foundry Environment
Blog Post: SAP BTP Cloud Foundry: Switching to higher security level Root Certificate Authority
Blog Post: SAP BTP ABAP Environment – New Root Certificate Authority
GitHub: SAP BTP Trust Store

To ensure your applications continue to operate smoothly and securely, we suggest you take the necessary steps to update your trust stores as soon as possible.

Thanks,

Meet Your Ops Agents - Powered by SAP Automation Pilot and Joule

2026-02-23T11:10:00.063000+01:00

Building on our latest innovation around SAP Automation Pilot and AI-powered IT Operations, I am excited to share that we are already seeing real productive use cases for Day-2 Operations Agents which are powered by SAP Automation Pilot content and consumed directly in Joule in a truly agentic manner.

🎥 Meet Your Ops Agent

See an example about Ops Agent powered by SAP Automation Pilot and discover how easy it is to set up an MCP server, expose automations, and trigger them in an agentic way through Joule.

This approach unlocks a completely new way to ops automation where AI agents can reason, execute, and orchestrate operational tasks seamlessly following customers requests and needs.

The demonstration walks through a scenario about an S/4HANA Health Monitoring Ops Agent in Joule, designed to:

Provide system health & diagnostics insights;
Perform automated analysis & deliver actionable recommendations;
Proactively send alerts when potential issues are detected;

📖Just the beginning

There is an unlimited range of Ops Agent scenarios enabled through SAP Automation Pilot, including for example:

SAP BTP Operations (e.g. Cloud Foundry applications, SAP HANA Cloud, SAP cTMS, etc.);
SAP Build and Day 2 Operations for your apps;
SAP Integration Suite checks and actions via automated API calls;
Integrations with custom solutions;
And many more …

Stay tuned as we will be revealing more real-life agentic operations scenarios in the coming weeks.

🚀 Get involved: Join Our Customer Engagement Initiative

If you would like to bring your own automation scenario and experience first-hand the AI-driven operations capabilities of SAP Automation Pilot and Joule, join our Customer Engagement Initiative: Agentic AI Operations with SAP Automation Pilot

⏳Registration is open until March 15, 2026 - secure your spot soon!

Learn More

If you would like to explore MCP servers in more detail or start using them in your own landscapes, please check out the SAP Automation Pilot official documentation which provides further insights:

Looking forward to collaborating and shaping the future of agentic IT operations together.

Leading with SAP Business Data Cloud innovation and roadmap

2026-02-23T16:00:00.021000+01:00

At SAP, innovation only matters if it helps you lead better customer conversations.

That’s exactly why we’re hosting “Leading with SAP Business Data Cloud innovation and roadmap.”

In this session, we’ll unpack the strategy behind SAP Business Data Cloud, walk through the technical architecture, and spotlight the innovations announced at SAP Sapphire. Not just what’s new, but why it matters when you’re in front of a customer navigating complex data landscapes.

The thing is, customers don’t ask for “architecture diagrams”. They ask how to simplify fragmented data, reduce risk, and move faster. We’ll help you connect those challenges directly to SAP BDC capabilities, so you can step in as a trusted advisor, not just a product expert.

Plus, we’ll cover roadmap direction and key product areas to help you guide the start of your customer’s data management journey with confidence.

Join us. Bring your questions. Leave ready to lead.

Register now. https://partneredge.sap.com/en/library/education/psd/2025/dec/e_oe_te_w_PSD_WEB_00010744.html

#SAP #SAPBTP #SAPPartners #SAPBusinessDataCloud #SAPSapphire #DataStrategy #PartnerEnablement

Gregor Wolf

2026-02-23T18:24:58.182000+01:00

About Gregor

Germany | SAP Mentor since 2007 | Follow Gregor on LinkedIn

I am an independent SAP solution architect, developer and SAP Mentor. I focus on SAP Business Technology Platform, SAP Cloud Application Programming Model (CAP), Node.JS, SAP Fiori Elements and Security. I've supported several customers during their SAP Cloud ERP Private Edition (S/4HANA On Premise) implementation. Since the end of 2024 I support the technical topics at an SAP Cloud ERP Public Edition Customer.

Topics of interest: SAP Business Technology Platform, SAP Cloud Application Programming Model (CAP), SAP Cloud ERP public and private, SAPUI5, OpenUI5, SAP Fiori, SAP HANA Cloud

Gregor, what inspired you to become an SAP Mentor?

A key influence early in my SAP Community journey was Mark Finnern. He is the father of the SAP Community. Mark encouraged me to move beyond answering questions and start sharing detailed technical how-to's but also event reports in blog posts. In 2007 Mark also founded the SAP Mentors program which gave me the opportunity to provide structured, experience-based feedback to SAP product teams and help bridge the gap between product vision and real-world implementation.

What advice would like to share with other SAP community members?

My advice to other SAP Community members is simple: contribute consistently and think long-term.

Start by answering questions and helping others solve real problems - but don’t stop there. Document your lessons learned, share architectural insights, and write about what worked and what didn’t. That’s how collective expertise grows. And you will be amazed how often you research years later and find your own answers and blog posts to solve a problem you're just facing. Despite all the new stuff SAP has quite a long tail that doesn't change quickly.

Engage constructively, challenge respectfully, and focus on signal over noise. The community is not just a support forum - it’s an ecosystem where practitioners can influence product direction, elevate standards, and shape the future of SAP together.

Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenario

2026-02-24T12:11:45.065000+01:00

In many organizations, B2B transactions are not always handled using pure standard formats. Over time, custom XML structures are introduced on top of EDIFACT messages to align with internal processing or EDI broker requirements.

I encountered a similar scenario in one of my recent projects. Through our EDI broker, we were consuming EDIFACT messages in an XML representation. With the upcoming S/4HANA migration, the same integrations needed to be moved to SAP Integration Suite.

Interestingly, the migration itself was not the biggest challenge. The real concern was monitoring and trading partner mantinance.

In our existing SAP PI/PO landscape, we have more than 400 active interfaces processing approximately 200,000+ transactions. Monitoring in such a landscape is already complex. Moving to Integration Suite without a structured monitoring approach would only increase the operational overhead.

Why We Considered B2B Advisory

To address this, we evaluated B2B Advisory capabilities in Integration Suite. The key expectations were:

Automatic payload logging retention for a defined number of days
Clear identification of trading partner information
Agreement-based processing for structured partner management
A dedicated monitoring environment for B2B transactions

Another important aspect was our S/4HANA clean core strategy. By leveraging B2B Advisory features properly, we see opportunities to reduce custom logic and keep the core system less cluttered with monitoring-specific enhancements.

Migration Context: From PO Without TPM to Integration Suite
In our SAP PO system, we were not using Trading Partner Management (TPM). As a result, many partner-specific handling rules were built into custom logic. While setting up B2B Advisory in Integration Suite, we started seeing clear structural benefits — especially around agreement handling and partner-based message identification. Even at this in-progress stage, the difference in approach compared to PO is quite visible.

This blog focuses on how I configured B2B Advisory to support our XML-based custom EDIFACT messages. Since we could not directly use the standard packages as-is, I made specific adjustments to adapt them to our scenario. I will walk through:

How the standard B2B Advisory packages behave
What limitations we observed with custom XML EDIFACT
What modifications were required
Key learnings during configuration

This is still work in progress, but the insights gained so far are already valuable, especially for teams moving from PI/PO to Integration Suite without prior TPM usage.

I have devided thie blog into 3 parts where current blog refers the configuration what we need to do in TPM (Trading partner Management such as Compnay profile, Partner profile, Identifiers, Communication configuration etc.
2nd blog will be based on --> agreements and couple of features i have used.
3rd blog will be how Iflows are configured and customized as per the need.

Quick Concept: How B2B Advisory & Integration works

Above is the a explanitary flow how messgae processing works with B2B Advisory. Here the brain is TPM Setup and Iflows are executing engine. Let's break down the setup I have created within TPM.

TPM Setup for B2B Advisory

As explained in the processing flow, the standard B2B Advisory packages rely heavily on Trading Partner Management (TPM). The iFlow itself does not contain hardcoded partner logic. Instead, it dynamically resolves sender, receiver, and agreement details from TPM configuration at runtime. The TPM setup was structured as follows.

Company

The Company object represents our organization within the B2B landscape. In our case:

It reflects our enterprise entity interacting with external partners
This acts as the anchor for all agreements.
All inbound and outbound B2B agreements are defined relative to this Company.

Important consideration:
We ensured that the company identifiers align with the values extracted from the XML payload. If the identifiers do not match exactly, agreement resolution will fail.

Here I have created 2 identifiers from SAP where 1st "BTPISEDI" is the one i'm using for all outbound from SAP (Idoc always) as this is the port we have defined for IDoc in WE21. and "DS4CLNT120" for all inbound to SAP as that is the logical system for all inbound. How those will be used will be describe in coming setps.

On the continuation on Company profile, we have Identifer where we can add individual identifer and Group Identifier. Group will be used when we have the varite of identifers.

Identifier	Actual value from the payload which will be use to identify the flow
Alias	Representation of the identifer which will be display at config level
Type System	Type System means the Source Document type in simple language
Scheme Name/Code	Kind of the identifer number for internal use eg : Customer Number or Partner Profile
Agency Name/Code	Kind of the identidier for the trading partner eg : DUNS number or Sender ID

Within the Trading Partner Management setup, the Systems tab allows us to define communication system details such as IDoc or Process Direct configuration parameters.

However, it is important to understand that these are not actual adapters.

The configurations maintained here do not represent runtime adapters directly. Instead, they act as logical placeholders that the standard B2B package references during execution.

How It Works Conceptually:

In TPM, we define a System for:

External partner side
Our backend system (e.g., S/4HANA)
Type System (System version)

Under the System definition, we maintain adapter-related attributes such as:

Endpoint url of the system (internet/On-Prim)
Location ID (if applicable)
Process Direct url
Credentails if application

These settings are then picked up by the standard B2B iFlow at runtime. The iFlow reads the resolved Agreement --> identifies the associated Systems --> and dynamically maps the configured values into the actual adapter that is connected in the integration flow.

Learning from various hit/try : If under system purpose is maintain as test, then in case of inbound to SAP, Idoc will never post for automatic posting it should be marked at production.

Partner Profile

Next step would be maintain the system and trading partner information. Here 2 section are devided into 2 maintinance. 1st is the Communication Partner (EDI Broker/Trading Partner Connected System/any other middleware) and Trading Partner (your actual customer/vendor).

Quick concept on Communication Partner :

protocol supported Process Direct and AS2.
only connection details are requried under communication partner.
technical placeholder for connection.
certificates/signatature (for signing and encrption) are available (mostly used with AS2)

Trading Partner

Same setup what we do in company profile need to be recreate here. Except, we can ignore the communication part (channel details/type system). Just adding the reference of the communication partner is sufficient.

Here in the identifier for trading partner I have used group of identifiers instead of individual identifier (nothing intresting just because I have tried individual). These Identifier are used to fetch the correct agreement which will have a better monitoring view per trading partner.

How to extract Identifiers

Ok, we have discussed about how to maintain identifer, but how to find the identfier the a little complex.

Company Profile
- Control Records from Idoc should be the first choice as that have all the Sender/Receiver information such as Logical system, Sender port, Receiver partner profile code etc.
  - For Company Profile (Outbound) : As generally we have a single company profile so we should choose a value which is common accross all the Outbound flow (Logical system/XML Port are preferable)
  - For Company Profile (Inbound) : Preferable option is the Logical System which we pass in RCVPRN

Trading Partner Profile

Check the file which you will be consuming and the section where Sender/Receiver information is being transfer

Standard	Segment	Sender Position	Receiver Position
EDIFACT	UNB	S002 (4th element)	S003 (5th element)
ANSI X12	ISA	ISA06	ISA08
VDA (Classic)	511	Pos 4-12	Pos 13-21
EDIWheel	Buyer/Seller Party	-	-
Customized format	Sender/Receiver section

Next series of this blog will be on how agreements can be create (will not be too standard as I have faced couple of challange) and additional paramters which are useful. Also, the configuration we made in this part, how these play a valuable role and where these will be visible at runtime.

link (will be update once published) : Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenarios part - 2

Thanks

Aman Sharma

SAP Mobile Start: A comprehensive demo session

2026-02-24T15:02:09.461000+01:00

Imagine your customer’s workforce opening one app… and everything they need is just there. Approvals. Tasks. Insights. No hunting. No switching between tools.

That’s the idea behind SAP Mobile Start: A comprehensive demo session, and we’re excited to show you what it looks like in action.

In this live session, we’ll break down the core functions, share real-life use cases, and talk honestly about the benefits of a “launchpad app for employees”. The thing is that mobility is no longer a nice-to-have. It’s the expectation.

We’ll also dive into architecture and technical requirements, so you leave not just inspired, but equipped. You’ll understand where it fits, how it works, and what’s needed to implement it successfully.

If you’re advising customers on modern workplace strategies, this one matters.

Register now and let’s rethink mobile together. https://partneredge.sap.com/en/library/education/psd/2026/feb/e_oe_te_w_PSD_WEB_00013129.html

#SAP #SAPBTP #SAPPartners #SAPMobileStart #FutureOfWork #SAPTechnology #DigitalTransformation

Part 1: Creating and Deploying a SAP CAP Application with SAP HANA on SAP BTP (Cloud Foundry)

2026-02-25T07:35:57.804000+01:00

Note: This blog is the First Part of series - Building and Deploying SAP CAP Applications on BTP: From Database to Work Zone

Introduction

SAP Cloud Application Programming Model (CAP) is often demonstrated through local examples, but its real value becomes clear when the application is deployed to SAP Business Technology Platform (BTP) and backed by a managed database.

In this blog, we will go through creating a basic SAP CAP application using the SAP Business Application Studio (BAS) CAP template, binding it to SAP HANA Cloud, and deploying it to SAP BTP using the Cloud Foundry runtime.

The goal here is not to build a complex application, but to establish a clean, working reference point. I start with a minimal CAP project to keep the focus on deployment rather than domain complexity.

This blog serves as a baseline for a series where the same CAP application will later be deployed using different databases and runtimes. The focus here is not application complexity, but establishing a clean, working reference point.

Pre-requisites:

Please make sure that you have these before starting the development:

SAP BTP Account
Cloud Foundry instance
Active Hana Cloud Instance
SAP BAS / VSCode for development
If using BAS, have a dev space running
If using VSCode then make sure that you have installed Node.js and CLI installed

Now, let’s start with the development.

Create a CAP Project from Template given in the BAS:

SAP Business Application Studio provides a template for creating a CAP project with the required structure. The positives of using the template is that it automatically builds your Multi-Tenant Application file (mta.yaml) with the required deployment modules.

Follow the following steps:

Open BAS
Click on the Side Menu on the top-left corner
Click on File
Click on New Project From Template
Select CAP Project
Configure the project as follows:
- Project Name: cap-hana-app
- Runtime: Node.js
- Database: SAP HANA Cloud
- Deployment Environment: Cloud Foundry
- Runtime Capabilities: XSUAA
Click on Finish

CAP Project creation wizard with SAP HANA selected

This will create a CAP project for you with mta.yaml automatically updated. The generated project follows standard CAP structure:

app – UI
db – Schema and data files
srv – Service Definition

Now that the project is created, let’s get into development.

Development:

Follow the following steps:

Define a Simple Data Model:

If you have schema.cds under db/ folder, then update it with the following code snippet. If you do not have schema.cds, then create one.

namespace com.mycompany.capapp;
entity Products {
    key ID          : UUID;
        name        : String(100);
        description : String(500);
        price       : Decimal(10, 2);
        stock       : Integer;
        category    : String(50);
        createdAt   : Timestamp;
        modifiedAt  : Timestamp;
}

Expose the Model via CAP Service:

If you have service.cds under srv/ folder, then update it with the following code snippet. If you do not have service.cds, then create one.

using com.mycompany.capapp from '../db/schema';

service CatalogService {
    entity Products as projection on capapp.Products;
    }

CAP automatically exposes this service as an OData endpoint without requiring manual REST configuration.

Add Data:

Run the following in the project terminal:

cds add data --records 5

Run the Application locally:

Run the following command:

cds watch

You should be able to see the data in the Products

You can also use the SQLite as a database while running locally. Execute these before starting the application:

cds build
cds deploy

Add a Managed Approuter:

Right click on mta.yaml
Click on Create MTA Module from Template
Select Approuter Configuration
Fill in the required details
Click Finish

This is important to view the data once deployed.

Prepare the Project for Deployment:

Since we have created the project from the BAS Template, we already have the mta.yaml updated and deployment ready. This file already includes:

CAP Service Modules
SAP HANA HDI Container
Required Service Bindings

Build the CAP Project:

First things first, install node modules. Run the following in the Terminal:

npm i

To build the project, you can either run the following in the terminal:

mbt build

or can do it manually:

Right click on mta.yaml
Select Build MTA Project

This will build your project for deployment. Watch-out at the project structure. You might see a new addition to the structure mta_archives which consists the mtar file of the project.

Deploy the Application:

To deploy the application to your BTP using Cloud Foundry, you will have to login to Cloud Foundry. Run the following in Terminal:

cf login

This will ask for your subaccount credentials. Provide them and you will be logged in successfully. Remember to map the correct space and org.

Once you are logged in successfully, you are ready to deploy the application. Remember the file generated while building the CAP project, this is the same file that will be deployed.

Run the following command:

cf deploy mta_archives/cap-hana-app_1.0.0.mtar

or, you can just right click on cap-hana-app_1.0.0.mtar under mta_archives folder, and click on Deploy MTA Archive.

Successful Cloud Foundry deployment

During deployment:

HDI Container is created
Database schema is deployed
CAP Service is bound to the database automatically

Confirm the Deployed Instances

Verify the Deployed Application:

When the deployment is successful, you will get a application route. Copy the same and open it in the new tab of your browser and access the service endpoint: /catalog/Products

If the deployment is successful, you can see the data displayed in a JSON format.

Browser showing the OData service response

Conclusion

With that, we have successfully created a minimal SAP CAP application, connected it to SAP HANA Cloud, and deployed it to SAP BTP using the Cloud Foundry runtime. While the application itself is intentionally simple, the deployment pipeline we established here — from schema definition to MTA build to Cloud Foundry deployment — reflects a production-ready workflow that scales well as complexity grows.

The key takeaways from this exercise are that the BAS CAP template significantly reduces boilerplate by auto-generating the mta.yaml with the necessary modules and bindings, the HDI container handles schema deployment seamlessly, and CAP's convention-over-configuration approach means your OData service is ready without any manual REST wiring.

This baseline will serve as the foundation for the rest of this series, where we will explore deploying the same application with different databases, runtimes, and configurations — making it easier to understand the trade-offs of each approach. Stay tuned for the next part!

Next Steps

In the upcoming blogs, we will focus on creating the same application using a PostgreSQL, Hyperscaler Option.

Joule of the century - Supercharging SAP Analytics Cloud with artificial intelligence

2026-02-25T09:00:00.014000+01:00

What if your analytics solution didn’t just report the numbers… but worked alongside you?

In our upcoming session, “Joule of the century – Supercharging SAP Analytics Cloud with artificial intelligence”, we’ll explore how SAP Business Data Cloud, SAP Datasphere, SAP Analytics Cloud, and Joule are reshaping planning and analytics with embedded AI.

The thing is, we’re all navigating the same challenge: dashboards everywhere, insights nowhere. AI changes that. Generate KPIs in seconds. Turn plain language into analysis. Create formulas and SQL without the blank-page anxiety. Even deploy autonomous AI agents that reason, plan, and act.

And yes, we’ll show how Joule moves from “Tell me how” to “Do this task” to “Give me insights” seamlessly inside your workflows.

If you’re working in xP&A and wondering how to bring real AI value to customers, this is the session.

Register now and see what happens when analytics finally feels… effortless. https://partneredge.sap.com/en/library/education/psd/2026/feb/e_oe_te_w_PSD_WEB_00013148.html

#SAP #SAPBTP #SAPPartners #SAPAnalyticsCloud #SAPDatasphere #BusinessAI #xPA