Protocol Revision Request will be created by TX SET to include 48 hr Re-try Queue for A76 ESI ID Not Found when 814_20 Maintenance Transactions are received. This will also be a SIR potentially scheduled for February 2007 implementation.
Protocol Revision Request will be created by TX SET to include 48 hr Re-try Queue for A76 ESI ID Not Found when 814_20 Maintenance Transactions are received. This will also be a SIR potentially scheduled for February 2007 implementation.
Background
Status:
Closed
Date Posted:
11/02/2006
Sponsor:
ERCOT
Urgent:
No
Sections:
814_20, 814_21
Description:
When a TDSP submits an 814_20 Add and an 814_20 Maintain for the same ESI ID within a short period of time, it is possible for the 814_20 Maintain to process first at ERCOT, and be rejected for A76 - ESI ID Invalid or Not Found. The 814_20 Add processes later and creates the ESI ID. The TDSP then has to resubmit the 814_20 Maintain to make the necessary change. About 30% of the 814_20s that reject for A76 are for ESI IDs that are eventually created in ERCOT’s system. In addition most of the ESI IDs that are valid are created in ERCOT's system within 48 hours of receiving the 814_20 Maintain.
Reason:
This is causing manual work for the TDSPs in the form of having to resubmit the 814_20 Maintains for these ESI IDs. ERCOT would like to implement an 814_20 Maintain Retry queue, much like the MVI Retry queue that exists currently. The 814_20 Maintain that originally rejects for A76 will be held and retried for 48 hours on business days, but no only counting business hours. This will allow the 814_20 Add that maybe waiting to process time to create the ESI ID and prevent the reject from occurring.
