Which possible entries are there in the command field (sometimes also called “OK code”)?

Solution
The design of the R/3 System is such that all programs can be called via menu options. In addition to ergonomic advantages (no need to learn transaction codes), this procedure offers higher security, as the menu path tells the user the work area to which a program belongs.

Use of the command field should be limited to exceptions. In particular, there is no guarantee that the functionality of the command field is fully supported.

Possible entries are listed below. These are only meant for experts (system administrators). Some of them (for example. “/nex”) are dangerous, because they override safety measures. “Normal” users should avoid using the command field. It is often easier to call a known transaction with “/nxxxx”, but this can be achieved just as simply via a user menu.

Direct call of transactions, session handling:
/nxxxx
This terminates the current transaction, and starts transaction “xxxx”, for example, “sa38” for reporting.
/n
This terminates the transaction. This generally corresponds to pressing F3 to go back.
/nend
This terminates all separate sessions and logs off (corresponds to “System -> Log off”).
/nex
This terminates all separate sessions and logs off immediately (without warning!).
/oxxxx
This opens a new session and starts transaction xxxx in this session.
/o
This lists existing sessions and allows deletion or opening of a new session.
/i
This terminates the current session (corresponds to “System -> End session”).
/i1, /i2,…
This terminates the session with the number given.
.xyzw
“Fast path”: “xyzw” refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).

Batch input:

The following commands can be entered in correction mode (“Process in foreground” or “Display errors only”) when processing a batch input session:

/n
This terminates the current batch input transaction and characterizes it as “Failed”.
/bdel
This deletes the current batch input transaction.
/bend
This terminates batch input processing and sets the session to “Failed”.
/bda
This switches from “Display errors only” to “Process in foreground”.
/bde
This switches from “Process in foreground” to “Display errors only”.

ABAP/4 debugging:
/h
This switches into debugging mode.
/hs
This switches into debugging mode and activates the debugging of system functions.

Buffer commands:

WARNING: Resetting buffers can significantly change the performance of the entire system for a long time. It should therefore only be used when there is a good reason to do so. As of release 3.0B system administator authorization is required (authorization object S_ADMI_FCD). The action is noted in the system log.

/$SYNC
This resets all buffers of the application server (ATTENZIONE: ESEGUIRE SOLO A UTENTI SCOLLEGATI!!)
/$CUA
This resets the CUA buffers of the application server
/$TAB
This resets the table buffers of the application server
/$NAM
This resets the nametab buffers of the application server
/$DYNP
This resets the screen buffers of the application server

Out-of-date commands:
Pxxx
From the menu system:
Starts Transaction Pxxx
If an ABAP list is displayed:
Sends command Pxxx to the list processor (for example, P+, P–, PRI)
From a transaction screen:
Sends command Pxxx to this transaction
xyyy (where x is not ‘P’, ‘/’, ‘=’ or ‘.’)
From the menu system:
Starts Transaction xyyy
Within a transaction:
Sends command xyyy to this transaction
/*xxxx
Starts Transaction xxxx and skips the first screen. So, it has the same effect as /nxxxx followed by ENTER.
=xxxx
This entry is still possible for compatibility reasons, but is no longer supported.
%sc
Searches for a string in lists (like “System -> List -> Find String”)
%pc
Downloads lists
%pri
Prints lists
?STAT
Displays the status popup (like “System -> Status…)