Monday 31 May 2021

Avoid Hardcoding in SAP by TVARVC or SETLEAF

At the time of discussing client’s pain points and challenges which they are facing or reviewing the ABAP codes we have noticed that many variables are hardcoded or many Z-tables are present in the SAP system for maintenance of data to use in user exits, BADI’s, Reports, Forms, etc.

Due to Hardcode, code changes is required every time for addition/modification/deletion in the data which requires additional technical efforts along with functional for inputs & testing. Due to Z-table creation also Additional ABAP efforts are required for DDIC creation, table maintenance generator, domains creation or assignment, etc.

Wednesday 26 May 2021

How to create and approve ATC exemptions in SAP BTP ABAP Environment

With SAP BTP ABAP Environment 2105 we delivered the basic scope of ATC exemptions. Now you can create and approve ATC exemptions using ADT in Eclipse and transport them between different SAP BTP ABAP Environment systems.

NOTE: In order to incorporate feedback from early adapters before making this functionality free available for all, it is currently available via the feature toggle. You need to create a customer ticket on the BC-CP-ABA component to turn it on in your SAP BTP ABAP Environment system.

Let’s take a look at the ATC exemption process in detail. The following class contains the hard-corded user name and will be checked with the ABAP Test Cockpit for security violations:

Monday 24 May 2021

SAP oDATA V4 API – Using ABAP Restful Programming

Challenge:

Create a ABAP V4 – API with Parent and Child Relationship using existing Standard CDS Views Provided by SAP without Writing an ABAP Code

Note: Some of the code are not pasted so that readers try it with hands on.

Business Scenario: Get All Business Partner Details – Supplier – Customer – Expanding from Parent Child

Friday 21 May 2021

Extension and enhancement of SXI_MONITOR Generic Search Framework

Introduction

This blog post describes the technical background of the SXI_MONITOR Generic Search Framework and explains how to create your own enhanced searches.

Content of an XML message

The SXI_MONITOR Generic Search Framework is used to filter XML message based on its content. The following figure shows how an XML message is structured.

Monday 17 May 2021

Filters Push down in ABAP CDS views – For a better performance of the application!

In this blog post I have discussed on various technics those can be used to push down the consumption level filters to the database table level

1. Pushing down the single selection filters from the fiori application using parameterized ABAP CDS views

2. Pushing down the multiple selection filters from the fiori application using the dynamic where clause – In combination with the ABAP Managed Database Procedure (AMDP ) table functions and ABAP CDS views.

Tuesday 11 May 2021

Upload Variant table using transaction CU60E – RCU_UPLOAD_EXCEL_TO_VTAB

Learn about how to upload variant table contents from excel in .csv format using transaction CU60E.

Business requirement: In general , in Variant configuration module it is always require to upload the values to Variant table as a content from excel file. It will be always challenging for the functional consultants to load the data from excel file to SAP particularly in project implementations.

When we have a characteristics values being filled in excel sheet we can upload via transaction CU60E with .csv format.

Wednesday 5 May 2021

Getting acquainted with automating ABAP unit testing – Part 10

Part 9 – Write a third unit test

To recap from the preceding blog, we added a new unit test for testing production subroutine set_alv_function_module_name and, when executed, this unit test triggers a warning. Here is the source code as we left it in the previous blog:

Monday 3 May 2021

Getting acquainted with automating ABAP unit testing – Part 9

Part 8 – Fix the production code bug identified by the second unit test

To recap from the preceding blog, we fixed the production code highlighted by a unit test failure, which caused the unit test to now pass and the production code, when executed, to retrieve the correct rows from the persistence repository. Unfortunately, we also found that when we request the output in ALV grid format we still are presented with the ALV report in classic list format. Here is the source code as we left it in the previous blog: