<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ABAP Memory in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory/m-p/3148359#M748534</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;Many a times we come across situations when we have to use field symbols to acess data in the abap memory.&lt;/P&gt;&lt;P&gt;we need to know the name of the report and the variable there in.&lt;/P&gt;&lt;P&gt;My question is how do we find out what is there in the mem and what is not.&lt;/P&gt;&lt;P&gt;one way is to type the name in the new debuggers data variable display or to try and see what all programs were called looking at the call stack.&lt;/P&gt;&lt;P&gt;in the global variables section we can only see what global variables are present.&lt;/P&gt;&lt;P&gt;is there a convinient and comprehensive way to know what all valid data is accessible via the ABAP memory.&lt;/P&gt;&lt;P&gt;Please keep your answers precise.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 09 Dec 2007 06:04:21 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-09T06:04:21Z</dc:date>
    <item>
      <title>ABAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory/m-p/3148359#M748534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;Many a times we come across situations when we have to use field symbols to acess data in the abap memory.&lt;/P&gt;&lt;P&gt;we need to know the name of the report and the variable there in.&lt;/P&gt;&lt;P&gt;My question is how do we find out what is there in the mem and what is not.&lt;/P&gt;&lt;P&gt;one way is to type the name in the new debuggers data variable display or to try and see what all programs were called looking at the call stack.&lt;/P&gt;&lt;P&gt;in the global variables section we can only see what global variables are present.&lt;/P&gt;&lt;P&gt;is there a convinient and comprehensive way to know what all valid data is accessible via the ABAP memory.&lt;/P&gt;&lt;P&gt;Please keep your answers precise.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Dec 2007 06:04:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory/m-p/3148359#M748534</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-09T06:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory/m-p/3148360#M748535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi anup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there is no convinient and comprehensive way to know what all valid data is accessible via the ABAP memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It depends very much on the routine being processed at a distinct moment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The approach to look at the call stack (in new or old debugger, I prefer the old one because it's faster and has the same information) is the best I know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that the value of local fields of routines not  in the call stack is never available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a function to acces the call stack at run time. I think callstack is part of the name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Dec 2007 13:11:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory/m-p/3148360#M748535</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-12-09T13:11:09Z</dc:date>
    </item>
  </channel>
</rss>

