NOTICE DATE: October 2, 2009 NOTICE TYPE: R-B100209-01 Extracts - Retail SHORT DESCRIPTION: Intermittent discrepancy between the ESIIDUSAGE.TIMESTAMP record value and the corresponding ESIIDUSAGE_DELETE.SRC_TIMESTAMP record value on the ESIID Usage and Service History Extract. INTENDED AUDIENCE: CRs and TDSPs DAY AFFECTED: October 1, 2009 LONG DESCRIPTION: An Intermittent discrepancy between the ESIIDUSAGE.TIMESTAMP record value and the corresponding ESIIDUSAGE_DELETE.SRC_TIMESTAMP record value on the ESIID Usage and Service History Extract has been discovered. This discrepancy only affects the ESIIDUSAGE_DELETE table. This issue resulted in a timing difference between the timestamp included in the ESIIDUSAGE_DELETE varying one second from the timestamp included in the ESIIDUSAGE file. The ESIID Service History and Usage Extracts posted today include all ESIIDUSAGE_DELETE records for 10/01/2008 to current date, including the records with the corrected ESIIDUSAGE_DELETE.SRC_TIMESTAMP. The extract logic has been updated to provide the same database timestamp between a record received in ESIIDUSAGE and a delete record received in ESIIDUSAGE_DELETE. ADDITIONAL INFORMATION: To ensure that market participants do not have any ESIIDUSAGE records loaded in their ESIID Service History & Usage Extracts systems that ERCOT has as deleted, ERCOT has created a ESIIDUSAGE_DELETE file which contains all delete records from 10/01/2008 to current date. This Supplemental ESIID Service History & Usage Extract includes the records with the corrected ESIIDUSAGE_DELETE.SRC_TIMESTAMP. Market participants should use their typical delete processing to process this file. The supplemental file will be posted with the same naming convention as the daily ESIID Service History and Usage Extract and only include the ESIIDUSAGE_DELETE file. There will be no counter file included in the supplemental extract. The normal daily extract for 10/2/09 will include the counter file as usual. The root cause was due to the ESIIDUSAGE.TIMESTAMP field and ESIIDUSAGE_DELETE.SRC_TIMESTAMP field not being populated in the extract using the same database field. The daily extract logic has been modified to continue to send the ESIIDUSAGE_DELETE.TIMESTAMP based on the same database field being sent in the ESIIDUSAGE.TIMESTAMP field. CONTACT: If you have any questions, please contact your ERCOT Account Manager. You may also call the general ERCOT Client Services phone number at (512) 248-3900 or contact ERCOT Client Services via e-mail at [log in to unmask]<mailto:[log in to unmask]>. If you are receiving e-mail from an ERCOT distribution list that you no longer wish to receive, please follow this link in order to unsubscribe from this list: http://lists.ercot.com<http://lists.ercot.com/> JR/DH