When we started sharing the news about the redesign of the ABAP Keyword Documentation, we got a lot of feedback from you. Your feedback focused on whether the content was made for beginners or not, whether examples were too complicated or just right,...
A few weeks ago, we informed you about changes in the design of the ABAP Keyword Documentation. The new design is applied to the ADT version as well as the Web and Help Portal versions. In this blog, we will take a look at the ADT version that was re...
The ABAP Keyword Documentation has been around for many years and is the first resource for ABAP developers searching for ABAP keywords, syntax, or release-specific changes. Pressing F1 on a keyword, calling transaction abaphelp or abapdocu, or looki...
A null value is a special value returned by a database to indicate an undefined value or result. There are no special null values in ABAP, and it's not easy to add such a feature to the language these days. The value range of a data type takes up the...
Yep, we already spilled the beans in our last blog which introduced the language element STEP for ABAP internal tables (SAP BTP ABAP Environment 2202). Nonetheless, if you haven't heard of it yet... Here's another new ABAP language element: It's FINA...
Hi Ferenc,0 to many should be included in frq="*": If you read further in the documentation it says "For frq="?" and frq="*", the expected element must not necessarily exist in the inbound XML stream."Best regards,Lena
Hi imro_dev1,If you have elements with optional content in your XML file, you have to work with conditions. ST expects exactly what you define, so in your case, content is expected.Best regards,Lena
Yes, still a fix in the documentation And now, good news, vlad_s, we had to fix the latest version and so, the note is available here: https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abennew_constructor_params_itab.htm...