R3_GET_APPLICATIONLOG
Use the R3_GET_APPLICATIONLOG script element to retrieve messages from the application log (transaction SLG1) and write them to a report or file. You can filter messages using application log criteria. By default, located messages are written to the AE report. You can also write them to a file defined in the FILE= parameter.
This script element enables access to the SAP Banking Accounts Management application log, allowing messages from processes and process networks started by a script to be analyzed in your AE system. For more information, see BCA_ACTIVATE_PROCESS.
Transaction: SLG1
Interface: AE
Syntax
R3_GET_APPLICATIONLOG [OBJ[ECT]=...][,SUB[OBJECT]=...][,FROM_D[ATE]=...][,FROM_T[IME]=...][,TO_D[ATE]=...][,TO_T[IME]=...][,USER=...][,TAC=...][,PROGRAM=...][,MESSAGE_CL[ASS]=...][,FILE=...][,EXTNUMBER=...][,LOG_C[REATION]=...][,ENCODING=...]
Important Considerations
-
Use precise selection criteria in the script element parameters to keep the number of application log messages manageable.
-
By default, generated files are stored on the computer on which the agent is installed.
Parameters
| Parameter | Description | Format | Allowed Values | Default Value |
|---|---|---|---|---|
| OBJ[ECT]=
(Optional) |
Object name (application code). You can use the asterisk (*) as a wildcard. | Script literal | n.a. | * |
| SUB[OBJECT]=
(Optional) |
Name of a sub-object. You can use the asterisk (*) as a wildcard. | Script literal | n.a. | * |
| FROM_D[ATE]=
(Optional) |
Start date for message selection. | Script literal | n.a. | 20010101 |
| FROM_T[IME]=
(Optional) |
Start time for message selection. | Script literal | n.a. | 000000 |
| TO_D[ATE]=
(Optional) |
End date for message selection. | Script literal | n.a. | Current date |
| TO_T[IME]=
(Optional) |
End time for message selection. | Script literal | n.a. | 235959 |
| USER=
(Optional) |
Name of the user who triggered a logged event. You can use the asterisk (*) as a wildcard. | Script literal | n.a. | * |
| TAC=
(Optional) |
Name of the transaction used to activate a logged event. You can use the asterisk (*) as a wildcard. | Script literal | n.a. | * |
| PROGRAM=
(Optional) |
Name of the program that activated a logged event. You can use the asterisk (*) as a wildcard. | Script literal | n.a. | * |
| MESSAGE_CL[ASS]=
(Optional) |
Problem class indicator for a message. Values range from 1 (very important) to 4 (additional information). | Script literal | n.a. | 4 |
| FILE=
(Optional) |
Name of the file in which to store the found messages. When specified, the selection result is not written to the report. | Script literal | n.a. | n.a. |
| EXTNUMBER=
(Optional) |
External identification number of the application log, as assigned by the application program. | Script literal | n.a. | n.a. |
| LOG_C[REATION]=
(Optional) |
Operation mode in which the application log was created. | Script literal |
|
"" |
| ENCODING=
(Optional) |
(Optional) Encoding that should be used for the generated output file (FILE= parameter). Example: UTF-8 Default value: ISO-8859-1 When you specify an encoding format that is not supported or invalid, the job aborts with an error message. The SAP Forms provide an input assistant for this field which lists all the supported encoding formats. |
n.a. | n.a. | n.a. |
See also: