SAP Function CACS_PROGINDICATOR_SHOWS - Generalized SAPGUI_PROGRESS_INDICATOR

Parameter Reference Type Length Default Optional Text
MESSAGECLASS 0 SPACE X Message Class (In case TEXT initial)
MESSAGENUMBER 0 000 X Message (In case TEXT initial)
MESSAGEPAR1 0 SPACE X Parameter 1 for Message (In case TEXT initial)
MESSAGEPAR2 0 SPACE X Parameter 2 for Message (In case TEXT initial)
MESSAGEPAR3 0 SPACE X Parameter 3 for Message (In case TEXT initial)
MESSAGEPAR4 0 SPACE X Parameter 4 for Message (In case TEXT initial)
PERCENTAGE 0 0 X Size of Bar ( 0 <= PERCENTAGE <= 100 )
TEXT 0 SPACE X Text to be Displayed
TIMECONDITION 0 0 X Minimum Seconds Between Two Calls
XBATCH BOOLEAN_FLG C 1 'X' X Display in Batch? (=> Job Log)
XDIALOG BOOLEAN_FLG C 1 'X' X Display in Dialog? (=> PROGRES_INDICATOR)
XNEWMESSAGE BOOLEAN_FLG C 1 SPACE X Display Only New Messages?

Functionality
Generalized SAPGUI_PROGRESS_INDICATOR

Example
Functions like SAPGUI_PROGRESS_INDICATOR. Nevertheless, the messageinterface can also be used as an alternative to the TEXT parameter.
Contrary to SAPGUI_PROGRESS_INDICATOR, this function module candifferentiate between dialog and batch run. In the batch run, the me
ssages are output as S-message and they appear in a batch log as soon asthe next COMMIT WORK is sent. The batch log can thus be used fordetailed status tracking or processing level of a batch run, similar tothe dialog mode.

Notes
A minimum waiting time between two calls can be defined by usingTIMECONDITION in order to avoid a large flow of messages in the log orto limit the communication with the front end. Other calls within thistime lead to the suppression of output. The time to the last call isalways measured, independent of its "damaliger" TIMECONDITION.
The messages appear in the batch processing only after the next COMMITWORK in batch log. That is why it is recommended to use this module atcorresponding COMMIT times.