SAP form does not allow dashes in the Job Name

Document ID : KB000084762
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U02000009 Job '' with RunID 'xxxxxxx' ended with return code '115'.

A SAP job fails with a return code 115 when the Forms tab contains a dash (-) in the Job Name.

Investigation

1. Create a SAP import job.
2. In the Forms tab, select a Job Name that has a dash (-) in it.
3. Save and Execute the job.

Expected 
SAP job from SAP application gets imported into AE.

Actual
SAP job fails because it cannot interpret what a dash is in the job name so it converts it into a square box character (this is what you see in the UI) or a question mark (this is what you see in the PLOG).

 

Cause:
Cause type:
By design
Root Cause: This is a limitation not a bug. The Automation Engine (AE) can only store characters, which are defined in the character set being used within the AE database.
Resolution:
N/A

Fix Status: No Fix

Additional Information:
Workaround :
Avoid using dashes in the Job Name of the SAP job's Forms tab. SOLUTION As SAP Systems usually run in multi byte character mode (Unicode) and Automic does not support this. The SAP Agent must convert the Data from SAP (in this case the JobName) into the XML Encoding being used in the rich Java client or Automic Web Interface (AWI) for characters, which cannot be converted (i.e. a ? or a square box character). This conversion is a one-way conversion (cannot be converted back), which explains why the job fails at runtime. The solution is to use only those characters in SAP Job Names that can be converted into Automic Character Set.