a) activating the table
<sid>ko<no>-for client indipendant objects(cross client)
<sid>kt<no>-for client specific objects
<sid>kx<no>-for client specific texts
in Ecc6, Please set the profile parameter:login/no_automatic_user_sapstar=0,then restart the sap system and logon with password 'pass'.
in the SUIM t-code we have option called Change document,
use this option or you can use use trace in ST01 to trace
check point is a process of db which runs for every 60
sec... when ever check point occurs all the processes of db
like log writer, db writer, smon, pmon will get
in tms return code 247 is related to buffers i think so...
any body plz correct dis if it is wrong
Go to se11 T-Code..from there go to the table agr_agrs. You will be asked to provide the Access key ..then enter the object that needs to be added to 100 roles...then Select the range of roles in which the objects needs to be added and then save or Activate whatever option is given.
garbage collector automatically frees the variables and objects from the memory when they are not in use. user program can't directly free the object from memory instead it is the job of garbage collector to automatically free the objects which are no longer referenced by the program.every class inherits finalize() from java.lang.Object finalize() is called by garbage collector when it determines no more reference to object exist.
development and production!!
There are mainly 4 types of RFC communication in SAP. They are
Synchronous RFC (sRFC) : In this type of RFC communication,
the calling program waits until the requested processing
step on the remote system has ended and then continues to
In other words, both the systems involved must be available
at the time the call is made.
Asynchronous RFC (aRFC) : In this type of RFC communication,
the calling program gives the request to the remote system
and immediately continues to work locally. The requested
processing step is executed on the remote system in isolation.
If the remote system cannot be reached at the time of the
call, the asynchronous calls of the RFC client are lost
Transactional RFC (tRFC) : This type of RFC communication is
similar to asynchronous RFC but by allocating a transaction
id(TID) it guarantees that if a request is sent several
times because of network problems it is processed only
once. Unlike asynchronous RFC, in Transactional RFC the
remote system does not have to be available at the moment
the RFC client program start the call. The data is held in
the source system until the target system is available.
The report program RSARFCSE is called in the background at
regular intervals and tries to place the unsuccessful
requests, identified by their transaction id again.
Queued RFC (qRFC) : This RFC communication is an extension
to the transactional RFC. In this method, all the requests
are queued up(inbound queue and outbound queue) and are
processed in a sequence only if it is certain that all
preceding calls are processed correctly. This method
guarantees that all the requests are processed in the
sequence in which they are received.
This type of RFCs will be used in SCM (APO) systems for CIF
queues etc where requests have to be processed in an order.