ABAP BOOLC and XSDBOOL use-cases

Posted by -

 In the previous post ABAP Convert Logical Expressions Into Boolean Values, I talked about BOOLC and XSDBOOL functions and their respective features. I thought I would elaborate on their use cases with examples.

BOOLC:

  • Set boolean flag:

  • Set custom flags like Y/N or 0/1 using ABAP built-in processing functions.

  • Pass return to methods expecting ABAP_BOOL parameters,

When not to use BOOLC:

    Comparison against ABAP_BOOL types:

    Despite the name BOOL and C, the function doesn't return ABAP_BOOL type nor a C.
    Instead, it returns a STRING like result.
    Due to ABAP comparison rules when STRING is compared against type ABAP_BOOL( type 
    C length 1 internally), the later gets converted from C to STRING and ignores any blanks.

This leads to unexpected behavior, for example, this code prints "instead I will be printed."
Even though 1 = 2 is false , boolc returns a string with space which is compared to a converted string with ignored spaces( BLANK) hence the comparison fails.

XSDBOOL ( available from ABAP 740 SP08 )

  •    Set boolean flag:

  •    Pass return to methods expecting ABAP_BOOL parameters.

  •    Comparison against ABAP_BOOL.

When not to use XSDBOOL:

    Comparison with STRING types:( Hope you see the pattern here)

    As discussed above,
    Due to ABAP comparison rules when STRING is compared against type ABAP_BOOL(                    type C length 1 internally), the latter gets converted from C to STRING and ignores any blanks.

Since XSDBOOL returns ABAP_BOOL, the false results get ignored.

Passing its return to ABAP built-in processing functions that take string type argument as input such as TRANSLATE would have an unexpected behaviour,
Picking the same example from BOOLC to set a custom flag,
This code doesn't work as expected due to conversion rules being at play.

I hope you liked the BOOLC and XSDBOOL use cases.

Both of the Boolean functions have their use cases and should be used appropriately. The pitfalls around their usage come due to the nature of  ABAP comparison rules and should be kept in mind.

Popular posts from this blog

ABAP convert internal table to excel (.xlsx) format and Send email or download

Posted by -
Reporting is incomplete without file interfacing. Sometimes the requirement is to send a file via email or download it to a PC. but what to do when the user requests the file in XLSX format? In today's post, I am sharing how to convert an internal table to .xlsx format and then send it to a PC or email. One of the quickest ways I found it been done is using SALV classes. Below is the Code snippet Now once you have the xstring with you, simply pass it to relevant libraries to handle the output. Downloading to PC: Sending via Email It's that simple. Hope you like the post and use it in your day to day work.
Read more

ABAP read excel(.XLSX) file to internal table in ABAP using CL_FDT_XL_SPREADSHEET

Posted by -
You are given a requirement to upload data to a custom DB table where the user provides you with the file path of the excel on his PC and the report loads the data from it to the Custom table. For experienced Abapers, the requirement is quite straightforward, except that the user wants to upload an XLSX file. There are not many options to read data from XLSX/XLS file. The TEXT_CONVERT_XLS_TO_SAP  function module is one of them but is a performance killer and uses OLE. In this post, I wanted to showcase How we can read data from the XLSX files using CL_FDT_SPOREADSHEET class. Let's start with uploading the file. Now that we have the file in xstring table, let's pass it to CL_FDT_XL_SPREADSHEET to get its object reference. From the object reference, we can retrieve each worksheet data. The data is returned in the form of an anonymous data object which can be dereferenced into a field symbol and passed to the target internal table. Below is the cod
Read more

Application Logging in ABAP

Posted by -
Image
Whether you are working with integration or a critical application or a complex report, logging becomes an obvious choice and activity.  Traditionally, Abapers have been logging information using a custom DB table defined specifically for a particular application. While useful, The approach has some flaws,      - Every application needs to have its own logging table      - Record purging/archiving needs to be set up in order to make sure old records are either deleted         or archived.      - There is no reusability of either the setup or the logic to log. With the introduction of Application Logging from SAP, the traditional approach can be left out.  In this post, I will be talking about how we can leverage the SAP application Logging Library to make logging easy. What is an application log? An application log is a rich type log. It contains information like User, Time, Expiry date of the log along with the actual message raised by the
Read more