Here is the questions for series -2. From this series let us concentrate on one topic so that we can have a better understanding of that subject, from this week we will have separate questions on lock management.

1. What are the transport tables and what are they used for?

2. Can update records be deleted? What are the precautions that need to be taken?

3. How many profile files will be there for the below scenario and please name them.

4. In which parameter can you set the default client that needs to be present when u open a system through SAP GUI?

5. Which transaction is used to change time zone?

Questions on lock management

1. How many types of locks are there? Please explain briefly?

You can use tcodes 0s07, rz03, rz10, Smlg

2. You have configured a application (Basically a ABAP program) where a mail will be sent to some person. But the Queue does not move out automatically, u have to sent it manually. What might be the problem and what services you need to check?

SAPCONNECT is running, else schedule to run report RSCONN01 like every 5 mins

SCOT –> click on Job icon ( Shift + <F7> ) , if you see a job there check the Period , it

will show how often this job is executed. If you don’t see any job there click on create

button to there to Schedule the job. Other way of checking is SM37 –> enter RSCONN01

against ABAP program name , user * , jobname * ; if scheduled it will show the job

3. How to delete SAP*, list command? Any precaution needs to be done?

* Delete from usr02 where bname = ‘SAP*’ and mandt = ‘***’;  

* Can delete from SU01

If you delete the userid, SAP*, from the database, SAP has this userid defined in its kernel (the SAP executable code that sits at

the operating system level, i.e., disp+work).So it will allow to login again with sap* after system restart. And it will have the following properties

The user is not subject to authorization checks and therefore has all authorizations.

The user has the password “PASS”, which cannot be changed

To avoid this the parameter login/no_automatic_user_sapstar should be set to a value greater than zero in default profile.

http://help.sap.com/saphelp_nw2004s/helpdata/en/52/671792439b11d1896f0000e8322d00/content.htm

or

delete from <SID>.USR02 where BNAME=’SAP*’ and MANDT=’<client>’.

Ensure all the charecters in USR are capital and <SID>= SID of your system

After doing this you can login to corresponding client with user sap* and default password

“pass”

When you delete the user SAP*, please make sure you also add the parameter

login/no_automatic_user_sapstar = 0 to instance profile (your need to restart the SAP

insttance)

As NW2004S, that parameter prevent SAP* login using PASS password.

But before you do this, please just try to delete the SAP* user first and login using PASS

password, if that not work than you should add the parameter and restart the SAP.

4. Explain Lock concepts? Briefly?

Lock concept is detailed, in short..dialog work process processes the user request and triggers the enqueue work process which locks that record against that user id. The lock table resides in the main memory. To release lock either go to sm12 or end user session via sm04.

It works in First In First Out manner when it comes to unlocking an Object.

When it happens automatically system will not log it but when you manullay unlock it using SM12 it will log.

5. How many minimum dialog work process an instance must have and why?

• Dialog work processes handle screen changes and interaction with the SAP graphical user interface (through the dispatcher). By default, two dialog work processes are assigned to each instance; the maximum number of dialog work processes is 99 per instance.

• The number of other work process types can only be increased if there are more than two dialog processes. Number of DIA processes must be larger than or equal to the total number of update processes and background processes.

• When a tcode is executed, it is carried out in a number of dialog steps in parallel in order to enable this we must have minimum of 2 dialog processes.

• if the tRFC is called from the update or the background processing, it needs a free dialog work process.

One place where I get to meet people is the cab in which I travel to office in the morning and evening. After a tiring day of work, it feels very relaxed to travel by this cab. The people traveling despite their age differences are very friendly with one another; they keep teasing each other and pulling each others legs.

If a person starts traveling new in this cab they are sure to name that person, myself and my friend were named London friendsJ, there is a person called senior citizen, one called Mr. Brain (not because he is intelligent, because no one can ask silly questions as he does, his intelligence as a matter of fact overflows).

Every now and then these people give treats to one another, for no reason at all there will be a treat in which one has to sponsor the treat. They just stop the cab by a near by baker and poor one whoever is sponsoring the treat for the day, he is the scrape goat of the day:(

The silly jokes, the teasing, the jut-pat treats everything make this cab journey a very interesting one.

One such lovely moment happened to me recently, my best friend has given birth to a boy baby and I went to see him… What a lovely child, hours flew by just sitting beside him and watch him smile…. I thought how lucky my friend was, she is a mom now, one of my other friends who had come with me told her, the greatest achievement that she has done is become a mother…how true it is

After coming home, I remembered the poem I had written many years back of how the child would feel when he first opens his eyes…. Something really special about this poem is that, it was first read and named by the most special person in my life…. By the way forgot to tell you the name of the poem, it is called “Ode to Love”… Here are the lines of that poem for you….

A bright star twinkled,

as I opened my lids.

Strange was the world

as it ever would be

What is that I heard,

exotic noises they seemed – A

Droning reverberating around

Terrifying appeared this planet

I clasped my hands – as

A gush of fear rolled

Helpless I felt – as

My eyes roved everywhere

And my heart pounded

Security did it seek

Darkness seemed to fall upon

Tears rolled down my cheeks

As I screamed for peace

Then in a blink of eye

Lovable hands held me,

An instant fears flew – and

Eden it was – in hands

Of that beautiful angel.

 SAP_REORG_UPDATERECORDS: The standard job SAP_REORG_UPDATERECORDS that was contained in some delivered versions must no longer be executed. In its new version, the underlying ABAP Program RSM13002 is programmed so that it terminates when running in a job (that is, in the background). Therefore, the job SAP_REORG_UPDATERECORDS always terminates in this case. In any case, the job SAP_REORG_UPDATERECORDS should be deleted from the pool of standard jobs, if it is still there. In addition, released jobs that may exist and contain report RSM13002 should be deleted. (Refer Note 67014 for details)         SAP_WP_CACHE_RELOAD_FULL: 

 The job SAP_WP_CACHE_RELOAD_FULL is normally used to update data from the workplace component system to the workplace server. This job can only be run on a workplace server, otherwise it will terminate. In the future, this job will no longer be delivered as a standard job.If this job has been scheduled for your system, but you do not need it, delete the scheduled job in transaction sm37.

To avoid this error, we need to register the program ABCD on the gateway. The server program is responsible for its registration on the gateway.

To register the program login into the OS level as sudo su – <sid>adm and execute the following command.

 rfcexec –g<program id> -a<gateway host name> -x<gateway service>

rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW.

The connection will fail once this command is terminated or the user executing this command logs off

To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini

To do this, execute the following command 

sudo su – <sid>adm

 rfcexec –D<destination name>

<destination name> is the RFC destination name in SM59

Eg: rfcexec –DXYZ

 Where XYZ is the name of the RFC destination in SM59

To check if the program is registered,

 In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered) 

 Something that is really fascinating about my work is that each day it is a new and learning experience…. I strongly believe that knowledge grows when you share, so why not share what I learn, the problems I solved and things like that… Come Learn SAP, in particular Basis with me…..