How to Start Developing on Your Own SAP ABAP server “Developer Edition”

How to Start Developing on Your Own SAP ABAP server “Developer Edition”

In this article I will comment the tools with which we can work the ABAP server “Developer Edition” that I have installed in the posts: How to Install SAP Development Environment for Free [Updated 2021] – Part 1 & How to Install SAP Development Environment for Free [Updated 2021] – Part 2

This server, which you can download from the SAP demos page, includes among other things, a Gateway server so that we can create and publish OData services, a Front-end server with pre-installed sample applications and access to the different development and configuration transactions.

Once we log in with the SAP GUI to our newly installed server, we will see that some of the most common transactions for developers appear by default in the user menu.

Next I will comment on what I think as developers you will use more frequently; Although it will depend on the approach of each profile (back-end, front-end or full-stack), and the example data model that we can use in our developments.

Important Transactions for a developer

  • SE80 – Object Navigator:It has been the development environment par excellence in SAP; although in recent years, and increasingly, it is being replaced by Eclipse + ABAP Development Tools (ADT), given its versatility.

As I mentioned in previous posts, I recommend that you get to work with Eclipse. It is true that currently much of the SAP ERP installed base uses an ABAP version lower than 7.40 SP05; from which “artifacts” such as CDS, DMPA, CDS Annotations, etc, begin to appear; But this will soon cease to be the case, and it is better to be prepared.

Personally, I still use the SE80 quite a bit, especially for working with OData services and method redefinitions (it is much more comfortable); But every time I am doing many more things with Eclipse. Among other things, when I build OData services I try to pull CDS and / or AMDP whenever I can, because of the benefits they have in terms of performance and the flexibility they offer. These types of development objects – for example – can only be created using Eclipse + ADT.

  • SICF – Maintenance of HTTP services:Allows you to enable or disable HTTP services (BSP, OData, etc.). It is very important when developing Fiori applications to bear in mind that, once the OData service has been added and the application deployed on the front-end server (BSP), it is necessary to activate both services.
  • PFCG – Maintenance of roles:It is a transaction that Fiori developers usually use when creating new Fiori Application Groups and Catalogs, to assign them to user roles. In real projects it is usually the task of the Basis team.
  • /IWFND/MAINT_SERVICE – Activate and Maintain Services:Typically used to publish OData services on the front-end server.
  • /IWFND/ERROR_LOG – SAP Gateway Error Log:As its name suggests, it allows you to view the Gateway error log on the front-end server.

Netweaver Enterprise Procurement Model

For some time now, SAP has been introducing this data model for the realization of examples in Netweaver systems, as it did at the time with the “flights” model (Fligth).

This model will serve as a basis for those developments where you do not need to create “custom” or “Z” objects as it is known in the SAP world.

Development packages

The local “developer” user package ($tmp) includes several objects including a BOPF, a few CDS, annotations, and Fiori applications, a Gateway project, and so on.

If you have in mind working on the development of Fiori applications, you will need to install, in addition to Eclipse and ADTs, the SAP Cloud Connector and create a “trial” account in SAP Cloud Platform if you do not have one.

In the next article How to Install SAP Cloud Connector on your SAP ABAP server “Developer Edition”. I explain step by step what you must do to install the SAP Cloud Connector on the SAP NetWeaver AS ABAP Developer Edition server.

This Post Has One Comment

Leave a Reply