ABAP text field literal vs text string literal

Posted by -

Have you ever had a variable containing text? I am sure you did and regularly do. What is your preferred way to do declare it?

If you don't know or use the second option, then this post is for you. There is a minute difference in the way text literal has been defined in options one and two. 
First of all the declaration is a literal being passed to a variable, and some of you may ask:

what is a literal?

    Literals are defined in the source code of a program by specifying a string representing a value.
    Possible literals are numeric literals and character literals. The character literal comprises text 
    field literals and text string literals.

So there are two kinds of text literal, let's see them in detail.

Text Field Literals:

  - Defined using single inverted commas (').
  - Data type is c with the length of the included characters, including trailing blanks.
  - There is no empty text field literal:
     This means, The text field literal '' is identical to the text field literal ' ' of length 1.
   - The length of the text field literal( not of type c) is from 1 to 255.

Text String Literals:    

   - Defined using single backquotes (`).
   - Data type is a string.
   - The empty text string literal `` represents a string of length 0.
   - The length of the text string literal( not of type string) is from 0 to 255.
   - Trailing blanks are not ignored.

Alright, now that you know the difference, guess the output of this code.
The unexpected output is the manifestation of ABAP comparison rules of string to char or vice versa.

Armed with the new knowledge, the old example can be rewritten like this:

 In Conclusion:

   Appropriate text literal should be used when defining them to avoid superfluous type conversions. 
   The type to be used is determined by what type of variables they are going to be assigned. 
   Hope you liked the post and it helps you in your day to day work. Here is a good use example to
   sign off.

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