Fiori Adoptation Project for Extending Standard Fiori Application for onPremise using BAS

Prerequisites:

◉ On BTP: Cloud Connector Connection to Gateway system and Destination 

◉ OnPremise: Activating required standard Fiori Application

Step 1: Open Template Wizard and select the application type as SAP UI5 Adoptation Project.

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.

Purchase Order Email with PDF Attachment On Approval

The article will let you go through purchase order email when an approval workflow is triggered at the time of release purchase order.

This article will include following:

1. Purchase Order PDF Conversion

2. Create HTML Content of Purchase Order Email

3. Send Purchse Order Email with Purchase Order Document in PDF format

Create and Deploy MTA Project to Cloud Foundry account using Business Application Studio

Deploying Fiori List Report and Object Page application to Cloud Foundry account.

We have created Fiori List Report and Object Page Application as MTA Project using Business Application Studio.

Below video shows step by step detailed process of deployment.

Step By Step Guide Create and Deploy MTA Project

What is MTA Project

MTA stands for Multi Target Application. Multi Target Application logically created with multiple different parts which may be written using different languages or technologies. All of these different parts works together to complete application life cycle.

ABAP Restful Application Programming : Real Time validation on field input in transactional Fiori Application

Introduction:

Main aim of any application is to keep the transactional document error free. That says how important is error handling and validations in the application process.

In this blogpost, I will explain how we can implement real time validations on field input in a transactional fiori application with ABAP RAP framework. Instead of executing the validations at the save in the end.

ABAP Restful Application Programming : Real Time validation on field input in transactional Fiori Application

Introduction:

Main aim of any application is to keep the transactional document error free. That says how important is error handling and validations in the application process.

In this blogpost, I will explain how we can implement real time validations on field input in a transactional fiori application with ABAP RAP framework. Instead of executing the validations at the save in the end.

Problem statement :

In the traditional approach ( link ), the validations can only be executed at SAVE in the end. The disadvantage in this approach is that inconsistent values have already been entered and the document becomes inconsistent. if it is a draft enabled application, then these inconsistent values have already been stored in draft tables and transactional buffers. This is additional work for the user to clear all those errors at the end. As a user, he/she always expects to display the error on field input.

ABAP Restful Application Programming : Enabling draft feature to the custom implemented Actions

Introduction:

Enabling Draft is most common feature in current projects irrespective of Managed/Unmanaged scenario in fiori applications.

In short, lets see what the draft is.

Draft-enabled applications allow the end user to store changed data in the backend and continue at a later point in time or from a different device, even if the application terminates unexpectedly. This kind of scenario needs to support a stateless communication and requires a replacement for the temporary in-memory version of the business entity that is created or edited. This temporary version is kept on a separate database table and is known as draft data. Drafts are isolated in their own persistence and do not influence existing business logic until activated.                                                          

Problem statement:

Standard RAP framework takes care of creation/modification of draft records for all standard operations (CREATE / UPDATE) but it is developer’s responsibility to implement draft for all custom actions in the applications. In this blog post, we will see how we can implement draft for custom actions.

SAP S/4 HANA Custom Fiori app for Project & WBS using CDS View Table Function, SmartFilter & Tree table

In this blog, I would like to present the custom Fiori app that I developed for searching for Projects, WBS elements, and settlement cost centers. This blog will present details on how to read Project and WBS data using CDS views and table functions and then render the data in a tree table with a smart filter.

Here is a snapshot of the custom Fiori application showing Project, WBS element and settlement cost center data in a nice tree view table with a smart filter bar:

CDS View Entity

The purpose of this blog is to show the created CDS view entities including Analytic Query, Extended entity, Annotate Entity in the system.

Test system

◉ S/4HANA On premise 2020 Initial shipment stack

◉ ABAP Platform Initial shipment stack (SAP_BASIS 755/0000 with SAP Kernel 781 patch19).

