Empty SAP Reports sent when no Joblog exists on SAP

Document ID : KB000084710
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

The Automation Engine (AE) sends empty Reports in cases where no Joblog exists on the SAP side.
 
Environment:
OS Version: N/A
Cause:
Cause type:
By design
Root Cause: Behavior was introduced with Output Handling feature, where a directory tab for the reports was introduced. The directory is available before the job has ended hence during creation of the directory the system does't know if it will stay empty.
Resolution:
The behavior was introduced with the Output Handling feature, where a directory tab for the reports was introduced. The directory is available before the job has ended. Therefore, during the creation of the directory the system doesn't know if it will remain empty.
 
The behavior will not be changed, as sending empty attachments is something that some may want to do intentionally.  For example, sending a file that shows up in the report directory (which can be empty) but would be of interest to the receiver.  An empty report is a report although it is empty.  Changing this behavior could also affect the following:
  1. Existing scripts using prep_process_report
  2. Output scans
The Agent log indicates why the report is empty and the Agent log is attached as well.

An enhancement to the product that would make this option configurable would require the submission of a product enhancement.  


Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
Use the Agent Log (also attachable) to determine the real cause for the empty Report.
An empty report shows that something went wrong on SAP side.