How to Create a Custom Validation from Fiori App Manage Substitution and Validation Rules

As we are moving to Fiori first yet cloud ready approach for any development, why restrict us to GGB0 or GGB1 for creating validation or substitution rules?

We can utilize the Fiori application - Manage Substitution and Validation Rules to create the rules which will be applied to all the standard processes such as standard interfaces, GUI T-codes and managing standard processes in custom program.

In this blog, we will create a custom-defined function in the validation rule on asset creation or modification done through the Fiori app - ‘Manage Fixed Assets’. The rule will validate against the supplier assigned to the asset master record.

Calling Fragment Form & Send it as an attachment using ABAP Walk-Through

This Blog is based on the Output Management Form and has all of its configuration completed 

Ex for dunning: use maintenance view: V_T047E using code: sm30 to switch between frameworks through drop-down list

Creating custom DANFE | Output Management | S/4 HANA Public Cloud Edition | release 2308

Introduction

In S/4 HANA Public Cloud, we exclusively work with Adobe Forms to handle standard or customized forms. To develop a customized form, it is necessary to customize it using Adobe LiveCycle Designer and apply some settings in the environment so that the form in question can be used. I bring an example with one of the most requested forms by clients: the dear DANFE.

Need

Customization and implementation of a customized DANFE form to meet the needs of the end user. S/4 HANA Public Cloud environment – release 2308

Alternative option for IMPORT/ EXPORT using Shared Memory SHMA approach.

Motivation:-

In this blog you will learn how to use shared memory as alternative option of ABAP Memory(Import/Export).

Business Scenario:- Many of times we need Import & Export at the time of SAP Enhancement or other requirements so Here use of shared memory which is also alternate option of Import/ Export and as per SAP standard guideline this approach is highly recommended.

SAP ABAP RAP: Custom Entities with compositions relationship in a Fiori Elements App

Introduction:

ABAP Restful Application Programming is an efficient and cloud-compatible development model that enables rapid creation of Fiori apps.

This programming model facilitates both Managed and Unmanaged Implementation approaches, although the core data source must originate from a CDS view or a table within the same system in both scenarios. However, the non-key fields can be calculated on the fly using virtual elements.

When retrieving data from a remote source through an API or performing complex calculations, managing CDS view entities becomes challenging. Further complexities arise when compositions  are involved.

Vendor and Customer Code in G/L Line Items for Accruals, Deferrals, and Provision Accounting Entries Enhanced Through In-App Extensibility

Introduction

In your business operations, it is customary to manage manual accruals, deferrals, and provision accounting adjustments by utilizing the automatic reversal feature when posting general journal entries. These transactions take place at the G/L level without involving specific vendors or customers, making it challenging to generate vendor or customer-wise reports for accruals, deferrals, and provision accounting when required.

SAP S/4HANA Cloud, public edition, ABAP Environment Case 5: Purchase Requisition Mass Upload

This is a detailed step-by-step technical guide document to introduce a Developer Extensibility case followed by this blog.

1. Case Background:

In this case, we create an custom Fiori application, which can create multiple purchase requisitions from an Excel file template. Furthermore, you can define the upload template based on your own requirement.

Your Guide to Calling S/4HANA APIs from SAP Build Apps

A year ago, people got busy building S/4HANA extensions with SAP Build Apps, and demanded a feature that would make their OData calls easily – by using $expand to get more data with fewer calls. That feature was recently delivered.

But people are still were confused.

When you create a connection to an OData service, SAP Build Apps automatically provides you with the schema so you can reference all the fields. But even when you expand the associations, the schema for the associated objects is not (readily) available.

How to Manage and Move Transport Request in S/4HANA Public Cloud in 3 System Landscape

Purpose of this Document

This document helps you understand moving transport request from Development to Q system and Q system to Production system in 3 System Landscape. Transports for business configuration, key user extensibility, and developer extensibility are of the different categories and that is why these are separated. So, we need to understand all of three.

ABAP RAP: Side Effects in CDS Behavior Definition and its variants

Introduction

 

​The most awaited feature was released for SAP BTP – ABAP Environment in 2302. It is none other than ‘Side effects in CDS Behavior Definition’.

I have been waiting for this feature and can’t stop myself from trying it. I thought the syntax would be complicated and was surprised when I realized they were so simple and readable.

​​​Side effects are useful in UI scenarios based on draft-enabled BOs to notify a Fiori Elements UI that data changes of defined fields require the recalculation of other data values, permissions or messages.​

Developer Extensibility for SAP S/4HANA Cloud on the SAP API Business Hub

This blog post helps in understanding developer extensibility for SAP S/4HANA Cloud (aka Embedded Steampunk) and discovering them on the SAP API Business Hub.

Problem Description

Today, customers and partners can use key-user extensions and side-by-side SAP Business Technology Platform (BTP) extensibility to extend SAP S/4HANA Cloud. What is the motivation behind introducing Developer Extensibility? Do customers need all these? When to use what? And finally, where to discover the released artifacts from SAP.

Extensibility in SAP S/4HANA Cloud

Introduction

