Escolar Documentos
Profissional Documentos
Cultura Documentos
asfan.amin@gmail.com
User
Context
Reered
:
Data
which
is
generated
by
transacJon
process
Variables,
Internal
table
&
screen
list
New
sesion
=
new
user
context
Data
is
stored
independently
in
dierent
memory
areas
Stored
in
SAP
roll
memory,
SAP
extended
memory,
&
SAP
Heap
Memory
Sesions
divide
into
:
q External
sesion
opened
explicitly
by
user
q Internal
sesion
opened
implicitly
by
program
submit,
call
transac.on,
call
dialog,
call
screen,
call
func.on
in
update
task,
call
func.on
in
background
task,
and
call
func.on
star.ng
new
task
asfan.amin@gmail.com
Process
Flow
Pres.
server
SAP
ApplicaJon
Sever
DB
Server
SAP GUI
Database buer
Dispatcher Queue
dispatcher
asfan.amin@gmail.com
Roll
in
copying
user
context
from
shared
roll
area
to
local
roll
area
Roll
Out
copying
user
context
from
local
roll
area
to
shared
roll
area
asfan.amin@gmail.com
Work Process1
ztta/roll_first
Roll Buffer (shared) Roll (local) Roll In / Roll Out Roll file
rdisp/roll_SHM
ztta/roll_area
rdisp/roll_MAXFS
asfan.amin@gmail.com
asfan.amin@gmail.com
Shared memory which mostly of user context stored All SAP work process can edit stored user context directly Roll in rather only copied the address (pointer) of where a user context located on the SAP extended memory Makes roll process much faster
em/initial_size_MB
ztta/roll_extension
asfan.amin@gmail.com
asfan.amin@gmail.com
Area which allocated variably as local memory as required. Released ager a transacJon is complete.
asfan.amin@gmail.com
abap/heap_area_(non)dia abap/heap_area_total
asfan.amin@gmail.com
User Context
Roll memory to
zttz/roll_extension
- Data stays in work process - No context switch possible - Work process in private mode
asfan.amin@gmail.com
User Context
Roll memory to
abap/heap_area_dia
Mapping the data during context change - Data stays in work process - No context switch possible - Work process in private mode
asfan.amin@gmail.com
asfan.amin@gmail.com
SAP
Paging
Memory
Main
Parameters
:
o rdisp/PG_MAXFS
size
of
SAP
Paging
Memory
o rdisp/PG_SHM
size
of
SAP
Paging
Buer
(shared
memory)
Error
caused
by
SAP
Paging
Memory
:
u TSV_TNEW_PG_CREATE_FAILED
u SYSTEM_NO_MORE_PAGING
asfan.amin@gmail.com
Parameter transferred when programs and transacJon called SUBMIT REPORT, CALL TRANSACTION, CALL DIALOG, CALL SCREEN, CALL FUNCTION IN UPDATE TASK, CALL FUNCTION BACKGROUND TASK, CALL FUNCTION STARTING NEW TASK Data extracts created by statement EXTRACT (up to basis 4.5)
Local memory
Additional local heap memory (if required)
Local memory
Local memory
Local memory
1:n
SAP Roll File SAP Paging File
asfan.amin@gmail.com
1:1
Work Process Work Process Work Process
asfan.amin@gmail.com
Zero
administraJon
memory
magement
:
PHYS_MEMSIZE
parameter
denes
how
much
of
a
computers
total
physical
memory
should
be
used
for
the
SAP
instance.
asfan.amin@gmail.com
Address Space
SAP Work Process
asfan.amin@gmail.com
em/address_space_MB User Independent WP Local SAP Buffers (Shared) Roll Memory (Shared) User Context SAP Extended Memory (Shared)
abap/heap_area_(non_)dia
Address Space
SAP Work Process
asfan.amin@gmail.com
The memory of user context is used up STORAGE_PARAMETERS_WRONG_SET, SYSTEM_ROLL_IN_ERROR, TSV_TNEW_BLOCKS_NO_ROLL_MEMORY, TSV_TNEW_PAGE_PAGE_ALLOC_FAILED, TSV_TNEW_INDEX_NO_ROLL_MEMORY System can not create the program buer because there is not not sucient shared memory at that Jme PXA_NO_SHARED_MEMORY The Program encounters a memory boIleneck during an operaJon in the database interface DBIF_RTAB_NO_MEMORY, DBIF_RSQL_NO_MEMORY The Program encounters a memory boIleneck during sorJng. EXSORT_NOT_ENOUGH_MEMORY AIemp to create error log fails ager a terminated program due to lack of memory. RABAX_CALLING_RABAX The SAP paging memory is used up SYSTEM_NO_MORE_PAGING, TSV_TNEW_PAGE_ALLOC_FAILED The memory for SET/GET parameter (SPA/GPA memory) is used up. SET_PARAMETER_MEMORY_OVERFLOW Volume limit of memoy allocated to single call (zIa/max_memreq_MB) is set too low SYSTEM_NO_ROLL
asfan.amin@gmail.com
asfan.amin@gmail.com