Adding features to FIORI Element List Report using CDS views and annotations

In this blog, I will provide CDS annotation details, some tips and tricks along with examples to demonstrate how we can add features to a basic FIORI elements List report without having to change much in the UI code. This is especially helpful to backend /ABAP developers as these features can be implemented only using CDS views.

After you have created a basic list report application, you can add the following features using CDS,

Fiori Elements extensibility using CDS and KUE (Key User Extensibility Tool)

Prerequisites

UI Adoptation with KUE( Key user extensibilty) required certain security Roles.

Please make sure to assign  security Role SAP_UI_FLEX_KEY_USER to your user id in Fiori Front system.

Fiori Elements-Value help on a selection field within a value help dialog

This is about featuring the capability of Value help on a selection field within a value help dialog in Fiori Elements based List Report.

Business Scenario

Let’s consider Business scenario where Fiori Elements based List Report displays Purchase Order with Vendor as one of the selection field.

Embedded CDS View exposure to Fiori

1. Introduction

As we are aware that in SAP S/4HANA system, most of the DDIC tables has been converted to CDS views or DDL SQL Views. SAP is trying to mold all the technical changes/ABAP using these CDS views.

Fiori elements utilizing CDS with Virtual Elements

This Blog is about utilizing the CDS’s virtual elements feature which as exposed as ODATA Via SADL (direct in SEGW / with ODATA Publish true annotations). This ODATA can be further consumed by Fiori Elements based application.

Also following SAP standard documents are helpful for understanding of CDS with Virtual elements.

Fiori Elements – Bullet Micro Chart in List Report

Introduction

In this blog, I’ll explain Micro Bullet chart’s feature and how to use it in List Report using CDS annotations. I have added screen shot from annotation modeler and respective xml code in case you are using one of these approach.

The bullet chart features a single, primary measure. It compares that measure to one or more other measures to enrich its meaning (for example, compared to a target), and displays it in the context of qualitative ranges of performance, such as poor, satisfactory, and good.

Creating a draft enabled Sales Order Fiori App using the new ABAP Programming Model – Part 6: Converting the draft instance into an active instance & wrap-up

Converting the draft instance into an active instance

In the previous part we were able to provide our app with basic functionalities and draft handling. By now our app should be able to:

◈ Search for Sales Orders
◈ List Sales Orders
◈ Display Sales Order details
◈ Lock Sales Orders
◈ Delete Sales Orders
◈ Create new Sales Order draft instances
◈ Convert an existing Sales Order into a draft instance

Creating a draft enabled Sales Order Fiori App using the new ABAP Programming Model – Part 5: Adding determinations

Adding determinations

In the previous part we were able to provide our app with basic functionalities. By now our app should be able to:

◈ Search for Sales Orders
◈ List Sales Orders
◈ Display Sales Order details
◈ Lock Sales Orders
◈ Delete Sales Orders

Creating a draft enabled Sales Order Fiori App using the new ABAP Programming Model – Part 4: Implementing locking & delete functionality

Adding logic using BOPF

In the previous blogs we’ve prepared our virtual data model which we exposed using an OData service and created a Fiori Elements App on top of the OData service. We now have a very basic app up and running. Time to add additional functionality using ABAP and the BOPF framework to make our app fully functional!

Creating a draft enabled Sales Order Fiori App using the new ABAP Programming Model – Part 3: Defining the UI & Creating the Fiori Elements App

Defining the UI using Metadata Extensions

In the previous part we’ve defined the data model for our app. Now it’s time to define how our app should look like. We’ll do this by adding UI annotations to our consumption views using Metadata Extensions.

Creating a draft enabled Sales Order Fiori App using the new ABAP Programming Model – Part 2: Virtual Data Model & Consumption views

Building the Virtual Data Model

To provide our app with data and draft capabilities, we’ll build two CDS views which will form the base for our business object. I won’t go into details on how to create CDS views here, as there are enough guides available on how to create them.