Operating Tips

General SAP operating tips

Often in R/3 there will be some R/2 hangovers which are kind of useful now & then, but which aren't documented in the R/3 Help. Such as how to use a matchcode without going through the little matchcode windows or how to get out a foreground process of a batch input session quickly without going through the menu tree.

Matchcodes - Finding an account or master record number quickly - no sub windows
Batch Input Session Commands - eg: getting out of a session in a hurry!
Viewing reports online Save those trees - print only the pages you want etc
Using transaction codes and Managing sessions through the command line
Find a transaction code or program name by clicking on "system/status" when in the transaction or report parameter screen

Fast Entry of a Matchcode or Search method:

Each matchcode or search method has a code (eg: D, or A for customer matchcodes) and has a defined sequence of fields. If you regularly use a matchcode to find you customers or GL accounts, then you may want to try the R/2 method:

Enter to Account Number field	Search method or matchcode for Account Type	Example Fields in Matchcode
*=S.good..*company code to look for an account with "good" in the long text description	'S' ID for GL Accounts	Long Text Language Company Code etc
=A.searchterm	'A' in Customer Number	Search Term etc
=D.searchterm....company code		Search Term Postcode Country ?? Company Code etc

Once you know the sequence of fields for the particular search code, just enter a period '.' between field values or for each field value you want to leave out. You only need to enter the additional periods if you want to enter a value for a field that is lower down in the list. Once you get the hang of it, it is much faster than working through the little pop up windows.

Fast exit from Batch Input Session Foreground Process (no menu):

Type "/bend" (think of it as "batch end") in the command line field. This is the equivalent of 'System/Services/Batch Input/Edit/Cancel'. Your session should now be in the error list to pick up later.

"/n" in the command line will skip to the next record/transaction in a batch input session, leaving the skipped transaction to be processed later.

Using transaction codes and Managing sessions through the command line

"/nend" End all R/3 sessions and logoff
"/nxxxx" End the transaction and Call the transaction xxxx in the same session
"/o" Generate a session list
"/oxxxx" Open a new session and call the transaction xxxx
"/i" Delete the current session

Save those trees !! View your reports online:

Option 1: Execute in background and view the Spool List

Paradoxically every IT project seems to go through loads of paper. View those reports online !! You don't just have to keep it up on your screen, you can use the Spool list feature to keep your report online for a few days, or as long as the techies will let you !

Execute your report in background. This is also a good idea if it is a big report. From the execution parameter screen, menu : program / execute in background. Ensure the 'Print immediately' option is switched off.

Monitor your job ('System/Services/Job Overview', click refresh(now & then!) till finished,
Select your job,
click on 'spool list',
select the listing you want if there is more than one and
click on display icon to display online.

If you then need to print a page or 2, you can scroll up and down, determine the page numbers, when then in the print window, just print the pages you need.

Option 2: Saving the Report Data

With some types of reports, especially those that are aimed at being used online (eg: CO-PA), the equivalent option is to Save the Report data once you have brought up the report data (sometimes called 'Extract').