SAP Community - NW ABAP Customizing Tools

Sizing HANA. Enfoques.

2016-04-12T00:49:50+02:00

Última entrada de la serie Sizing HANA.
En el camino recorrido hasta ahora, habíamos tratado una pequeña introducción al Sizing:

Sizing HANA. Introducción.

Así como un breve resumen de las herramientas que disponemos para llevar a cabo dicha actividad:

Sizing HANA. Herramientas.

En el día de hoy, nos centraremos en los distintos enfoques de los que disponemos a la hora de efectuar nuestro sizing
y como estos determinan el resultado final.

Dicho esto, empecemos!

Enfoques para una migración a HANA.

A la hora de comenzar un Sizing para SAP HANA contamos básicamente con 3 enfoques:

Sizing Inicial.
Partimos de cero, nuestro escenario inicial no cuenta con ninguna plataforma SAP de donde tengamos que migrar a SAP HANA.

Migraciones a HANA.
A diferencia de lo anterior, se cuenta con una plataforma SAP que se desea migrar a SAP HANA.

Escenario Sidecar.
Aunque se cuenta con una plataforma SAP y se desea implantar SAP HANA,
esta servirá como apoyo sin llegar a sustituir. Para este escenario,
es sizing dependerá del uso que le queramos dar a HANA,
por lo que su análisis en esta entrada no tiene mucho sentido.

Sizing Inicial.

En este supuesto deberemos basarnos en la herramienta Quick Sizer para SAP HANA.
www.service.sap.com/hanaqs

Como ya comentamos en la entrada que antecede a esta,
existen una serie de vías para recabar información:

Independientemente del camino escogido inicialmente se deberá acabar en el Quick Sizer.
Este nos informará de la cantidad de SAPS, memoria y disco con la que deberemos contar.

Migraciones a HANA.

Partimos de un escenario SAP, el cual se desea migrar a HANA.
Para tal propósito existe un reporte que se ejecuta en el sistema a migrar,
que calcula los recursos necesarios para dicha migración.

1872170 - Suite on HANA sizing report

Algunas consideraciones de este reporte:

Es independiente de la BBDD fuente.

Considera el de-clustering / de-pooling.

Considera las diferencias en los índices secundarios.

Funciona con SAP_BASIS 620 o posterior.

Compatible con todos los productos de SAP Business Suite (ERP, CRM, SRM, etc)

Siempre se debe contar con la última versión del reporte.

Con esto ponemos fin a la serie de Sizing HANA.

SAP Customizing Documentation Generation Tool

2017-11-30T23:54:08+01:00

In this Blog, I would like to share with you the easy way to generate a documentation file based on the customizing transport request.

Quite often customers request documentation of the entire customization effort made during the implementation and especially the PoC projects. Not talking about how useful it is but nevertheless, the document is a part of the contract and must be delivered.

Not sure how many times you faced it – this happened quite often to me and consumed a lot of my time.

How did we solve this normally? I did the stupid monkey routine of taking hundreds of screenshots based on what I remember I customized, sometimes also checking customizing transport requests to remind myself what I’ve done.

That's how I came to the idea that this should have already been automated. If transport requests have all the changes we made, there should be a way to download such a report. But, really? I have not found anything, neither in Google nor in SCN/SolMan.

So we decided to create this solution ourselves and share it with the community.

Some answers to the questions you might already have:

What is this solution?

It’s an SAP GUI report designed to be executed in SE38. It takes customizing transports (content of the tasks released) and Microsoft Word template as an input and produces another MS Word document containing all the customized entries with descriptions as an output.

How can I install it?

Download the code and the template from the GitHub.

Create a report ZREP_CUST_DOC on your ABAP NetWeaver system in transaction SE38

Copy the code into the report and activate it.

MS Word template has its own instructions on how to change the logo and customer/project names.

How does it work?

We reused the SAPLink source code (many thanks to them) to get the contents of the customizing transports, then the solution selects the complete entry from the customizing table/view, reads all the fields/table/view descriptions from DDIC in the given language and downloads all the information in a readable way to the MS Word document as per template provided by the user.

Is it safe to install? Yes, as you can audit the code before installation. Also, please only create the report in the development/customizing system and never in a production environment.

What NetWeaver versions are supported?

I hope everything from 7.0, maybe even below.

Any functional prerequisites, would it work on ERP/SCM/PLM, etc. systems?

This will work everywhere. And there are no functional prerequisites.

Are there any restrictions?

Unfortunately, due to MS Word limitations, we only show the first 10 columns of the customized entry in the final document. However, in most cases it is sufficient.

Can I use this freely?

Yes, but we would highly appreciate the feedback and reviews.

Do you plan to support the report?

Why not, if you have any ideas what needs to be extended, or see any bugs, please let me know.

What does the template look like?

See the screenshot, but it is better to download the template.

What does the result look like?

See the screenshots below or download the example file.

Many thanks to everyone and hope to hear your comments.

Translate Table T166U

2018-02-15T15:45:46+01:00

When you try to translate the “Form Titles for Purchasing Document Printouts”, which is Table T166U, “Translation” is grey in the customizing:

