How to Find SAP Objects in Requests & Tasks

This program searches for objects in requests and tasks. You can specify the objects in the selection screen. Some object types used frequently are already listed, you only need to enter the name of the object itself (generically if you want). You can enter other object types yourself. You can restrict the requests/tasks by entering, for example, the number of the request, the owner, date changed, status, or the request type.

1. Execute transaction code SE03, select on Search for Objects in Requests/Tasks and click execute. Select any objects you want to find, put the requests/tasks list and execute again.

2. Tick the box at the left side of request and click on speck icon for details.

3. As the result, you can find the objects short description, program ID, object type and object name.

Additional note:
• Objects often consist of many sub-objects. If you also want to search for all sub-objects, select the option Also search for sub-objects. This option is normally deactivated, since the set of objects can be very large.

How to Troubleshoot Mapping Error: JCO Communication Failure

Sympton

• In transaction code SMQ2, you received "XI Error JCO_COMMUNICATION_FAILURE.MAPPING: Queue error".
• When executing the RFC test connection on AI_RUNTIME_JCOSERVER, AI_VALIDATION_JCOSERVER, LCRSAPRFC and SAPSLDAPI, you received error " ERROR: program AI_RUNTIME_SID not registered".

Cause

At first, go for the logs file. From there, you'll find the specific root cause of the error. Normal caused are,
• Connection broken between ABAP and Java
• Out of memory / overload
• SAPJSF user

Solution

• Restart the XI Java engine
• Delete & recreate the JCO RFC destinations (need to restart the Java engine)
• Check the SAPJSF user authorizations, validity and password.

How to Delete Short Dumps from the SNAP Table

There are different ways of deleting short dumps from the SNAP table. However, before you delete them, you must analyze the cause of the short dump using transaction code ST22. If the issue related to short dumps is resolved, you can proceed to remove the short dumps before they all filling up the hard disk of your system. Here are the several ways to delete the short dumps:

1. Dump analysis: Reorganization
• Go to transaction code ST22. Choose 'Reorganize'. You can now select all short dumps older than n days for deletion.
CAUTION: If a large amount of records are deleted simultaneously during the reorganization, ORACLE error ora1562 'failed to extend rollback segment …' may occur. In this case, refer to error Note 6328.

2. Drop and recreate the SNAP table
• With the database utility transaction code SE14, you can drop and recreate the SNAP table.
CAUTION: When you do this, ALL short dumps are deleted.

3. Reorganization program RSSNAPDL
• To avoid database problems, this program deletes old short dumps gradually from the SNAP table unless they are selected for retention. With standard setting all short dumps that are older than 7 days and that are not flagged are deleted. Since this program occupies the database when large datasets are processed, it should be scheduled to run overnight.

4. The SNAP is also automatically reorganized. With each short dump that occurs in the dialog box (the dump is displayed as soon as it occurs), a maximum of 20 short dumps are deleted from the SNAP that are older than 7 days. In normal production operation this reorganization should be sufficient.

How to Lock & Unlock Whole SAP System

You can lock and unlock whole SAP system using command prompt. This example is tested in UNIX and Linux environment. Please use adm user when executing the command.

• To lock the whole SAP system execute this command:

> tp locksys  pf=/usr/sap/trans/bin/TP_DOMAIN_.PFL

initial value of NLS_LANG: 'AMERICAN_AMERICA.UTF8'

This is tp version 372.05.14 (release 700, unicode enabled)

Warning: Parameter DBLIBPATH is no longer used.

tp finished with return code: 0

meaning:

Everything OK

You will received an alert  ' Upgrade Still Running : Logon Not Possible',  when you are trying to login to the system.

• To unlock the whole SAP system execute this command:

> tp UNLOCKSYS  pf=/usr/sap/trans/bin/TP_DOMAIN_.PFL

initial value of NLS_LANG: 'AMERICAN_AMERICA.UTF8'

This is tp version 372.05.14 (release 700, unicode enabled)

Warning: Parameter DBLIBPATH is no longer used.

tp finished with return code: 0

meaning:

Everything OK