This blog contains experience gained over the years of implementing (and de-implementing) large scale IT applications/software.

SAP Command Field Codes

Extracted from SAP Note 26171 – “Possible entry values for command field (“OK-code”)”

Calling transactions & Session Handling:

    This terminates the current transaction, and call transaction “xxxx”, for example, “sa38” for reporting.

    This terminates the transaction. This generally corresponds to going back with F15.

    This terminates all separate sessions and logs off (corresponds to “System -> Log off”).

    This terminates all separate sessions and logs off immediately (without any warning).

    This opens a new session and starts transaction xxxx in this session.

    This lists existing sessions and allows deletion or opening of a new session.

    This terminates the current session (corresponds to “System -> End session”).

/i1 , /i2 ,…
    This terminates the session with the specified number.

    “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)

Background Input:

    This terminates the current background input transaction and characterizes it as “Failed”.

    This deletes the current background input transaction.

    This terminates background input processing and sets the session to “Failed”.

    This switches from “Display errors only” to “Process in foreground”.

    This switches from “Process in foreground” to “Display errors only”.

ABAP/4 debugging:

    This switches into debugging mode.

    This switches into debugging mode and activates the debugging of system functions.

Buffer commands:

    This resets all buffers of the application server.

    This resets the CUA buffers of the application server.

    This resets the table buffers of the application server.

    This resets the nametab buffers of the application server.

    This resets the screen buffers of the application server.

Out-of-date commands:

    From the menu system:
Calls transaction Pxxx.

If an ABAP list is displayed:
Send command Pxxx to the list processor (for example, P+, P–, PRI, and so on)
From a transaction screen:
Send command Pxxx to this transaction

xyyy (where x is not ‘P’, ‘/’, ‘=’ or ‘.’) )
    From the menu system:

Calls transaction xyyy
Within a transaction:
Send command xyyy to this transaction

   Calls transaction xxxx and branches to the next screen. So, it has the same effect as /nxxxx followed by ENTER.

   This entry is still possible for compatibility reasons, but is no longer supported.

    Searches for a string in lists (like “System -> List -> Find String”)

    Downloads lists

    Prints lists

    Displays the status dialog (such as “System -> Status…) )

HowTo: Find the Transaction Codes used in SPRO

It’s not easy trying to grant specific access to customising transactions when you;re not sure which ones will be required.

If you know they are accessible from SPRO, then you can find them using the following query, which lists TCODES from SPRO customising that has been performed after installation (note the date of 2001):

SELECT distinct cobj.tcode
FROM cus_actobj cobj,
cus_acth cacth
WHERE cobj.act_id = cacth.act_id
AND cacth.fdatetime > '20019999999999'