IWS C1-Bill SearchBill Operation Is Using Multiple Date Formats For Field Output Field BillDate
(Doc ID 3061258.1)
Last updated on DECEMBER 02, 2024
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.9.0.1.1 to 2.9.0.1.1 [Release 2.9]Oracle Utilities Customer Care and Billing - Version 2.9.0.1.1 to 2.9.0.1.1 [Release 2.9]
Information in this document applies to any platform.
Symptoms
IWS C1-Bill searchBill Operation is using multiple Date formats for field output field BillDate
IWS C1-Bill for Operation searchBill
The date format for Search Bills output field "BillDate" varies for different input requests.
If "serviceTypeBreakdown" is "Y", the "BillDate" appears as "2023-10-20" as YYYY-MM-DD
If "serviceTypeBreakdown" is "N", the "BillDate" appears as "10-20-2023" as MM-DD-YYYY
Channel applications levering this OOB service need extract and consistent date format.
Request to please provide fix on this.
Steps to Recreate:
---------------------
If "serviceTypeBreakdown" is "Y", the "BillDate" appears as "2023- 10-20".
1. Go to Inbound Web Service.Search for IWS C1-Bill.
2. Click View Specification.
3. Go to POST operation Search bills .
If "serviceTypeBreakdown" is "N", the "BillDate" appears as "10-20- 2023".
- Go to Inbound Web Service.
- Search for IWS C1-Bill.
- Click View Specification.
- Go to POST operation Search bills .
Expected Result: The API should give a response with 200 status code and the response body should be populated same date format for billDate parm
Actual Result: The API should give a response with 200 status code and the response body populating different date format for billDate parm.
Changes
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 |
Changes |
Cause |
Solution |
References |