SAP Community - SAP Build Process Automation

Automatic Service Order creation with SAP Build Process Automation and Generative AI

2024-03-15T20:15:28.015000+01:00

Motivation

In the fast-paced digital era, businesses seek efficiency in every operation. Yet, the process of creating service orders for faulty equipment remains labor intensive, requiring manual data entry and analysis.

Our solution leverages the power of SAP Build Process Automation as a SAP BTP extension, a web service hosted on SAP BTP Kyma runtime, and generative AI powered by SAP AI Core, to transform this tedious process into a seamless, automated workflow. This blog outlines the approach.

The Original Business Process

Traditionally, the creation of service orders is a manual and time-intensive process.

The cons? Lots of tedious toggling between email and S/4HANA system service order creation page, involving several steps that are not only prone to human error but also lead to delays and potential customer dissatisfaction.

This is how it originally looks like:

Image 1: Outline of the original service order creation workflow

Receive customer email requesting a service order for faulty equipment.
Manually extract key information from the email, such as equipment details, purchase date, and analyze attached images for consistency with the equipment description.
Download, rename, and document descriptions of attached images for organization.
Develop a comprehensive problem description based on the email and images, manually entering this along with all extracted information into the S/4HANA system.
Manually upload images to the service order form.
Create the service order.
Confirm service order creation with the customer via email.

Solution

We aim to automate the manual aspects of this process, creating a system that automatically processes customer emails, including attachments, to generate service orders in S/4HANA without manual input.

This solution relies on two main components:

SAP Build Process Automation, an extension of SAP BTP, for workflow automation.
Generative AI, powered by SAP AI Core and delivered through a web service on SAP Kyma runtime, to interpret and process data.

Image 2: SAP Build Process Automation as an SAP BTP extension

SAP Build Process Automation, an SAP BTP extension, streamlines business process automation and decision-making with minimal coding. It features intuitive drag-and-drop interfaces for easy process design and quick integration within the SAP ecosystem, thereby boosting operational efficiency and facilitating digital transformation.

The automation workflow, created with SAP Build Process Automation, monitors the inbox for service order requests, extracting content and attachments from emails. This information is processed by our web service on SAP Kyma runtime, where the “magic” happens.

Image 3: SAP Build Process Automation workflow

Generative AI is an exceptional component in solutions like ours. Within our web service, we utilized the open-source vision model Llava 1.6 to interpret attached images and GPT-4 for analyzing email content, all powered by the SAP AI Core.

Image 4: Vision and text models, powered by SAP AI Core

We then use the results to populate the S/4HANA system via POST requests, ensuring that the entire service order form is filled accurately and thoroughly. Multiple image attachments are also supported, with the attached images being uploaded and renamed automatically.

Last but not least, to end off the automation workflow, we can send an automated email reply to the customer with an update on their server order number and status.

Results

From just a single customer email,

Image 5: Original email sent by the customer

we unlock all these capabilities shown below, hands-free and without any human intervention!😉

Image 6: The service order is successfully created in the S/4HANA system

Image 7: Results generated by LLaVA 1.6 and gpt-4-32k

Image 8: Uploaded attachments of renamed images

Image 9: Automated email response sent to the customer

Conclusion

The most remarkable aspect of this solution is its complete automation, which can lead to the significant advantages below:

Faster creation of service orders (~2 min per email)
Increased accuracy of service orders
Higher scalability where hundreds of requests can be handled simultaneously
Better customer satisfaction due to rapid response and accuracy

Beyond service order creation, the potential applications of AI and SAP products can extend to various other business processes, including warranty claim automation, invoice posting automation, and many others.

This video summarises the automatic service order creation process using SAP Build Process Automation and Generative AI:

If you’re interested in the technical details of this solution, you can visit this blog. Also, if you're interested in exploring solutions like this or wish to learn more, feel free to reach out to me.

References

SAP Build Process Automation
SAP AI Core
SAP AI Core service guide
Generative AI @ SAP
Service Order documentation
Generative AI hub sdk

10+ ways to reshape your SAP landscape with SAP Business Technology Platform – Blog Series

2024-03-19T16:26:59.370000+01:00

Blog 2: The role of Business Technology Platform as an extension and innovation platform

This blog is part of the “10+ ways to reshape your SAP landscape with SAP Business Technology Platform Blog Series”

Summary: In this blog series we will look at the role of the SAP Business Technology Platform to reshape your SAP landscape including SAP and Non-SAP systems. In this second blog we discuss SAP Business Technology Platform capabilities around process automation, application development, enterprise integration, and AI. And how these capabilities support the most demanding businesses.

What does Mercedes AMG Petronas Formula One have in common with SAP Business Technology Platform? -- Tons of it.

Just like any other sophisticated business, Mercedes-AMG PETRONAS Formula One is in the cutthroat business of racing. And it competes in one of the most challenging environments in global sports. Combining elite teamwork, modern technologies, high-performance management, and exceptional driving skills, Formula One is a technologically innovative form of motorsport, where incremental gains yield significant results and can be the difference between winning and losing.

So what is common with Business Technology Platform?

The Formula One team has to compete in 22-24 different race tracks during a season. Each race track presents a different set of challenges, which can only be mastered when all the data is well understood. Data is what drives strategy in Formula One. Strategy is based on a set of decisions made by track engineers, drivers, and strategists to try to maximize the result in the race and qualifying by optimizing the tools at their disposal to make important calls such as tire decisions, the timing and amount of pit stops, and the management of the cars in the race. And all the decisions for each of the scenarios require intensive data analysis. We will cover data management and analytics in Blog 11: The role of Data & Analytics in the transformation by Wolfgang Epting.

The challenges above are similar to those experienced by our customers where they have to navigate changing market situations and customer demands, and analyse and respond to dynamic requirements, all while managing quality, cost, navigating through processes, and time to market.

In this blog, I want to emphasize the Business Technology Platform, which brings cutting-edge cloud services around application development, process automation, enterprise integration, analytics, and AI, all of which should help IT deliver fully integrated rapid enhancements. The value of AI and Gen AI for business increases exponentially when combined with industry-specific data and deep process knowledge, and this is exactly what SAP does. Joule, the generative AI assistant, revolutionizes how you interact with SAP business systems, making every touchpoint count and every task simpler. More on AI later from Mark on Blog 4: The Role of AI in the transformation. Stay tuned for that.

With the switch to S/4HANA, business can build their competitive car on a new chassis. The focus is on cloud first strategy and clean core, i.e. a largely untouched SAP core. BTP is used to develop, provide, and scale new applications in the cloud. Add-on solutions on the BTP can therefore be easily connected to SAP S/4HANA, while the SAP system remains 100% clean.

Let us look at some specific areas.

Formula One has long had active aero on cars – the rear-wing-opening overtaking aid, DRS, for instance. This is part of the aero package. Obviously, the extremes would be Monza/Spa for low downforce, and Monaco/Hungary for highest. With Silverstone as maybe the ultimate “compromise” setup on the less draggy side but also needs good high-speed downforce, especially for Copse/Maggotts/Becketts where the driver experiences lateral forces upto 6Gs during acceleration, braking and cornering.

Quite the same way, SAP Business Technology Platform, is the best path to rapidly build and enhance enterprise applications, processes, and experiences on top of the S/HANA chassis for various industry and internal business requirements. The prime idea is to build competition-beating processes and application enhancements quickly and deliver them to business. An example is building intuitive applications for field staff that provide necessary data points and actions intending to reduce paperwork. Or using AI to generate work orders with necessary steps which allows planners to execute orders faster. A clean core enables you to become future-proof by ensuring faster deployment with smooth upgrades – all while using BTP allowing you to innovate at market speed.

Think about this as developing the rear wing of the car and delivering upgrades during the season. Teams have to find the sweet spot between elements such as endplates, flaps, gurney flaps, and DRS. Teams can make changes to optimize the car's performance on different tracks.

From a business perspective, this is where we employ SAP Business Technology Platform BUILD capabilities. This allows you to:

Simplify your cloud application development to get more value and ignite innovation
Deliver agile process automation to automate and optimize processes and tasks
Connect people, data, and processes with engaging experiences

Approach it from a business angle. SAP Build is SAP’s low-code offering, designed to empower users of all skills to easily create and augment their SAP and non-SAP business applications with visual drag-and-drop, without requiring programming skills.

An example here is a shipping and logistics company that has built a Mobile App within 3 weeks, to allow drivers to capture damages to their vehicles. This app has greatly reduced tons of paperwork. This has been coupled with automation to help fleet managers plan required repairs and/or schedule them for a later date based on spare parts availability.

SAP Build brings together SAP Build Apps, SAP Build Process Automation, SAP Build Work Zone and SAP Build Code with generative AI-based code development into a unified development experience with new innovations to rapidly build apps, automate processes, and create business websites. These "four carriages" work together to help users accelerate application development and process automation, empowering every employee in the organization:

Build visually: Rapidly create enterprise apps, automate processes, and design business sites.

Integrate seamlessly: Accelerate development with prebuilt connectors and lines of business-specific content for SAP and non-SAP systems.

Collaborate securely: Foster collaboration between business and development teams with built-in governance and lifecycle management.

In addition, SAP Build Code, generative AI-based code development with Joule copilot, will provide optimized Java and JavaScript application development abilities, providing a turn-key environment for coding, testing, integrations, and application lifecycle management.

SAP Build Code brings:

Generative AI-based code development with Joule copilot - uses AI to generate app logic, data models, and test scripts.
Tailored for SAP development – helps you connect seamlessly with prebuilt integrations and APIs.
Enhanced fusion development – helps you drive collaboration between professional developers and business experts.

Each Formula One car is made up of around 14,500 individual components. Each element such as chassis, power unit, gearbox, aero package, braking systems, battery, cooling systems, telemetry, radio communications, tires, driver, etc. have to be truly well integrated to ensure the car is ready to race, is reliable and will win.

Similarly, in business, systems in isolation will never work and provide a full picture of business. They have to be integrated with core systems, and external applications, leverage 3rd party data and provide all of these integrated insights to business race engineers, and enable them to make race-winning decisions.

Hence SAP Integration Suite is essential to integrate on-premises and cloud-based processes, services, applications, events, and data and provide them securely to all stakeholders to consume and process information. This is where we offer SAP BTP Integration Suite which addresses hybrid integration strategies.

The strategy to support innovation is clear.

Accelerate innovation and integrate without obstacles
Speed connectivity and realize value faster
Connect customers and workers to automated processes
Conquer process fragmentation and drive productivity
Streamline workflows and improve the employee experience
Connect with partner systems and improve collaboration

Top nine ways SAP Integration Suite drives innovation

BTP Integration Suite therefore offers:

Prebuilt integrations managed and updated by SAP
Harmonized access to popular third-party cloud applications
Tools for designing, publishing, and managing APIs
AI-assisted development and integration optimization
Tools-based, guided approach to define, document, and govern your integration strategy
Edge Integration Cell to run integration scenarios within customer-managed private landscapes for on-prem to on-prem workloads.

The new world of innovation through Generative AI via the SAP perspective.

I would equate the race engineer to Gen AI today. Simply because today, race engineers are crucial assets in every Formula One team, as they are the intelligence who ensure drivers and their vehicles are attuned to put on a show on the track. They analyze and call on all data points. I would use the parallels where the car is business applications, drivers as users, track and weather data is external data, car data is business data, custom setups during races as Gen AI content and radio communications as prompts for business users.

SAP Business AI is aimed at making our business applications more intelligent, infusing AI technologies into our applications. Furthermore, we provide business process-specific AI services that our customers can adapt to their workflow, e.g., business document processing, data attribute recommendation, RPA, etc.

Building data understanding is essential for the success of business AI. SAP has access to business data covering finance, supply chain, human resources, travel, and tons of external data relevant for business.

To make business AI successful, we continue to build the best technology and leverage the best tools on the market.

This includes strategic partnerships with others in the industry, such as Open AI, AWS Bedrock, Aleph Alpha Luminous, Meta Llama 2, Falcon, etc.
Embed their tech into our products such as SuccessFactors, S4, CX and Spend Manegement.
Enable customers to build custom ML models on SAP data easily and securely.

To conclude SAP Business Technology Platform (SAP BTP) is the platform of choice to modernize, upgrade, and drive innovations in your applications. It allows you to extend and personalize SAP applications, integrate and connect landscapes, and unleash business users to connect processes and experiences, make decisions with confidence, and drive business innovation.

Let’s get out there and win every race.

The Blog Series 10+ ways to reshape your SAP landscape with SAP Business Technology Platform will be published regularly and the newest blogs can be found here: Video & Blog Series - SAP BTP MEE Overview (brandcast.io)

To get more insights, please also visit one of our BTP Innovation Days:

Innovation Day Vienna: Vienna 04-Apr-24 SAP BTP Innovation Day Vienna
Innovation Day Switzerland: Bern 14-May-24 SAP | SAP BTP Innovation Day Switzerland
Innovation Day Germany Essen 16-May-24 SAP | SAP BTP Innovation Day

10+ ways to reshape your SAP landscape with SAP Business Technology Platform – Blog Series

2024-03-20T19:32:03.027000+01:00

Blog 2: The role of Business Technology Platform as an extension and innovation platform

This blog is part of the “10+ ways to reshape your SAP landscape with SAP Business Technology Platform Blog Series”

What does Mercedes AMG Petronas Formula One have in common with SAP Business Technology Platform? -- Tons of it.

In this blog, I want to emphasise the Business Technology Platform, which brings cutting-edge cloud services around application development, process automation, enterprise integration, analytics, and AI, all of which should help IT deliver fully integrated rapid enhancements.

In Formula One, a team has to compete in 22-24 different race tracks during a season. Each race track presents a different set of challenges, which require a set of decisions made by engineers, drivers, and strategies like tyre selection and sub-2 second pit stop execution, to try to maximize the result in the race.

The challenges our customers face are similar, where they have to navigate changing market situations and customer demands, and analyse and swiftly respond to dynamic requirements, all while managing product quality, cost, process quality, and pressure on time to market.

With the switch to S/4HANA, business can build their competitive car on a clean new chassis. The focus is cloud-first strategy and clean core, i.e. a largely untouched SAP core. BTP should be used to develop, integrate, and scale new functionality and applications on top of the core. Customers here need guidance, as this is an area that needs design and mind-shift change.

Let us look at some specific areas.

Formula One has long had active aero on cars – for instance, the DRS which is the rear-wing-opening overtaking aid. Obviously, the extremes would be Monza/Spa for low downforce, and Monaco/Hungary for highest. With Silverstone as maybe the ultimate “compromise” setup on the less draggy side but also needs good high-speed downforce, especially for Copse/Maggotts/Becketts where the driver experiences lateral forces upto 6Gs during acceleration, braking and cornering.

Quite the same way, SAP Business Technology Platform, is the best path to rapidly build and enhance enterprise applications, processes, and experiences on top of a clean S/HANA chassis for various industry and internal business requirements. The prime idea is to build competition-beating processes and application enhancements quickly and deliver them to business.

A few examples are building intuitive applications with document information extraction for field staff that provide necessary actions to reduce paperwork. Or using AI to generate work orders with necessary steps which allows planners to execute orders faster. A clean core enables you to become future-proof by ensuring faster deployment with smooth upgrades – and innovate at market speed.

This is where we employ SAP Business Technology Platform BUILD capabilities in addition to key-user extensibility and on-stack extensibility.

BUILD allows you to:

Simplify your cloud application development to get more value and ignite innovation
Deliver agile process automation to automate and optimize processes and tasks
Connect people, data, and processes with engaging experiences

How can business rapidly build a meaningful application? An SAP shipping and logistics customer built a Mobile App within a period of 3 weeks, to allow drivers to capture damages and take necessary actions. This would have taken months using traditional development methods. This new app has greatly reduced tons of paperwork and human errors. This has been coupled with automation to help fleet managers plan required repairs and/or schedule them for a later date based on spare parts availability. I regularly see such use cases in public, manufacturing, discreet, process, and retail industries.

SAP Build brings together SAP Build Apps, SAP Build Process Automation, SAP Build Work Zone and SAP Build Code with generative AI-based code development into a unified development experience with innovations to rapidly build apps, automate processes, and create business websites. These "four carriages" work together to help users accelerate application development and process automation, empowering every employee in the organization:

Build visually: Rapidly create enterprise apps, automate processes, and design business sites.

Integrate seamlessly: Accelerate development with prebuilt connectors and lines of business-specific content for SAP and non-SAP systems.

Collaborate securely: Foster collaboration between business and development teams with built-in governance and lifecycle management.

To optimise the Build process, SAP Build Code, a generative AI-based code development with Joule copilot, will provide optimized Java and JavaScript application development abilities, providing a turn-key environment for coding, testing, integrations, and application lifecycle management.

SAP Build Code will help developers with:

Generative AI-based code development with Joule copilot - uses AI to generate app logic, data models, and test scripts.
Tailored for SAP development – helps you connect seamlessly with prebuilt integrations and APIs.
Enhanced fusion development – helps you drive collaboration between professional developers and business experts.

Each Formula One car is made up of around 14,500 individual components. Each element such as chassis, power unit, gearbox, aero package, braking systems, battery, cooling systems, telemetry, radio communications, tyres, driver, etc. have to be truly well integrated to ensure the car is ready to race, is reliable and will win.

Hence SAP Integration Suite is essential to integrate on-premises and cloud-based processes, SAP as well as non-SAP applications, services, events, and data and provide them securely to all stakeholders to consume and process information. This is where we offer SAP BTP Integration Suite which addresses hybrid integration and innovation strategies.

Top nine ways SAP Integration Suite drives innovation

The new world of innovation through Generative AI via the SAP perspective.

AI wanted to change the world in 2024. SAP is taking a pragmatic approach to this. SAP Business AI is aimed at making our business applications more intelligent by infusing AI technologies into our applications. Building data understanding is critical for the success of Business AI. SAP Business AI will come with business context, provide business-friendly user experience, and accelerate business outcomes.

To make business AI successful, we continue to build the best technology and leverage the best tools on the market.

This includes strategic partnerships with others in the industry, such as Open AI, AWS Bedrock, Aleph Alpha Luminous, Meta Llama 2, Falcon, etc.
Embed their tech into our products such as SuccessFactors, S4, CX and Spend Management.
Enable customers to build custom ML models on SAP data easily and securely.

To conclude, SAP Business Technology Platform (SAP BTP) is the platform of choice to modernize, upgrade, and drive innovations in your applications. It allows you to extend and personalize SAP applications, integrate and connect landscapes, and unleash business users to connect processes and experiences, make decisions with confidence, and drive business innovation.

Let’s get out there and win every race.

To get more insights, please also visit one of our BTP Innovation Days:

Innovation Day Vienna: Vienna 04-Apr-24 SAP BTP Innovation Day Vienna
Innovation Day Switzerland: Bern 14-May-24 SAP | SAP BTP Innovation Day Switzerland
Innovation Day Germany Essen 16-May-24 SAP | SAP BTP Innovation Day

SAP BTP - A Deep Dive into SAP Build Capabilities

2024-03-21T15:36:03.932000+01:00

A Deep Dive into SAP Build Capabilities

Citizen development is transforming the way businesses build applications. SAP BTP Build sits at the forefront of this movement, empowering everyone, not just professional coders, to create custom applications that address specific business needs. In this comprehensive blog, we'll delve into the intricacies of SAP BTP Build, exploring its core services, functionalities, and the benefits it offers.

Demystifying SAP BTP Build: A Suite of Powerhouse Services

SAP BTP Build isn't just a single tool; it's a unified platform housing three robust services, each catering to distinct application development needs:

SAP Build Apps (formerly SAP AppGyver):
- Visual Development Paradise: Unleash your creativity with a drag-and-drop interface. Build web and mobile applications intuitively, using pre-built components and functionalities. No coding experience required!
- Seamless Integration: Connect your applications seamlessly with existing SAP and non-SAP systems using pre-built connectors and APIs. This eliminates the need for complex integrations, saving time and resources.
- Offline Functionality (Mobile Apps): Keep your mobile applications operational even without an internet connection. This ensures uninterrupted workflows and enhances user experience, especially in scenarios with limited connectivity.
- Advanced Features: For those with a coding background, SAP Build Apps offers JavaScript extensions for more granular control and customization.
SAP Build Process Automation (formerly SAP Process Automation):
- Wrangle Repetitive Tasks: Feeling bogged down by repetitive tasks? Automate them with SAP Build Process Automation!
- Intuitive Flow Builder: Design automated workflows visually using a user-friendly interface. Connect various steps, decision points, and actions to streamline complex processes.
- Pre-built Connectors: Leverage pre-built connectors to integrate with diverse systems like SAP S/4HANA, Salesforce, and more. This eliminates the need for custom coding and accelerates automation implementation.
- Advanced Monitoring and Error Handling: Track the performance of your automated workflows, identify errors promptly, and configure robust error handling mechanisms to ensure smooth operation.
SAP Build Work Zone (formerly SAP Work Zone and SAP Launchpad service):
- Centralized Information Hubs: Create captivating business sites with SAP Build Work Zone. These sites serve as central hubs, providing users with easy access to information, applications, and processes.
- Branding and Customization: Tailor the look and feel of your business sites to match your company's branding. Embed logos, customize colors, and layouts to create a cohesive user experience.
- Single Sign-On Integration: Streamline user access by integrating SAP Build Work Zone with your existing single sign-on (SSO) solution. This allows users to access all applications and resources with a single login.
- Personalization Capabilities: Cater to individual user needs by personalizing the content and functionality of business sites. Deliver a more relevant and engaging experience for each user.

Unveiling the Benefits of SAP BTP Build: A Citizen Developer's Dream

By leveraging SAP BTP Build, businesses can unlock a treasure trove of benefits that empower employees and streamline operations. Let's explore some key advantages:

Empowering Citizen Developers: Bridge the gap between business needs and IT capabilities. Anyone can now build applications without writing code, fostering a culture of innovation and problem-solving across the organization.
Increased Productivity: Automate manual tasks and streamline workflows, freeing up valuable time for employees to focus on more strategic initiatives. Employees can also build custom tools to enhance their daily tasks, leading to significant productivity gains.
Enhanced Agility: Respond quickly to changing business requirements by rapidly building and deploying custom applications. This allows businesses to adapt to market shifts and seize new opportunities with greater agility.
Improved User Experience: Build applications with a user-centric approach. SAP BTP Build's visual development tools ensure applications are intuitive and user-friendly, leading to higher user satisfaction and adoption rates.
Reduced Development Costs: Eliminate the need for extensive coding resources and complex development environments. Build applications faster and at a lower cost compared to traditional development methods.

Who Can Benefit from SAP BTP Build? A Wide Spectrum of Users

The beauty of SAP BTP Build lies in its accessibility. Here's how different user groups can leverage the platform's capabilities:

Business Users: Build custom dashboards, reports, and approval workflows to streamline their daily tasks. Imagine a sales manager creating a mobile app to track leads on the go or a finance professional building a dashboard for real-time budget insights.
HR Professionals: Automate onboarding processes, manage leave requests, and build self-service portals for employees

To delve deeper and explore more use cases relevant to your organization needs, technical configurations for complex scenarios or to know more on value add feel free to connect.

Flattening an Object using Action Editor

2024-03-22T18:45:05.057000+01:00

Motivation:

This blog focuses on the concept and usability of flattening object feature within an Action of the Action Project.

Parent Blog:

Actions Editor – Feature List, Usage and Maintenance of Actions Project | SAP Blogs

Concept & Need:

Flattening objects refers to the process of transforming nested or hierarchical data structures into a flat structure. This can be helpful if you need to simplify data for easier processing in your business process. As a result of flattening, citizen developers are able to take advantage of the nested input and output body parameters of the action by moving up the flattened fields one level in the object hierarchy.

Flattening an object:

Use Case:

An Action Designer can use the flattening icon present with the key name for each parameter of type object with some properties to flatten that parameter. Let us try to understand this with an example.

Example:

Flattening an input parameter object.

An object can be flattened by using the flattening icon present with the key name as shown in figure 1.

Figure 1: Flattening an object.

When flattening icon is clicked, keyword flattened is shown along with the key name as shown in figure 2.

Figure 2: An object is flattened.

When an object is flattened, the properties present inside the object can be accessed one level up in the object hierarchy. The same can be seen in the test table as shown in figure 3.

Figure 3: Test table after flattening.

Flattening is also possible for objects present in output body as shown in figure 4.

Figure 4: Flattening available in output body

Flattening of objects present in output body helps get output parameters one level up in object hierarchy.

Note: Flattening is possible at multiple level of hierarchy as shown in figure 5.

Figure 5: Flattened object present inside a flattened object.

When test is performed after flattening parameters present in output body, the response is generated according to the new object structure as shown in figure 6.

Figure 6: Response after flattening.

Blog Reference:

Part 1 of the Blog Series: The New Actions Project – Major Changes including the Actions Editor Available Now !! | SAP Blogs

Part 2 of the Blog Series/Parent Blog: Actions Editor – Feature List, Usage and Maintenance of Actions Project

Thanks for reading and I hope it helped to understand the concept of object flattening within the Actions Editor. Please feel free to leave a comment if there are any questions and I would be happy to receive any feedback.

Deep Dive into SAP Build Process Automation with SAP S/4HANA Cloud Public Edition - Retail

2024-03-28T14:19:12.526000+01:00

This blog is intended to complement my previous blogs on automation and augment Retail scenario with SAP S/4HANA Cloud Public Edition as described with available scope items for Retail and SAP Help documentation.

Customers are eager to take charge and explore potential avenues for innovation, aiming to streamline enterprise automation across diverse landscapes. This proactive approach empowers companies to address the challenges of disjointed processes, ensuring they focus their automation efforts where they're most needed.

A Retail company striving to revolutionize its operations, particularly in managing the intricate logistics of end-to-end retail processes. They seek to seamlessly integrate sales from both backyard distribution channels and physical storefronts, even when inventory might not be stored on-site. This pursuit of efficiency reflects their commitment to enhancing customer experience and staying ahead in a competitive market.

Let's explore a typical business situation where sales happen in stores using cash registers (POS systems). These sales involve things like selling items, customers paying for orders, and handling money transactions. To keep track of all this, we need to automatically create documents showing when goods leave the store, including steps like gathering items, putting them in packages, and officially marking them as sold and out of the store.

Real-time stock levels are monitored within SAP Customer Checkout Manager for immediate visibility. Data is moved from S/4HANA Public Cloud Retail to SAP Customer Checkout Manager, focusing on master data replication. Financial and sales transactions flow from SAP Customer Checkout Manager back to S/4HANA Public Cloud Retail. Learn more about Integration of SAP Customer Checkout Manager with S/4 Public Cloud Retail with documentation.

Executing enterprise automation with SAP Build Process Automation / SAP Integration Suite Middleware using SAP Event Mesh with business events, help trigger fully automated process. Customer can set up their custom enterprise automation bots and workflows by leveraging and extending the available best practices content on SAP Bot Store. Ex. documents for goods movements such as outbound delivery, Picking, Packing and Post Goods Issue need to be automatically accomplished. You can learn more with documentation.

SAP Event Mesh is a fully managed cloud service running on SAP BTP for enabling applications, integrations, and extensions to communicate asynchronously through events. It is part of SAP’s event driven ecosystem and powers end-to-end event driven architectures. SAP Event Mesh allows applications to communicate through asynchronous events.

Experience greater agility and scalability when you create responsive applications that work independently and participate in event-driven business processes across your business ecosystem. Learn more with SAP Help | Documentation

Currently all public business events for SAP S/4HANA Cloud listed on Business Accelerator Hub are supported and can be used to streamline the process with automation.

Customers envision to have AI-powered SAP Build Process Automation solution to integrate applications such as SAP S/4HANA Cloud Public Edition with their point-of-sale (POS) system, discover process inefficiencies and automate business processes.

SAP Build Process Automation provide the flexibility for the customer to automate across the enterprise to improve efficiency and reduce errors, along with Event Mesh set up. Event-Broker-as-a-Service decouples communication between event sources and event consumers in a plug-and-play fashion.

Streamline Goods Movement and Posting Billing Document
Extend pre-build Template packages to customize and perform automation using Business Events

Customer vision is to have real time business updates on significant changes in business applications for their logistics and Retail sales process, throughout their business ecosystem and increase flexibility and scalability by loosely coupling business applications and infrastructure.

Automated Goods Movement and Posting Updated Billing Document using SAP Build Process Automation

Utilizing automation through the API API_MATERIAL_DOCUMENT, the system orchestrates the creation of postings to maintain a seamless availability of articles on the storefront. Additionally, it initiates the generation of material documents following a trigger event at the Event Mesh, occurring subsequent after the creation of a point-of-sale (POS) receipt.

Within the Event Mesh framework, occurrences related to material documents are captured. These events manifest when a material document is generated (MaterialDocument.Created.v1) or when an item within a material document is canceled (MaterialDocument.Canceled.v1). Further insights into Material Document Events can be obtained for deeper understanding with SAP Help | Documentation

Furthermore, the allocation of specific delivery groups to outbound deliveries is imperative using SAP Build Process Automation BOT. This ensures that the requisite shipment resources are appropriately assigned to undertake subsequent outbound delivery tasks. The assignment of outbound delivery groups is managed externally to the cloud ERP system, documented within a spreadsheet, and synchronized with the SAP S/4HANA Cloud, Public Edition for updates and maintenance.

SAP Build Process Automation helps automatic creation of Picking and Packing, goods issue and monitor process using process visibility. Notification events or data events can be sent from the event source to inform of the change. Message holding the event description in an encoded format is sent through an event broker, where event consumers have registered with the event broker and are informed of the event.

SAP Build Process Automation best practices content extended to update the delivery group for outbound deliveries assignment.

SAP Build Process Automation perform automated goods movement tasks such as Picking, Packing and Goods Issue.

SAP Build Process Automation helps updating the billing document for sales for with specific attributes, Proof of Delivery, reference point-of-sale (POS) number, as well as the respective financial postings in SAP S/4HANA Cloud.

For Retail business scenario, solution leverage Store Connectivity POS Outbound (3I2) to send the (Articles, B2C prices etc.) information from SAP S/4HANA Cloud system to point-of-sale (POS) system.

POS outbound service operation enables you to send product master data, sales price information, and additional information, such as purchase price information and bills of material, to point-of-sale (POS) systems. You can learn more with Documentation | SAP Help Portal and API Documentation

For Retail business inbound scenario, solution leverage POS Inbound (3HV) functionality to transfer information from POS Sales receipt and means of payment for articles available at Store front and backyard distribution channel.

In addition, configuration set up can be done to transfers aggregated sales, aggregated payment list, sales per receipt and returns, and customer order payment information by creating material and billing documents in SAP S/4HANA Cloud system.

"POS Sales Transactions - Create" inbound asynchronous service to replicate POS sales transactions in SAP S/4HANA Cloud system. You can learn more with SAP Help Finance Transactions. Documentation | SAP Help Portal

POS Sales Transaction - Receive Confirmation outbound service enables you to receive a confirmation as soon as you successfully posted a POS sales transaction in the SAP S/4HANA Cloud system. Documentation | SAP Help Portal

"POS Financial Transactions - Create" inbound asynchronous service enables you to replicate point-of-sale (POS) financial transactional data to SAP S/4HANA Cloud system. You can learn more with SAP Help Finance Transactions Documentation | SAP Help Portal

POS Financial Transaction - Receive Confirmation outbound service enables you to receive a SOAP confirmation as soon as you successfully posted a POS financial transaction in the SAP S/4HANA Cloud. Documentation | SAP Help Portal

POS Inbound (3HV) create billing Document for sales and means of payment. Billing Document Events are triggered and received by Event Mesh that informs a external system about created, changed, and canceled billing documents in an SAP S/4HANA Cloud. Event mesh will have automated execution for SAP Build process automation bot that reads the billing information via API based bot (https://api.sap.com/api/API_BILLING_DOCUMENT_SRV/overview) and send it to POS system.

In general, SAP recommend using the SAP Omnichannel Sales Transfer and Audit solution which can be further evaluated in the given scenario. This solution will further optimize by having aggregated transactions (and, in specific use cases, nonaggregate (receipt-level) transactions) are periodically pushed to the back end for further processing.

Let’s take a deeper look at technical configuration steps using Event Mesh with SAP S/4HANA Cloud, Public Edition with 10 simple steps that can get your event driven automation up and running.

Setup Connectivity and Extensibility

You can set up the connectivity between Event Mesh and the SAP S/4HANA Cloud Public Edition Tenant that enable the exchange of credentials between the two systems. Administrator should first create an SAP S/4HANA Cloud Extensibility service instance with service plan messaging. Learn more with documentation.

Maintain Extensions on SAP BTP - To build extension applications for your SAP S/4HANA Cloud system, you need to connect your SAP S/4HANA Cloud system to your SAP Business Technology Platform global account. SAP Business Technology Platform Cockpit, open your global account and choose Systems - Add System. Learn more with Documentation | SAP Help Portal
Set Up Entitlements for Your Subaccount Documentation | SAP Help Portal
Set up your subaccount entitlement for SAP Event Mesh - Click on Configure Entitlements and then on Add Service Plan. In the Subaccount Entitlements dialog box, select the service Event Mesh. In the Service Details: Event Mesh screen area, check both options the default service plan and the Standard (Application) and then click on Add Service Plans.

Messaging to consume SAP S/4HANA Cloud events and create event-based extensions using the event bus from SAP Event Mesh and api-access for generic access to SAP S/4HANA Cloud APIs.

Navigate to SAP S/4HANA Cloud Public Edition Home -> Communication Management tab and choose the tile Maintain Extensions on SAP BTP.

On the Maintain Extensions on SAP BTP screen in the Integration section, choose New.

In the Integration Token field, paste in the integration token generated and copied from the SAP Business Technology Platform. Enter a description for your system integration token and save it.

Both Services will be displayed in the list of entity assignments.

3. Navigate to your BTP subaccount and allow SAP Business Technology Platform applications to consume events and APIs from SAP S/4HANA Cloud, you need to create the relevant service instances of SAP S/4HANA Cloud Extensibility for the service plans api-access and messaging.

Inside the subaccount. Select in the left menu Services -> Instances and Subscriptions. Then Click on the button “Create”.

4. In the screen for create wizard the available Services will be displayed in the Plan dropdown list, select the service SAP S/4HANA Cloud Extensibility with plan messaging.

5. In Runtime select Cloud Foundry. Then choose the space created, for this example “dev”, then the systems linked to the BTP are displayed in the list, here choose the S4HANA Cloud to be extended “XXX”. Choose a CLI name "XXX-SBPAEvents" for your instance (e.g. XXX-SBPAEvents). And click Next.

The next screen for parameters request the Client Id with 4 chars and the system name. then click Next

6. Create a new service. Inside the subaccount. Select in the left menu Services -> Instances and Subscriptions. Then Click on the button “Create”.

7. In the Create wizard in the Service dropdown list, select the service SAP S/4HANA Cloud Extensibility. Select the Service Plan api-access, ex. "XXX-SBPAEventAPI" which you use for generic access to APIs in your SAP S/4HANA Cloud system. The communication arrangement A2X_OD_0106 is created in SAP S/4HANA Cloud, Public Edition using scenario SAP_COM_0106

After the creation of the service, you can check the automatic creation of the communication arrangement in SAP S/4HANA Cloud, Public Edition system. Navigate to Communication Arrangements and look for A2X_OD_0106.

8. Navigate to SAP S/4HANA Cloud Public Edition - Enterprise Event Enablement - Configure Channel Binding, Select your event channel from the list SAP_CP_XF_XXX

In the new screen, click Create over “Outbound Topic Bindings” section. Select the Topic that will be used for the event. Then you can create the topic. The topics will appear in the list.

9. Navigate to SAP BTP Tenant. Create a new service (Event Mesh).

Inside the subaccount. Select in the left menu Services -> Instances and Subscriptions. Then Click on the button “Create”.

Search for Service “Event Mesh”, Plan “default”, Run Environment “Cloud Foundry”, choose the space in Cloud Foundry, and the name for the instanceSBPAEventMesh and click , Create Event Mesh Instance

To manage the Event Mesh Instance, create a new service for Event Mesh now for Standard Plan. Inside the subaccount. Select in the left menu Services -> Instances and Subscriptions. Then Click on the button “Create”.

Search for Service “Event Mesh”, Plan “Standard” and click Next

10. Navigate to BTP Sub Account and access the Event Mesh Cockpit, you need to subscribe to SAP Event Mesh and assign several roles to your user. Go to option Security -> Roles. Now create the role ex. "Event Custom Roles".

Now your " Event Mesh" Application is ready to be executed that will capture events triggered from SAP S/4HANA Cloud, Public Edition System.

You can jumpstart automation projects with hundreds process content packages available in public bot store, SAP Build Process Automation bots and connectors designed specifically to enhance the capabilities of your SAP applications.

SAP Build process automation connectors, create Actions to communicate with external systems or leverage Automation SDK providing different activities for an automation.

Stay tuned for more updates in the next quarters!

Where to Find More Information:

Watch the replays of our exclusive SAP S/4HANA Cloud Public Edition 2402 Early Release Series here: https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/watch-the-replays-of-our-excl...
Explore the ready-to-run cloud ERP here: https://www.sap.com/products/erp/s4hana.html
Watch our SAP S/4HANA Cloud product update videos on YouTube: https://www.youtube.com/playlist?list=PLWV533hWWvDnnyN2j-CcUheNN-GaNCb3H
Check out our digital enablement wheel here: https://chart-bdmaicr0au.dispatcher.eu2.hana.ondemand.com/index.html?hc_reset
Find out how to switch from groups to spaces and pages here: https://blogs.sap.com/2023/11/06/deactivation-of-groups-in-the-sap-fiori-launchpad-in-sap-s-4hana-cl...
Become an early adopter for Joule in SAP S/4HANA Cloud Public Edition here: https://influence.sap.com/sap/ino/#campaign/3612
Check out the SAP Activate Roadmap for early adopters here: https://go.support.sap.com/roadmapviewer/#/group/658F507A-D6F5-4B78-9EE1-0300C5F1E40F/roadmapOvervie...
Review the PPL content here: https://go.support.sap.com/roadmapviewer/#/group/658F507A-D6F5-4B78-9EE1-0300C5F1E40F/roadmapContent...
Listen to our podcast here: https://podcast.opensap.info/inside-sap/
Watch our openSAP microlearnings to learn about SAP S/4HANA Cloud topics at your own pace here: https://microlearning.opensap.com/
Find best practices on SAP S/4HANA Cloud Public Edition here: https://me.sap.com/processnavigator/SolS/EARL_SolS-013/latest?region=DE
Check out what’s new here: https://help.sap.com/doc/ce01d82756b947a1a043a5d5a3204226
Find help here: https://help.sap.com/docs/SAP_S4HANA_CLOUD
Read the feature scope description here: https://help.sap.com/doc/7c9e0bbbd1664c2581b2038a1c7ae4b3

Declaring Dynamic UI5 Fields in SAP Build Process Automation

2024-04-03T10:54:30.852000+02:00

While automating SAP Fiori applications, one might come across some dynamic UI5 elements such as mentioned in the snapshot below.

In most cases, recorder may not be able to uniquely identify the elements, thus terminating the automation where it may not find the suitable elements.

In such cases, SAP provides an extremely useful functionality to declare the elements manually using Design Console’s screen and tree feature.

Let us look at the steps required to fulfill the requirement.

Switch to ‘Both’ view.
In the Screen panel, click the target element.
Find the element in the ‘Tree’. (It’s recommended to find element type till the last child DIV)
Hover and right click the element and select ‘Declare Element’.

You might find that element has been uniquely identified or not, but we need to make sure that element must not use ‘id’ as an identifying criterion as it is static criteria, and we need to deal with dynamic elements.

5. Add the ‘class’ criteria from all the available criteria and remove ‘id’.

6. Now, we need to add all the parent DIVs until we find the DIV which has a criterion named ‘nth-child-tag =X’. (Here X can vary on the number of parent DIVs)

7. For this, hover to the immediate parent DIV, right click and select ‘Add to criteria’. Repeat step number 5

Once you find DIV with ‘nth-child-tag=X’ criteria, you will also find that now your element has been uniquely identified.

Element structure would look something like this.

8. Since recorder uses SAPUI5 SDK automatically, make sure you change the element class and select a SAP UI5 recorder.

9. Make sure to set the target element in automation to current declared element and you’re all set.

Hope this blog finds helpful in your automation journey.

Automating Fiori applications becomes much easier as SAP provides various SDKs to interact with Fiori elements and other platform services such as Microsoft.

But there are some important factors which needs to be considered while automating using SPA tool which includes declaring elements uniquely, adding wait functionality as required, defining similar screens uniquely etc.

In this series of blog posts, we are going to deep dive into various other important factors of this RPA tool as well.

More blogs to follow.

Trigger a process in SAP Build Process Automation from SAP Build Apps without using API

2024-04-04T19:03:30.681000+02:00

SAP Build is a low-code solution that helps accelerate development and automation. It helps to

Build visually: Create enterprise apps, automate processes, and design business sites without writing code.
Integrate seamlessly: Accelerate Trigger the process
Get process attributes
Update process instances
Retrieve process instances development with prebuilt connectors and business content for SAP and non-SAP systems.
Collaborate securely: Foster collaboration between business and development teams with built-in governance and lifecycle management.

SAP Build Products :

Build apps SAP Build Apps helps you create enterprise applications without code.
Automate processes SAP Build Process Automation enables you to automate workflow processes and tasks with simple drag-and-drop capabilities
Create business sites SAP Build Work Zone enables you to design engaging sites to get work done quickly across all your enterprise application

This blog will take you through how application built in Build Apps can easily integrate with SAP Build Process Automation and trigger a process in a Citizen Developer friendly way without the need to make direct API calls.

Refer to this blog if you would like to know on how to integrate SAP Build Apps with SAP Build Process Automation using API calls.

Need for the integration between SAP Build Apps and SAP Build Process Automation

Citizen Developer of SAP Build Apps would want to have the option to model their application to trigger a Business process in SAP Build Process Automation project so that Business process can be automated with the capabilities of process, decisions and automations along with complete E2E insights of the process with Visibility scenarios
Customers are looking for a native Android or iOS mobile application experience and not a web application for both triggering the process and for approvals as well .
Customer Experience and Success Factors Work zone uses SAP Build Apps as Application Extension and they need forms to be modelled in SAP Build Apps with rich styles and UI capabilities and at the same time trigger approvals for their process in SAP Build Process Automation

How does this integration simplify the life of a Citizen Developer?

Build Apps developer can discover the published Build Process from Library and consume it in their application in a low code no code way and doesn’t have to configure the API endpoint and parameters as was the case before.

What are the pre-requisites for using this integration ?

BTP Subaccount should have the following service assignments under entitlements :

Click on the links below to do the initial setup for both the services.

Now, business process can be created in SAP Build Process Automation and the application can be created in SAP Build Apps.

Usecase –Release Credit Blocked Sales Order in S/4HANA

We will take the use case of Releasing a Credit Blocked Sales Order in S/4HANA to illustrate this integration scenario between SAP Build Apps and SAP Build Process Automation.

In S/4HANA, there are Business Partners for whom credit limit can be set .Now when the sales orders are created for these Business Partners with the total amount of sales orders exceeding the credit limit , the sales orders will get blocked automatically. To unblock these sales orders, approval will be required which can be done in SAP Build Process Automation.

Release Sales Order Credit Block process enables SAP S/4HANA customers to review the credit block on sales orders in SAP Build Apps application and send for approval to SAP Build Process Automation to decide about release, or reject of the credit blocked sales orders.

For all APIs for Credit Blocked Sales Order in S/4HANA , refer to the list on Business Accelerator Hub.

Sample Business Process Flow:

Lets go to the unified SAP Build Lobby and create a Project for Business Process to release a credit blocked sales order in S/4HANA

The sample business process looks like below. The Build Process Automation project needs to be released ,deployed and in addition, Published to Library also so that it can be discovered and triggered from Build Apps application.

Steps in the process :

Create a process with API Trigger which takes a Credit Blocked Sales Order Number as input

Read the Credit Blocked Sales Order Document details from S/4HANA using Actions

Read the Sales Order Document Item details from S/4HANA using Actions

Determine Approver using Decisions

Create an Approval Form with relevant Sales Order details where the approver can Approve or Reject the Credit Block removal
- If its approved, Release the Credit Block in S/4HANA using Actions and End the process
- If its rejected , End the process

For complete explanation on this scenario and Build Process Automation project, you can refer to the Devtoberfest youtube video on “Start Automating your work with SAP Build Process Automation”

This is a sample flow but the complete flow can be customized and implemented as required.

Build Apps Application Flow:

Now that we have the Build Process Automation project ready, we can see what will be the configurations needed at Build Apps to enable triggering of a process in a low code no code fashion.

Please follow the blog What’s New in SAP Build – Seamless Integration of Processes and Apps from EsmeeX for steps to configure SAP Build Apps initial setup . Then, follow the below steps for project specific configurations.

Enable BTP Authentication

BTP Authentication can be enabled in the Auth tab

Add the process for integration

Discover the published process from library by searching with the Project name and add the process in the Data tab

Enable process

Once the process is discovered and chosen as in the above step , Enable the process
By enabling the process, the process actions gets enabled which enables to
1) Trigger the process
2) Get process attributes
3) Update process instances
4) Retrieve process instances

Trigger process

Trigger Process can be added in the UI Canvas tab . In the option to “Add Logic” to the Submit button , Trigger Process can be dragged and dropped from the tab “INSTALLED” in the Logic canvas and connect the input and output accordingly to the page variables.

Inputs of Trigger process

Outputs of Trigger process

Retrieve process instances

In the application, we can retrieve process instances to see the current status of the triggered process. Go to the “Add Logic” of the ICONLIST ITEM in the UI Canvas.

In the “INSTALLED” tab of the Logic Canvas, “Retrieve instances” can be dragged and dropped and connect the input and output accordingly to the page variables as shown below.

On similar lines, the Build Apps application can be extended to use the Process Actions “Get process attributes” and “Update process instances” as well.

Launch Build Apps application

When the Unblock Credit Blocked Sales Orders application in Build Apps is launched in the Launch tab, it shows the History of previously triggered processes for Unblocking the Credit Blocked Sales Orders with their process instance id triggered with “Retrieve Instances” process Action and the user who triggered it ,on which date and the current status of the process if its Running or Completed or Erroneous and so on .

The user has the option to enter the Sales Order Document Number whose Credit Block needs to be removed and then Submit it to trigger the process in SAP Build Process Automation

We have seen now how easily a Citizen Developer can integrate Build Apps to SAP Build Process Automation without knowing the underlying API details and so on to trigger the business process.

How to develop Customer creation Application in SAP Build Apps with OData service

2024-04-05T16:34:12.935000+02:00

Objective: -

Implementing SAP OData URI to SAP Build and Creating Customers in SAP BUILD which can replicate to SAP System

Business Scenario: -

How to create Customers using SAP Build Apps and OData Service.

Prerequisites: -

-> You Have an SAP BTP account or trial account.

-> Inside the BTP account, go to Instances and Subscriptions and create an instance of SAP Build Apps

-> Now go to Security -> Users Tab and assign Role to the user for SAP BUILD Apps

Now, we have to create the SAP Backend connection to SAP BTP : -

Before mapping data from S4H or our SAP System to Build Apps, we need to create a Destination in the BTP and give the required details of the S4H system with ODATA Uri too which we will consume (BTP->Connectivity->Destination )

Connection is now established to that service.

Now go to SAP Build Apps and navigate to Create to create a project.

Now click on Build an Application to create a Application

Now Click on Web & Mobile Application

Now Give the project name and Description and You are good to go.

Inside the app you are working on SAP Build App go to the Authentication section and implement authentication

Now create an App Variable that holds all fields that are present in our OData service.

Now create a page and install a template from the marketplace which is Basic List and implement your UI for Customer Creation and a home page where all customers are displayed.

Now go to the DATA Section then go to SAP Systems and connect to your s4h System and the service that you called from the destination from SAP BTP will be available to you now.

Now Click on this list go to ‘list resource’ fill in all the fields and configure authentication from Properties

Now Go to the Logic section of List and implement logic like this

Now click on the Create button go to Show logic for Button then implement this logic

Now create another page as shown below and build a form to create Customer Data using input fields.

Now do data binding to all fields by clicking on it and then assigning value to it

Now do a similar mapping for every field

Also, implement a condition to alert that an empty value is not allowed.

Now on the submit button implement logic that submit the data and updates the data to that OData service and thus will be reflected in the database table too

Preview Your Developments: -

Now when everything is done go to the Launch section then Preview your app.

By this, we can preview our application either on the web or can be previewed in Smartphones.

Our Application Now looks like-

When we click on the create button the second page appears

Fill out details and now our customer is created.

So now your customer is created in your database table which you can check by going to se11->KNA1

And you can see your entry got updated in table KNA1

Customers and Partners are using SAP BTP to Innovate and Extend their SAP Applications

2024-04-08T19:45:22.343000+02:00

At SAPinsider EMEA 2023 Conference in Copenhagen, we met up with SAP BTP customers and partners to capture their inspiring stories.

SAP BTP Customers

Nordzucker, one the world's leading sugar manufacturers and produces animal feed, molasses, fertilizers, and biofuels. Improved and simplified their maintenance processes with 2BM Mobile Work Order built with SAP BTP.
delaware, a global IT solutions and services provider, uses SAP BTP internally to create a real-time integration framework that delivered higher customer satisfaction and reduced costs.
Maxion Wheels, the world's #1 wheel producer, leverages SAP BTP with SAP Datasphere to provide a single business data fabric for their sales, finance, inventory, and logistics departments.
Satair, spare parts division of Airbus, has 4 hours to get a spare part to a plane to get it flying again, it uses SAP BTP as its Swiss army knife.

SAP BTP Partners

