ISAIM 2.1.3 resolved issues

This section lists significant issues that have been addressed in ISAIM 2.1.3.

AMI Billing Export (ABE)

2748580: (SR#:01129808) Register readings decimal values longer than the SAP system can handle were being sent, causing a rejection of the MRO response.

Resolution: The conversion of register reading value to the meter's number of dials has been corrected. It now results in the correct decimal response.

2759060: (SR#: 01133286) During a volume test, the SAP BillingExport task raised the following error when processing the ABE exportfiles: Unexpected System Exception:#XmlException - Root element is missing.received - contact Application manager.

Resolution: This was because ABE copied the tmp file to a new XML export file, and the XML file was picked up before this process completed. The ABE logic has been enhanced. It now renames the tmp file to XML instead of creating a new file, no longer picks up the file if it is empty, and ensures it never creates empty files.

2762285/3039365: (SR#: 01129600/01265414) When cancelling an MRO request, the following error was observed: Unexpected System Exception:#NullReferenceException - Object reference not set to an instance of an object.

Resolution: This is because the code did not handle null value correctly when searching for the corresponding MRO task using Meter ID or Correlation ID. The MRO cancellation has been corrected. The error is no longer observed.

2880372: (SR#: 01182533) For some MRO requests from SAP for a specific month, it was observed that IEE returned a read with for the month prior or the month after.

Resolution: This issue occurred when ABE processes more than one requests simultaneously for the same meter and the same channel, but with different dates. When selecting the read, ABE did not consider the date in the individual request, and returned the same read selected for the first request. This issue does not occur when the requests are received and processed separately. The ABE process has been corrected. In this scenario, ABE now selects the correct read for each request. The fix is in IEE core (ABE). No change in ISAIM.

2965101: (SR#: 01222277) When SAP sends interval billing request for Max Demand and Onpeak Average Demand, IEE's response use different UtilitiesTimeSeriesCalculationResultCategoryCode even though both have the same KW UOM.

Resolution: The logic has been corrected. IEE now sends the billing response to SAP with the correct UtilitiesTimeSeriesCalculationResultCategoryCode based on UOM.

2993208: (SR#: 01236587) The MRO result value sent to SAP is not the same as thevalue being recorded in the IEE database.

Resolution: This is due to the rounding. The rounding logic has been corrected to resolve this issue.

3021033: (SR#: 01255628) When SAP sends a billing request with the optional Peak parameter, occasionally IEE only returns the KWH request even though both KWH and KW reads are available.

Resolution: This issue occurs occasionally when ABE processes the KWH and KW requests separately. The code has been enhanced to ensure that KWH and KW requests are always processed together.

Configuration

2018960: (SR#: 00921713) After performing a meter swap, the meter multiplier retained the CT ratio from the old meter.

Resolution: The logic code has been corrected. If the difference between the old meter's end date and new meter's start date is less than one day, the old meter's CT ratio will be retained; otherwise, the new meter's CT ratio will be applied.

2668734: (SR#: 01093257) During a meter exchange, the End Dates for old and new meter in the Custom Temporal Property (CTP) table in IEE are not updated correctly and become out of sync with SAP.

Resolution: The logic has been corrected. During a meter exchange, End Dates in the CTP table are updated correctly for old and new meter.

2888136: (SR#: 01182503) In a Bulk Replication Sync with multiple meters in the same request, due to incorrect null handling, the meters that contain installation reversals failed with the following error: Unexpected System Exception:#NullReferenceException - Object reference not set to an instance of an object. This results in the subsequent meter also failing.

Resolution: The Bulk Replication Sync has been corrected to correctly handle null condition. In this scenario, replication for all meters are now processed successfully.

2987437: (SR#: 01230461) An issue is observed in the following scenario:

  • MeterA (on Program1) is installed at ServicePointA

  • MeterB (on Program2) is installed at ServicePointB

  • Uninstall MeterB from ServicePointB at a non-midnight date

  • On the same date, reprogram MeterB to Program1 - In this step, because a meter version is created more than once in a single day, MeterB is incorrectly re-installed at ServicePointB.

  • Uninstall MeterA from ServicePointA

  • Install MeterB at ServicePointA - This step fails because the meter is already linked to a service point.

Resolution: The logic has been corrected. When a meter version is created more than once in a single day, to uninstall a meter and reprogram the meter, the logic no longer re-installs the meter.

3001042: (SR#: 01241536) During a meter exchange, UMTID entries for the old meter were incorrectly removed from the CTP table, so that the subsequent Profile Allocation replication sync failed.

Resolution:  The logic has been corrected. UMTID entries are now managed correctly in the CTP table for a meter exchange.

3031106: (SR#: 01261379) Configuration sync from SAP using bulk replication failed with no reason provided.

Resolution: This issue occurred when the request contains a meter version that specifies a program ID, and a service point program with that program ID does not exist in IEE. For example, when the meter version pre-dates the ISAIM installation. The code has been enhanced. In this scenario, ISAIM now logs a warning, skips this meter version, and continues executing the rest of the request. The warning is as follows: “Service Point Program [ProgramID] not found when processing meter [MeterID] version [StartDate] - [EndDate]. This can be a pre-ISAIM or not ISAIM compatible version. Ignoring this version".

DeviceComm

2864512: (SR#: 01175745) For remote disconnect/reconnect request from SAP, ISAIM returns an exception.

Resolution: This issue occurs when the SAP clock is a few seconds ahead of IEE clock. The AMI disconnect/reconnect is created as future dated task, and the Correlation ID is not saved. Even when the disconnect/reconnect is successful, ISAIM cannot find the task using Correlation ID and logs an error. The AMI disconnect/reconnect has been corrected. Added a time buffer, so when SAP clock is a few seconds out of sync, the disconnect/reconnect is not created as a future dated task. When the disconnect/reconnect request is future dated, the Correlation ID is saved as task parameter, so ISAIM can return the correct result. The fix is in IEE core (DeviceComm). No change in ISAIM.

Performance

3056875: (SR#: 01276654) When processing Register Changes from SAP, the SapRequestImport task was stuck in Running state, caused database lock, and consumed high memory usage.

Resolution: The Register Change code has been enhanced to reduce the number of database calls.

Reading Import

2764641: (SR#: 01130300) When importing a reading from SAP, IEE uses the specified MeterReadingDate as the reading timestamp, even when the ActualMeterReadingDate is specified in the payload.

Resolution: The reading import logic has been changed. If IEE receives only MeterReadingDate, the MeterReadingDate will be used as the reading timestamp. If IEE receives both MeterReadingDate and ActualMeterReadingDate, the ActualMeterReadingDate will be used. If IEE receives only ActualMeterReadingDate, the ActualMeterReadingDate will be used.