Extensibility covers a broad spectrum of topics that allow customers and partners to adapt standard business software to their business needs. This includes business configuration, integration, custom fields, and logic, layout adaptation of user interface (UI), forms, and reports. It also covers custom terminology and translation for customer-specific applications. (SAP, 2022)

Extensibility in SAP S/4HANA Cloud can be divided into three parts:

◉ In-App/Key User Extensibility

◉ Side-by-Side Extensibility

◉ Developer Extensibility/Embedded Steampunk

Realizing a Clean SAP Core: A pragmatic approach towards digital transformation

Introduction

The world today witnesses a massive digital transformation, impacting organizations globally through fast-evolving business models. Likewise at SAP, key products and solutions are advancing with all the more flexibility and robustness. To enable this agility within the foundations of ERP, has repositioned its flagship product offering to a new ‘digital-core’ in the form of S/4HANA. With the recent S/4HANA releases also on Cloud, the new digital core offers a fascinating array of new innovations, ranging across digital-age User Experiences, next-gen Business Processes and Embedded Intelligence, through seamless integration and automation options.

Numerous existing customers however, are still on the former SAP ERP (ECC or older) systems with many of them also engaging industry specific components to support their businesses. With SAP’s future plans of withdrawing support and maintenance for its legacy ERP software versions, customers are required to devise an upgrade strategy to move to S/4HANA solutions, mostly through Brownfield implementation projects. In the process, project teams typically deal with several technical hiccups in managing custom code, around aspects like complexity, dependency with SAP standard, upgrade stability etc. This is where the catchphrase ‘Clean-Core’ comes in, which essentially emphasizes on fitting to standard offerings, extending them appropriately, and decoupling custom objects with minimal dependency to standard solution lifecycle outside the central ERP, therefore making the ‘Core’ clean. The coming sections will elaborate the needs, benefits and ways to achieve a realistic and modern ‘Clean Core’ SAP solution.

Explore Business Add-Ins (BAdIs) for SAP S/4HANA Cloud on SAP API Business Hub

This blog post describes how to explore released Business Add-Ins (BAdIs) from SAP S/4HANA Cloud on SAP API Business Hub.

Problem Description

If Developer Extensibility with Embedded Steampunk is for ABAP Developers and technical users, then where can they find the APIs to build the extensions? Also, are there any technical documentation available for developers which they can refer to?

Explore Business Object Interfaces for SAP S/4HANA Cloud on SAP API Business Hub

This blog post describes how to explore released Business Object Interfaces or RAP BO from SAP S/4HANA Cloud on SAP API Business Hub.

Problem Description

If Developer Extensibility with Embedded Steampunk is for ABAP Developers and technical users, then where can they find the APIs to build the extensions? Also, are there any technical documentation available for developers which they can refer to?

How to Set Up the Email Notification for Flexible Workflow in SAP S/4HANA Cloud

Background

SAP has provided a Standard Solution to notify the users about new work items generated by flexible workflow and displayed in the ‘My Inbox’ app.

Introduction

The default notification in SAP S/4HANA Cloud is through alerts that are displayed in the SAP Fiori Launchpad, but it is also possible to configure the system to notify users via email about new work items in their inbox.

Moreover, it is possible to configure the system to send notification for approval or rejection of requests.

Transactional Fiori App using ABAP Restful Programming Model

UI Apps development is getting simplified with the evolution of ABAP. In my experience when UI5 was released i had to learn JavaScript ,jQuery concepts and use them to create even a simple UI App ,and then with the advent of  ABAP Programming model for Fiori it changed the approach, since using BOPF with annotations we can easily create  simple Transactional UI app’s with minimal frontend code. Now with ABAP RAP programming which is an evolution of latter, it further simplified and made flexible for UI App development.

CDS based data extraction – Part III Miscellaneous

Back to the CDS view extraction..

After the Overview in part I and Delta deep dive in part II, I would like to spend the final blog on some miscellaneous points regarding CDS view based extraction.

Hierarchy extraction

The topic of hierarchy extraction deserves a small section, as some things have changed here in contrast to the classical extractors. You will need to make some changes to your hierachy bearing characteristics in order to work with the hierarchy CDS views. This is due to the fact that the node texts are not delivered by the actual hiercharchy CDS view, but a separate one.

CDS based data extraction – Part II Delta Handling

As promised in part one, let’s have a closer look at the delta handling in CDS based extraction.

In cases, in which big data volumes with a frequent changes are expected, e.g. transaction data like sales orders or similar, the application needs to provide delta records. In most of the cases daily (nightly) full uploads are not what you want, as time windows for data extractions are limited. Extraction of transaction data should always be delta enabled as this allows a seamless loading and reporting scenario.

CDS based data extraction – Part I Overview

Anyone interested in the state of the art extracting data in the SAP universe and beyond? This blog (series) is meant to provide a comprehensive overview of the topic, highlight the main features but also make sure you understand the meaning and implication of all available annotations related to the topic. I am aware of the fact that various documents/blogs have been published on the topic already, but for sake of completeness I will repeat parts here which you might already know.