R3_GET_APPLICATIONLOG

Use the R3_GET_APPLICATIONLOG script element to retrieve messages from the application log (transaction SLG1) and have them written to a report or file. You can select messages according to particular application log criteria. Located messages are regularly written to the AE report. You can also write them to a file that you can define in the FILE= parameter.

This script element enables access to the SAP Banking Accounts Management application log. Messages from processes and process networks that were started by a script can so be analyzed in your AE system. For more information, see BCA_ACTIVATE_PROCESS.

Notes:

  • Use precise selection criteria in the script element parameters so that the number of application log messages can be handled.
  • By default, the generated files are stored on the computer on which the agent is installed. Example: R3_GET_JOB_SPOOL; FILE=

Transaction: SLG1
Interface: AE

Syntax

R3_GET_APPLICATIONLOG

    [OBJECT=...]
    [,SUBOBJECT=...]
    [,FROM_DATE=...]
    [,FROM_TIME=...]
    [,TO_DATE=...]
    [,TO_TIME=...]
    [,USER=...]
    [,TAC=...]
    [,PROGRAM=...]
    [,MESSAGE_CLASS=...]
    [,FILE=...]
    [...]
    [,LOG_CREATION=...]

Parameters

  • R3_GET_APPLICATIONLOG
    Retrieves messages from the application log (transaction SLG1)

  • OBJ[ECT]=
    (Optional) Object name (application code)
    Format: script literal
    Default value: *
    You can use the asterisk (*) character as a wildcard for any characters.

  • SUB[OBJECT]=
    (Optional) Name of a sub-object of an object
    Format: script literal
    Default value: *
    You can use the asterisk (*) character as a wildcard for any characters.

  • FROM_D[ATE]=
    (Optional) Start date for message selection in the format YYYYMMDD
    Format: script literal
    Default value: 20010101

  • FROM_T[IME]=
    (Optional) Start time for message selection in the format HHMMSS
    Format: script literal
    Default value: 000000

  • TO_D[ATE]=
    (Optional) Completion date for message selection in the format YYYYMMDD
    Format: script literal
    Default value: current date

  • TO_T[IME]=
    (Optional) Completion time for message selection in the format HHMMSS
    Format: script literal
    Default value: 235959

  • USER=
    (Optional) Name of the user who has triggered a logged event
    Format: script literal
    Default value: *
    You can use the asterisk (*) character as a wildcard for any characters.

  • TAC=
    (Optional) Name of the transaction that was used to activate a logged event
    Format: script literal
    Default value: *
    You can use the asterisk (*) character as a wildcard for any characters.

  • PROGRAM=
    (Optional) Name of the program that has activated a logged event
    Format: script literal
    Default value: *
    You can use the asterisk (*) character as a wildcard for any characters.

  • MESSAGE_CL[ASS]=
    (Optional) Indicator that a message belongs to a problem class. Message indicators are values between 1 (very important) and 4 (additional information).
    Format: script literal
    Default value: 4

  • FILE=
    (Optional) Name of the file in which the result, the found messages, should be stored. If you use this parameter, the selection result is not written to the report.
    Format: script literal

  • EXTNUMBER=
    (Optional) External identification number of the application log that is allocated by the application program
    Format: script literal

  • LOG_C[REATION]=
    (Optional) Operation mode in which the application log was created
    Format: script literal
    Allowed values:

    • "" (default)
      Any

    • B
      Batch

    • D
      Dialog

    • I
      Batch input

  • ENCODING=

    (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.

See also:

seealso

About SAP JCL