The entries can be translated using transaction SE63. In SE63, go to Translation -> ABAP Objects -> Short Text:

On the popup screen select A6 Table Entries -> TADG Tables (Customizing - No SAP UPD, Only INS):

On the next screen, enter the source and target language for translation and search for “*T166U*:

On the popup screen click continue:

The Object Name is filled. Click on “Edit”:

On the next screen, select the entries you want to translate:

On the next screen, you can enter the translations:

In order to transport your translations, you can use transaction SLXT.

ABAP Recursive Code to Identify root nodes in Hierarchy fromTable Data

2018-07-06T15:05:19+02:00

Dear ABAPers,

I have come across a scenario where I need to find out the root entry from a hierarchy. I would like to share the approach which I followed for the same. It might not be the best one but hope will help you in one or the other way 🙂

Consider the test data for our case:

Here First Column is the Child Node and Second Column is Parent Node.

Problem Statement: We need to identify the final child nodes for Parent '1' and '2'.

For e.g: For parent 1 root nodes are A and B. And again for A the root node are C, D out of which D is final root node and for C we have again two child nodes M and N which are at end the root nodes.

Same way we need to identify all the root nodes.

ABAP Code For the same:

*&---------------------------------------------------------------------*

*& Report ZAM_RECURSIVE_TEST

*&---------------------------------------------------------------------*

*&

*&---------------------------------------------------------------------*

REPORT zam_recursive_test.

TYPES: BEGIN OF ty_data,      "To hold test data

         field1 TYPE char1,   "Child

         field2 TYPE char2,   "Parent

       END OF ty_data,



       BEGIN OF ty_out,      "To Filter

         field1 TYPE char1,

       END OF ty_out,



       BEGIN OF ty_sel,      "Range Table

         sign TYPE TVARV_SIGN,

         opti TYPE TVARV_OPTI,

         low  TYPE char32,

         high TYPE char32,

       END OF ty_sel.



TYPES tt_data TYPE TABLE OF ty_data WITH EMPTY KEY.



DATA: it_data TYPE TABLE OF ty_data,

      wa_data TYPE ty_data,

      it_rec  TYPE tt_data,

      wa_rec  TYPE ty_data,

      it_out  TYPE TABLE OF ty_out,

      it_sel  TYPE TABLE OF ty_sel,

      wa_sel  TYPE ty_sel.



"Create Test Data

wa_data-field1 = 'A'. wa_data-field2 = '1'.

APPEND wa_data TO it_data.

wa_data-field1 = 'B'. wa_data-field2 = '1'.

APPEND wa_data TO it_data.

wa_data-field1 = 'C'. wa_data-field2 = 'A'.

APPEND wa_data TO it_data.

wa_data-field1 = 'D'. wa_data-field2 = 'A'.

APPEND wa_data TO it_data.

wa_data-field1 = 'E'. wa_data-field2 = 'B'.

APPEND wa_data TO it_data.

wa_data-field1 = 'K'. wa_data-field2 = '2'.

APPEND wa_data TO it_data.

wa_data-field1 = 'L'. wa_data-field2 = 'K'.

APPEND wa_data TO it_data.

wa_data-field1 = 'M'. wa_data-field2 = 'C'.

APPEND wa_data TO it_data.

wa_data-field1 = 'N'. wa_data-field2 = 'C'.

APPEND wa_data TO it_data.

wa_data-field1 = 'O'. wa_data-field2 = 'E'.

APPEND wa_data TO it_data.

wa_data-field1 = 'P'. wa_data-field2 = 'B'.

APPEND wa_data TO it_data.

"Sort Test Data

SORT it_data by field2.

"Fetch Data for Parent 1

it_rec = VALUE tt_data( FOR wa_rec2 IN it_data WHERE ( field2 = '1' ) ( CORRESPONDING #( wa_rec2 ) )  ) .

"Call recursive code

PERFORM f_fetch TABLES it_rec.

"Fetch Data for Parent 2

it_rec = VALUE tt_data( FOR wa_rec2 IN it_data WHERE ( field2 = '2' ) ( CORRESPONDING #( wa_rec2 ) )  ) .

"Call recursive code

PERFORM f_fetch TABLES it_rec.



"Write Data

WRITE /: 'Original Data'.

WRITE /: 'Node'.

WRITE: '     Parent'.

LOOP AT it_data into wa_data.

"Loop on Original Data

  WRITE /: wa_data-field1.

  WRITE '       '.

  WRITE wa_data-field2.

ENDLOOP.



DATA ls_out TYPE ty_out.

WRITE /: '----------------------------------------------'.

WRITE /: 'Children Nodes Identified'.

LOOP AT it_out INTO ls_out.

"Loop for Children Node

WRITE /: ls_out-field1.

wa_sel-sign = 'I'.

wa_sel-opti = 'EQ'.

wa_sel-low = ls_out-field1.

APPEND wa_sel TO it_sel.

ENDLOOP.



WRITE /: '----------------------------------------------'.

WRITE /: 'Complete Details for Children Nodes'.

WRITE /: 'Node'.

WRITE: '     Parent'.



LOOP AT it_data into wa_data where field1 IN it_sel.

"Loop on Children complete data

  WRITE /:  wa_data-field1.

  WRITE '       '.

  WRITE wa_data-field2.

ENDLOOP.





FORM f_fetch TABLES pt_rec TYPE tt_data.

  DATA: ls_rec   TYPE ty_data,

        wa_data2 TYPE ty_data,

        ls_out   TYPE ty_out,

        lv_lines TYPE i.

  LOOP AT pt_rec INTO ls_rec.

    READ TABLE it_data INTO wa_data2 WITH KEY field2 = ls_rec-field1 BINARY SEARCH.

    IF sy-subrc IS INITIAL.

      DATA(it_pass) = VALUE tt_data( FOR wa_rec2 IN it_data WHERE ( field2 = ls_rec-field1 ) ( CORRESPONDING #( wa_rec2 ) )  ) .

      DESCRIBE TABLE it_pass LINES lv_lines.

      IF lv_lines GE 1.

        PERFORM f_fetch TABLES it_pass.

      ELSE.

        CLEAR: ls_rec,it_pass.

        ls_rec-field1 = wa_data2-field1.

        APPEND ls_rec TO it_pass.

        PERFORM f_fetch TABLES it_pass.

      ENDIF.



    ELSE.

      ls_out-field1 = ls_rec-field1.

      APPEND ls_out TO it_out.

    ENDIF.

  ENDLOOP.



ENDFORM.

Output :

Happy Learning 🙂

Copy Customizing Path

2018-08-15T11:23:36+02:00

Hello,

I developed useful functionality for SPRO

I detected that is common the necessity of copy IMG path when you navigated of SPRO Tree Customizing .

With the following code you can copy the path very easy

The change is only apply in Developer System and is necessary register one standard object.

Step 1: Add customer Button in Status GUI IMG_DISP of Function Group S_IMG_TOOL_1.

Create a Custom Function Code "ZCOPY_P"

Add custom Function Code "ZCOPY_P"

Add Custom Code Functions in Interface and Key Function

Step 2: Insert Implicit Enhancement in INCLUDE: LSHI01F0X - end of FORM execute_user_command

Step 3: Add the following ABAP code and active the implicit enhancement

DATA: lv_nodekey TYPE tv_nodekey ,

      le_item TYPE shi_item,

      le_node TYPE treev_node,

      lv_relatkey TYPE tv_nodekey,

      lv_text(500) TYPE c ,

      lv_relatship_ant TYPE int4,

      lt_path TYPE STANDARD TABLE OF char100,

      le_path TYPE char100,

      lv_choise TYPE  sy-tabix.



CASE fcode.

  WHEN 'ZCOPY_P'.

    CHECK g_tree_data->tree IS NOT INITIAL.

    READ TABLE g_tree_data->nodes INTO le_node WITH KEY node_key =  g_tree_data->node_key  .

    CHECK sy-subrc = 0.

    READ TABLE g_tree_data->items INTO le_item WITH KEY node_key =  g_tree_data->node_key  item_name = 'TEXT'.

    CHECK sy-subrc = 0.

    le_path =  le_item-text.

    APPEND le_path TO lt_path.

    lv_relatkey  = le_node-relatkey.

    lv_relatship_ant = le_node-relatship.

    WHILE lv_relatkey IS NOT INITIAL.



      READ TABLE g_tree_data->nodes INTO le_node WITH KEY node_key =  lv_relatkey .



      READ TABLE g_tree_data->items INTO le_item WITH KEY node_key =  le_node-node_key item_name = 'TEXT' .



      lv_relatkey = le_node-relatkey .



      IF  le_item-text IS NOT INITIAL AND  lv_relatship_ant = '4'.

        CONCATENATE le_item-text '->' INTO le_path.

*        le_path =  le_item-text.

        INSERT le_path INTO lt_path  INDEX 1.

      ENDIF.

      lv_relatship_ant =  le_node-relatship..

    ENDWHILE.



    CALL FUNCTION 'POPUP_WITH_TABLE_DISPLAY'

      EXPORTING

        endpos_col   = 130

        endpos_row   = 10

        startpos_col = 40

        startpos_row = 1

        titletext    = 'Ruta de Configuración'

*      IMPORTING

*        choise       = lv_choise

      TABLES

        valuetab     = lt_path

      EXCEPTIONS

        break_off    = 1

        OTHERS       = 2.

    IF sy-subrc <> 0.

* Implement suitable error handling here

    ENDIF.

Step 4: Active all objects and test de functionality. TCode SPRO--> F5 --> "Copy IMG Path"

Web Dynpro ABAP: New Customizing UI with UI Guideline FIORI

2019-10-23T10:00:05+02:00

Introduction

The UIs of your Web Dynpro ABAP applications (including those built with Floorplan Manager) don't always meet your exact requirements and you must adapt them accordingly.

And, you as an administrator, can make these UI adaptations using the customizing UI.

Until recently, the customizing UI had plenty of functionality but wasn’t the easiest to work with. Things have changed! Starting with SAP_UI 7.54 (for ABAP 1909), there is a totally new UI for customizing.

This UI is only available with UI guideline FIORI. Of course, the adapted applications can also be used with other guidelines.

Highlights of the new UI

Clear separation between the adaptation UI and the application itself

Easy navigation to the elements you want to change

Most important changes are easy to do

Undo/Redo functionality

Immediate save

Let’s have a look at the procedure with a dedicated example, the EPM demo application.

Start the customizing

First things first...

Your system must have release SAP_UI 7.54, aka 1909.

You have customizing authorization (see the topic “Authorizations for Personalizing and Customizing” in the Web Dynpro ABAP Configuration Framework documentation on the SAP Help Portal https://help.sap.com/viewer/9c02f1c9f89a49448c6b55b39f7121c4/201809.latest/en-US/47ced9edf5072fe2e10000000a42189d.html).

You are working in the customizing client of a test or customizing system.

So, let’s start...

Run the Web Dynpro application S_EPM_WD_PO_LIST (you can find it in the Workbench (SE80) as a sub-node of the Web Dynpro component with the same name).

You will see that the application is not shown with the FIORI guideline, but with theme SAP_TRADESHOW_PLUS. Change it by adding “&sap-theme=SAP_BELIZE” to the URL. Now it looks FIORI-like.

Open the context menu and select “Call Application in Customizing Mode”.

A new tab is opened for the new customizing mode.

Please note the black toolbar on top. If you have open customizing requests for your user, the input field is enabled, and you may select one of them. Or you do your customizing without adding it to a transport request. Press OK and the toolbar will change.

We will look at the purpose of the visible toolbar buttons later.

Click on one of the Purchase Order IDs to navigate to the details view.

Hide a simple UI element

The first thing we want to change is to get rid of the “Print Preview” button.

Open the context menu of the preview button, choose, “Adapt”, then “Hide”. Done!

By the way, the change is saved automatically. You can check it by going back to the tab with the application not in customizing-mode, refresh and choose another purchase order.

Hide a Group

Similarly, we want to hide the “Dates” group. Same procedure on the text “Dates”.

Result:

Oh! This is not what we wanted to do! The “Created” entry is still there! We have only hidden the header line.

First, we must undo this step. Fortunately, the “Undo” button is active. Press it!

Now, let’s try again. Open the context menu and choose “Adapt”. Now stop and have a closer look at the toolbar.

On the left-hand side there are some buttons. Particularly useful is the “Parent” button. Press it once and check what happens to the group.

The whole group has a blue border around it, and the adaptation menu is titled “Group:… ”. This is what we want to hide. So, choose “Hide” . Now the whole group is gone.

Change the Save Buttons

There are 2 “Save” buttons in the toolbar. One is enough, thank you. We’ve decided we only want the “Save and Back” functionality but with the simple “Save” text. The icon should also be like the simple “Save” one.

Step 1: Rename the “Save and Back” button:

Context Menu -> Adapt -> Rename -> change the text->Tick. Done.

To change the icon property, you must use the “Advanced” dialog. If you do not know the icon source ID, just copy it from the other button. Adapt the second “Save” button, switch to the “Advanced” view, open the “Texts” panel and press the button “Image Source”. Now you see the icon source.

Copy the source and click somewhere outside of the dialog to close it without changing the second button. Now adapt the first button. The dialog is already in advanced mode. Open the “Texts” panel and the “Image Source” field and overwrite the current value. Click on the “Done” (Tick) button. The button has changed, but the dialog is still open.

Click somewhere outside of the dialog to close it.

Now there are 2 buttons with the same UI but with different functionality. Hide the second one. To do so, use the “Back” button to return to the simple dialog and press “Hide”.

Now you have 1 Save button with the functionality of “Save and Back”.

Styling

The “Purchase Order ID” is very important, so we want to highlight it in some way.

Open the “Advanced” adaptation dialog of the “Purchase Order” text view. Within the “Visual Presentation” panel you will find the “Style Class” property. Press it to open the field. Open the value help for the field.

Now you see all the CSS styling possibilities for the text view.

Please note that we do not guarantee that the changed styles will really affect the field because they may be overwritten by some framework style settings. This is also dependent on the theme and/or guideline being used.

Press the value help on the “fontWeight” and choose “bold”. Or choose one of the available font colors. Close the value help and click on the “Done” button next to the “Style Class” tokenizer. Click outside the dialog to close it.

Unhide a UI element

Once a UI element is hidden, it is hard to get it back. If you want to get back the “Print Preview” button, you first must find it. In the old UI, there is a list of changed UI elements but the ID or label is not always enough to know what it was.

In the new Customizing UI it is easy to unhide elements. There is a dropdown list box in the toolbar showing the current view. The default is “Show Adapted UI”. Change it to “Show Hidden Elements”.

Now you see all the elements you have hidden with a light green background. Open the context menu on the “Print Preview” button and set it as visible.

There is another entry in this dropdown list box: “Show Changed Elements”. Use it when you want to get an overview of what you have changed so far.

Further information

“Undo” and “Redo” are available as long as you stay within the same session.

Reset can be used when you want to reset all customizing changes for the application. The “Info” button leads to a list of changed component customizings within your application. You can click on one of the links to see the changes in a new Web Dynpro session.

The “Help” button provides you with some important information on getting started with the new customizing UI.

Currently, not all functionality of the classic customizing is available in the new customizing UI (e.g. adding decorative elements or customer enhancement fields is not possible). To get this functionality, navigate to the classic customizing via the context menu.

The new customizing UI is only available with the FIORI UI guideline (even the theme FIORI_3 aka Quartz is not supported).

The URL parameter for the new customizing UI is “sap-config-mode=A”.

So, this is the first step for the new Customizing UI. Stay tuned!

Please tell us your opinions about the new UI. We can use them to improve it.

How to get to know every important Transaction code related to IDOC?

2020-07-15T23:33:10+02:00

Introduction

After working with SAP for more than 15 years and travelling across the Globe for SAP Projects one issue I always use to have how can I keep track of all the SAP Transaction Codes associated with IDOC. If you are working as a SAP ABAP Consultant you need to keep the name of Transaction Codes in your Fingertips. Sometimes this you know from other Experts and sometimes you have to dig it out. After exploring I found a very easy way to dig out the SAP Transaction Codes associated with IDOC. Just check this blog and conquer the SAP world.

Solution

Login to SAP and type WEDI in Command Bar

Wala below we have all the important Transaction Code for IDOC

Conclusion

You can use this blog anywhere everywhere in every SAP Project. Enjoy

For video version check below Link

https://youtu.be/cP6TfUHpb7M

Organize transport requests using projects

2021-07-02T11:48:56+02:00

Optimize release cycles by organizing your SAP transports

CTS: Change and Transport System

Projects

Further reading

Conclusion

CTS: Change and Transport System

The Change and Transport System (CTS) is a tool built into SAP systems. CTS helps organize development projects in ABAP Workbench and customizing and then transporting the changes between the SAP systems in the system landscape. Everyone working on developing or maintaining processes within an SAP system works with (parts of) CTS. This includes functional consultants, technical consultants, and system administrators.

Projects

About projects in CTS

Using CTS projects allows planning development work and customizing activities in structured groups. Changes are structured independently of each other in different projects and can be imported independently into target systems. Projects are a valuable tool for going live with different projects at different times, linking development work in a single area, or simply keeping track of all transports for a specific change or release cycle.

Creating Projects

Transaction `SPRO_ADMIN`

In order to enjoy more extensive project management functionality than just grouping transports, it is best to create a CTS Project based on an IMG (Customizing) Project. Achieve this via transaction SPRO_ADMIN.

- Execute transaction SPRO_ADMIN, click the left-most button, Create Project (F5), and fill in a project name. Note that project names are limited to 10 characters.

Add a project title/description. Optionally define other attributes such as scope and team members.

Save the project via the Save button or the keyboard combination Ctrl+S.

Enable CTS functions for the IMG project to allow managing transport requests. Open the Transp. Requests tab and click the button labeled ‘Active CTS Functions’.

That’s it. The newly created project can now be assigned to transport requests.

Report `RSWBO_AUX_PROJECT`

The report works just as its description suggests: ‘Use CTS Projects Without IMG’. The report allows creating, deleting, and editing CTS projects and their descriptions without creating a corresponding IMG project first.
It’s important to note that customers cannot use these ‘barebone’ CTS projects for fully-fledged project management. The reports' documentation says the following:

This report program was written for temporary usage of the CTS project functions. You normally use the IMG Project System to create CTS projects. This report lets you use the CTS project functions without involving the IMG Project System. You can create, edit and complete test projects. This report is in no way intended to replace a proper project system.

Apart from the above, the report can show a list of all requests for a given project and the Project Piece List. The project piece list contains all of the objects impacted in a project. When requests are released, the object list of the request is added to the piece list.

To create a project with RSWBO_AUX_PROJECT, first, execute the report and press the Create button (1). Next, enter a description for the project (2) and confirm the creation. That’s it. The newly created project can now be assigned to transport requests.

Assigning projects to transport requests

After creating at least one CTS project, transport requests can be assigned to a project in the Transport Organizer during the creation or editing of a project.

As mentioned by mfourmy_2016 in the comments below, it is possible to make assigning a project mandatory when creating a transport request. This is achieved by changing the settings for attribute SAP_CTS_PROJECT in transaction SE03 (Transport Organizer Tools) under "Display/Change Request Attributes".

CTS Projects vs IMG Projects

There are two options for CTS projects. Barebone CTS projects are an excellent tool for release management. They allow organizing and bundling transport requests and easily importing them all in one go. IMG projects with CTS functions enabled, on the other hand, offer the same features plus a bunch of extra project management features. These include defining project scope, specifying projects start and end dates, and assigning team members to projects.

In conclusion, creating IMG projects is best practice and recommended when additional project management features are desirable. However, if your organization does not yet use IMG projects and you are looking for a way to organize transports as a development team, then basic CTS projects may well be sufficient. They will allow you to experiment without the extra bells and whistles.

Conclusion

This post touches on projects and transports in SAP. You learned how to create projects and how to use them to group transport requests. You also know the difference between IMG projects and CTS projects. Want more information? Be sure to check out the links above.

Are you already using projects to manage releases at your company or customer?
Got any tips to share? Post it in the comments 👇

CDS Annotations for – New And Experienced professionals- 3

2022-02-25T04:59:28+01:00

Premise-

There are many SAP blogs out there that explains inner working of CDS views or core data services in SAP’s S/4 boxes. But there are still struggle among experienced professionals who is switching from ECC system to S/4.

This blog is dedicated towards experienced professionals working on ECC systems for many years and yet to jump to S/4.In the next few min, we will look at a very basic concept of a CDS view and try to evaluate inner working of the CDS using classic SAP tools.

Pre-Requisites –

You have read / understood / Prototype items on Previous blogs.

SAP CDS for New And Experienced professionals | SAP Blogs

Consuming CDS for – New And Experienced professionals- 2 | SAP Blogs

Lets Start –

At this point you have understood CDS views a little better. Just to recap CDS views are not a single object but an Entity consist of a SQL view and a Data Definition.

While creating our first CDS view we didn't change the annotations written on top of CDS views.

The annotations are always start with "@" and there are few several pre-defined annotations.

What are CDS annotations?

Annotations are properties of a CDS entity. A way to enrich the CDS entity. These annotations are evaluated at the run time to decide the behaviour of a CDS entity.

Lets try to decode some Header Annotations -

@AbapCatalog.sqlViewName: 'ZVSQL_TRAVEL' - Defines the SQL View name for the CDS entity.

@AbapCatalog.compiler.compareFilter: true - CDS view specifies how filter condition (Where condition) is evaluated at run time.

@AbapCatalog.preserveKey: true -
Specifies the definition of the key fields in the CDS database view of the CDS view. (Whether to use keys defined in the original data base table or the one defined in CDS views).

@AccessControl.authorizationCheck: #CHECK -

Authorization check for CDS. Defines the implicit access control when Open SQL is used to access the CDS view.

@EndUserText.label: 'CDS View for Travel Data'-

Description of the CDS view for end users.

Common Questions related to Annotations-

Is CDS Annotations a way to manage technical settings in SE11 and buffering?
- Answer: Annotations are a way to control technical settings, buffering as those are also properties of data dictionary object in S/4. But Annotations are way more there are several other properties that annotations can control.

Where can I see all SAP annotations for my current S/4 level?
- Answer: SAP Annotations are available in help document I have added as a reference to this blog but also you can search annotation using SE16 from table - ABDOC_CDS_ANNOS. Remember in this table you will see different kind of annotations, not only related to ABAP CDS but others please refer to the references for more just to give a little bit of more understanding see the categories as below.

- - Analytics Annotations
  - AnalyticsDetails Annotations
  - Consumption Annotations
  - DefaultAggregation Annotations
  - EnterpriseSearch Annotations
  - Hierarchy Annotations
  - ObjectModel Annotations
  - OData Annotations
  - Search Annotations
  - Semantics Annotations
  - UI Annotations
  - VDM Annotations

Important Tip - Take a look at table - CDSVIEWANNOPOS all the annotations related to a CDS view can be found here. Also check CDS* in SE16 for other CDS views in your S/4 system.

Exercise- Lets add a simple ABAP Annotation (Header) to our existing CDS Header. start this by typing "@" or CTRL+Space key from your keyboard.

Lets us add @AbapCatalog.buffering then press "." to look at further options or hit CTRL+SPACE from eclipse.

select status: #swtiched_off.

Let us try to change the property of the buffering status from switched off to something else. You can only allow pre-defined values for buffering status so check the reference ABAP Keyword Documentation (sap.com) you will notice the different values are explained by SAP. Also you can remove the #SWITCHED_OFF and use CTRL+SPACE to find applicable values.

In this case we choose -@AbapCatalog.buffering.status: #ACTIVE

When you add the buffering type active and try to activate you might get an error. requesting to specify a buffering type.

Lets us also add a buffering type.

Now lets look at the SQL view technical settings after this change. You would notice the buffering is activated and fully buffered.

Remember not all annotations around CDS entity is visible in SE11 or SE12 as many of these properties are at data base level. Lets add another Annotation against Data Aging.

Defines the handling of obsolete data on a SAP HANA database when Open SQL is used to access the CDS view - If we set this to True then open SQL will read all data and can lead to performance problems if the database is really old and huge.
Where as if you set this to false then Open SQL will read only current data.

Conclusion:

Annotations are properties of CDS entity that allows us to pre-define behaviour of the CDS entity at runtime. Congratulations now you know Annotations. Keep learning.

See you in the next blog - CDS in Real life requirements – New And Experienced professionals- 4 | SAP Blogs

Reference Documents-

All About - CDS Annotations (sap.com)

ABAP CDS Annotations - ABAP Keyword Documentation (sap.com)

Examples - ABAP Keyword Documentation (sap.com)

CDS Annotation Grouping - ABAP Keyword Documentation (sap.com)

CDS Architecture – New And Experienced professionals- 5

2022-02-26T04:26:30+01:00

Premise-

There are many SAP blogs out there that explains inner working of CDS views or core data services in SAP’s S/4 boxes. But there are still struggle among experienced professionals who is switching from ECC system to S/4.

This blog is dedicated towards experienced professionals working on ECC systems for many years and yet to jump to S/4.In the next few min, we will look at a very basic concept of a CDS view and try to evaluate inner working of the CDS using classic SAP tools.

Pre-Requisites –

You have read / understood / Prototype items on Previous blogs.

SAP CDS for New And Experienced professionals | SAP Blogs

Consuming CDS for – New And Experienced professionals- 2 | SAP Blogs

CDS Annotations for – New And Experienced professionals- 3 | SAP Blogs

CDS in Real life requirements – New And Experienced professionals- 4 | SAP Blogs

Recap-

We started this journey with creating a simple CDS for a custom table in the first blog.

In the second blog we looked at simple way to consume CDS views in ABAP executables.

Took a deep dive into annotations in third blog.

Finally looked at an approach to extend CDS views.

Lets Start –

What we haven't looked at till this point is how CDS architecture is different than R/3 views.

This is extremely important to understand. Based on our experience in other four blogs let us list down what we already know.

We know CDS views consist to two individual object.
- SQL View generated automatically.
- A Data Definition.

We also know CDS entity (It is called an entity as this consist of more than one object) can be consumed the same way we consume a data base table in ABAP executable.
- We also took a runtime trace that showed us the SQL view is visible on run time trace but the data definition is not.

There are additional features / properties that can be set on the CDS view using Annotations.

We can extend standard SAP CDS views.

Lets Remember how the R/3 Architecture used to be.

All DB's communicate to Application layer via Open SQL (Each SQL to be decoded by Optimizer to the right native SQL command). Many of you have used secondary keys and multiple performance technique on SQL statements to ensure right primary key or secondary key is used to fetch the data.

In R/3 Architecture the main component that decides which SQL statement to use is the Optimizer.

Now this process is slower and when the move to S/4 was decided one of the major changes proposed is for programmers to use database operation with much ease and this is exactly what CDS does.

CDS Architecture:

CDS entities are a layer in between the DB and the application, this is an extremely powerful tool for developers to be able to model data as per business need.

Code Pushdown is the main principal - This allows you to get rid of the optimizer and run some DB modelling at the DB level instead of the application level.

Now combine this principal with HANA in memory DB. Then you have an extremely powerful concept that merges Application/ DB layer into one mesh of systems.

Conclusion:

CDS Architecture is in the middle of application running on S/4 and the actual DB.

Now you know the architecture and hopefully a better understanding of CDS. Keep learning.

Next Blog - CDS Exposing to Odata – New And Experienced professionals- 6 | SAP Blogs

IDA ALV Dump CL_SALV_IDA_STRUCTDESCR Except CX_SY_STRUCT_COMP_NAME

2023-06-19T10:56:46+02:00

Hi Everyone,

In previous versions, we were able to give the column names numerical or custom expression for the reports, but the structure of this has changed a bit with hana. If we give the column names numerically or letter , we may get an error while downloading excel in IDA ALV.

Now, if you have kept the structure of the tables used in the report with 'DDIC' as a standard, column names should only start with a letter.But I will suggest a practical solution for this. If you encounter this error like me, you can continue with my method.

For example, I created a structure from transaction code 'SE11'. Some of these structure components start with numbers.

SE11 Structure

In such cases, if you directly name this structure as the type of the table with this structure, you will get a dump. This is because it appears as a 'DDIC' data type. In ALV_GRID structures ( for example IDA_ALV ) it cannot start with a number if 'DDIC' is a structure.

Standart Program Column Name Check

If you encounter an error like below (dump). You can solve this error in your reports with the way I suggest.

Example Dump

Image

If you are getting this error in IDA ALV , it is because it is checking whether your data type( structure or table type ) is in 'DDIC' as in 'Image2'. If your data type( structure or table type ) is 'DDIC' and the column name in this data type starts with something other than letter, you will get a dump.

Image2

As a solution to this, I made a simple change as follows.

BEFORE



DATA : gt_output  TYPE zbc_s_t0007.

By the way 'zbc_s_t0007' ddic structure( se11 )



      CALL METHOD go_alvgrid->set_table_for_first_display

        CHANGING

          it_outtab                     = gt_output

          it_fieldcatalog               = gt_fcat

        EXCEPTIONS

          invalid_parameter_combination = 1

          program_error                 = 2

          too_many_lines                = 3

          OTHERS                        = 4.





After



TYPES : BEGIN OF tt_s0007.

          INCLUDE TYPE zbc_s_t0007.

TYPES : END OF tt_s0007.



DATA : gt_output  TYPE TABLE OF tt_s0007,



      CALL METHOD go_alvgrid->set_table_for_first_display

        CHANGING

          it_outtab                     = gt_output

          it_fieldcatalog               = gt_fcat

        EXCEPTIONS

          invalid_parameter_combination = 1

          program_error                 = 2

          too_many_lines                = 3

          OTHERS                        = 4.

( The 'GT_OUTPUT' table contains the on-screen data for the report. )

In this way, column names can start with numbers and can be downloaded to excel.

I made the above correction in my own report. Here I used the ALV_GRID structure and got an error because the column names start with numbers. I then fixed this as I mentioned above. If you do, your data type will not be detected as a 'DDIC' structure. This allows you to start column names with numbers.You will also experience this error when exporting the data in the report to excel. The solution to this problem is the same (tried).

I hope it has been informative and a logical solution to the error you encountered. Waiting for your comments and questions.

How to find a configuration or IMG activity path for any object with the help of a Transport request (TR) number in SAP ERP

2023-11-16T18:14:31+01:00

Hi All,

Hope you are doing good.

This is my first SAP blog. With the help of this blog, we can understand how to find Configuration/SPRO IMG path for any TR created in the SAP system.

Introduction:

Sometimes we will get a requirement or need to find a configuration or IMG path for an object that has already been created. Now we have a TR number. We need to find out exactly where the object changes were made in the SPRO path, and we need to identify which objects were created or modified in that TR.

In this blog, I will explain and share the steps, along with screenshots, on how we can find an IMG path for any object in SAP by using Transport request numbers.

This method will work for all the Functional consultants who are working in SAP ERP.

Main Topic:

Steps:

Firstly, I have a TR number of DS4K902896.

1.Insert the TR number in the E071K table.

E071K TABLE:

2. Take the object name: V_FAGL_SEGM. or table name: FAGL_SEGM In this example, I am using the object name V_FAGL_SEGM

3.Go to SM30 and paste the object name: V_FAGL_SEGM and click on Customizing

4. Click on Continue w/o Specifying Project

5. That's it. We had now arrived at the exact configuration path. Check out the screenshot below.

6. Click on Define Segment:

7. If we see that I created Segment 760000, the same segment number we can see in the E071K TABLE under Object name.

8. Object name: 1000000760000 i: e: Client 100 Segment: 0000760000 (unconverted)

Conclusion:

In the E071K table, we can input Parent TR or Child TR; anyone is fine. We can take TABLE NAME (FAGL_SEGM) or OBJECT NAME (V_FAGL_SEGM) to input into the SM30 table. For faster results, use OBJECT NAME (V_FAGL_SEGM).

This way, we can quickly find the configuration or IMG path for any TR created in the SAP

Thanks for reading this blog and if you find it informative, please like and share this blog.
If you have any query or questions regarding this blog let me know in comment section. Please follow my profile for similar content.

Thanks.

Scenes from an ASUG Mid-Atlantic Chapter Meeting

2024-03-25T19:33:57.636000+01:00

This past Friday Fairfax Water hosted an ASUG Mid-Atlantic Chapter meeting. First I want to thank Gwendolyn Glasner, who set up the meeting, Lauren Milligan, who executed the meeting, Atul Patankar, our ASUG Volunteer who introduced the meeting and all of our speakers:

Special thanks to our sponsors:

Agenda:

8:30	9:00	Breakfast and Registration Open
9:00	9:15	ASUG Mid-Atlantic Chapter Welcome
9:15	9:45	Intelligent Automation for SAP Transformations: How Automation De-Risks Custom Code Modernization	Jason Narnian, smartShift
9:45	10:00	Networking Break
10:00	10:45	ASUG Customer Roundtable Discussion	Patty Brown, ASUG
11:00	11:45	You've Paid For It, So Let's Use It	Kristen Scheffler, SAP
11:45	12:30	Lunch & Learn: ECC TO S/4HANA Conversion Approach	Alex Borokov, Naviste
12:30	1:15	Plant Tour
1:15	1:30	Closing and giveaways

After introductions, Jason from smartShift presented:

Clean core is a popular topic this year so interest was high.

Next, for the first time I can recall, we had ASUG's Patty Brown present at our meeting about the value of ASUG.

Patty reviewed the ASUG member benefits. She leads the editorial team, producing ASUG First Five.

Patty thanked the volunteers at the meeting. She was very upbeat and supportive.

Next, the great Kristen Scheffler presented "You Paid for it, so Let's Use it".

Kristen covered several areas regarding SAP Support and many attendees told me they were looking forward to her slides.

Source: SAP

I've used these options (try chat first, then if it's too long of a wait, I will call CIC).

I didn't know about this, so I will have to try it out later:

Source: SAP

Kristen provided an update on SolMan, a product I've used for years. Many of us will need to decide what to do after SolMan 7.2.

Lastly, Alex from Navisite provided a great session about migrating to S/4HANA

Source: Navisite

I invite you to attend our upcoming Mid-Atlantic Chapter meetings:

July 26: Topgolf Baltimore
Call for Sponsors: https://www.cvent.com/c/abstracts/3edfe457-f452-4be3-8cd2-90aa7ebd2d54
Link to Register: https://www.asug.com/events/asug-mid-atlantic-chapter-meeting-july-2024
September 27 – Lewis Ginter Botanical Gardens, Richmond, Virginia
October 25 – Topgolf DC

Sponsor tables:

I *forgot* to take pictures of the food!

Until next time.