814_27 containing REF~1P~HUU does not close the Business Process at ERCOT
Next Step:
Since other exceptions are not outlined in the RMG it was decided that only Stacking Documentation would be updated. Kathryn Thurman (ERCOT) will update and re-post the Stacking Documents.
Since other exceptions are not outlined in the RMG it was decided that only Stacking Documentation would be updated. Kathryn Thurman (ERCOT) will update and re-post the Stacking Documents.
Once these are cancelled by ERCOT any historical usage that comes in from the TDSP will still be forwarded to the CR. ERCOT needs the process outlined in the Retail Market Guide to clearly show that ERCOT is allowed to manually cancel these business processes. Johnny will draft an PRR to be reviewed next month’s meeting.
Texas SET provided input that filing MarkeTraks on these issues seems to be a waste of time and the end result should be that the HUU closes the BPI at ERCOT. ERCOT will review possible solutions and will bring a recommended action plan back to Texas SET. Note: will most likely need changes to the 814_27 for long term solution
Background
Status:
Closed
Date Posted:
06/22/2009
Sponsor:
CenterPoint Energy
Urgent:
No
Sections:
814_27
Description:
CenterPoint Energy received an 814_26 and since the premise has no historical usage available to provide an 867_02 Historical Usage response CenterPoint responded with an 814_27 REF~1P~HUU with the expectation that this would close the Business Process Instance (BPI) on the 814_26 for the CR and ERCOT. ERCOT did not close the Business Process for the Historical Usage. Manual workaround being required to issue, investigate and complete MarkeTraks by ERCOT and CenterPoint Energy to investigate and resolve MarkeTraks open to manually send 867_02 transactions for these 814_27 HUU sent from CenterPoint to ERCOT to close ERCOT’s BPI.
Reason:
When ERCOT receives an 814_27 with an REF~1P~HUU~HISTORICAL USAGE UNAVAILABLE would close the Business Process Instance (BPI), therefore no follow-up 867_02 is necessary and no MarkeTraks would be required to resolve any issues relating to this same scenario.
