Prerequisites:
Steps:
SAP Cloud ALM continues to evolve as an indispensable tool for managing and monitoring SAP landscapes. The latest updates to Job Monitoring bring significant enhancements, enabling organizations to efficiently manage automated processes, improve transparency, and streamline operations.
This blog explores these updates in depth, offering insights into how they can empower businesses to optimize their IT operations and adapt to evolving business needs.
The PO Workbench in SAP S/4HANA is designed to simplify the management of purchase orders by offering a user-friendly interface and powerful features. It enables users to efficiently manage large volumes of POs and STOs, saving time and reducing the administrative burden associated with procurement processes. One of its standout features is the ability to assign open, account-assigned purchase requisitions to available POs, ensuring that procurement activities adhere to business rules and objectives. With capabilities such as mass maintenance, quick changes, and improved traceability, the PO Workbench not only streamlines procurement activities but also ensures they align with overall business goals.
Within SAP Datasphere a task chain is a structured sequence of tasks or operations designed to be executed in a specific order or concurrently. It automates the process of running multiple related tasks, ensuring that they are executed in a predefined sequence or parallel, depending on the requirements. Such objects can be Remote Table Replication, View Persistency, Intelligent Lookup, Data Flow, Replication Flow and Transformation Flow runs.
SAP Datasphere now allows also the integration of SQL Procedures directly into Task Chains. To achieve this, you start creating a SQL Procedure within the underlying SAP HANA database. Once the procedure is created, it can be incorporated into your Task Chain. This guide provides a quick overview of the necessary steps and considerations for this process.
This blog describes how to execute SAP C4C/BYD OData services using client certificate when testing custom/standard OData services in the Postman.
As in the custom/standard OData service, you can use the business user and technical user basic authentication in the Postman. In addition, you can use the SSL certificate-based authentication in postman.
SCENARIO: Testing SAP C4C/BYD OData service using client certificate-based authentication in Postman.
Welcome to the first segment of this two-part series. In this introductory blog, I want to provide an overview of the following key aspects in relation to data access control in SAC and going from SAC to Datasphere:
In Public Cloud all of us are familiar with Key User Extensibility for extending custom fields in Standard apps /objects. With 2408 version, the new feature extension field wizard can be used to add extension fields to existing RAP business objects. The entire data model of the business object is extended, from the database table to the UI/API OData Service. This feature is available in development tenant and can be used from ADT.
Let’s have a look at quick demo
When we talk about outbound communication where Cloud Integration acts as client, we must mention that Cloud Integration doesn’t offer any choices about how the user associated with the outbound request should be authorized to execute certain actions in the receiver system.
Therefore, as integration developer, you can’t specify any authorization options. This situation is plausible for the following reason: How the permissions of a calling entity are checked can only be defined by the technical capabilities of the server (in the outbound communication case, the receiver system). Because Cloud Integration (as a client in this case) can’t decide which technical capabilities are offered by the receiver system, SAP Cloud Integration cannot allow you to specify any authorization options in a receiver adapter.
The real test of any product is what happens when the rubber meets the road. In this post, we’ll look at a practical example of SAP Cloud ALM.
Many SAP partners both lead the front in tool adoption and go a step further by creating enhancements on top of it using our published APIs. They also help to shape the product by providing early feedback. We are thankful to RBEI for sharing the following story from their customer projects.
RBEI is a 100 percent owned subsidiary of Robert Bosch GmbH. It is one of the world’s leading global suppliers of technology and services, offering end-to-end engineering, IT, and business solutions. Syed You suff, Practice Head, Cloud and IT Infrastructure Platform at RBEI, provided insight on how RBEI took advantage of the SAP Cloud ALM.