Automation Engine Script Guide > AE JCL for Applications > SAP > R3_GET_APPLICATIONLOG

R3_GET_APPLICATIONLOG

Retrieves messages from the applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. log (transaction SLG1) and writes them to a report or 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=...]
[,EXTNUMBER=...]
[,LOG_CREATION=...]

Syntax

Description/Format

OBJ[ECT]=

Object name (application code).
Format: script literal

Default value: "*"

You can use the "*" wildcard for any characters.

SUB[OBJECT]=

Name of an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task's sub-object.
Format: scriptA particular Automation Engine object type. literal

Default value: "*"

You can use the "*" wildcard for any characters.

FROM_D[ATE]=

Start date for message selection in the format "YYYYMMDD".
Format: script literal

Default value: "20010101"

FROM_T[IME]=

Start time for message selection in the format "HHMMSS".
Format: script literal

Default value: "000000"

TO_D[ATE]=

Completion date for message selection in the format "YYYYMMDD".
Format: script literal

Default value: current date

TO_T[IME]=

Completion time for message selection in the format "HHMMSS".
Format: script literal

Default value: "235959"

USER=

Name of the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. who has triggered a logged eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase..
Format: script literal

Default value: "*"

You can use the "*" wildcard for any characters.

TAC=

Name of the transaction that has been used to activate a logged event.
Format: script literal

Default value: "*"

You can use the "*" wildcard for any characters..

PROGRAM=

Name of the program that has activated a logged event.
Format: script literal

Default value: "*"

You can use the "*" wildcard for any characters.

MESSAGE_CL[ASS]=

Indicator that a message belongs to a problem class.
Format: script literal

Default value: "4"

Message indicators are values between "1" (very important) and "4" (additional information).

FILE=

Name of the file in which the result (found messages) should be stored.
Format: script literal

The selection result is not written to the reportA report provides more detailed information about a task's execution or a component. if this parameter is used.

EXTNUMBER=

Application log's external identification number which has been allocated by the application program.
Format: script literal

LOG_C[REATION]=

Operation mode in which the application log has been created.
Format: script literal

Allowed values: "" (default value), "B", "D" and "I"

"" - Any
"B" - Batch
"D" - Dialog
"I" - Batch input

ENCODING=

Encoding for the generated output file (Parameter FILE=).

For example: UTF-8

Default value: ISO-8859-1

When you specify an encoding that is not supported or invalid, the jobAn Automation Engine object type for a process that runs on a target system. will abort with an error message.

The SAP Forms provide an input assistant for this field which lists all the supported encodings.

Comments

This script element can be used to select messages according to particular application log criteria. Located messages are regularly written to the AE report. Alternately, you can also write them to a file that has been defined by using the parameter FILE=.

For example, this script element enables access to the SAP Banking Accounts Managements application log. Messages from processes and process networks that were started with BCA_ACTIVATE_PROCESS can so be analyzed in AE.

Automic recommends using script-element parameters in a way that the number of application-log messages can be handled. You can do so by using precise selection criteria.

By default, the generated files are stored on the computer on which the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host is installed  (for example, R3_GET_JOB_SPOOL; FILE=).

 

See also:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH