The Japanese Localization Function "Get Computation Period" Is Not Working Correctly.
(Doc ID 2198863.1)
Last updated on OCTOBER 02, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.4.0.3.0 to 2.4.0.3.0 [Release 2.4]Information in this document applies to any platform.
Symptoms
On : 2.4.0.3.0 version, ENV - Environment
ACTUAL BEHAVIOR
---------------
The Japanese localization function "Get computation period" is not working correctly.
Executing billing batch on batch submission screen, the registered value of CI_BSEG.END_DT is not correct.
This issue don't occurs when creating bill on Billing screen. This issue occurs only in batch.
EXPECTED BEHAVIOR
-----------------------
After execute Billing batch, expected result is "CI_BSEG.END_DT = '2015-12-15'".
Now result of execute billing batch is "CI_BSEG.END_DT = '2015-12-17'".
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Primary data for execute Billing tests.(PER,ACCT,SA,SP,MTR etc.)
-> Bill cycle date is 2015-12-17.
2. Register MR data.
-> Service cycle date and Meter read date are 2015-12-15.
3. Execute billing batch on batch submission screen.
-> Batch service date is 2015-12-15.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
CI_BSEG.END_DT is incorrect.
The system test cannot be executed. Customer cannot meet their milestone of 11th October if this issue isn't resolved.
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 |