ABAP Shared Objects in Netweaver.

25 views

Skip to first unread message

Ragu Chandrashekar

unread,

May 4, 2006, 12:45:58 AM5/4/06

to Netweaver

Dear All,
Its again a yawning gap between messages. This time lets
gaze about ABAP Shared Objects. This might be more technical. Whenever
a user session is created during any transactions, objects are created
in memory. If another user is accessing the same object another copy is
created in the memory - which means accessing objects is one copy per
user per session (Session Memory).

Until before SAP Application Server 6.40 these objects cannot accessed
by other sessions or other programs. The concept of Shared Memory
enables to access this memory if the object is not locked by that
session. SAP Provides a class for accessing shared memories -
CL_ABAP_MEMORY_AREA. Static methods are available in this class for
binding a session to the memory area.

What are the Advantages of Shared Memory?

~Data is kept only once in Memory.
~The Data will be in the memory as Memory Tables that reflect the
structure of Database table.
~Fast access at Main Memory Speed.
~Saves Memory (Saves Approximately 3MB Per user per Session.