Inline Decleration (Değişken Tanımlama)

-

Note : If you want to use instant variable declaration in ABAP, you can do so using the new syntax supported in version 7.40 and above.


When declaring a global variable, we use the prefix "gv_" (global variable) to indicate its scope. On the other hand, when declaring a local variable using inline declaration, we use the prefix "lv_" (local variable). This is done to differentiate between global and local variables and to indicate their respective scopes. By using the prefix "gv_", it becomes clear that the variable is intended to have a global scope and can be accessed across different parts of the program or system. On the other hand, by using the prefix "lv_", it signifies that the variable is intended to have a local scope and is limited to the specific block or routine where it is declared. The prefixes "gv_" and "lv_" are naming conventions commonly followed in ABAP programming to enhance code readability and maintainability. They help developers quickly identify the scope of variables and understand how they can be accessed within the program. It's important to note that these prefixes are not enforced by the ABAP language itself but are recommended practices followed by developers to adhere to coding standards.



Yorumlar

Yorum Gönder

Bu blogdaki popüler yayınlar

Transaction Code assignment for Query created in SQVI - SQVI Raporu Tcode Bağlanması

-
Resim
 What is SQVI SQVI is a basic query tool in SAP that enables you to choose a data source, define selection criteria, and layout for ad-hoc reports. The report can be run, with the option to export it or analyze the results on-screen. How to assignment SQVI to a Tcode Firstly, an SQVI report created in the development system is not a report that gets transported to the Production system; it can be created in each system separately. Therefore, you need to perform the process according to the respective system. To link an SQVI report created in the Production system to a tcode, you need to create a tcode in the Production system. If you don't have the authorization to do this in the Production system, you can use a second method: create a new tcode in the development system and transport it to the Production system. However, you will then need to fix the development and test systems again, otherwise, you will encounter dumps when executing the tcodes. Auth Err.  
Read more »