2BM Software, develops and sells maintenance, service and warehouse applications exclusively for SAP built with SAP BTP.
delaware, a global IT solutions and services provider, helps customers solve their business needs of today and tomorrow using SAP BTP for integration, application development and automation, AI, and data and analytics.
Precog, helps customers get their SAP and Non-SAP application data out easily and into SAP BTP with SAP Datasphere to harmonize their data.
NTT Data, delivers end to end processes, innovates new business models, and builds solutions for their customers with SAP BTP. NTT Data is the partner supporting Satair’s successful SAP BTP projects.

Learn more about SAP BTP. Explore more SAP BTP partner stories.

If you are a partner, get more SAP BTP resources on SAP PartnerEdge.

Introducing in-place Migration from SAP Intelligent RPA to SAP Build Process Automation

2024-04-09T18:36:13.740000+02:00

Dear Community,

In the coming weeks we will enable the ability to upgrade an existing Intelligent RPA tenant for becoming Build Process Automation tenant in few steps. No need to export existing projects and then import projects in another tenant. No need to deploy, create trigger, register agents and so on.

Few steps are required to transform an Intelligent RPA tenant to a Build Process Automation tenant.

Pre-requisites

Let's be clear, we enable the in-place migration to ensure the migration will be smooth and effortless. To that end, we have some requirements to avoid data loss and partial transformation.

No more Desktop Studio projects or packages in the tenant
No more Maintenance projects in the tenant

If some content block the in-place migration, you can download the details.

We have prepared a SAP Note 3334979 with some details available here.

If everything is good the seven steps are the following:

Steps	Where
Step 1 - Add SAP Build Process Automation entitlements in your tenant	BTP Cockpit
Step 2 - Click on "enable migration"	Cloud Factory
Step 3 - Subscribe Build Process Automation	BTP Cockpit
Wait a couple of minutes the time the subscription happens and the migration is performed
Step 4 - Add and/or modify the Role Collections	BTP Cockpit
Step 5 - Connect to Build Process Automation and Check the results	Build Process Automation
Step 6 - Check or Update Agents (optional)	On-Premise Agents
Step 7 - Unsubscribe (delete) SAP Intelligent RPA	BTP Cockpit

Before you start

It's a good practice to clean your tenant of unnecessary content no longer used or accurate. As usual it's also a good practice to update to the recent SDKs or Agent version. Check your contract terms as well before.

The steps

Step 1 - Add SAP Build Process Automation entitlements in your tenant

For subscribing to Build Process Automation, some entitlements are required. Otherwise, you won't be able to go further. Assuming your global account has already the corresponding entitlements (you need to check with your contract) here the steps for a given sub-account:

Click on "Entitlements"
Click "Edit"
Click "Add Service Plans"
Search for "Build"
Select the different services and options such as Standard (Application) automation-attended automation-unattended standard-user advanced-user api-calls
Add the Service Plans
Configure the values
You can now "Save"

Your sub-account is ready to subscribe Build Process Automation.

Step 2 - Click on "Enable migration"

Connect Cloud Factory as Officer. A new tile should be displayed.
The button "Enable Migration" would be shown. Click and a confirmation is required.

Your tenant is now Enabled for the migration and it will unlock the dual subscription.

If the tile is displayed this instead
Download the report and fix the blockers. More details will come in the documentation.

Step 3 - Subscribe Build Process Automation

You can either subscribe within your sub-account or use the Booster:

The procedure is well described in the documentation here.

Migration from Intelligent RPA to Build Process Automation is a one-way upgrade, irrevocable. After the confirmation, please note that the Cloud Factory will be unavailable and all jobs won't launch. So plan the migration accordingly to avoid a long interruption.

Subscription and Migration are performed behind the scenes...

Please wait a couple of minutes the time for the system to transition from Intelligent RPA to Build Process Automation.

Step 4 - Add and/or modify the Role Collections

Build Process Automation comes with three default Role Collections. Existing users would need either to be assigned to this role collection OR you can modify the existing Role Collections by adding the roles from Build Process Automation. For more information about the roles and role collections check this topic in our documentation.

Step 5 - Connect to Build Process Automation and Check the results

After a successful subscription and migration, you can now connect to Build Process Automation. A banner should be displayed if you connect as ProcessAutomationAdmin:

You can now check quickly the content was migrated properly and the corresponding environments as well.

Step 6 - Check or Update Agents (optional)

If you are using a recent version of the agent, agents will be automatically connected with the new URL. A restart of the agent might be needed. If this is not the case, you simply need to provide the new url to the agent. For more information check this topic in our documentation.

Step 7 - Unsubscribe (delete) SAP Intelligent RPA

Assuming that the content has been checked and agents are fully connected, you can terminate SAP Intelligent RPA for unlocking SAP Build Process Automation capabilities (including the ability to create new projects). Once unsubscribed, the "rollback" cannot happen.

Click Delete for SAP Intelligent Robotic Process Automation

Confirm (DELETE)

If the subscription to Build Process Automation was successful, the data from Intelligent RPA is now Build Process Automation enabled. Existing data won't be deleted as they are now powered by Build Process Automation.

Final thoughts

With in-place migration we aim to run faster the transition to SAP Build Process Automation with a effortless solution.

What happens if...

While we have been working on this topic to ensure a smooth migration, if an error happens contact the support immediately and do not delete or unsubscribe.

Additional resources

Transition guide
SAP Note 3334979
Documentation (available soon)

What’s New in SAP Build – Seamless Integration of Processes and Apps

2024-04-19T11:13:49.972000+02:00

Greetings Builders!

We’re pleased to announce this major feature release for our low-code portfolio SAP Build. It is now possible to trigger and consume processes from SAP Build Process Automation directly in SAP Build Apps.

By bridging the gap between the two products, this new capability is a significant step towards a more unified experience across SAP Build. Previously, the primary way to establish a connection was via APIs – the process is described in this blog. Now when developing applications and automations, the integration steps have been simplified to a smooth transition, allowing developers to get deeper insights into process and decision scenarios while enabling a native mobile or web experience.

How to get started

Before getting started with this feature in your projects, we recommend looking at the guide Best Practices: A Strategic Approach to SAP Build Apps. While the low-code approach allows both citizen and professional developers to get started quickly, it’s important to understand optimal approaches, especially for data integrations, to create enterprise apps and extensions that are both scalable and secure.

SAP BTP prerequisites

You will need a BTP Subaccount with service assignments for both SAP Build Apps and SAP Build Process Automation under your entitlements. See the initial setup guides for both:

Setting up the integration

👉 For the complete steps to set up this integration, see the Help Portal.

Important note:

When configuring destinations in the SAP BTP Cockpit, check your service destination (technical name: sap_process_automation_service_user_access) and make sure you have added the following properties: AppgyverEnabled – true, and MobileEnabled – true. This is mainly for subaccounts that were previously provisioned with SAP Build Process Automation via booster. For new ones, the booster should add these properties automatically.

To start discovering and utilizing processes within your applications, you will need to create at least one Business Process and release it in SAP Build Process Automation.

Check out this blog from Rama Murari to explore these steps with a use case for releasing credit blocked sales orders in SAP S/4HANA.

You will find your published processes in the SAP Build Library, which is a new integration option for connecting SAP Build products. Once you enable the selected process, you can begin to leverage it in your apps by adding a logic function that will trigger the process.

Important notes:

Only processes with an API Trigger are visible in the SAP Build Library.
SAP Build Apps can only access the latest published process version. Make sure to always publish the newest version to the library.

After completing the integration steps, you can test it out with the preview app to see that your process is running. In the SAP Build Lobby, you can also confirm your process is successfully triggered with the exact inputs entered into the app!

👉 See the complete steps for this feature in the Help Portal.

We’re excited to make this feature available to our customers as it brings SAP Build closer together with a more harmonized low-code experience. Let us know your thoughts and feedback in the comments.

Happy Building! 🥳🤝

***

▫️Check out what else is on the horizon this year in the Roadmap Explorer: SAP Build Apps and SAP Build Process Automation

▫️ For all recent releases, see What’s New: SAP Build Apps and SAP Build Process Automation

▫️Stay connected with the latest in SAP Build: Builders Group, LinkedIn, YouTube

Accelerate Business Process Development with SAP Build Process Automation Pre-Built Content

2024-04-20T18:48:27.667000+02:00

SAP Build Process Automation is one the three services of SAP Build. SAP Build is a low-code and no-code solution of SAP that provides services and capabilities to create applications, automate tasks and processes and design business sites with drag-and-drop approach and simple configurations.

With low-code no-code tools, SAP is already helping organizations to accelerate their developer efficiency thereby addressing the challenges faced by scarcity in skilled developers and empowering citizen developers or non-IT developers to contribute to the application and process development.

To further accelerate the solution development, SAP Build has published wide variety of pre-built content packages across different industries and line of businesses on common identified whitespaces. These 450+ pre-built content can be explored from SAP Business Accelerator Hub where the content is published by SAP (available for free) and by our partners (available with price).

Each content package contains pre-built processes/workflows, business rules, automations, business monitoring dashboards, UI5 applications, DOX (document extraction) templates and many other artifacts that are needed for the pre-built use case. Organizations can import and configure these content packages – for free – without writing even a single line of code.

Isn’t that what you want when you are working on common scenarios like creating and managing business partners, dealing with mass maintenance of billing blocks in sales orders, or working with journal entry external approvals before posting or invoices processing etc.

If you too are planning to start development on any new scenarios or upgrade existing scenarios in Finance, Procurement, Human Resources, Sales, Asset Management, Manufacturing etc. in your organization, then this blog will help you to kick-start your project with pre-built content.

In this blog, you will find answers to all the queries on the content like where can I discover the content, how to search for the right content, what is SAP Store and how is it different from Business Accelerator Hub, how to import the content, can the content be extended, where to get the support, how to publish content as a partner and many more. If you still do not find the answer, then please leave a comment and I will address it.

Let us start with very basic query:

Why Pre-Built Content?

You may ask why we should go for pre-built content when I have an IT team or implementation partner to build the same use case. Valid point! An enterprise solution requires an IT team or team of professional or solution developers to create an end-to-end use case. There are many building blocks to an enterprise solution. They can create these building blocks using SAP Build or SAP BTP tools and services. But it takes time!

Pre-built content just helps these teams to accelerate their development by saving resources, saving time to market, having a modularized approach, and reducing waste with less coding and testing efforts. Then why not leverage the enterprise ready template or ready-to-use pre-built content that are available for free, aligned with SAP best practices and having full scope of customization and extension.

I strongly recommend my customers and stakeholders, to look for the pre-built content for their industry use cases, import them, extend them if needed and finally integrate them with their applications or other components of their solutions.

… now you will wonder where to look for these pre-built content?

How to find the right content?

SAP Build content can be discovered from:

SAP Business Accelerator Hub from the following direct link: https://hub.sap.com/build
Store option in SAP Build Process Automation subscription application.

where SAP Business Accelerator Hub store is free to explore which means that you can navigate through the store without the need for license of SAP Build or Build Process Automation service but for embedded Store option you will need SAP Build or Build Process Automation service subscription.

Let me start with Business Accelerator Hub options and same steps will apply for embedded store as well.

When you reach to the Business Accelerator Hub – SAP Build Domain page, you will be provided with search and filter options on the left panel. Using these options, you can filter the content or direct type in the search-term to find the content you are looking for.

For example: I want to search for all Finance content, so I will expand Line of Business section and select Finance and you will get the list of related content.

Another example: let us say you know the few terms based on your use case, then you can directly write in search-text. Say Fixed Asset

Go across all the results to find the right content by looking at the title and the description. If you want to know more about the content, then click on content tile and it will take you to the details.

In the overview, you will find the long description of the content which explain what this content does and how it extends the standard solution, including a solution diagram
(which explains the component interactions)

On switching to Artefacts, it gives an overview of complete list of artefacts it bundles. These are the artefacts that you will configure and extend after importing the content.

Documents section provides a detailed step-by-step setup and configuration guide. This will be needed once you decide to use the content. It is the first set of instructions you will need to consume the content in your project.

How to import and use the content?

To import the content, you will need respective SAP Build service. For now, as most of the content is based on capabilities of SAP Build Process Automation service so:

First thing you have to do is install SAP Build Process Automation, if you do not have the subscription already ( follow this help documentation to setup the service in your enterprise or trial account )
Open SAP Build Process Automation subscription application which will take you to Lobby. From Lobby, click to open Store from the left panel.
Store or embedded Store provides the view of only SAP Build content packages as seen in SAP Business Accelerator Hub, with options to import the content. Here as well you can filter or directly search the content with search-text. Same experience as from accelerator hub.

note: you will notice button options like Create from Template, Add or both.

Add option is shown for ready-to-use content which means these content packages are imported as-is and only minimum configurations are allowed.
Create from Template is shown for template content which means the new business project will be created from this template, and you get full scope for any customization or extension.
There will be few contents which has both options, which means you can use them as ready-made, or template based on your requirements.

you can find more details on these metadata properties here.

4. Import the content using Add or Create from Template one-click action.

Important Note: You must follow the setup and configuration guide ( attached with each content) to ensure that you have created and configured all the needed mandatory artefacts like destinations to connect to S/4HANA system, embedded UI5 application as Start tile in Work Zone, setup cloud connectors for any on-premise based content etc.

5. Once the content is imported in the Lobby, you can navigate into the respective project to configure, customize, or extend the content

All the artefacts, templates (excel, PDF or DOX) and source-code (for SAPUI5 apps, CAP models etc.) are provided to you with the imported business project. You can now follow the documentation to first configure the mandatory artifacts, as explained in the document and then choose to extend it based on the requirements or use it with the minimum configuration.

That’s it, that it all it needs to use the SAP Build content. If you haven’t explored them yet I would recommend trying them out in your ongoing or next project – and I am sure you will be pleasantly surprised with the variety of the content and how much it helps you ease your work.

-----------------------------------------

Let me now cover some commonly asked questions:

1. How to get support for the content?

Not all contents are supported. The content that are supported, the respective support information is provided in the documentation. It will either be an email or support component where you can raise ticket for any bug or consultation.

2. What is difference between SAP Store and SAP Business Accelerator Hub?

For SAP Build Process Automation content, SAP Store is the commercial hub which means any partner or LoB who wants to publish a paid content – will have to publish the content in SAP Store. The same gets replicated in SAP Business Accelerator Hub or embedded Store. You cannot directly import the paid content from the embedded Store.

You will notice the Buy option for such content when opened in the embedded store. Clicking this option takes you to SAP Store – which means you must first buy the content from respective vendor, and they will provide instructions to use the content.

3. Can customer or partner publish the content?

Currently only partners can create and publish the content in the store. All the guidance to publish the SAP Build Process Automation content is available in Partner Edge portal.

-----------------------------------------

In upcoming blogs, you will find interesting details on some of our selective and most-sought-after content for different industries. Concluding this blog with some important links that will help you learn further:

Support for API Business Hub Enterprise in Actions Project

2024-04-24T10:35:30.043000+02:00

Motivation

Actions Project built using API Business Hub Enterprise as a supported consumption source will provide the capability to explore, consume and access business and enterprise data connected across various landscapes from the customer’s API Business Hub Enterprise application.

More Information on API Business Hub Enterprise and its usability is available here.

Parent Blog

Actions Editor – Feature List, Usage and Creation/Maintenance of Actions Project

Prerequisites

The official help document Creating an Action Project via API Business Hub Enterprise is available here. It also has details on key prerequisites below to allow the creation of an Action project with API Business Hub Enterprise.

Access to API Business Hub Enterprise application.
- If you want to access API Business Hub Enterprise from SAP Integration Suite, you would need a subscription to the Integration Suite.
Generation of a service key.
Creating a destination for the API Business Hub Enterprise instance with the configurations and additional properties illustrated below.

Destination Configuration

Field	Value
Name	Enter the name of your choice.
Type	HTTP
Description	Enter an optional description for your destination.
URL	URL of the API Business Hub Enterprise application.
Proxy Type	Internet
Authentication	OAuth2ClientCredentials
Client ID	Provide the value of the clientid field from the service key you created. For more information, see Creating Service Key.
Client Secret	Provide the value of the clientsecret field from the service key you created. For more information, see Creating Service Key.
Token Service URL Type	Dedicated
Token Service URL	Provide the value of the url field from the service key you created. Example https://<url-retrieved-from-service-binding>/oauth/token

Additional Properties

Property	Value
sap.applicationdevelopment.actions.enabled	true
sap.build.usage	apihub_enterprise

Note: URL, Client ID, Client Secret and Token Service URL should be entered correctly to ensure that the destination works fine.

Selection of Destination

The Action Designer can navigate to the API Business Hub Enterprise source by first selecting Integration Suite, and then API Business Hub Enterprise in the Actions creation dialog. Next, the user can select the preferred available destinations that have been set up using the above prerequisites. These destinations would connect with the API Business Hub Enterprise instances. A sample illustration is shown below.

Selection of Product

Based on the API Business Hub Enterprise destination, a list of products will be shown. The Action Designer can choose a specific product for their use case.

Selecting the API

Based on the selected product, the Action Designer can choose an API from the available list of API’s.

Review the Methods for the API

The Action Designer can now review the methods/operations that are available within the chosen API.

Create the Action Project

Finally, the Action Designer can create the Action Project using the API chosen in the last step. The project name and description will be populated by default based on the name and description of the chosen API. The Action Designer can modify these details based on their choice before creating the project.

After the Action Designer clicks on the Create button, the system will validate the OpenAPI specification standards in the attached specification. If the validation is successful, the Action Project will open in a new tab of the browser. If the validation fails, Lobby will display an error to the Action Designer.

Testing an Action

After successfully creating the project, the Action Designer will follow the regular steps to select, edit and save details of a selected Action. Before testing the Action, the Action Designer will need to create a new runtime destination. The details required to create the runtime destination are shown below and more details can be seen in the Test tab of the Action Editor. After creating the runtime destination, the Action Designer can test the Action following the regular steps.

Thanks for reading! I hope this post helped you to understand the concept of leveraging API Business Hub Enterprise for the creation and consumption of an Action Project. Please feel free to leave a comment if there are any questions and I would be happy to receive any feedback.

References

Part 1 of the Blog Series: The New Actions Project – Major Changes including the Actions Editor Available Now !!

Part 2 of the Blog Series/Parent Blog: Actions Editor – Feature List, Usage and Maintenance of Actions Project

SAP Build Process Automation Pre-built content for Finance Use cases

2024-04-25T08:07:03.067000+02:00

The definition of pre-built content, how it helps your business to jump-start your automation development and how to discover them is explained in the blog, ‘Accelerate Business Process Development with SAP Build Process Automation Pre-Built Content’

This blog covers the pre-built content for finance use cases specifically.

Financial operations refer to the management of finances and resources within a company. These operations include, accounting, budgeting, cash management, financial forecasting etc. They are the backbone of any organization and require strong and robust solutions to accomplish them.

SAP S/4HANA Finance is SAP’s flagship financial solution. There are many competitive and core features of S/4HANA Finance that helps you solve your Finance and Accounting requirements.

Though SAP S/4HANA Finance solution offers various solutions for widely used finance operations across the industries, there are some features that must be extended with BTP with side-by-side extension approach in order to solve customer requirements.

Side-by-side extensions mean extension and integration with custom or standard business applications of the SAP Business Technology Platform (BTP). This is either via stable APIs or through business events from an SAP product, for example, SAP S/4HANA.

SAP Build Process Automation is used along with the SAP S/4HANA Finance application as a side-by-side extension, to solve complex business use cases that are not planned in the near future as a feature in SAP S/4HANA Finance module. These are identified and validated as a white space in the SAP S/4HANA finance product. Examples of the processes include, Mass processing of Accruals, Creation of Supplier Invoice by Reference Invoice, External Approval while posting Journal Entry etc.

Currently there are 100+ finance use cases for which pre-built content exists in SAP Business Accelerator Hub

These are the widely used use cases in finance industry across various organizations and sectors.

They can be used with no or very minimal changes which makes it as industry best practice.

In order to discover the finance use cases, follow the steps mentioned in the blog ‘Accelerate Business Process Development with SAP Build Process Automation Pre-Built Content’

Or you can simply use the below link to see them in SAP Business Accelerator Hub.

https://api.sap.com/build?$filter=(LinesOfBusiness:%5B%22Finance%22%5D,ProjectTypeHierarchy:%5B%22Process%3ETask%20Automation%22,%22Process%3EBusiness%20Process%22,%22Process%3ELive%20Process%22%5D)

Explaining some of the SAP S/4HANA Finance Use-cases:

1: Journal Entry Posting Approval

A journal entry records financial transactions that a business engages in throughout the accounting period. These entries serve as the initial step to create ledgers and trial balances. Eventually, they are used to compile a full set of financial statements for the company.

This pre-built content covers the capability to validate the journal entry details and based on the document checks, it is posted to SAP S/4HANA on-premise system.

SOLUTION ARCHITECTURE:

This template automates the posting of journal entries to general ledger accounts like making adjustment entries during period end closing or recording business transactions that do not have a source of document etc. It has the below features:

StartUI for data input used for entering the journal entry details with create or upload options
TaskUI approval form for the journal entry approval.
Approval process for approval of journal entry data by determined approver(s) that need to be posted to SAP S/4HANA.
Automations for document check & document post.
Decisions to determine approvers to approve the journal entries.

You can add the pre-built content into your tenant and explore more details via the below link.

Link to the template in Business Accelerator Hub

YouTube video for Journal Entry Posting Approval Process

2: Mass Fixed Asset Acquisition

Business organizations need to acquire long-term assets for their business, which is known as Fixed Asset acquisition. Examples include purchasing machinery, furniture, land and buildings, software, vehicles, or other tangible investments that will be used for a period of more than one year. The fixed asset acquisition process involves researching and evaluating potential purchases to ensure they are necessary and appropriate for the business, negotiating terms, obtaining approvals, managing the payment and delivery processes, and recording details in the books of accounts.

This pre-built content enables business experts to accelerate the mass asset acquisition posting process.

SOLUTION ARCHITECTURE:

This template facilitates the creation of Mass Fixed Asset Acquisition and has the following features:

Start UI screen, to collect the initial selection criteria (Download/Upload) so that required fixed asset acquisition data can be read from SAP S/4HANA Cloud system.
Once the data is read, it is stored in an excel sheet in a specified folder as provided by the requestor of the process.
The data can be reviewed/enhanced by the user and upload it again in the Start UI so that approval workflow gets triggered.
Once the approval is provided by the decision determined approver, the new data gets posted into SAP S/4HANA Cloud system.

You can add the pre-built content into your tenant and explore more details via the below link.

Link to the template in Business Accelerator Hub

3: Mass Creation of Bank Master

Bank master data includes essential details about banks that your company interacts with, such as their addresses, control data, and unique identifiers. This data is maintained once and reused across transactions without frequent changes.

Bank master creation in SAP refers to the process of setting up and maintaining information related to banks within the SAP system.

This pre-built content enables businesses to create bank master in an automated way after approval is provided by a designated approver.

SOLUTION ARCHITECTURE:

This template facilitates read and create of the bank master in SAP S/4HANA cloud system and has the following features:

Check the email with attachment of excel file and save it in a specified folder.
Read the excel file and check the existing bank master data in SAP S/4HANA cloud system.
If data already exists in the SAP S/4HANA cloud system, then details are copied from the system and sent to the requester to review. If details are not existing in the system, an approval flow is triggered so that approver reviews bank master and take a decision on approval.
Once approval is done, data is added into SAP S/4HANA Cloud system.

You can add the pre-built content into your tenant and explore more details via the below link.

Link to the template in Business Accelerator Hub

4: Manage Invoices without Purchase Order

Businesses use non-PO invoice that doesn’t have any associated Purchase Orders (PO), which are usually the result of spending outside of the usual procurement process.

A non-PO invoice, as opposed to a PO-based invoice, hasn’t been pre-approved and, therefore, needs to go through the invoice approval process within the purchasing department.

This pre-built content enables SAP ERP customers to automate the creation and update of non- PO Vendor Invoice in a transparent approach and provide flexibility to meet business requirements. It includes processes, decisions, automation, and visibility scenario artefacts.

SOLUTION ARCHITECTURE:

This template contains API trigger that triggers the process with required invoice details that is submitted from SAP UI5 application form. The template has the following features:

The SAP UI5 screen has invoice details of header and item level, attachments and comments, which can be used to fill details of the invoice and trigger the process.
Invoice data can be validated with decisions that provide easy & flexible use of business validation.
Approver(s) & watcher(s) are notified via email about the request.
This template also uses a decision to group invoice item details for delegation of approval request to the responsible approvers.

You can add the pre-built content into your tenant and explore more details via the below link.

Link to the template in Business Accelerator Hub

Other interesting use cases that you may want to explore in SAP Business Accelerator Hub with respect to Finance LOB are:

1: Central Finance Mappings (CFIN Mapping)

SAP Central Finance is used as a single repository of financial accounting. It replicates the master data from different source systems into SAP Central Finance running on SAP S/4HANA RISE (private cloud).

This template automates the process of mapping, replication and is also capable of resolving issues that may occur or provide insight into the issue which would assist an analyst in resolving it.

This pre-built content is maintained by Central Finance team.

2: Safe Deactivation Procedure for Central Finance Replication

Central Finance uses SAP Landscape Transformation Replication Server (SLT) to transfer data between Source System(s) and the Central Finance system. In a standard replication, users simply deactivate and reactivate replication. However, Central Finance recommends a multi-step procedure for safe deactivation and reactivation.

This template helps in identifying and performing safe deactivation and reactivation of central and non-central finance replication. Creation of log for the execution and facilitates to send email to designated recipients.

This pre-built content is maintained by Central Finance team.

3: Creation of Supplier Invoice by Reference Invoice

Businesses need to create supplier invoices with reference to preceding documents, such as purchase orders, goods and services receipts, inbound deliveries, or purchasing contracts.

This pre-built content streamlines and automates the process of supplier invoice creation with variable amount by monthly / weekly reference invoice within the SAP S/4HANA public cloud system.

SAP Build Apps - より簡単になったSAP Build Process Automationとの連携

2024-04-26T08:04:11.506000+02:00

実はこのブログを書く前に、SAP Build AppsとSAP Build Process Automationの連携についての解説ブログを書いていたのですが、より簡単な機能がリリースされましたので検証がてらご紹介させていただきます。

~~なお、書いていたブログはブログで別のパターンで役に立つので後ほど公開させていただきます。~~
公開しました。トリガーをフォームのまま行いたい、APIトリガーに変更するのが難しい場合はこちらを参考にしてください。

SAP Build Library機能

https://help.sap.com/docs/build-apps/service-guide/sap-build-library
として、SAP Build AppsでSAP Build Process Automationのプロセスを実行する機能がSAP Build Appsに実装されました。

最近SAP Build Process Automationをブースターを使用してセットアップした場合、この機能を使用するためのものがブースターによりセットアップされているのですが、以前にセットアップした場合、もしくはマニュアルでセットアップした場合は前準備が必要です。一応以下が整っているか確認したほうが良いでしょう

１．SAP Build Process Automationのサービスインスタンスの有無
　SAP Build Process Automationのサービスインスタンスが作成されているか確認してください。サブスクリプションでは有りません。サービスインスタンスが作成されているかはBTPコックピットでサブアカウントのInstances and Subscriptionsからインスタンスの一覧を確認します。サブスクリプションの一覧では有りません。インスタンスの一覧です。

ここにService:SAP Build Process Automation、Plan:Standardが存在すればインスタンスが存在していることになります。存在しない場合はCreateボタンから

PlanでInstancesのStandardを選択してインスタンスを作成してください。

※なお、このインスタンスの料金は「サブスクリプションに付随するもの」という扱いで無料です。このインスタンスはSAP Build Process Automationに対してAPIでのアクセスを可能にするものです。よってSAP Build Process Automationがサブスクライブされていないと意味がありません。

インスタンスを作成したらサービスキーを発行してください。サービスキーの中身を２で使用します。

２．sap_process_automation_service_user_accessというDestinationの有無
　BTPコックピットでDestinationを確認し、sap_process_automation_service_user_accessというDestinationが存在しているか確認してください。存在しない場合は新しく作成する必要があります。内容としては

Name: sap_process_automation_service_user_access

Type:HTTP

Description:

URL: <1のサービスキー情報のendpoints/apiの値>

Proxy Type:Internet

Authentication: OAuth2JWTBearer

Client ID: <1のサービスキー情報のuaa/clientidの値>

Client Secret: <1のサービスキー情報のuaa/clientsecretの値>

Token Service URL Type: Dedicated

Token Service URL:<1のサービスキー情報のuaa/urlの値に/oauth/tokenを追加>

Additional Propertiesとして下記を設定します。

HTML5.DynamicDestination=true

WebIDEEnabled=true

MobileEnabled=true

sap.processautomation.enabled=true

Appgyver.Enabled=true

sap.applicationdevelopment.actions.enabled=true

上記を設定したDestinationを作成します。Destination名は決まっているので注意してください。

使用方法

まず、呼び出される側のSAP Build Process Automationのプロセスを作成します。このプロセスのトリガーはAPIである必要があります。トリガーがフォームの場合はこの機能を使用することができません。

トリガーはAPIで作成する必要があります。
APIトリガーの場合の入力の設定は

Process DetailのProcess Inputsから行うことができます。フォームトリガーのプロセスをAPIトリガーに直す場合はこちらでトリガーフォームで入力していた内容を設定する必要があるということです。

トリガーがAPIである必要を除き、他は通常のSAP Build Process Automationのプロセスとして作成することができます。

ワークフローの作成が完了したらデプロイします。デプロイした後に、必ずそのプロジェクトをロビーから

ライブラリに公開するを選んで公開してください。これを行わないとSAP Build Apps側からこのプロジェクトが見えません。

SAP Build Apps側では必須の条件として「SAP Build Appsはsap_process_automation_service_user_access Destinationが存在するサブアカウントで動作させる必要がある」「BTP認証が必須」があります。

まず、SAP Build Appsのプロジェクト上でBTP認証を有効化します。

そしてDataタブのADD Integrationボタンから

SAP Build Libraryを選択します。
すると先程公開したプロセスが表示されます。

ここで出てこないという場合は、Destinationの作成や、SAP Build Process Automationで作ったプロセスの公開をし忘れていないか確認してください。

表示されたSAP Build Process Automationのプロセスを選択し、

Enable Processボタンを押してプロセスを有効化します。

これで連携の定義ができました。次はどのように実行するかです。
簡単にこちらのような画面を作りました。

このボタンをクリックするとプロセス（ワークフロー）起動としたいと思います。
ということでボタンにロジックを追加します。

プロセスの起動を行うロジックは標準に存在しませんのでMARKET PLACEをクリックします。
MARKET PLACEで「TRIGGER」と入力し、

Trigger Processロジックをインストールしてください。

インストールしたTrigger Processをボタンのタップなどのイベントに接続し、
プロパティを設定します。

プロパティのINPUTに表示されている項目はSAP Build Process Automationのプロセスに設定した入力と同じ項目であることを確認してください。
これでSAP Build AppsからSAP Build Process Automationのワークフローが起動できるようになりました。

なお、SAP Build Process Automationのワークフローを起動するのはSAP Build Appsで作ったアプリケーションを使用するユーザーとなります。そのため、このユーザーは両方のアプリを使用する権限が必要となります。

かなりシームレスに連携ができるようになりました。

SAP Build Process Automationの欠点としてフォームの自由度が低いというものがあります。例えば申請などで、申請内容を大分類→中分類→小分類とたどって項目を選択させようと言うことは残念ながらSAP Build Process Automationではできません。この手の作業は大体は最初の１枚目のトリガーとなるフォームで行うことがほとんどです。このようなときトリガーフォームの代わりとしてSAP Build Appsで作ったアプリを使うことでより柔軟な申請フォームとして使用することができます。

ぜひこの機能を活用してみてください。

SAP Build AppsとSAP Build Process Automationの連携（フォームトリガーの場合）

2024-04-30T06:25:48.082000+02:00

※この記事を書いている間にSAP Build Appsに新しい機能がリリースされました。通常はそちらの方法をおすすめします。そちらの機能の解説はこちらです。
この記事はSAP Build Process Automation側でプロセスのトリガーとしてフォームを使用している場合、そしてそれをAPIトリガーに変更することが困難な場合に適用できる方法としてご紹介したいと思います。

SAP Build AppsのアプリケーションからSAP Build Process Automationのワークフローを呼び出したいというときがあります。結論から言うとこれはワークフローをAPI経由で起動させることで可能です。これを行うには前準備作業が必要です。

前準備作業

ここにService:SAP Build Process Automation、Plan:Standardが存在すればインスタンスが存在していることになります。存在しない場合はCreateボタンから

PlanでInstancesのStandardを選択してインスタンスを作成してください。

インスタンスを作成したらサービスキーを発行してください。サービスキーの中身を２で使用します。

２．SAP Build Process AutomationのAPIへアクセスするDestinationの作成
１で作成したインスタンスのサービスキーの情報を利用してBTPコックピットのサブアカウントDestinationを作成する必要があります。

Name: <自由です>

Type:HTTP

Description:

URL: <1のサービスキー情報のendpoints/apiの値>

Proxy Type:Internet

Authentication: OAuth2JWTBearer

Client ID: <1のサービスキー情報のuaa/clientidの値>

Client Secret: <1のサービスキー情報のuaa/clientsecretの値>

Token Service URL Type: Dedicated

Token Service URL:<1のサービスキー情報のuaa/urlの値に/oauth/tokenを追加>

Additional Propertiesとして下記を設定します。

HTML5.DynamicDestination=true

WebIDEEnabled=true

MobileEnabled=true

sap.processautomation.enabled=true

Appgyver.Enabled=true

sap.applicationdevelopment.actions.enabled=true

注意１：正しくはDestinationは必須ではありません。しかし、Destinationを使用しないと認証部分をBuild Apps側でロジックとして書かなければならなくなります。これは結構めんどくさい作業です。Destinationを使用することでそれらの作業をスキップすることが可能で、APIを呼び出すだけとすることができます。
注意２：こちらの記事で作成した/あるいはブースターで作成されたsap_process_automation_service_user_accessというDestinationが存在する場合、それをそのまま使用することができます。

SAP Build Process Automation側の作業

フォームをトリガーとしたプロセスを作成してください。既存のプロセスでも良いでしょう。特に制限はありませんが、強いてあげると、ファイル添付機能を持ったフォームは少々厄介です。これは後で別のブログで解説しようかと思いますので今のところはこの記事に沿った作業を行う場合はファイル添付を行うフォームをトリガーフォームとして使用しないようにしてください。

厄介な部分として、SAP Build Process Automationのファイル添付機能はSAP Document Management Serviceにファイルが保存されます。SAP Build Appsをトリガーとして使用する場合、SAP Build AppsからDocument Management Serviceにアクセスしてファイルを保管する事が必要です。この部分だけで１本記事が書けるレベルですので別解説とさせていただければと思います。

そして、ポイントとなる作業ですが、まずこのプロセスを一度普通に、トリガーフォームから開始してください。トリガーフォームの全ての項目に実際に値を入れて送信してください。
その後、SAP BuildのロビーからMonitoring→Process and Workflow instancesと進み、実行しているワークフローのインスタンスを確認し、Contextの情報を確認します。

startEventというエントリの下にある項目に注目です。これがトリガーフォームで渡された値です。
これと同じ形式の情報をSAP Build Apps側からSAP Build Process AutomationのAPIを実行する際に付与する必要がありますのでコンテキスト情報をコピーしておいてください。
SAP Buildのロビーを開きましたのでもう一つ、同じくMonitoringからProcess and Workflow Definitionsと進み、連携させるワークフローを選択してIDという項目の値を保管しておいてください。この値もAPI実行時に必要です。

SAP Build Apps側での設定

Destinationを使用するためBTP認証は必須となります。
ワークフローを実行するAPIはREST形式で実行しますので

DATAタブでのデータ連携設定ではSAP Build Apps classic data entitiesの下にあるSAP BTP Destination REST API Integrationを選択します。
Data entity nameは任意に設定し、BTP Destination nameは前準備２で準備したDestinationを選択します。

ここで、好みの問題がありますが、このAPIを呼び出すときに引数として明確に扱われるようにResourceSchemaを設定します。

設定する内容はSAP Build Process Automation側でワークフローを実行し、取得したコンテキストのstartEventフィールドに含まれているものを設定します。例として

"startEvent": {
"itemNumber": "AAAA",
"itemName": "LAPTOP1",
"price": 799.99
}

このようにstartEventフィールドに有りましたのでこの３つを設定します。

データ型はSAP Build Process Automationのワークフロー側に合わせる必要があります。トリガーフォームでのフィールドのデータ型を参考にして設定してください。

ワークフローを実行するAPIはhttps://api.sap.com/api/SPA_Workflow_Runtime/path/post_v1_workflow_instances
の/v1/workflow_instancesです。（複数ありますが、start a new instanceと書いてあるものです。）
これはPOSTで実行することが求められていますので、Buils Apps側ではCreateメソッドを用いることにします。create横のスイッチボタンを有効化します。

APIとしては/v1/workflow_instanceを呼び出すことになるのですが、エンドポイントとしては/public/workflow/rest/v1/workflow-instancesとなります。Relative path and queryに追加のパラメータを設定し、Static Textとして/public/workflow/rest/v1/workflow-instancesを追加します。

このAPIはBODYの内容をJSONで送信する必要がありますのでRequest HeadersにContent-Type : application/jsonを設定します。これはRequest Headersの設定で

List of Valuesの方を選択し

直接書き込むことで設定します。

BODY部分はJSONで送信する必要があります。確実にJSONで送信されるように
Request Body Mapperで式を用い、ENCODE_JSON関数を用いて設定します。

