getScalarValue Fails When BSA_SCREEN_LEVEL Is DEBUG (Doc ID 2258456.1)

Last updated on APRIL 24, 2017

Applies to:

Oracle Retail Advanced Inventory Planning - Version 15.0.1 and later
Information in this document applies to any platform.

Symptoms

Using BSA_SCREEN_LEVEL with value other than NONE causes getScalarValue to store more than just a single value. It stores the output of the screen level. Subsequent use of the scalar value as input to mace expression causes the mace expression to fail.

 

<B 2016Nov28 14:57:27.949> 14:57:09 : INFORMATION : getScalarValue[-] - Current directory: /vol.nas/u03/qc/rpas11code/Linux/15.0.1/aip/aip
<B 2016Nov28 14:57:27.949> 14:57:09 : INFORMATION : getScalarValue[-] - Parameters: ipbydplnhzng
<B 2016Nov28 14:57:27.949> 14:57:09 : INFORMATION : getScalarValue[24] - _call executing command 'cd /vol.nas/u03/qc/rpas11code/Linux/15.0.1/aip/aip'
<B 2016Nov28 14:57:27.949> 14:57:09 : INFORMATION : getScalarValue[24] - _call of command 'cd /vol.nas/u03/qc/rpas11code/Linux/15.0.1/aip/aip' complete
<B 2016Nov28 14:57:27.949> 7
<B 2016Nov28 14:57:27.949> 14:57:11 : INFORMATION : getScalarValue[51] - Program completed successfully.
<B 2016Nov28 14:57:27.949> 14:57:11 : INFORMATION : getScalarValue[51] - Exiting script with code: 0
<B 2016Nov28 14:57:27.949> 14:57:11 : INFORMATION : getScalarValue[1] - NO_EXIT_STATEMENT resulted in syntax error at 11.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms