Every ABAP developer wants a little slice of the hot cake that is ABAP on Cloud and RESTful ABAP Programming (RAP). We have made an effort to divide the course material into manageable chunks so that even a complete beginner can grasp the new ABAP Cloud path.

Our customers’ love, support, and incredible response have inspired us to take bigger risks and share more. How the CDS behaves and what causes it to do so have been really interesting to observe. Ultimately, how do we observe it acting? The central piece of this entire series is this article. Please proceed slowly and participate in the hands-on activities with us.

The Metadata Extension issue, which we left for the last post, needs to be put on hold for the time being because a Fiori Application is required to experience its full usefulness. Seeing all the moving pieces come together in a fully functional Fiori application would be entertaining.

Behavioral Definition: What Is It?

The Behavior Definition is the next item on the list to be produced.
Take note of the behaviors that a dog exhibits.

It is evident that we have precisely identified the action that a dog is performing. One bite, one chew, one leap, etc.

Apply the same principle to our situation. The behavior of the root CDS view must be determined in accordance with the business requirement. Definitions from textbooks:

A root entity may have just one behavior definition, and it may be necessary to include information on the behavior of the child entities as well. A behavior specification, on the other hand, contains only one root entity.

A behavior description can be implemented in one behavior pool, or in multiple behavior pools, which are collections of ABAP classes. This implies that a behavior definition (a 1:n relation) can be allocated to any number of behavior pools.

FIRST STEP:

Once you perform a right-click on the Interface View, select “New Behavior Definition.”

Step 2:

Select the package and, above all, the “Implementation Type.

Observe that we have taken into consideration the Managed Scenario for the ease of demonstration. In the upcoming articles how and when to utilize the Unmanaged Scenario, pros and cons of both shall be discussed in detail.

Step 3:

After selecting the standard Transport Request, click “Finish.”

Step Four:

The screen that follows is displayed. Remove the comment on line 5, where “lock master” is specified. Turn on the defining of the behavior.

Shortcut to remove a line’s comments: Press and hold the number seven.
Activation shortcut: Ctrl + F3

No errors

We have indicated in the above example that we will be using a Web API or our Fiori Application’s Create, Update, and Delete functions.

It is important to keep in mind that every operation in an Unmanaged Behavior Definition must be coded completely in Entity Manipulation Language, or EML.

Here, we’re keeping things straightforward and requesting that the system handle the fundamental CRUD functions.

As and when the definition of unmanaged behavior is covered, we will delve deeper into these.

That relates to the steps in creating a behavior specification. We then draft the service description.

Step Five:

Select “New Service Definition” by doing a right-click on either Root View or Interface View.

Step 6:

Enter the necessary information, such as the service definition’s name. The prefix “Z_I_EMP_DTLS_SD” in this instance refers to the main root view, while SD stands for service definition.

STEP 7:

Complete the creation of service by selecting the default TR and then “Next” and finally “Finish” with default template of exposing the root view.

Step 8:

Select the service definition that we just defined in Step 7 by right-clicking on it.
Select “New Service Binding” as your option.

Maintaining the correct service definition is crucial in this situation. Check again, then move forward.

Step Nine:

Enter “Z_I_EMP_DTLS_SB,” where SB is an acronym for “Service Binding.”

An important observation is the decrease in the Binding Type.

When we develop an external API that non-SAP applications or systems can use, keep this in mind. We’ll need to examine how the other “ODATA V2 – Web API” is being used.

Step 10:

Select the default TR by clicking “Next.”
A new screen, one that would be utilized customarily from now on, and one that is frequently used is as follows:

After selecting “Activate,” give it a few seconds.

Whoa! Completed! Excellent Work! Just one step separates us from appreciating all of this time’s hard work.

Look at the display below:

After choosing the Entity, select Preview. Recall that this is only a preview.

The BUILT-IN Preview of the Fiori App within the Eclipse IDE is one of our incredible tools. This helps us understand the behavior of the CDS root Entity and the typical Fiori Layout’s placement of the Fiori Elements.

Step 11:

Give the password and email address used to access the SCP trial account.

Click on “Log On”.

STEP 12:

Yo Beauty!! But wait.
OOPS !!! No Data ???

Give the Green Signal for seeing the results. DO it !

Amazing we are seeing the contents of the table.

STEP 13:

Let’s try other CRUD Operation – Create in this Article  & Update and Delete in Next Article.

Create:
Click on Create Button.

Well we have done no mistake. Enter the details and see the magic.

Similarly, we have a great deal to learn and talk about.
Have faith and trust that we will eventually develop Just ONE Fiori App.
Continue to support, but first:

Reminder: To monitor our advancement in the article series, we will have a tracker with the article number. This will enable us to monitor our progress and better manage the situation. “Thumbs Up”?

And MORE and MORE…

Kindly follow our Facebook page, Instagram, Twitter, LinkedIn Group, and LinkedIn Page…

Comment Please!!

The post ABAP for Cloud – 8 – Binding & Output, Behavior Definition, and Service Definition first appeared on TECHNICAL GYAN GURU.

When ABAP 7.4 and 7.5 released a few years later, I was really happy about its additional features. After arriving at work, I launched a development system and began experimenting. Syntax/compilation errorI didn’t know at the time what syntaxes and prerequisites were necessary to write the new lines of code that I had only recently read about.

That instant transported me back to my first year as a newbie SAP ABAP user.I needed to be able to practice the new abilities I would need for my profession somewhere.If only I could set up SAP on my desktop computer at home.

Bring on miniSAP!MiniSAP is a BASIS SAP system that enables us to practice ABAP or BASIS administration from the comfort of our own home computer. It lacks the business modules (no FI, no CO, no nothing, sorry to everyone who thought we could issue small purchase orders or tiny invoices).

Hopefully, by the time you complete reading this post, you will be among the proud owners of a playable SAP installation.For the inexperienced Sergio, it had been helpful, and I think it will be helpful for anyone attempting to learn ABAP or stay current with its new features.

Conditions

A 64-bit version of Windows, Linux, or MacOS must be installed on the computer!

On our PCs, we’ll utilize a virtual machine such as VirtualBox or VMWare. Oracle’s VirtualBox will be used in this course.

Therefore, it is ideal to have at least 6 GB of RAM available (but this is not required).

We will require about 100 GB of hard drive space for the VM image. Go ahead and use it if you have an SSD; you’ll thank yourself later.

 The downloaded files are quite large, so it helps to have a decent internet speed.

Be patient. There are certain steps on this list that take a long time to complete. If you lack patience, I recommend getting a six-pack of beer and watching a taped version of one of your favorite football (or Usian Bolt’s sprints, cricket, or American football :D) games on TV to pass the time.

Now let’s get going!

Acquiring the SAP information

The mirror can be found here if you are experiencing problems downloading from the official page. He has informed me that deleting them is not in his plans. If they go, though, it’s my fault for bothering him and requesting these data, not his. Many thanks,ndboost!

A list of SAP items for download will appear. We wish to download the SAP Netweaver AS ABAP 7.x Developer Edition in our instance. As of the tutorial’s publication, the version is 7.5 SP2:

After selecting Download, we have our first terrifying possibility.

Yes, it is correct! Eight files, totaling about 1500 MB each, will be downloaded to you. Now is the time to crack open the first beer from your six-pack.

Please download all of these files, and we will respond to you as soon as it is complete.

While waiting for…

How to Set Up Linux in VirtualBox

For myself, I’ll download VirtualBox for Windows.

Simply click the installation file to begin VirtualBox installation, and follow the prompts to the very finish, much like everyone’s annoying aunt who is always installing spyware on her computer.I assure you that this time will be secure. If you simply click Next till the very end, you should be good. However, you could want to uncheck the boxes to create Desktop icons and other things.Whether your computer is running Linux or macOS, the process is the same.

This is the screen that greets us when VirtualBox is up and running.

Disregard the virtual machines that are now set up on my computer. Together, I shall begin one from the beginning.

To run SAP in VirtualBox, we need an operating system, and Linux Mint is my personal favorite.Installing Ubuntu is recommended if you wish to take advantage of its increased popularity.Please read the remainder of my article in a mocking rather than a joyful tone. :O

It doesn’t matter which one you choose, although I suggest mate or cinnamon. On my personal computer, I run Cinnamon as a full-featured operating system, but because Mate uses less resources, I’ll use it in a virtual machine.Select 64-bit; the SAP installation requires it.

Next, select the nation you wish to download from (typically the one nearest to you or your own), and we’ll get started.

We may now begin the installation of Linux since we have the image file. To do it, select New in VirtualBox.

Give your system a name on the next screen. It’ll be known as Linux4SAP. Verify that the Version is the 64-bit version and that the Type is Linux.

After clicking Next, a screen appears where we must choose the amount of RAM that our system will need. The amount we have available on our own system determines this selection. With 16GB of RAM on my PC, I have plenty to spare. Even while I believe we can function just fine with 4GB of RAM, I still like to go a little bit higher. We’ll go with 6GB.

You have the option to type 6000 on the box or drag the slider. Yes, I am aware that 6GB is actually 6144MB, but allow me to explain.

Select “Create a virtual hard disk now” by clicking Next, then hit “Create.”

Select Expert Mode from the following screen.

You may simply copy my settings from there. It should be noted that even though we have selected 100GB of space, the dynamically allocated option indicates that the virtual machine may use this amount of hard drive space rather than how much it will. Its size can expand to meet your needs, however it can only hold 100GB.

Make careful to utilize dynamically allocated and VHD.

Next, we select the location of the virtual machine files on our computer by clicking on the icon in the File location:

To keep your computer’s hard drive from being cluttered, you can utilize an external hard drive. Having been something of a megalomaniac (a person fixated on their own abilities) when constructing my own computer, I now have three internal hard drives, one of which is just utilized for SAP storage:

After selecting Save, select Create.

We are almost ready to go, but let’s make a few settings changes first:

Click Network and select Bridged Adapter.

Select your network card by selecting it from the drop-down menu. This will make it possible for us to have an internet connection later on while we’re operating our virtual computer.

Additionally, select Shared Folders and click the Plus button:

Although everything doesn’t actually need to be in this particular folder, I prefer to have things that way. It’s convenient to be able to copy files from one system to another since everything you put in this folder will be visible from both your computer and the virtual machine. Press Select Folder now, and select Auto-mount from the list of alternatives below.In this manner, this folder is automatically mounted on your virtual machine upon startup, giving us access to it.

After two clicks of OK, VirtualBox returns to its home screen. We are going to start the virtual machine now.

Take another sip of that beer. After a little while—sometimes it takes a minute—the following screen appears, and you click on the folder icon.

After choosing the ISO file you previously downloaded from the Linux website, click Open.

Press the Start button.

like this

I would like to speak with you regarding the top message first. That simply implies that VirtualBox will record your keyboard inputs each time it is focused. That is, if you use VirtualBox on Windows and decide you would like to ALT+TAB out of it at any time. You’ll be ALT+TABing on Linux, so good luck.See how irritating it can get by giving it a try.However, there is a solution to this.

By pressing the key that’s marked in the lower right corner (in my case, the CTRL DIREITO; for those who don’t speak Portuguese, that’s the right CTRL key). I only need to touch it once to exit VirtualBox using ALT+TAB. Of course, you can accomplish the same thing by clicking anywhere outside of the VirtualBox window, but what fun is that?You can hold your beer bottle with one fewer hand.

But enough of it. Now let’s get Linux installed!Hold on! Is it not already installed?No… Apologies. All we have here is a live image of Linux that we can experiment with and test. Simply click the Install Linux Mint button on the desktop to begin the installation process for Linux.

Let’s quickly go over the majority of these screens. Choose your favorite language first.

For graphics, etc., click Install third-party software.

While installing Ubuntu, make sure to check the box for Download updates. That being said, why would you install Ubuntu over Mint? Mint is quite lovely.

Press the Next button.

Select your keyboard, then click “Next.”Press Detect Keyboard Layout if you’re unsure of your keyboard’s layout. It will make the choice for you after posing few questions to you.

Finally, select a username and password by filling out the following form.

REMEMBER: The password for this system and the SAP installation will be the same. The password must contain only capital letters, small letters, digits, and no other characters, and it must be at least seven characters long for the SAP installation. This is where we’re going with Abap2017.

ATTENTION 2: Nothing else will work in the Computer name field; we absolutely need to enter vhcalnplci. I’ve heard that there are certain hard-coded values pertaining to this computer name someplace in the miniSAP instance, thus anything different wouldn’t function.

You can choose how the rest is done:

Additionally, I selected to log in automatically since I find typing my username and password at system entry to be a hassle and because I feel quite secure using my home network.

When the Linux installation completes, press Continue to enjoy your remaining beer while you wait for the installation to finish. This is where HDD owners have an advantage over SSD owners—you have more reasons to enjoy your beer.

Press Enter to bring up the following screen:

You now have access to this. You have installed Linux:

The post Part 1 of the miniSAP Installation first appeared on TECHNICAL GYAN GURU.

2. System Validation: Preparing for SAP Fiori

Before diving into the setup and configuration of SAP Fiori, it is essential to validate your system. This step ensures that your environment meets the necessary prerequisites for Fiori deployment.

2.1 Checking System Requirements

1. SAP NetWeaver Version: Confirm that your SAP system runs on SAP NetWeaver 7.50 or higher, as Fiori Apps require this version or newer. This version supports the necessary components for Fiori implementation.
2. SAP Gateway: Verify that the SAP Gateway is installed and configured. SAP Gateway is essential for enabling communication between Fiori Apps and the SAP backend.
3. SAP Fiori Front-End Server (FES): Ensure that the Fiori Front-End Server is properly installed. The FES is responsible for delivering the Fiori user interface and should be compatible with your SAP version.

A) Setup and Configuration of the System

Examine patches and add-ons, install any missing components, and make sure the system is ready.
SAP NetWeaver Gateway activation
Establish a reliable RFC between the gateway and the backend system.
SAP System Alias Creation for Applications
Activate the PFCG Roles and Authorizations for OData and ICF Services.
B) Configuration unique to the Fiori App

Admin and end user authorizations for the Fiori Library’s backend OData service and frontend UI service are activated.

SAP Fiori Course. Part 2. Configuration Particular to the Fiori App

A) Installation and Configuration of the System

i. Verify Add-Ons and Profile Parameters for System Integration with Fiori

Extras:

Please ensure that you have at least these three add-ons installed if your system is less than SAP Netweaver 7.4: IW_BEP, GW_CORE, and IW_FND.

Check the Components by going to t-code SAINT. Install it if you can’t find the three add-ons mentioned above.

Parameters for the profile:

Verify that the two profile settings listed below are kept up to date in t-code RZ11.

Accept_sso2_ticket_login = 1

login/make_ticket_for_SSO2 = 2

ii. SAP NetWeaver Gateway activation

Activate or Deactivate SAP NetWeaver Gateway under SAP Transaction SPRO > SAP NetWeaver > Gateway > Odata Channel > Configuration > Connection Settings

iii. Establishing a trusted RFC between the gateway and the backend system

To retrieve data or even initiate SAP GUI Transactions or Web Dynpro Transactions from the app, front-end applications frequently need to establish a connection with the back-end. The frontend (Launchpad) and the back end server need to establish an RFC connection in order for the user to complete the task without difficulty.

To establish trust between the two systems in the Central Hub Deployment scenario (which involves distinct front-end and back-end systems), establish an RFC destination using transaction SMT1.

Only establish one RFC connection to itself in t-code SM59 if our system is configured as an embedded deployment, which combines front-end and back-end functionality.

iii. Developing the Applications SAP System Alias

The system connection’s logical name is SAP System Alias. To enable the separation of the SAP Gateway service and the RFC Destination, it adds a new layer to the latter.

Your system alias configuration would vary based on whether you have an embedded system, a Hub with development in the backend, or a Hub with development in the front end.

Manage SAP System Aliases under SAP Transaction SPRO > SAP NetWeaver > Gateway > Odata Channel > Configuration > Connection Settings > SAP NetWeaver Gateway to SAP System

a) Hub Deployment Aliases with Backend Development (Front-end GW + Back-end separate)

v. Turn on the ICF and OData services.

Check to see whether they are active by going to t-code SICF now. If not, you may manually activate them by selecting the service and choosing Menu >Service/Host >Activate, or you can right-click and choose Activate.

vi. Authorizations and Roles of the PFCG

To carry out SAP Launchpad Designer activities, the Standard PFCG Role SAP_UI2_ADMIN is authorized. Use this standard role to add and customize the five TADIR services that we produced before.

To obtain the precise Service Document Identifiers, navigate to Maintenance View “/IWFND/V_MGDEAM” (Assign SAP System Aliases to OData Service).

/IWFND/MAINT_SERVICE is the T-Code.

/UI2/TRANSPORT /UI2/INTEROP /UI2/PAGE_BUILDER_PERS /UI2/PAGE_BUILDER_CONF /UI2/PAGE_BUILDER_CUST
SICF (Secure HTTP Services for SAP Fiori Launchpad) in T-Code

/sap/bc/ui2/nwbc /sap/bc/ui2/start_up /sap/bc/ui5_ui5/sap/ar_srvc_launch /sap/bc/ui5_ui5/sap/ar_srvc_news /sap/bc/ui5_ui5/sap/arsrvc_upb_admn
SICF (Activate HTTP Services for UI5) in T-Code

/sap/public/bc/ui5_ui5/ui2 /sap/bc/ui5_ui5

We have already shown you how to identify the hostname and port of your SAP system in our SAP Netweaver Gateway and OData Tutorial. Kindly review what you learned from it.

ABAPers, add the following t-code to your SAP favorite if you would rather not add the Fiori Launchpad link to your already full list of browser favorites. Additionally, this will direct you to the Fiori Launchpad. You may forget about the lengthy URIs.

SAP Fiori Launchpad’s transaction code is /UI2/FLP. It would direct you to the Fiori log-in page.

Conclusion :-

Setting up and configuring SAP Fiori involves a series of essential steps to ensure a seamless and efficient user experience. From validating system requirements to configuring the SAP Fiori Launchpad and backend services, each step plays a crucial role in the successful implementation of Fiori Apps. By following this comprehensive guide, professionals can effectively prepare their SAP environments for Fiori deployment, ultimately enhancing productivity and user satisfaction.

The post Part I of the SAP Fiori Tutorial: System Validation, setup, and Configuration first appeared on TECHNICAL GYAN GURU.

System configuration checks are more base/administrative in nature, but configuration and design linked to Fiori apps are unquestionably the domain of front-end and ABAPer developers. Thus, ABAPers, hone your focus and remain receptive to learning about this practical subject of examining the SAP Fiori Library, verifying the Add-Ons for the selected Standard Fiori Apps (two instances), and turning on the Services.

Fiori Library 
Authorizations (Admin & End Users) for the front-end UI Service and the back-end OData Service
Open the Fiori Launchpad 
Designer and click “Start.”

Step 1 Fiori Library

How is a visit to the SAP Fiori Library necessary?

Visiting the SAP Fiori Library is essential for several reasons. Firstly, it provides comprehensive documentation and details about available Fiori Apps, including their functionality and prerequisites. Secondly, it helps in understanding the app’s integration requirements and customization options. Thirdly, the library offers valuable resources for troubleshooting and best practices. Additionally, it assists in aligning your implementation with SAP’s latest updates and innovations. Overall, the SAP Fiori Library is a crucial tool for effective planning and execution of Fiori App deployments.

Verify the Product Versions Installed. It satisfies every prerequisite listed in the Fiori Library’s Installation Section.

SAP ERP HCM USING SAP FIORI

Step 2: Frontend UI Service and backend OData Service activation

Configuring the “My Time Event” and “Approve Timesheets” (Version 2) apps at the same time will be done. You must follow the exact same procedures (hands-on for you) to approve timesheets as we would walk you through step-by-step for the My Time Event. Every screenshot seen above was taken using the My Time Event App.

The SAPUI5 application (service) should be activated. Within the Front-end framework

Navigate to SICF t-code. Give the service name HCM_CICO_MAN (the Fiori Library provided this service name), then run. If the service is not active, right-click on its name and activate it.

ii. Back-end OData Services are activated

2) service name (HCM_CICO_MANAGE_SRV)

c) Click Add Selected Services after selecting the row.

d) Stick with the Technical Service Name by default or modify it to follow the project naming practice.

e) This Pop-Up Notification would appear;

f) Return to the IWFND/MAINT_SERVICE t-code.

Step 4: Designer for Fiori Launchpad

How can we find out our SAP system’s hostname and port number?

Use the t-code /UI2/FLPD_CUST command or navigate to your Fiori Launchpad Designer URL. This is what a blank screen should look like.

Click the plus icon at the bottom after selecting the Catalog Menu.

Create Reference& Delete

As we previously stated, the numbers for the tiles and the target mapping should match. But in this instance, it does not match.Let’s now add the target mapping.

Make a note of the action and semantic object.

Let us review our customized catalog once again.Tiles and Target Mapping match this time.

Verify that the Tiles are still recognized.

Why may the Tiles/Apps Reference be broken?

Now us examine the customized catalog tile once more.

You will no longer see a Reference Message when you click on the Employee Time Events tile.Have you noticed that the dotted border on the non-reference tile in the preceding image disappears but remains on the reference tile?

Clicking on the Employee Time Events tile will no longer result in a Reference Message.In the above image, have you observed that the dotted border on the non-reference tile vanishes but stays on the reference tile?

Now let us add the custom Catalog to this group.

Since we added two Tiles in the Custom Catalog, we have two available for the group.

How may a SAP user be assigned to the new Catalog and Group?

Answer: Create a role by going to t-code PFCG. Select Menu, Insert Node, SAP Fiori Tile Catalog, and Group each item individually.

Step 5) Start the Fiori Launchpad

http://hostname:port number/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html

Keep in mind that we only added the Employee Time Events Tile to the Group.As a result, when we log into the Fiori Launchpad, just one tile is visible.As of right now, the Approve Employee Timesheet tile is hidden.Allow us to also include the approved employee timesheet tile in the group. There should be two tiles visible on the Employee Time Booking and Approval Group when we log in again.

How to use the custom Group to add the second tile:Visit the private group we set up. Include the Employee Timesheet Approval Tile.

All Green.

The second tile has been added to the Group. Let’s log back into the Fiori link once more. The second tile would also be visible to us. I hope this makes it clear that in order for the catalog tiles to be accessible to the user, they must be included to the group.

Without writing a single line of proprietary code, let’s test the two apps that we recently built and implemented using the SAP delivery model.

The My Time Event App

My Time Event App

Approve Timesheets

Thank you! You’ve completed the end-to-end implementation of two standard Fiori Apps.

The post Part II of the SAP Fiori Tutorial: End-to-End Fiori App Development first appeared on TECHNICAL GYAN GURU.

German is the language of the SAP Fiori Launchpad. How can I translate it to English?

Review SAP Fiori Tutorial Part III: Three Flow Charts to get the idea of improving the standard Fiori apps. As an example, let’s say you work as a developer in the UK and are unexpectedly given a project that involves non-English speaking nations like Germany, France, Portugal, etc. You ask yourself, what’s the big deal?You could manage it because ABAP is a common language.

As a developer for Fiori, your first job is to figure out why users in the UK are seeing the Fiori Launchpad in German.

You access the client’s Citrix/VPN and notice the German log-on below.

You make a quick guess: it’s possible that German, DE-Deutsch, is the GUI Logon Pad’s default language. As a result, German appears in the Fiori Launchpad as well.

Let’s examine the SAP Logon Pad. You’re correct. Yes, DE (German) is the default language on the Logon Pad.

You continue to do this. By taking the actions listed below, you can set EN (English) as the default language.

It would request the confirmation listed below if you clicked OK. Press OK once again.

Start the Logon Pad again now.

That you finished the case in under two minutes makes you proud. Let’s take another look at the Fiori Launchpad. Since we have changed the default language in the SAP Logon Pad to EN, we anticipate that the language will also change to EN.

Whoops! It’s still in German on the Fiori Log On Pad.

The fiori launchpad and SAP Log On Pad are unrelated, we have learned. See Also: SAP Fiori Tutorial, Section I: Installation, Configuration, and System Check. you now acknowledge the gravity of the situation. After much searching, you eventually arrive at www.technicalgyanguru.com and discover this post.

The Internet Explorer (or Firefox/Chrome, etc.) default language determines the language that the Fiori Launch Pad displays by default.

The three steps listed below must be followed in order to modify Internet Explorer’s default language:

In Internet Explorer, click Tools.

2. Select the General Tab, then click Languages under Internet Options.

3. The German language would be displayed as the first choice. Simply use the arrows or the move up and down buttons to bring English—which isn’t the initial option—to the top.

Click OK, OK, to restart the Fiori Launch Pad’s internet browser.

The sorcery was successful. The Fiori Launch Pad is now available in your native tongue. Fiori, which translates to “flower” in Italian, meaning “have fun.”

Ever desired to master SAP ABAP for HANA? but were unsure of where to begin? View these tutorials on ABAP for HANA.

Thus…How Do You Feel?

We would now like to speak with you.

What are your thoughts on this matter?You will undoubtedly run into a language barrier if you ever work on an international project whose execution is taking place across continents.We previously encountered translation problems with Adobe, SAPScripts, SmartForms, and ABAP reports. The Fiori Apps are now in the spotlight.

you may be interested in this blog here:-

Good Practices for Salesforce Maintenance and Optimization

Understanding and Addressing “FOR UPDATE” Lock Issues in MySQL

Navigating SAP’s E070 Table in SAP: The Heartbeat of Transport Management

The post Part IV: SAP Fiori Tutorial. How can I modify the Fiori Launch Pad’s default language if it’s not English? first appeared on TECHNICAL GYAN GURU.

We had to create a report using splitter containers and a ALV tree structure per a client request. Although handling the combination of these two may seem challenging, it is actually rather simple. We quickly constructed a prototype, and it was flawless.

The basic programming skeleton of the prototype described below can be improved in a number of ways, but it should not change. We discovered certain hotly debated subjects online as we developed, and I’ve tried to hone in on them and address them in this piece.

Goal

This article’s goal is to clarify the usage of the TREE MODEL (TREE_STRUCTURE) and SPLITTER CONTAINER in OOPs ABAP report generation that integrates standard events.

The second, and more significant goal, is to permanently dispel our phobia of using Splitter Containers and Tree Models.

Range

• This article addresses the following typical issues that developers run into:
• When divided into many sub-containers, the custom container can be used to fill the entire screen.
• Registering custom events using the tree model’s standard events
• Customize splitter container widths.

Overview

The report with two containers in the list screen is displayed using the code that follows. The tree model is intended to be contained in the left panel container, while the contents of the left panel document will be displayed in the right container in response to a double click. This example shows how to design a tree structure using sales orders and sales contracts as the antecedent documents. Certain selection screen criteria can be applied to these sales orders in order to choose them. When the leaf node is clicked, the system will show the sales order data in the appropriate container in an ALV format (fig. 1).

fig. – 1

Program Structure

Step I: Declare all necessary tables and structures
Step II: Declare the references to the different classes
Step III: Event class definition
Step IV: Putting the Event Class into Practice
Step V: The Choosing Screen
Step-VI: Subroutine to obtain the fundamental data for the tree model
Step VII: Design of the Screen
Step VIII: Module for creating different classes of objects. (In the output screen’s PBO)
Step IX: The event registration module. (In the output screen’s PBO)
Step X: The output processing module. (In the output screen’s PBO)

Step-I: Declare all required structures and tables

Tables: vbak,vbap,vbfa.

*&---------------------------------------------------------------------*
*&            Structures and Table Declarations
*&---------------------------------------------------------------------*
Data: ls_vbak type vbak,
lt_vbak type table of vbak,
ls_vbap type vbap,
lt_vbap type table of vbap.

Types: begin of ty_vbfa,
vbelv type vbfa-vbelv, "Preceding SD Document
posnv type vbfa-posnv, "Preceding SD Document Item Number
vbeln type vbfa-vbeln, "Subsequent SD Document
posnn type vbfa-posnn, "Subsequent SD Document Item Number
vbtyp_n type vbfa-vbtyp_n, "Subsequent Document Category
vbtyp_v type vbfa-vbtyp_v, "Preceding Document Category
end of ty_vbfa.

Data: ls_vbfa type ty_vbfa,
lt_vbfa type table of ty_vbfa.

Data: ls_vbfa_copy type ty_vbfa,
lt_vbfa_copy type table of ty_vbfa.

Types: begin of ty_vbak,
vbeln type vbak-vbeln,  "Contract Number
audat type vbak-audat,  "Document Date
ernam type vbak-ernam,  "Name of Person who Created the Object
auart type vbak-auart,  "Sales Document Type
end of ty_vbak.

Data: ls_vbak_cont type ty_vbak,
lt_vbak_cont type table of ty_vbak.

Step II: Declare the references to the different classes

*&---------------------------------------------------------------------*
*&            Type Reference of Various Classes
*&---------------------------------------------------------------------*
Data: ref_split type ref to cl_gui_splitter_container,
ref_cust  type ref to cl_gui_custom_container,
ref_alv1  type ref to cl_gui_alv_grid,
ref_alv2  type ref to cl_gui_alv_grid,
ref_cont1 type ref to cl_gui_container,
ref_cont2 type ref to cl_gui_container.
Data: ref_tree  type ref to cl_simple_tree_model.

Step – III: Definition of event class

*&---------------------------------------------------------------------*
*&                       Event Class
*&---------------------------------------------------------------------*
class lcl_event_handler definition.
public section.
methods: node_dc for event node_double_click of cl_simple_tree_model
importing node_key sender.
endclass.

Step – IV: Implementation of Event Class

class lcl_event_handler implementation.
method: node_dc.

Data: lt_children type tm_nodekey,
v_so        type vbeln,
v_item      type posnr.

Data: ls_layout type lvc_s_layo.
* 'sender' is an implicit event parameter that is provided by
* ABAP Objects runtime system. It contains a reference to the
* object that fired the event. You may directly use it to
* call methods of this instance.

CALL METHOD SENDER->NODE_GET_LAST_CHILD
EXPORTING
NODE_KEY       = node_key
IMPORTING
CHILD_NODE_KEY = lt_children.

* ‘Level_count’ in expand_node method determines in which level of the tree
* we want the double_click method to be triggered.

if lt_children is not initial.
CALL METHOD SENDER->EXPAND_NODE
EXPORTING
NODE_KEY            = node_key
LEVEL_COUNT         = 2.
endif.

split node_key at space into v_so v_item.

refresh: lt_vbap.

select * from vbap
into table lt_vbap
where vbeln = v_so.

if sy-subrc = 0.

ls_layout-grid_title = text-002.
ls_layout-zebra      = 'X'.
ls_layout-smalltitle = ''.
ls_layout-cwidth_opt = 'X'.

CALL METHOD REF_ALV2->SET_TABLE_FOR_FIRST_DISPLAY
EXPORTING
I_STRUCTURE_NAME              = 'VBAP'
IS_LAYOUT                     = ls_layout
CHANGING
IT_OUTTAB                     = lt_vbap.

CALL METHOD REF_ALV2->REFRESH_TABLE_DISPLAY.

endif.

endmethod.
endclass.

Step – V:  Selection Screen

*&---------------------------------------------------------------------*
*&                   Selection Screen
*&---------------------------------------------------------------------*
selection-screen: begin of block b1 with frame title text-001.
select-options: s_vbeln for vbak-vbeln, "Document Number
s_audat for vbak-audat, "Document Date
s_ernam for vbak-ernam. "Name who Created the Object
selection-screen: end of block b1.

Step-VI: Subroutine to obtain the fundamental data for the tree model

*&---------------------------------------------------------------------*
*&                   Start Of Selection
*&---------------------------------------------------------------------*
start-of-selection.
perform Get_Data.

*&---------------------------------------------------------------------*
*&      Form  GET_DATA
*&---------------------------------------------------------------------*
*       Get All the display relevant Data for Tree Structure
*----------------------------------------------------------------------*
FORM GET_DATA .

select vbeln audat ernam auart
from vbak
into table lt_vbak_cont
where vbeln in s_vbeln and
audat in s_audat and
ernam in s_ernam.

if sy-subrc <> 0.
message E001(ZMSG) with 'No Record Found' display like 'I'.
elseif sy-subrc = 0.

select vbelv posnv vbeln posnn vbtyp_n vbtyp_v
from vbfa
into table lt_vbfa
for all entries in lt_vbak_cont
where vbelv = lt_vbak_cont-vbeln and
vbtyp_n = 'C' and
vbtyp_v = 'G'.

if lt_vbfa is initial.
message E002(ZMSG) with 'No Subsequent Record Found' display like 'I'.
else.
select * from vbak
into table lt_vbak
for all entries in lt_vbfa
where vbeln = lt_vbfa-vbeln.

select * from vbap
into table lt_vbap
for all entries in lt_vbak
where vbeln = lt_vbak-vbeln.

endif.
endif.
ENDFORM.

Step – VII: Screen Design

call screen 0100.

* The container should be drawn as large as possible. Also, the Lines/columns in the attributes tab of the screen painter are to be filled with the value 240 to get the full-screen splitter container.

Step – VIII: Module for object creation of various classes. (In PBO of output screen)

Create one module in the flow logic of the screen.

*&---------------------------------------------------------------------*
*&      Module  OBJECT_CREATION  OUTPUT
*&---------------------------------------------------------------------*
*       Object Creation for Classes
*----------------------------------------------------------------------*
MODULE OBJECT_CREATION OUTPUT.

CREATE OBJECT REF_CUST
EXPORTING
CONTAINER_NAME    = 'SPLIT_CONT'.

CREATE OBJECT REF_SPLIT
EXPORTING
PARENT            = ref_cust
ROWS              = 1
COLUMNS           = 2.

CALL METHOD REF_SPLIT->GET_CONTAINER
EXPORTING
ROW       = 1
COLUMN    = 1
RECEIVING
CONTAINER = ref_cont1.

The SET_COLUMN_WIDTH method can be used to change the splitter container’s width. As needed, pass the breadth.

CALL METHOD REF_SPLIT->SET_COLUMN_WIDTH
EXPORTING
ID                = 1
WIDTH             = 22.

CALL METHOD REF_SPLIT->GET_CONTAINER
EXPORTING
ROW       = 1
COLUMN    = 2
RECEIVING
CONTAINER = ref_cont2.

CREATE OBJECT REF_TREE
EXPORTING
NODE_SELECTION_MODE   = cl_simple_tree_model=>node_sel_mode_single.

CALL METHOD REF_TREE->CREATE_TREE_CONTROL
EXPORTING
PARENT                = ref_cont1.

CREATE OBJECT REF_ALV2
EXPORTING
I_PARENT  = ref_cont2.

ENDMODULE.                 " OBJECT_CREATION  OUTPUT

Step – IX: Module for event registration. (In PBO of output Screen)

*&---------------------------------------------------------------------*
*&      Module  EVENT_REGISTRATION  OUTPUT
*&---------------------------------------------------------------------*
*       Double Click Event Registration

*§4a. Frontend registration(i):  get already registered tree events.
*................................................................
* The following four tree events registers ALV Tree in the constructor
* method itself.
*    - cl_gui_column_tree=>eventid_expand_no_children
* (needed to load data to frontend when a user expands a node)
*    - cl_gui_column_tree=>eventid_header_context_men_req
* (needed for header context menu)
*    - cl_gui_column_tree=>eventid_header_click
* (allows selection of columns (only when item selection activated))
*   - cl_gui_column_tree=>eventid_item_keypress
* (needed for F1-Help (only when item selection activated))
*
* Nevertheless you have to provide their IDs again if you register
* additional events with SET_REGISTERED_EVENTS (see below).
* To do so, call first method  GET_REGISTERED_EVENTS (this way,
* all already registered events remain registered, even your own):

* (If you do not these events will be deregistered!!!).
* You do not have to register events of the toolbar again.
*----------------------------------------------------------------------*
MODULE EVENT_REGISTRATION OUTPUT.
Data: lt_events type cntl_simple_events,
ls_event type cntl_simple_event.

Data: event_handler type ref to lcl_event_handler.

CALL METHOD REF_TREE->GET_REGISTERED_EVENTS
IMPORTING
EVENTS = lt_events.

ls_event-eventid = cl_simple_tree_model=>eventid_node_double_click.
append ls_event to lt_events.

CALL METHOD REF_TREE->SET_REGISTERED_EVENTS
EXPORTING
EVENTS                    = lt_events.

create object event_handler.
set handler event_handler->node_dc for ref_tree.

ENDMODULE.                 " EVENT_REGISTRATION  OUTPUT

Step – X: Module for output processing. (In PBO of output Screen)

*&---------------------------------------------------------------------*
*&      Module  PROCESSING_OUTPUT  OUTPUT
*&---------------------------------------------------------------------*
*       Processing Output of the Table
*----------------------------------------------------------------------*
MODULE PROCESSING_OUTPUT OUTPUT.

Data: ls_node type treemsnodt.

CALL METHOD REF_TREE->ADD_NODE
EXPORTING
NODE_KEY                = 'ROOT'
ISFOLDER                = 'X'
TEXT                    = 'Orders'
EXPANDER                = 'X'.

loop at lt_vbak into ls_vbak.

