Buffer
WARNING: Resetting buffers can significantly change the performance of the entire system for a long time. It should therefore only be used where there is a good reason tdso. 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
/$CUA This resets the CUA buffer of the application server
/$TAB This resets the TABLE buffers of the application server
/$NAM This resets the nametab buffer of the application server
/$DYNP This resets the screen buffer of the application server
R/3 note no. 45507
The note summarizes general rules for processing batch input sessions in the foreground.
/*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 nlonger supported.
%sc Searches character patterns in lists
%pc Downloads lists
%pri Prints lists
Processing batch input sessions in the foreground is a correction mode. The operator was consciously given more freedom here. You can, for example, branch tother functions and then jump back tthe previous screen, data can be edited, data records can be deleted from the session and son. As a result, processing of sessions in the foreground is very sensitive toperating errors. You should therefore always known exactly what you are currently doing. User errors can, in the worst case scenario, cause data loss. The following points are of special importance:
The window size of the SAPGUI should be set tthe standard size before processing the session and should not be changed when you process the session. A resize can alscause various errors when processing batch input sessions in the foreground! In the background, the batch input automatically assumes the standard size (22 lines, 84 columns).
If the session in the foreground is processed tfind the cause of a termination in the background, only the ENTER key should be pressed tget from screen tscreen. The point of termination can really only be found this way.
There are some valid OK codes with which batch input processing can be influenced (/n /bend /bdel /bda /bde; see note 26171).
These OK codes can alsbe reached via the menu (System Services Batch input).
The keys 'Cancel' F12 or 'Back' or 'Exit' F15 in batch input mean: the transaction has been processed successfully and is deleted (see note 16629). As of Release 3.0F, a dialog box appears with a query before the action is actually executed. However, the following generally applies: only cancel the batch input prematurely via the OK code/bend or via the system menu (System Services Batch input Cancel'). The session then appears under 'Incorrect sessions' in the overview.
WARNING: Resetting buffers can significantly change the performance of the entire system for a long time. It should therefore only be used where there is a good reason tdso. 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
/$CUA This resets the CUA buffer of the application server
/$TAB This resets the TABLE buffers of the application server
/$NAM This resets the nametab buffer of the application server
/$DYNP This resets the screen buffer of the application server
R/3 note no. 45507
The note summarizes general rules for processing batch input sessions in the foreground.
/*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 nlonger supported.
%sc Searches character patterns in lists
%pc Downloads lists
%pri Prints lists
Processing batch input sessions in the foreground is a correction mode. The operator was consciously given more freedom here. You can, for example, branch tother functions and then jump back tthe previous screen, data can be edited, data records can be deleted from the session and son. As a result, processing of sessions in the foreground is very sensitive toperating errors. You should therefore always known exactly what you are currently doing. User errors can, in the worst case scenario, cause data loss. The following points are of special importance:
The window size of the SAPGUI should be set tthe standard size before processing the session and should not be changed when you process the session. A resize can alscause various errors when processing batch input sessions in the foreground! In the background, the batch input automatically assumes the standard size (22 lines, 84 columns).
If the session in the foreground is processed tfind the cause of a termination in the background, only the ENTER key should be pressed tget from screen tscreen. The point of termination can really only be found this way.
There are some valid OK codes with which batch input processing can be influenced (/n /bend /bdel /bda /bde; see note 26171).
These OK codes can alsbe reached via the menu (System Services Batch input).
The keys 'Cancel' F12 or 'Back' or 'Exit' F15 in batch input mean: the transaction has been processed successfully and is deleted (see note 16629). As of Release 3.0F, a dialog box appears with a query before the action is actually executed. However, the following generally applies: only cancel the batch input prematurely via the OK code/bend or via the system menu (System Services Batch input Cancel'). The session then appears under 'Incorrect sessions' in the overview.
감사합니다