以下のように設定します。書式としては

ENCODE_JSON({"definitionId":"<事前に取得したワークフローのIDの値>","context": {<startEventに存在する全てのパラメータ>}})

とおぼえておけばよいでしょう。ResourceSchemaで設定した変数はquery.record.<変数名>で参照することができます。
ポイントとして、ENCODE_JSON関数は中で使用された変数のデータ型までは見てくれないようです。そのため、数値型を使用する場合はスクリーンショットのようにNUMBER関数を用いて明示的に数字型として指定して下さい（ "price":NUMBER(query.record.price) ）。これを行わないと文字列としてダブルクォーテーションで囲まれた状態でAPIに引数として渡され、ワークフローの実行時にデータ型が合わないというエラーになります。

これでワークフローを実行するためのデータ連携設定が完了しました。
あとはこれを呼び出すだけとなります。
ボタンなどにロジックを作成します。

Create Recordロジックを接続し、

プロパティのResource Nameとして先ほど作成したデータ連携設定のものを指定します。Resource Schemaを設定してあればRecordの設定で

このようにわかりやすくパラメータを指定できるので便利です。
Input Fieldなどの値をここに設定することでそれが送信されて、SAP Build Process Automationのワークフロープロセスが起動します。

SAP Build Process Automation側から見るとトリガーフォームがBuild Appsのアプリケーションに入れ替わった形となります。したがってプロセス上はトリガーフォームの次のロジックから動作し始めるということになります。

SAP Build Process Automationのフォームでは不可能なこと、例えば

このようなカテゴリを選んで製品を絞り込んで申請する、大分類→中分類→小分類→製品と絞り込みたいという場合、トリガーをBuild Appsで作成するという手法を取ることができます。

SAP Build Process Automationのフォームにより自由度を持たせたいという場合はSAP Build Appsの使用もぜひ検討して下さい。

10+ ways to reshape your SAP landscape with SAP Business Technology Platform – Blog 7

2024-05-06T09:21:24.167000+02:00

Blog 7: The Role of Automation for Transformation Projects

In times of constant change, quickly emerging demands for digitalization and competitive markets, companies are looking for ways to further optimize their processes. Consequently, many organizations have turned to automation technologies, such as RPA tools, to automate mundane and repetitive tasks. The benefits of automation are quite obvious: Automated processes are faster, less prone to error and people can concentrate on more complex, higher value-added activities.

Especially for activities with high volumes the benefits can be huge. Let me illustrate this with an example: A few weeks ago, I talked to a company from the consumer products industry. While a lot of transactions with its suppliers run fully digital via B2B integration, they still receive roughly 4.000 documents per month such as invoices and purchase orders via email. Let us assume you need on average 2 minutes for processing one document, that is: Extracting and verifying the data, collecting approvals, creating it in the ERP system and so on. In total, this sums up to over 130 hours of manual work per month. Applying RPA tooling and AI for document understanding can drastically speed up the processing of these tasks, thereby freeing people from tedious copy & paste or data entry and export activities.

Why looking at automation only is not enough

To streamline their processes, many companies have also started looking into other technologies: Besides RPA, also workflow engines, integration middleware as well as tools for process mining and process analytics have risen. One big downside is that these technologies often are not well integrated and hence customers are struggling with setting up an aligned end-to-end approach.

With our Enterprise Automation offering we want to address this and provide a unified and interlinked approach. As described in the blog article by Angela Harvey, this concept is based on the combination of 3 products:

SAP Integration Suite: You cannot automate what you can’t connect to. Our suite provides unparalleled connectivity and integration for a variety of scenarios. Be it SAP / Non-SAP, Cloud / on-Premise applications, B2B, B2G, API-led or event-driven scenarios.
SAP Signavio: Before you optimize, you might need to understand where to start and uncover inefficiencies first. With SAP Signavio you can analyze, model and govern your business processes to drive operational change.
SAP Build: Drive automation of long-running processes with capabilities for app development, process automation and portal sites. Low-Code/No-Code and visual design tooling also empower citizen developers and business experts to contribute to the development process in an agile fashion.

It is important to note that Enterprise Automation is a flexible and modular concept. Hence, customers can start with whatever product they see fit. From a transformation perspective Enterprise Automation can provide significant benefits when modernizing your SAP ERP, so when moving from the classic SAP Business Suite to SAP S/4HANA. It can be applied at any stage, both before the migration as well as after the migration:

Before the move: Leverage Signavio’s “plug and gain” approach and LeanIX to analyze and clean up processes in advance and gain immediate benefits from applying automation (e.g. via pre-built content packages). Use the Integration Solution Advisory Methodology of the SAP Integration Suite to design and prepare a future-proof integration strategy.
After the move: Bring process excellence to the next level by combining process mining, integration and automation and enable a continuous improvement cycle. Enable a governed approach to accelerate and scale the building of process automations based on Low-Code/No-Code techniques.

Another advantage in terms of transformation is the versatility – similar to a Swiss Army Knife. Enterprise Automation allows process optimization across the enterprise and line of businesses: Be it sales, procurement, HR, finance, production or logistics. A comprehensive collection of use cases and end-to-end scenarios has been put together by Manuel Namyslo in his blog article: How to get started with Enterprise Automation.

The role of AI in Enterprise Automation

Let us take a closer look at the role of AI and how it fits into the picture of Enterprise Automation. When transforming business processes and modernizing enterprise applications, AI should be part of the agenda, due to the massive benefits it can provide. Within our Enterprise Automation offering, the AI capabilities are tightly embedded to make the consumption as easy, seamless and relevant as possible.

A few highlights of them include:

Use Document Information Extraction (DOX) within SAP Build Process Automation to grab data from documents like invoices, payment advices and purchase orders to automate their processing. We also plan to integrate the DOX premium edition to make the processing of arbitrary documents with varying structure and layout even simpler.
We plan to use AI to provide recommendations for workflows as proposals based on historic data. This will support and speed up the decision making for approvals and workflow items (see roadmap item).
Visual tools already cater towards ease-of-use and simplify the building of process automations by business experts. There are also plans to make the design process even more intuitive by leveraging Generative AI functions (see corresponding roadmap items). As illustrated in this preview video, users describe what they need or what they want to craft in natural language. This can be an entire process flow, but also single process steps such as a business rule. The system then automatically generates the respective building blocks. Apart from that the AI-based assistant will also help with the discovery of pre-built content by providing suitable proposals from the content catalog.

As you can see AI is a crucial factor in many ways. Not only for the automation of processes, but also to accelerate the design and development process in various aspects. In addition, Enterprise Automation can also help with infusing AI into the process layer, by providing the respective integration capabilities.

To conclude: Enterprise Automation should be considered as a strategic tool set in the light of any transformation initiative for ERP and enterprise application landscapes. Its modular style allows you to start small at any stage of your project: From simple workflow automation and high-level process modelling, up to a fully-fledged vehicle for continuous process excellence. While our offering is optimized for SAP applications and systems, we embrace openness and enable process excellence across heterogeneous IT landscapes.

Where to look next and where to start? I recommend checking out the blog article How to get started with Enterprise Automation to get further inspiration. In addition, Low-Code/No-Code tooling such as SAP Build is well suited for getting Hands-On experience. Therefore, feel free to reach out to your SAP account manager to experience the ease-of-use in a Hands-On workshop. Finally, start by looking into potential use cases and assess them with the help of SAP or partners on how to tackle them with Enterprise Automation.

Previous Blogs:

Blog 1: The Central Role of Clean Core and AI
Blog 2: The Role of BTP as Extension and Innovation Platform
Blog 3: How Clean Core can accelerate your SAP Business Transformation
Blog 4: Mastering the Data Dance: The Potential of Clean Core and AI
Blog 5: How hybrid Integration upholds the role of Clean Core
Blog 6: Clean Core Extensibility

Mass upload utility via API to SAP S/4HANA Cloud Public Edition with SAP Build Process Automation

2024-05-13T14:42:08.947000+02:00

Collaborative effort of Bhavneet Kaur and Pavalavel Kanagavel

This blog post will provide detailed information on how to build a utility to mass upload via API to SAP S/4HANA Cloud Public Edition using SAP Build Process Automation.

Introduction

Let’s take a scenario for Service contracts where we need to mass upload the contracts in SAP S/4HANA Cloud Public Edition. SAP Build Process Automation enables the business users to automate the mass upload via excel with low-code no-code. SAP Build Process Automation is available as a service on SAP Business Technology Platform (BTP).

Process steps

Following are the steps elaborated to setup the SAP Build Process Automation for the mass upload of service contracts via an excel:

Subscribe and configure to SAP Build Process Automation in the BTP Account: Help Link

2. Access SAP Build Process Automation application. Install and configure the latest version of Desktop Agent: The Desktop agent is responsible for running automations. Make sure to Connect/register your agent to SAP Build Process Automation. Help Link

3. Configure the destination in BTP account to connect to SAP S/4HANA Cloud Public Edition system. The destination is used by the build project to make a call to SAP S/4HANA Cloud Public Edition.

Make sure you have set up Communication arrangement for Service Contract in SAP S/4HANA Cloud Public Edition .

4. Import Destination from BTP cockpit to SAP Build Process Automation.

5. Create an Action using Service contract API:

Help Link

6. Set up Process Automation and call the action created in step 4:

Help Link

This is sample that’s created to show we can use Build application with no code to post documents to SAP S/4HANA Public Cloud Edition.

Sample excels.

Header tab

Item tab

Automation

Green (Step 2 and step 3) -> We are reading data from each excel tab and storing into data type.

Red (Step 4 and Step 7) ->Looping first at header and then for each header looping at item to add all the line items to a list.

Blue (Step 5 and Step 9) -> Condition -2 we are checking if the header row is not empty, in case not then. Condition -3 we are checking if the line-item row is not empty.

Now in excel only rows filled with data will be considered.

Now we are in nested loop.

Yellow (Step 11 & 12) -> we are checking if header dummy contract number matches with Item dummy header contract.

Purple (Step 13) -> we are adding it to a list.

List type

Black (Step 15) -> we are calling the action project. Here you can see the destination.

Step 16 and step 17 we are clearing the list. So that the iteration starts for next contract.

We are closing and releasing the excel. Further to it logging can be added. As mentioned, it samples to show product capabilities.

7. Create an unattended trigger for your process automation and run now.

Once the automation is deployed, we create an unattended trigger. For complex types we cannot schedule attended trigger.

8. View the Automation executed under the Monitoring> Automation Jobs tab

9. Result in SAP S/4HANA Cloud Public Edition cloud public edition

Conclusion

This blog post should help you to understand in detail how to use SAP Build Process Automation to mass upload documents in SAP S/4HANA Cloud Public Edition with low code no code.

Thanks for reading this blog post, hopefully the blog post was informative.

SAP Tech Bytes: SAP S/4HANA Cloud + SAP Integration Suite, AEM + SAP Build Process Automation

2024-05-20T13:25:58.571000+02:00

In this blog post, I share a couple of SAP Tech Bytes on how to enable eventing between SAP S/4HANA Cloud and SAP Build Process Automation via SAP Integration Suite, advanced event mesh. We will configure and trigger events from SAP S/4HANA Cloud, which will then be received by SAP Integration Suite, advanced event mesh, and finally forwarded to SAP Build Process Automation.

Enabling the end-to-end event-driven integration scenario between SAP S/4HANA Cloud and SAP Build Process Automation involves many steps and requires extensive documentation. Sometimes, it might be best to process all that information in video format.

If you're interested in learning how to enable the same scenario using SAP Event Mesh, check out this blog post: https://community.sap.com/t5/technology-blogs-by-sap/sap-tech-bytes-deliver-events-from-sap-eventmesh-to-sap-build-process/ba-p/13574547.

SAP Tech Bytes: Configuring SAP S/4HANA Cloud and SAP Integration Suite, advanced event mesh

Steps shown in the video:

Now that we've configured the communication between SAP S/4HANA Cloud and SAP Integration Suite, advanced event mesh, we can proceed to configure the delivery of events to SAP Build Process Automation.

SAP Tech Bytes: Delivering events from SAP S/4HANA Cloud to SAP Build Process Automation via AEM

Steps shown in the video:

In this SAP Tech Bytes, we’ve seen what’s required to configure eventing between SAP S/4HANA Cloud and SAP Integration Suite, advanced event mesh. Also, we created and configured a REST Delivery Point in AEM in order to forward events to SAP Build Process Automation. The REST Delivery Point functionality is not limited to SAP Build Process Automation; you can also deliver events to other systems that expose an HTTP endpoint to receive them. I hope you enjoy this video on event-driven integration, as there is more to come on this topic in the near future….

Happy eventing!