ls_node-node_key = ls_vbak-vbeln.

concatenate 'Sales Order#' ':' ls_vbak-vbeln
into ls_node-text
separated by space.

CALL METHOD REF_TREE->ADD_NODE
EXPORTING
NODE_KEY                = ls_node-node_key
RELATIVE_NODE_KEY       = 'ROOT'
RELATIONSHIP            = cl_simple_tree_model=>relat_last_child
ISFOLDER                = 'X'
TEXT                    = ls_node-text
EXPANDER                = 'X'.

endloop.

loop at lt_vbap into ls_vbap.

concatenate ls_vbap-vbeln ls_vbap-posnr
into ls_node-node_key
separated by space.

ls_node-relatkey = ls_vbap-vbeln.

concatenate ls_vbap-posnr ls_vbap-matnr
into ls_node-text
separated by space.

CALL METHOD REF_TREE->ADD_NODE
EXPORTING
NODE_KEY                = ls_node-node_key
RELATIVE_NODE_KEY       = ls_node-relatkey
RELATIONSHIP            = cl_simple_tree_model=>relat_last_child
ISFOLDER                = ''
TEXT                    = ls_node-text
EXPANDER                = ''.

endloop.
ENDMODULE.                 " PROCESSING_OUTPUT  OUTPUT

Change the design, but feel free to copy or refer to the included code. I would prefer to advise using the local class to help construct the complete report, or at the very least, using some modularization techniques. I utilized several PBO modules, which is strongly discouraged for any real-time object.

There are numerous different methods for creating tree topologies. There are a ton of documents available online. I chose the most straightforward method (the class name is, ironically, “cl_simple_tree_model”).Splitter containers have been extensively studied, although they are rarely utilized unless there are very particular needs.But all this claim is “Old wine in a new bottle,” that is all. I hope this eliminates our reluctance to use tree models and splitter containers.

Every post we write is the result of extensive planning, testing, and writing.It would be greatly appreciated by our team if you could forward this link to at least five friends or coworkers who you believe would find our content useful.In order to benefit everyone, keep our staff engaged, and ensure that our effort is not lost in the vast internet, we want our articles to be seen by as many people as possible.

Salesforce training modules

A World of History and Culture: Exploring the Past

The post OOP Report Applying ALV Tree Combination and Splitter first appeared on TECHNICAL GYAN GURU.

SAP Fiori Tutorial, It is one thing to grasp the idea and possess theoretical understanding of any technology; it is quite another to put that knowledge to use solving problems in real time.It is not enough to be good at racing games and expect to be a Formula 1 champion. Analyzing technical problems during Fiori App configuration can also be a little challenging and time-consuming if you haven’t worked directly on real applications.

But don’t be alarmed. I, Sumit from Invenio, am here to save the day for you!

While working on intricate real-world projects involving Fiori applications, I will attempt to assist application developers (ABAP and Frontend specialists) in comprehending and using various troubleshooting tools and techniques to speed up their analysis.

When configuring any configuration, we will verify the most frequently occurring error.

Since SAP Fiori development involves a number of infrastructure components, including back-end, front-end (gateway), web dispatched, UI application, etc., resolving such issues can be difficult, annoying, and time-consuming for novices. Furthermore, problems may arise in any of these elements.

So, the crucial query is:

Where do we begin when debugging Fiori problems?

In order to initiate front-end debugging and determine whether problems are present in the front-end or back-end components, developers frequently start by using the Well-Known Function Key F12 (or right-clicking and choosing INSPECT in the browser where the Fiori App is running). There are no problems shown in the console in our sample.

2 Verifying whether there are any errors in SAP Gateway is the next step. Depending on your gateway deployment method (Hub or Embedded), it could be your front-end or back-end system.

Use transaction “/IWFND/ERROR_LOG” to confirm whether Gateway Services has received any error log reports.

Thankfully, there have been no reported issues in this instance.

In the SAP Fiori launchpad, the next step is to use transaction “/UI2/FLIA” to verify that a provided INTENT (semantic object – action pair) has been assigned to a USER.

For a user, this report offers a summary of all of their intents. It lets you see which authorization role the purpose belongs to and whether a specific person is allocated to it.

The report’s results can be filtered according to the type of device (desktop, mobile, etc.).

The personalization layer is the default layer.

The check depends on the system. Launch the report in the system whose content you wish to check.

Check to see whether “Configuration error” for semantic “ZMat” and action “Create” exists.In this

After that, see if there is a “Customization error” for the Action “Create” and the Semantic “ZMat“.The customization error in this instance is reported as follows.

To examine the error message in more detail, select the error and then click Display.

Detailed Error Message: “Launchpad ZMM / transaction / ZMM01 does not exist in client 800”.

Transaction “/UI2/FLP_CONTCHECK” is another tool that developers may utilize to confirm Fiori Launchpad content. Here, developers can filter programs using packages. Let’s examine it more closely.

Developers can also use transaction “/UI2/FLP_CONTCHECK” to verify Fiori Launchpad content.

Developers can use packages to filter apps here. Let’s give it a closer look.

Under Configuration for Custom App ZMM, no errors have been recorded.

Verify the Customization aspect as well. The error message for the Catalog ZMM, which powers our unique application, is displayed below.

In this case, it is the same error that was encountered in Step 3.

See Also: Complete SAP ABAP for S/4HANA Tutorials

We now know the problem, more or less. Now is the moment to put an end to it and win the day!

Let’s investigate the meaning behind Launchpad Role “ZMM” and Launchpad Instance “transaction” alias “ZMM01”. The Launchpad role and instance that you set up in transaction “LPD_CUST” are the same.

LPD_CUST shows that both Role and Instance are kept alive.What’s wrong if the Role and Instance are configured?

Keep in mind that Target Mapping defines the launchpad role and instance, which may be accessed using transaction /n/UI2/FLPD_CUST (Fiori launchpad designer).

After choosing the Target Mapping, select “Configure.””.

It is obvious that Target Mapping maintains Role and Instance.

What then is the problem?

Where in the configuration are we making mistakes?

To unravel this mystery, you’ll need Sherlock Holmes’s powers of observation.

Semantic mapping and launchpad settings may be closely compared, and you’ll see that the instance is kept in Lower case Target Mapping (see screenshot above).We must keep it exactly as per the LPD_CUST setting in the same scenario.

Let’s make the modification to uppercase.

Save and open the app again. Success! It was successful!

You may think the error is a monster when you receive it. However, you could think it’s all for nothing once you understand the underlying problem. For the majority of typical problems, this is true. When we know the answer, the problem always seems really straight forward.

Coding and programming the fix is simple, as we often say. The majority of the work and time is spent determining the source and fundamental cause.

you may be interested in this Blog here:-

When Did I First Hear About SAP? A Journey Through Discovery

How can I change the color of the Langchain output agent ?

Making Your First Salesforce Appexchange: A Complete Strategy

The post SAP Fiori Tutorial. Part VI. How to Troubleshoot SAP Fiori Errors? first appeared on TECHNICAL GYAN GURU.

Fiori is at the forefront with S/4HANA.Additionally, in order to create SAP Fiori Applications, ABAP engineers must transform into stunning butterflies in order to sip the delightful nectar of the Fiori blossoms.

Paradoxically, the comparison is ideal. For SAP ABAP Developers, there is a paradigm shift from the dull blue SAP screen to the stunning Fiori Applications. Core Data Services (CDS) is the cornerstone of S/4HANA, and one of its pillars is the ABAP Programming Model for SAP Fiori. The three SAP programming languages of the future are expected to be CDS, BOPF, and OData. Thus, it is imperative that we begin studying these subjects.

It is something you cannot escape, even if you attempt to put it off as long as you can. We are aware that change can be challenging, but we will do our best to make the switch from the outdated ABAP Develper to the newest ABAP Programmer for Fiori as easy and enjoyable as possible. We have attempted to develop a crash course tutorial series in this brief series, which is a summary of several books released by SAP Press and SCN blog entries, so you can understand it quickly. In order to assist you in comprehending, learning, and using these new areas as soon as possible, we have kept all of the articles brief, sharp, and to the point.

The book that was released states that the “ABAP Programming model for Fiori supports the development of OData services optimized for SAP HANA for SAP Fiori applications. It covers analytical, transactional, and search application scenarios and is based on Core Data Services (CDS) Views.” The two main applications of the ABAP Programming Model for SAP Fiori are Read-Only Applications and Transactional Applications.

For read-only applications, all that is required is an underlying CDS data model and application-specific analytics or search annotations. The CDS data model and related annotations are then made available as an OData service via the Service Adaptation Description Language (SADL).

The creation of a Business Object Processing Framework (BOPF) Business Object is necessary for Transactional Applications in addition to Read-Only Applications. This is because BOPF Actions, Validations, and Determinations handle additional business logic in addition to handling Create, Update, and Delete operations.

Okay, so Technicalgyanguru wouldn’t be necessary if we typed every word that was in the book.This brings us to our explanations. Real-world tasks require two different kinds of apps.First, we simply retrieve information from the

Selecting the SAP Fiori App

The journey begins with selecting the right SAP Fiori app for your needs. The SAP Fiori apps reference library is an extensive repository that provides detailed information about available Fiori apps, including functionality, prerequisites, and compatibility. To start:

1. Access the SAP Fiori Apps Reference Library: Navigate to the SAP Fiori apps reference library on the SAP Support Portal or SAP Fiori launchpad.
2. Search and Filter: Use search and filter options to locate the specific app you need. This could be based on functionality, industry, or system requirements.
3. Review App Details: Examine the app’s description, prerequisites, and any related documentation to ensure it meets your requirements.

Planning Installation with Maintenance Planner

Once you’ve selected the app, the next step is to plan the installation using the Maintenance Planner. This tool is instrumental in preparing for system updates and new installations.

Steps for Planning Installation:

1. Log into Maintenance Planner: Access the Maintenance Planner through the SAP Support Portal. Ensure you have the necessary authorizations to perform planning tasks.
2. Create a New Maintenance Plan: Start by creating a new maintenance plan for your installation or update project.
3. Add System Information: Input details about your existing systems and the new components or updates you plan to install. Maintenance Planner will use this information to generate a comprehensive plan.
4. Analyze System Compatibility: Maintenance Planner checks for compatibility between your current system landscape and the new changes, ensuring that all components will work together seamlessly.
5. Generate Stack XML: Use Maintenance Planner to generate a consolidated stack XML file that outlines all planned changes. This file will guide the installation process and ensure all components are correctly applied.

Installing and Updating the System

With your plan in place, you can proceed to install or update the system. The installation process generally involves:

1. Download Required Files: Maintenance Planner allows you to push all necessary files for the installation into a download basket in a single step, streamlining the file acquisition process.
2. Install Components: Use the Software Update Manager (SUM) to apply the stack XML and install the new components or updates. Follow the guided steps provided by SUM to ensure a smooth installation.
3. Post-Installation Checks: After installation, perform necessary post-installation steps, such as applying any required configuration changes or running validation checks.

Advantages of Using Maintenance Planner

1. Consolidated Planning: Maintenance Planner enables consolidated planning by generating a stack XML that includes all planned landscape changes. This holistic view simplifies managing updates and ensures that all components are correctly synchronized.

2. Support for New System Installations: The tool supports the installation of new systems, making it easier to integrate new components into your existing landscape. It helps in ensuring that new installations are seamlessly incorporated.

3. Streamlined File Management: Maintenance Planner simplifies file management by allowing you to push all required files for the installation into a single download basket. This reduces the complexity of file handling and minimizes the risk of missing critical files.

Conclusion

The integration of SAP Fiori apps into your system landscape can significantly enhance user experience and operational efficiency. By leveraging the SAP Fiori apps reference library and the Maintenance Planner, you streamline the process of selecting, planning, and installing these apps. Maintenance Planner’s consolidated planning, support for new installations, and efficient file management capabilities offer substantial benefits, making system updates and installations more manageable and effective.

you may be interested in this blog here:-

The Journey of Alex: From Confusion to Clarity in SAP Software Meaning

Salesforce List: Your Essential Guide to Features and Functionalities

The post An Overview of SAP Fiori ABAP Programming Model – 1 first appeared on TECHNICAL GYAN GURU.

Beginners of ABAP CDS who wish to continue with the ABAP Programming Model in SAP Fiori without having to navigate and bounce between pages would find this tutorial to be helpful. However, if you want to go deeper into it, we strongly advise you to take our Core Data Services training series.

What transpires when CDS View is created?

When a CDS view is activated, two artifacts are produced: a CDS View Entity, which is a SAP HANA view on the database, and a corresponding SQL View, which is the Data Dictionary (DDIC) view in the ABAP Dictionary (@AbapCatalog.sqlViewName). With the object repository entry R3TR DDLS, just the CDS View definition is sent. Different sorts of annotations can be used to augment CDS views, which are built using CDS’s Data Definition Language (DDL), to cover various application scenarios.

Navigate to transaction SE11; the above-highlighted view will appear in the ABAP DDIC view options.

CDS Views’ naming convention

The following naming conventions are used to categorize CDS Views:

Private View (P_)

View Interface (I_)

Using Perspective (C_)

Exclusive Perspective

Private Views are made for internal use and will be accessible everywhere. Developers can build associations with this Private view or utilize it to develop CDS views.SAP does, however, advise users not to use Private views as they are not safer.In the future, certain columns might be added or removed in a way that would hinder our development because it depends on these viewpoints.

Please keep in mind that this does not mean we should never embrace their opinions. Steer clear of consumption if possible.

View of the Basic Interface

View of the Composite Interface

From a technical standpoint, Basic and Composite views differ in:

Master data is contained in Basic View, whereas both Master and Transactional data are contained in Composite View.Using I_ conventions, the Basic and Composite Interface views are identified.

View of Consumption

Interface views serve as the foundation for this view. This view serves as the data model’s pre-made solution. It is also much simpler to design and use a Fiori App using these views. It can also be used analytically; BI reports, for example, can be created. It is easy to develop if SAP already provides the Consumption views.

Key Features of CDS:

1. Semantic Layer: CDS views offer a business-oriented abstraction layer over raw data, making it easier for developers and end-users to interact with complex data structures.
2. Performance Optimization: Leveraging SAP HANA’s in-memory processing, CDS views are designed to optimize performance, enabling fast and efficient data retrieval and manipulation.
3. Reusability: CDS views can be reused across different applications, reducing redundancy and ensuring consistency in data representation.

Practical Application of CDS Views

Implementing CDS views involves several steps, each crucial for ensuring that data is modeled and utilized effectively:

1. Defining CDS Views: The first step is to define the CDS views using the ABAP Development Tools (ADT) in SAP HANA Studio or Eclipse. This involves creating a CDS view definition that specifies the data source, fields, and any necessary calculations or aggregations.

sqlCopy code@AbapCatalog.sqlViewName: 'ZMY_CDS_VIEW'
@EndUserText.label: 'My CDS View Example'
define view Z_MY_CDS_VIEW as select from some_table {
    key field1,
    field2,
    sum(field3) as total_field3
}
group by field1, field2

2. Exposing CDS Views as OData Services: To integrate CDS views with SAP Fiori apps, they need to be exposed as OData services. This is done using the SAP Gateway, which allows Fiori apps to consume the data via standard web protocols.

3. Integrating with Fiori Apps: Once the OData service is set up, it can be consumed by Fiori apps. Developers configure Fiori tiles and applications to use the OData services, ensuring that the data presented aligns with the business requirements.

4. Testing and Validation: Thorough testing is essential to ensure that the CDS views deliver accurate data and perform well under different scenarios. This includes validating data accuracy, performance, and the user experience in Fiori apps.

Conclusion

Core Data Services (CDS) views are a fundamental component of the SAP Fiori ABAP Programming Model, offering a powerful framework for data modeling and integration. By providing a semantic layer over raw data, CDS views enable developers to create efficient, real-time, and user-centric applications. Their ability to simplify data modeling, optimize performance, and enhance user experience makes them indispensable for modern SAP Fiori development.

Implementing CDS views effectively requires careful planning and execution, from defining the views to integrating them with Fiori apps. Embracing CDS views not only streamlines data management but also ensures that SAP Fiori applications deliver meaningful and actionable insights to users. As organizations continue to evolve and leverage advanced technologies, understanding and utilizing CDS views will remain a key factor in achieving success and driving innovation in the SAP ecosystem.

you may be interested in this Blog Here

Can I become full stack developer in 3 months?

Salesforce Incident Management: Streamlining Issue Resolution

How the Digital Services Act is Shaping the Future of the SAP Community

The post SAP Fiori ABAP Programming Model – 2 – CDS – Overview first appeared on TECHNICAL GYAN GURU.

The instructions for activating the previously built OData service are listed below.

Determine which OData service has been generated.
Turn on the OData service for the SAP Gateway.
Determine which OData service was created.
To create the OData service, the corresponding CDS view must be activated after applying the OData annotation.

Open the SAP Gateway System and activate the OData service.

The discovery of the OData service’s name does not imply that it is available for use. It needs to be turned on.

Follow these instructions to make the OData service active:

1. Using the SAP GUI, access the SAP Gateway system and navigate to transaction /IWFND/MAINT_SERVICE.

2. Click the Add Service option to add the service for activation once we are in the transaction.

3. Enter the name of the technical service and the system alias on the next screen. OData is the service name for technical services.

Choose the OData services result that was returned, then click Add Selected Services.

5. Select the bundle.

6. To verify if the service is enabled, return and filter the OData service by its name. Consequently, this will also activate and make the OData service available.

7. After that, proceed as normal to test the OData service and verify the entity data, as shown below. Please refer to the OData service testing from SAP Gateway system on the SAPYard website if this step is unclear.

In the realm of SAP Fiori development, the ABAP Programming Model offers a structured approach to building efficient, scalable applications. One of the key components of this model is the generation of OData services, which are critical for enabling seamless data interactions between the SAP backend and the Fiori front end. This blog post explores the steps involved in generating OData services using the ABAP Programming Model, focusing on practical insights and best practices to streamline your development process.

ABAP Programming Model and OData Services

The ABAP Programming Model is designed to align with modern development practices, emphasizing simplicity and efficiency. OData (Open Data Protocol) is integral to this model, facilitating a standardized way to create, read, update, and delete data. In the context of SAP Fiori, OData services serve as the bridge between your backend data and the user interface, making them essential for interactive and dynamic applications.

2. Prerequisites for OData Service Generation

Before diving into OData service generation, ensure you have the following prerequisites:

• SAP NetWeaver Application Server: Ensure you have a running SAP NetWeaver instance where your ABAP code will be executed.
• ABAP Development Tools (ADT): ADT in Eclipse is necessary for creating and managing ABAP artifacts.
• SAP Business Application Studio or SAP Web IDE: These tools will be used to develop and test your SAP Fiori applications.

3. Creating Core Data Services (CDS) Views

The foundation for generating an OData service lies in creating Core Data Services (CDS) views. CDS views provide a structured and reusable data model that can be exposed through OData services.

Steps to Create a CDS View:

1. Open ADT in Eclipse:
   • Start by opening the ABAP Development Tools in Eclipse.
2. Create a New CDS View:
   • Navigate to your ABAP package, right-click, and select New > Other ABAP Repository Object > Core Data Services > Data Definition.
3. Define the CDS View:
   • Use the following template to create your CDS view:
   abapCopy code@AbapCatalog.sqlViewName: 'ZMY_CDS_VIEW' @AccessControl.authorizationCheck: #CHECK @EndUserText.label: 'My CDS View' define view Z_MY_CDS_VIEW as select from my_table { key field1, field2, field3 } This CDS view selects field1, field2, and field3 from my_table, with field1 being the key.

4. Exposing CDS Views as OData Services

With your CDS view ready, the next step is to expose it as an OData service. This involves creating an OData service project and mapping the CDS view to it.

Steps to Expose a CDS View:

1. Create an OData Project:
   • Open transaction SEGW (SAP Gateway Service Builder).
   • Create a new project by entering a project name and description.
2. Import the CDS View:
   • Right-click on the Data Model node, select Import > DDIC Structure, and choose your CDS view from the list.
3. Define the Service:
   • After importing, define the service by creating Entity Types and Entity Sets that map to your CDS view.
4. Generate Runtime Artifacts:
   • Right-click on your project and select Generate to create the runtime objects necessary for the OData service.

5. Registering and Testing the OData Service

After generating the OData service, you need to register and test it to ensure it’s functioning correctly.

Steps for Registration and Testing:

1. Register the Service:
   • Use transaction /IWFND/MAINT_SERVICE to register your OData service. Enter your service name, and complete the registration process.
2. Test the Service:
   • Use transaction /IWFND/GW_CLIENT or a tool like Postman to test the OData service endpoints. Ensure that you can perform CRUD operations and that the service responds as expected.

6. Integrating OData Service with SAP Fiori

Once your OData service is up and running, integrate it into your SAP Fiori application.

Integration Steps:

1. Create or Open a Fiori Application:
   • Use SAP Business Application Studio or SAP Web IDE to create or open your Fiori application project.
2. Configure the OData Service:
   • In the Fiori project, configure the OData service as a data source. This involves setting up the service in the manifest file of your Fiori app.
3. Develop the UI:
   • Use SAPUI5 controls to build the user interface, binding your UI elements to the data exposed by the OData service. Ensure the interface is interactive and provides a seamless user experience.

7. Best Practices for OData Service Generation

To optimize your OData service development, consider the following best practices:

• Use Annotations: Leverage CDS annotations to enhance the metadata of your OData services, improving integration with SAP Fiori.
• Optimize Data Handling: Implement efficient data retrieval and filtering mechanisms to handle large datasets and improve performance.
• Ensure Security: Apply proper authorization checks and security measures to protect sensitive data and ensure that only authorized users can access the data.

8. Conclusion

Generating OData services using the ABAP Programming Model is a crucial step in developing effective SAP Fiori applications. By following the outlined steps and best practices, you can create robust and efficient OData services that enhance the functionality and user experience of your Fiori applications.

Embracing these practices will enable you to build powerful and scalable applications that leverage the full potential of SAP’s modern programming model. Dive into OData service generation today and take your SAP Fiori development skills to the next level.

Happy coding!

you may be interested in this blog here:-

The Journey of Alex: From Confusion to Clarity in SAP Software Meaning

Benefits of Using Salesforce Nonprofit Cloud for Event Planing

The post ABAP Programming Model – 5 – OData Service Generation for SAP Fiori first appeared on TECHNICAL GYAN GURU.