Finding and Resolving Errors

Your SAP job returned an erroneous status? Such errors can cause the agent to work improperly or individual tasks to be executed incorrectly. Use job reports, the attributes of executable objects, the SAP system user, log files, the SAP system log, and trace functions as possible resources that help you resolving errors.

The information that your SAP job returned an erroneous status does not help you solve the error cause. You must investigate further:

Check the PLOG Agent Report

This report provides helpful information about the actions the agent has taken while being connected to the SAP system. You see also how the particular actions have ended. See Reports

Check the Attributes of Executable Objects

Perhaps the error is caused by the attributes of an executable object. Make sure that the correct client and user are defined for the particular object.

Check the SAP System User

See system users (referred to as CPIC users in older releases) https://help.sap.com/saphelp_nw73/helpdata/en/23/cbce3b1bc7fa20e10000000a114084/frameset.htm.

An SAP user (client, name, or passport) must be defined in a Login object to be able to establish a connection to the SAP system. This user must exist with the same password in all the clients of an SAP system in which tasks are executed. Make sure that the Login object and the users in the SAP system are correct.

Within your SAP system, a system user represents the agent. This user requires the appropriate rights such as operator rights for background processing. Check the rights of the SAP system user. For details, see SAP Security Objects

Use the SM37 Transaction

The SM37 transaction and its job logs and spool lists provide information about job executions. The XMI log, which you can call by using RZ15 also supplies helpful records.

Check Log Files

Agent and Server log files provide exact information about the relevant point in time when the error occurred. These file contents are provided from the Administration perspective. The initial section shows the complete INI file including the parameters, which have been specified for the agent and server. This section is followed by a chronological list of all executed actions.

Check the SAP System Log

Error situations that occur in an SAP system are logged in the SAP system log. Use the SM21 transaction to view the system log. In particular cases, the SAP system log is automatically copied to the report window. This situation might occur when the agent fails to schedule a job step. See Special Reports for SAP Jobs.

Check the Trace Files

Compared to log files, traces provide very detailed information. They contain all messages that were sent from and to agent and server, or agent and SAP system (RFC trace). Activate traces in the INI file of the agent or the Administration perspective. Trace contents are stored in files in the working directory of the agent, or an individually defined directory.

Important!

Provide trace files if you request help from our support or development teams. These files are required for a thorough analysis process.
An activated RFC trace creates files on the agent side, but also on the SAP application server computer. To reduce the memory consumption of the hard disk, activate traces only for a short period of time. Set gw/accept_remote_trace_level to 0 if no trace files should be created in the SAP system.
Set an RFC trace on the SAP Agent always together with a TCP/IP trace (at least level 5).
For further details about RFC traces, see the SAP note number 532918