Homepage for SAP Professionals

Users have created a ton of batch input sessions and processed them with SM35. The users did not care about deleting unwanted sessions and there are a lot of old sessions, with almost any status (in processing/in background/processed/errors). All of them are junk (in your terms), and have to be removed from the system.

You can delete unwanted sessions with abap program RSBDCTL6  at once and then setup a background job that deletes the sessions for a specific session, user who created the session, date range, older than x days etc. that runs on a regular basis. continue reading…

Ever wondered what the error codes mean when analyzing your AIS  or trace logs? Here are some hints and how users or administrators should react to the messages:

1  Incorrect logon data (client, user name, password)
User: check the logon data entered (enter data again)
Admin: check the logon data for the service users, for example in the ITS service file
(usually wrong client) or in the RFC destinations
(usually wrong password)
continue reading…

Guess what: You have a system landscape with total 16 clients and created a fancy report variant. Now, the business folks want this variant in all systems & clients. What now?  Well, you can define the variant as global variant and transport it everywhere without having to recreate this darn variant. continue reading…

You may have come across the audit requirement to delete developers (developer keys) from your Development, Quality Assurance or Production system. Developer keys are stored in table DEVACCESS. If this table is not enabled in your system for maintenance via SM30, SE16 or SE16N transaction, you can write a small program and map it to a custom transaction, most likely with some basis authorizations so that not everyone can run it. continue reading…