Full screen list in Maintenance Views

Introduction

With or without Fiori in the picture, Maintenance View is one of the main tools for maintaining SAP configuration. Reliable and easy to use, it is a proverbial workhorse.

However, since widescreen monitors became a standard, it has always been frustrating to me to see how much space is left unused (not to say wasted) in the list of a Maintenance View. The obvious solution was to modify the screen manually, but this was overwritten whenever a list was recreated.

Today, I will show you a way of making the Maintenance View list use as much space as possible, always.

Exposing an oData Service from SAP S/4HANA Cloud Public Edition to the SAP BTP

This blog post will explain how to expose a CDS view as an API using developer extensibility in SAP S/4HANA Cloud Public Edition to be consumed in the SAP Business Technology Platform

Technical Procedure

Extending our solutions allows you to differentiate yourself from the competition, simplify processes, and adapt the software according to the specific needs of your business.

Can I extend a certain app? With Clean Core? How?

Extensibility is a very important part in SAP S/4HANA. Although we recommend to have a fit-to-Standard approach, we know that not everything can be covered; there is a need for extensibility. But we don't just want to go hack about our system (anymore), we want to do it Clean Core compliant, meaning:

• Extensions are clearly separated from SAP's code
• Extensions do not modify any SAP objects
• Extensions use only stable, released SAP APIs and extension points

But how to go about that? Well, I'm hoping to give some help on that. In this blog post I'm focusing on extending an SAP S/4HANA Standard app, as an example.

Customer Aging and Supplier Aging Reports at the Line Item Level using Analytical Query in S/4HANA Cloud, Public Edition

Introduction

Functional consultant or a business key user can effortlessly generate supplier and customer aging reports using the Custom Analytical Queries App for the scenarios outlined below.

Scenario – Accounts Payable Aging:

Your client requires a supplier aging report that displays the aging at different levels: Supplier level, Reconciliation G/L level, Supplier Region level, and Profit Center level. Additionally, they would like the option to access the aging information at the accounting document level in the same report.

Create new CO-PA Margin Analysis characteristic with existing table as code list

Introduction

In S/4HANA OP2022 there are several ways to create customer specific characteristics for Margin Analysis. While using transaction KEA5 might seem like the most intuitive and classic way to create new characteristics it will make it very hard to use those with any Fiori applications.

The “new” Fiori enabled way to create characteristics would be by using the Fiori app F1481 “Custom Fields” with the “Market Segment” business context.

Fiori PO Approver app Forward button customization from ECC backend

The first part of customization comes on the Forward Button. As per the approval matrix the approvers were maintained in the PPOME structure. The problem occurred when the approver was forwarding the PO to another approver. However, on clicking the Forward button it was displaying all the list of Users from SU01. This was creating a lot of confusion for the approvers. So the initial requirement came as to fix the list that was appearing on clicking the Forward Button.

I will be displaying the 2 possible approach for Forward Button customization from the Backend.

Managing Updates to abapGit in Shared Development Systems

If you are using abapGit as a tool to facilitate your development processes you at some point have to decide on an update strategy for abapGit itself. Most likely you are only updating abapGit when a feature or bug fix is released that you need or file diffs are displayed that are related to format changes that you want to get rid off. (Or you feel guilty not having updated for a while…) This is a bit of a shame as new features are added all the time and keeping abapGit up-to-date from a technical perspective is extremely easy. There are no notes to implement, no support packages to import, no migrations to do and no dependencies to worry about. Issues rather arise because of processes and communication between teams regarding ongoing developments when you are sharing systems.

How to Navigate Within ABAP CDS Source Code and Between ABAP CDS Objects?

In this blog, I will describe how to …

◉ navigate within ABAP CDS source code,

◉ come to another  CDS/Dictionary object

◉ navigate within the ABAP CDS object you currently work on

… using ABAP development tools for Eclipse (ADT) a.k.a. ABAP in Eclipse.

Note: When I talk about objects, I mean CDS objects such as data definitions and/or relating ABAP Dictionary objects such as database tables, classic views and so on.

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.

How to Copy Table Entries from One System to another using Adjustment Process?

Introduction

In every Project you work on there will be cases where you need to copy data from One System to another. This can be QA System to Prod system or the much awaited SAP ECC To S/4HANA. This is a life saver provided all the data related to Check tables are already maintained in the Destination System. Most of the time we create Program for each table and that can add up to a lot. This blog should be used only for Custom Table not Customized.

Solution

Go to SM30 Transaction Code

Hide ToC transports in ABAP Version Management (enhancement)

This time I come to you with an easy to implement enhancement, which will forever change your lives as ABAP developers.

How many times have you struggled with the ToCs cluttering your list of transports in the Versions Management view? Now there is a solution to that issue. After implementing the steps shown below you will be able to filter out all ToCs and enjoy clean list of transports. Enjoy!

Implementation

1. Enhance class CL_VERS_OBJTYPE_UI_ALV

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.

How to Change Screen Field Properties in Purchase Requisitions

In this post blog, I will show you how to change screen field properties and how to hide screen fields/tabs on purchase requisitions screens.(ME51N, ME52N, ME53N)

This blog post specifically will cover showing, hiding fields which can not be customized by using SPRO customizing settings.

In additional, it works on S/4HANA Cloud too.

In our example, I’ll show you, hiding the fields which are ‘Expected Value’ and ‘Overall Limit’ fields.

How to Add a Custom Field to QA11

I am a SAP ABAP consultant and recently I have been requested to make enhancements to QA11 screen. After some research, I could manage to put things together. And I thought, it is worth creating a complete tutorial on that topic.

Therefore, in this article, I would to share with you how to add the material group field to the QA11 screen and QALS table.

We need to complete following steps;

◉ Add our custom Z field to structure

◉ We create a Function Group.

    ◉ We are creating a screen.

    ◉ We write the input and output codes.

    ◉ We create functions.

◉ We are creating BAdI implementation.

    ◉ We enter the filter value and screen information.

    ◉ We write the GET_DATA and PUT_DATA methods.

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.

Add a validation to a Custom Field via Developer Extensibility in SAP S/4HANA Cloud

Introduction

With the introduction of Three System Landscape(3SL) in SAP S/4HANA Cloud, developers will now be able to create development projects via Eclipse IDE with the help of ABAP Development Tools (ADT)

In this blog, I will take you through a simple example of how to add a screen validation to a Custom field created via Key-User Extensibility in the Development 100 client using Developer Extensibility in the Development 080 client

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

Streams in RAP: Uploading PDF, Excel and Other Files in RAP Application

Uploading Large Object and media such as Excel or Image through your application is a common business requirement and the only way to do it through a RAP application was by extending the application and using UI5 tooling to upload the file.

With the latest SAP BTP ABAP 2208 release the RAP framework now supports OData streams. It is now possible to enable your RAP application to maintain and handle Large Objects(LOBs).This feature provides end users an option to upload external files of different file formats such as PDF, XLSX 

, binary file format and other types hence allowing media handling.

In this Blog we will explore how to upload and handle Large Object such as PDF or Binary files without the need to extend the RAP application in BAS.

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?