Incorrect parsing of language parameters for SAP Jobs in AE v10.0.8 HF1 and HF2

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

After updating the Automation Engine (AE) from version 8 to version 10, the settings of SAP R3 jobs may show the following inconsistency regarding the job language definition:
 
0EMb0000001Uk9V.png

Instead of displaying the language in the conventional two letters format (DE for German) the expression 'Chinese traditional is displayed. Actually, Chinese is the last entry in the language list.

If the Job is updated without setting the correct language setting again the Job will abort.

In older versions (<= version 8) this parameter could be defined with one character, for example 'D' for German. For instance:

8='400'A='D'E='0'

This could be verified using the following query on the JBA table by analyzing the JBA_REST field contained in the job:
 
select JBA_REST, oh.oh_name from JBA, OH where JBA_OH_Idnr in (select oh_idnr from oh where oh_name like '%' and oh_otype='JOBS');

The following output is produced by this error (indicates only a one character value 'D' for the language setting.
 
8='01'C='C'E='1'A='D'9=''B=''I='0'e='0'u=''v=''w='0'x='0'y='0'z='0'X='0'Y=''Z=''1='0'

This output from the JBA_REST table with a 2 character value for the language setting, which is the accepted value size since version 10.
 
8='01'C='C'E='1'A='DE'9=''B=''I='0'e='0'u=''v=''w='0'x='0'y='0'z='0'X='0'Y=''Z=''1='0'



 
Environment:
OS Version: N/A
Cause:
Cause type:
Defect
Root Cause: This is a legacy issue concerning elder versions of One Automation instances and their upgrade to version >=10.
Resolution:
Update to a fix version listed below or a newer version if available.

 

Fix Status: Released

Fix Version(s):
Component(s): AE and Initialdata

Automation Engine 12.1.0 – Available
Automation Engine 12.0.1 - Available
Automation Engine 11.2.4 – Available
Automation Engine 11.1.5 – Available
Automation Engine 10.0.8 HF3 – Available
Additional Information:
Workaround :
There are two recommended workarounds:
  1. Refrain from updating legacy Jobs, and they will keep working correctly as the first time the Job is created this is only a display issue and the Jobs will function with the correct language as long as there is no update of the job.
OR
  1. ​If the legacy jobs must be updated, it is mandatory to set the value of the language parameter again to the correct value in the 'Start Parameter' section of the SAP panel.