SAP R/3 Troubleshooting

• System gets stuck

It happens mostly when archive area is overloaded. Run the program brarchive with deletion option to release disk space.

• Short dump

Not always the problem is technical. Try to create all SAPoffice users through transaction SO32 (create all SAPoffice users) and review your application data carefully.

• Field exits are completely ignored

Make sure your SAP profile parameter contains the option abap/fieldexit = yes.

• Transaction SE16 (table contents) does not work properly

Make usage of the menu option to regenerate the display program. You can also try changing key words according to field names. Choose Option -> Parameters users.

• Rollback segments are too small

Before increasing up the rollback segment size you should verify your programs. Very often the problem belongs to them.

• Files for rollback segments are already enormous

Check the rollback segments configuration. It has to match the allocated area on tablespaces. Changes have to be done using Oracle tools.

• Extended help under windows does not link correctly

Check the file sapdoccd.ini under your presentation server. It must be present in the main windows directory and should assign to help files directory.

• Release procedure with classification does not work

As a matter of fact you are not the only one to notice it. It hardly works. Before using release strategy you should apply all notes on OSS. Pray might be useful too.

• Transport area is overloaded

The command tp clearold «SysID» cleans up the transport area according to parameters previously set on the plain file TPPARAM.

• Instance does not establish communication

Shutdown the whole system and check the Interprocess Communication Facilities. Any references should be found. Either the command IPCS (UNIX) or showipc «INSTANCE NUMBER» (SAP) show all message queue, semaphore set and shared memory identifier. Before trying again you have to remove them using the command IPCRM (UNIX) or cleanipc «INSTANCE NUMBER» (SAP).