FAQ - SAP Language Settings

The language that is specified in an SAP agent's INI file is used for the agent's log files. However, you can override these INI file settings by defining a language in a Connection object or an SAP job. This topic provides an overview of how the individual language settings interact with each other.

ClosedQ: In which language will a job run on the target SAP system if the language parameters in the Connection object and in the R3 job are not set (= NULL)?

A: The language parameter of the SAP agent's INI file will be used.

ClosedQ: What happens if the language parameter in the Connection object is not set and the language parameter in the R3 job includes a language that is not allowed (wrong shorthand symbol)?

A: The R3 job language parameter is used to connect to the SAP system, and the SAP system aborts the connection with the following message: "U02004007 Error 'JCO_ERROR_LOGON_FAILURE' in 'BAPI_XBP_JOB_OPEN' call. Select one of the installed languages on <SAP system name> sysnr <##>"

ClosedQ: The language parameter in the Connection object is not set and the language parameter in the R3 job includes a valid language shorthand symbol. What happens?

A: The R3 job language parameter is used.

ClosedQ: The language parameter in the Connection object is set with a language shorthand symbol that is not allowed and the language parameter in the R3 job also includes a language that is not allowed (wrong shorthand symbol)?

A: The agent needs an initial connection using the language parameter in the Connection object but that does not succeed. You will see error messages in the log file such as: "U02004172 Error while calling function module 'RFC_SYSTEM_INFO'. Select one of the installed languages on <SAP system name> sysnr <##>" As the initial connection does not succeed, the job does not start in the SAP system. The agent keeps on trying to establish the initial connection with the wrong language parameter.

ClosedQ: The language parameter in the Connection object is set with a language shorthand symbol that is not allowed and the language parameter in the R3 job includes a valid shorthand symbol?

A: The agent needs an initial connection using the language parameter in the Connection object but that does not succeed. You will see error messages in the log file such as: "U02004172 Error while calling function module 'RFC_SYSTEM_INFO'. Select one of the installed languages on <SAP system name> sysnr <##>" As the initial connection does not succeed, the job does not start in the SAP system. The agent keeps on trying to establish the initial connection with the wrong language parameter.

ClosedQ: What happens if the language parameter in the Connection object is set with a language shorthand symbol that is not allowed and the language parameter in the R3 job is not set?

A: The agent needs an initial connection using the language parameter in the Connection object but that does not succeed. You will see error messages in the log file such as: "U02004172 Error while calling function module 'RFC_SYSTEM_INFO'. Select one of the installed languages on <SAP system name> sysnr <##>" As the initial connection does not succeed, the job does not start in the SAP system. The agent keeps on trying to establish the initial connection with the wrong language parameter.

ClosedQ: The language parameter in the Connection object is set with a valid language shorthand symbol and the language parameter in the R3 job includes a language that is not allowed (wrong shorthand symbol)?

A: The R3 job language parameter will be used to connect to the SAP system, and the SAP system aborts the connection with the following message: "U02004007 Error 'JCO_ERROR_LOGON_FAILURE' in 'BAPI_XBP_JOB_OPEN' call. Select one of the installed languages on <SAP system name> sysnr <##>"

ClosedQ: The language parameter in the Connection object is set with a valid language shorthand symbol and the language parameter in the R3 job includes a valid shorthand symbol?

A: The language parameter in the R3 job is used.

ClosedQ: The language parameter in the Connection object is set with a valid language shorthand symbol and the language parameter in the R3 job is not set?

A: The language parameter in the Connection object is used.

ClosedQ: Are there any other dependencies regarding the language that is finally used in the R3 jobs?

A: No

See also: