Batch Not Using Predefined Value Defined In Batch Control
(Doc ID 2670611.1)
Last updated on MAY 31, 2024
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.6.0.1.0 to 2.7.0.3.0 [Release 2.6 to 2.7]Information in this document applies to any platform.
Symptoms
On : 2.6.0.1.0 version, Framework
ACTUAL BEHAVIOR
---------------
Batch not using predefined value defined in Batch Control if the parameter value's "required" checkbox is un-checked.
EXPECTED BEHAVIOR
-----------------------
If the parameter's value is set, no matter the "required" checkbox is checked or not, the batch should use the parameter during the job run.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Testing filePath parameter
=========
Test the following condition in environment:
1- Default File Path with no requirement option
Default file path is: C:\spl\sploutput\C2M260\Test
Run the following command on command prompt:
submitjob -b <batchname> -e THIN -g YYYY -u SYSUSER -x fileName=Extract_test.dat
File location defaulted to SPLOUTPUT directory and did not go to defined location.
2- Default File Path set as a "required" parameter
3- Run the following command on command prompt:
submitjob -b <batchname> -e THIN -g YYYY -u SYSUSER -x fileName=Extract_test.dat
File was created in the default file folder as defined online:
C:\spl\sploutput\C2M260\Test
Testing csvDelim parameter
============
Test the following condition in environment:
1- Default CSV File Delimiter with no requirement option
Default CSV File Delimiter is: "~"
2- Run the following command on command prompt:
submitjob -b <batchname> -e THIN -g YYYY -u SYSUSER -x fileName={BC}_{BN}_{RN}_{TN}.csv
CSV File Delimiter defaulted to comma but not "~"
3- Default CSV File Delimiter set as a "required" parameter
Run the following command on command prompt:
submitjob -b <batchname> -e THIN -g YYYY -u SYSUSER -x fileName={BC}_{BN}_{RN}_{TN}.csv
File was created with default file delimiter as defined online ("~")
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use the pre-defined parameter for batch control as expected.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |