Texas

Standard
Electronic
Transaction

814_08:
Cancel Switch Request

Electronic Data Interchange
ANSI ASC X12 Ver/Rel 004010
Transaction Set 814
Texas 814_08:
CANCEL SWITCH REQUEST

This transaction set...

... from ERCOT to the TDSP, is used to cancel a Switch Request, a Move-In request, a Continuous Service Agreement (CSA) Move-In request, Move-Out request, or Drop to AREP.

... from ERCOT to the current CR, is used to cancel a Drop Due to Switch (forced move-out or switch) request, a Move-Out request, or a Drop to AREP request.

... from ERCOT to the new CR, is used to cancel a Switch request, a Move-In request, or a Drop to AREP Enrollment request. 

... from the current CR to ERCOT, is used  to cancel a Move-Out request or Drop to AREP request.

... from the new CR to ERCOT, is used to cancel a Switch request or a Move-In request.

... from ERCOT to the CSA CR, is used to cancel a CSA Move-In request. 

Document Flow: 
•	ERCOT to TDSP
•	ERCOT to Current CR
•	ERCOT to New CR
•	Current CR to ERCOT
•	New CR to ERCOT
•	ERCOT to CSA CR
•	ERCOT to AREP
•	ERCOT  to POLR

The Functional Acknowledgement (997) transaction set from the receiver of the originating transaction to the sender of the originating transaction, is used to acknowledge the receipt of the originating transaction and indicate whether the transaction passed ANSI X12 validation.  This acknowledgement does not imply that the originating transaction passed Texas SET validation. “CR, TDSP, or ERCOT shall respond with a 997 within 24 hours of receipt of an inbound transaction.”

		Summary of Changes	
July 3, 2000
Version 1.0		
Initial Release	
			
August 23, 2000
Version 1.1		
The following changes were made:	
		•	Added Customer Name and Zip Code	
		•	Added gray box to reject reasons associated with a CR Objection, “We are not sure of the requirements of this information at this time.  When the rules are finalized we will revisit whether the CR can object to a switch for this reason.”	
		•	Change transaction description page.	
		•	Added gray box to DTM~150 Service Period Start code “On a Reinstatement, this date should match the date of the original cancellation”.	
			
December 12, 2000
Version 1.2		
The following changes were made:	
		•	Change the term Utility to Transmission Distribution Service Provider (TDSP) to match ERCOT Protocols.	
		•	Change the term Retail Electric Provider (REP) to Competitive Retailer (CR) to match ERCOT Protocols.	
		•	Change description page transaction purpose to read the same as ERCOT Protocols.	
		•	Insert the “How to use this Implementation Guide” page.	
		•	Remove “.” between X and 12 in all references to ANSI ASC X12.	
		•	Add BGN08 Element to indicate the TX SET Transaction Number per Change Control #2000-015.	
		•	Add examples to end of transaction.	
			
March 16, 2001
Version 1.3		
The following changes were made:	
		•	Removed Scenario Names from Transaction Description page	
		•	Corrected the How to Use this Implementation Guide page	
		•	Corrected X12 Structure Page	
		•	Changed RA/Clearinghouse to ERCOT	
		•	Removed Rejection Reason Codes, because they were not allowed in the rule:
B04 - Requested services will not be completed until outstanding payment is made 
CCA - Customer Contract Active	
		•	Example 2: Removed DTM~150 from Example 2 and statement about the date in the gray box. Corrected SE Count.	
		•	Example 4: Corrected SE Count	
			
August 3, 2001
Version1.4		
No changes for Version 1.4	
		•	Added REDLINES from Change Controls:
•	2001-191 Add the 814_16 Move-In Request to Segment Beginning Segment, BGN06 gray box.    10/5/01	
		•	Change Control 2002-295 – Change N1~SJ to Conditional.	
			
June 17, 2002
Version 1.5		The following changes were made:	
		•	Change Control 2001-231 – Added language to transaction flow for cancellation of a switch and provided example.	
		•	Change Control 2002-237 – Added Status Reason of “PNR” to REF02 of the REF~1P.	
		•	Change Control 2002-267 - Removed “9” value from the N103 in the N1~AY loop.	
		•	Change Control 2002-293 – Modified flow page to allow New CR to cancel their pending switch.	
		•		
		•	Applied Change Control 2002-317: Change Document flow page to read “…from ERCOT to the current CR is used to reinstate the Customer when  the Switch or  Move-In that caused a forced Move-Out/Drop Due to Switch has been canceled by the end use Customer.”	
8/5/02		Change Control 2002-353 – Corrected Implementation guide “Summary of Changes” by cleaning up previously missed or inaccurate additions to Summary of Changes:	
		•	Change Control 2002-353 – Updated Change Control Log to add approved Version 1.5 Change Control 2002-324. This was previously missed at time of update of implementation guide and is needed to reflect the approved cleanup change control.	
8/5/02		Change Control 2002 – 354 - Corrected Implementation guide “Summary of Changes” by cleaning up previously missed or inaccurate additions to Summary of Changes:	
		•	Change Control 2002-354: Clean-up Change Control for the 2002-295.  Removed Change Control 2002-295 from Change Control Log for version 1.5 and added  to Version 1.4 section.  Added detail for v1.4 Change Control 2001-191.	
9/15/02		•	Change Control 2002-360 – Corrected spelling of “Receipt” in the REF~1P	
		•	Change Control 2002-362 – Added 814_06 to Gray box of the BGN.06	
10/15/02		•	Change Control 2002-420 – Replaced references to POLR with AREP	
May 27th, 2003
Version 1.6		The following changes were made:	
5/27/03		•	Change Control 2002-386 – Removed D-U-N-S+4 from the N104 gray box in the N1~AY loop	
5/29/03		•	Change Control 2002-445  Update Document Flows on the Cancel Switch Request (814_08) so that it is consistent with the Visio Diagram.
	
5/29/03		•	Change Control 2002-451 Correct 814_08 N1~8R	
July 17, 2003
Version 2.0		•	Change Control 2002-446 - Removed DTM~150 Service Period Start from the 814_08	
8/15/03		•	Change Control 2003-547 – Please include the Move-In/Move-Out Task Force (MIMO) High Level Requirement Specification as part of the Baseline for Version 2.0.	
8/15/03		•	Change Control 2003-516 - To effect changes as requested by the Move In / Move Out task force	
8/15/03		•	Change Control 2003-540 - Clarification around which cancellation reasons are valid CR cancellation reasons, and removal of references to reinstatement	
9/18/03
		•	Change Control 2003-560 - Add a new status code to the 814_08 for manual cancels by ERCOT	
October 8, 2004
Version 2.0A
		Change Control 2003-573:
•	Remove references to the word “reinstate” references in ASI segment and examples.
Change Control 2003-594:
•	Adjust the verbiage in the PNR gray box on the 814_08 transaction.  MIMO rules states that the 814_08 will be sent if 20 days after the scheduled MVI date the permit is not received.
Change Control 2004-598:
•	Update Examples since CRs are not allowed to use the EB3 code to cancel.
Change Control 2004-602:
•	Remove text from the gray box of the N1~SJ segment indicating that the segment is optional from ERCOT to the TDSP when there is no current rep.  Now that the ERCOT’s evaluation for sending out 814_08s is done two days prior to the SMRD, there are instances where the N1~SJ will not be populated on the 814_08 going out to the TDSP.  Because of this ERCOT requests that the text ‘when there is no Current REP’ be removed.  The statement will read ‘Optional from ERCOT to the TDSP’.  
Change Control 2004-614:
•	Update REF~1P segment graybox to indicate that the REF~1P is only sent once.
Change Control 2004-620:
•	Update the BGN06 gray box to indicate the 814_08 BGN06 will match the BGN06 of the 814_14 or 814_22 in situations where there is a Drop to AREP or Move out to CSA
Change Control 2004-634:
•	As per discussions at the June 04 TX SET meeting, additional language should be added to each Transaction Set to identify the requirements and required response to the 997 Functional acknowledgement - The Functional Acknowledgement (997) transaction set from the receiver of the originating transaction to the sender of the originating transaction, is used to acknowledge the receipt of the originating transaction and indicate whether the transaction passed ANSI X12 validation.  This acknowledgement does not imply that the originating transaction passed Texas SET validation. “CR, TDSP, or ERCOT shall respond with a 997 within 24 hours of receipt of an inbound transaction.”
Change Control 2004-638
•	Update example # 5 of 5 to correctly show “New CR” in the description of the field.	
March 1, 2005
Version 2.1		Change Control 2003-569:
•	Provide gray box clarification to the LIN segment to indicate that the Texas Market supports only 1 LIN loop per EDI Transaction.
Change Control 2003-582:
•	Add verbiage to the gray box in the “TWO” status reason code to include references to the Switch and Drop processes.
Change Control 2004-649: 
•	Add membership ID to support Muni/Coop business requirements.  This Change Control has been reversed by 2005-685
Change Control 2004-642:
•	Update the 814_08/814_09 IG transaction flow to indicate the 814_08 can be used to cancel a drop to AREP
Change Control 2005-683:
•	Add clarity to the transaction notes section regarding the Texas Market use of characters in alphanumeric fields
Change Control 2005-685:
•	Reversal of Change Control 2004-649 – written to exclude the Membership ID from this transaction.
	
March 6, 2006
Version X>X		Change Control 2006-XXX:
•	Mass Transition Task force modification for Cancel MVO or MVI with request for POLR CR to submit new transaction per customer request. 	

How to Use this Implementation Guide

This section is used to show the X12 Rules for this segment.  You must look further into the grayboxes below for Texas Rules.

	Segment:	REF Reference Identification (ESI ID)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.

This section is used to show the Texas Rules for implementation of this segment.

	Comments:
Notes:		Required
	
		REF~Q5~~10111111234567890ABCDEFGHIJKLMNOPQRS	

One or more examples.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	Q5		Property Control Number	
	Electric Service Identifier (ESI ID)	
Must Use	REF03	352	Description	X		AN 1/80	
	A free-form description to clarify the related data elements and their content	
	ESI ID	

This column shows the Texas use of each data element.

This column shows the X12 attributes for each data element.

M = Mandatory
O= Optional
X = Conditional

AN = Alphanumeric
N# = Implied Decimal at position #
ID = Identification
R = Real

1/30 = Minimum 1, Maximum 30

These are X12 code descriptions, which often do not relate to the Texas descriptions.  
X12 cannot keep up with Texas needs, thus, Texas often changes the meaning of existing codes.  See the corresponding graybox for the Texas definitions.

   

814 General Request, Response or Confirmation

Functional Group ID=GE

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the General Request, Response or Confirmation Transaction Set (814) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request actions to be performed, to respond to a request for actions to be performed or to confirm information related to actions performed.

Notes:

Heading:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
M	010	ST	Transaction Set Header	M	1									
M	020	BGN	Beginning Segment	M	1									
			LOOP ID - N1			>1								
	040	N1	Name (Customer)	O	1									
	070	N4	Geographic Location (Customer Service Address)	O	1									
														
			LOOP ID - N1			>1								
	040	N1	Name (Transmission Distribution Service Provider)	O	1									
														
			LOOP ID - N1			>1								
	040	N1	Name (ERCOT)	O	1									
														
			LOOP ID - N1			>1								
	040	N1	Name (Competitive Retailer)	O	1									

Detail:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
			LOOP ID - LIN			>1								
	010	LIN	Item Identification	O	1									
	020	ASI	Action or Status Indicator	O	1									
	030	REF	Reference Identification (Status Reason)	O	>1									
	030	REF	Reference Identification (ESI ID)	O	>1									
														
M	150	SE	Transaction Set Trailer	M	1									

	Segment:	ST Transaction Set Header
	Position:	010
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the start of a transaction set and to assign a control number
	Syntax Notes:
	Semantic Notes:	1	The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
	Comments:
Notes:		Required
	
		ST~814~000000001	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	ST01	143	Transaction Set Identifier Code	M		ID 3/3	
	Code uniquely identifying a Transaction Set	
 	814		General Request, Response or Confirmation	
M	ST02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	

	Segment:	BGN Beginning Segment
	Position:	020
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the beginning of a transaction set
	Syntax Notes:	1	If BGN05 is present, then BGN04 is required.
	Semantic Notes:	1	BGN02 is the transaction set reference number.
		2	BGN03 is the transaction set date.
		3	BGN04 is the transaction set time.
		4	BGN05 is the transaction set time qualifier.
		5	BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
	Comments:
Notes:		Required
	
		BGN~13~200104021200719~20010402~~~200104011956531~~8	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	BGN01	353	Transaction Set Purpose Code	M		ID 2/2	
	Code identifying purpose of transaction set	
 	13		Request	
M	BGN02	127	Reference Identification	M		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	A unique transaction identification number assigned by the originator of this transaction.  This number must be unique over time.

Transaction Reference numbers will only contain uppercase letters (A to Z) and digits (0 to 9).  Note that punctuation (spaces, dashes, etc.) must be excluded.	
M	BGN03	373	Date	M		DT 8/8	
	Date expressed as CCYYMMDD	
	The transaction creation date - the date that the data was processed by the sender's application system.	
X	BGN04	337	Time	X		TM 4/8	
	Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)	
	??????????? CUBR did not have this element, do we want it?  Is there value added?  Do we do a time zone??	
X	BGN05	623	Time Code	O		ID 2/2	
	Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
>>	BGN06	127	Reference Identification	O		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Refers to the BGN02 of the...
... Enrollment Request (814_01),... Drop to AREP Request (814_10), 
... Move In Request (814_16),
... Move Out Request (814_24).  
Refers to the BGN06 of the…
...Drop Due to Switch Request (814_06)
...AREP Enrollment Request (814_14)
...CSA CR Move In Request (814_22)

This number will be tracked in the BGN06 through the lifecycle of the respective process.
	
	BGN07	640	Transaction Type Code	O		ID 2/2	
	Code specifying the type of transaction	
	This segment is used to initially identify the type of 814 that is being sent or received.  Ignore the ANSI X12 definition of the code.	
 	TS		Transfer Statement	
	Required when Cancel is for Mass Transition process.
Otherwise not used	
>>	BGN08	306	Action Code	O		ID 1/2	
	Code indicating type of action	
	This segment is used to initially identify the type of 814 that is being sent or received.  Ignore the ANSI X12 definition of the code.	
 	8		In Production Send	
	Indicates Texas SET Transaction 814_08	
X	BGN09	786	Security Level Code	O		ID 2/2	
	Code indicating the level of confidentiality assigned by the sender to the information following	
	Refer to 004010 Data Element Dictionary for acceptable code values.	

	Segment:	N1 Name (Customer)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		New CR to ERCOT: Required
Current CR to ERCOT: Required
All others: Not Used
	
		N1~8R~CUSTOMER NAME	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	8R		Consumer Service Provider (CSP) Customer	
	Customer	
>>	N102	93	Name	X		AN 1/60	
	Free-form name	
	Customer name as documented in the sender's application system.  This name field must be used in order to populate the zip code in N403.	
X	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
	Condition:  Required on the Request when this number is being used for validation. Required on the Response when available.	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Universal Identifier

Condition:  Required on the Request when this number is being used for validation. Required on the Response when available.

Universal Identifiers will only contain uppercase letters (A to Z) and digits (0 to 9).  Note that punctuation (spaces, dashes, etc.) must be excluded.	
X	N105	706	Entity Relationship Code	O		ID 2/2	
	Code describing entity relationship	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
	Refer to 004010 Data Element Dictionary for acceptable code values.	

	Segment:	N4 Geographic Location (Customer Service Address)
	Position:	070
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify the geographic place of the named party
	Syntax Notes:	1	If N406 is present, then N405 is required.
	Semantic Notes:
	Comments:	1	A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
		2	N402 is required only if city name (N401) is in the U.S. or Canada.
Notes:		New CR to ERCOT: Zip Code (N403) is Required.  The first 5 characters will be used for validation.
Current CR to ERCOT: Zip Code (N403) is Required.  The first 5 characters will be used for validation.
All others: Not Used

		N4~~~78111
N4~~~781110001

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
X	N401	19	City Name	O		AN 2/30	
	Free-form text for city name	
	Request: Not Used
Response: Required	
X	N402	156	State or Province Code	O		ID 2/2	
	Code (Standard State/Province) as defined by appropriate government agency	
	Request: Not Used
Response: Required	
>>	N403	116	Postal Code	O		ID 3/15	
	Code defining international postal zone code excluding punctuation and blanks (zip code for United States)	
	Postal codes will only contain digits (0 to 9).  Note that punctuation (spaces, dashes, etc.) must be excluded.	
X	N404	26	Country Code	O		ID 2/3	
	Code identifying the country	
	For country codes not listed, please refer to ISO 3166, a version of which can be found at http://treetops.commerce.net/research/stats/countrycodes.html.
	
	Request: Not Used
Response: Required	
X	N405	309	Location Qualifier	X		ID 1/2	
	Code identifying type of location	
	Request: Not Used
Response: Required if county/parish is available in the sender's system.	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	N406	310	Location Identifier	O		AN 1/30	
	Code which identifies a specific location	
	Service Address County/Parish
	
	Request: Not Used
Response: Required if county/parish is available in the sender's system.	

	Segment:	N1 Name (Transmission Distribution Service Provider)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required
	
		N1~8S~TDSP COMPANY~1~007909411 (ERCOT to Current CR)
N1~8S~TDSP COMPANY~1~007909411~~40 (ERCOT to TDSP)
N1~8S~TDSP COMPANY~1~007909411 (ERCOT to New CR)
N1~8S~TDSP COMPANY~1~007909411 (Current CR to ERCOT)	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	8S		Consumer Service Provider (CSP)	
	Transmission Distribution Service Provider (TDSP)	
>>	N102	93	Name	X		AN 1/60	
	Free-form name	
	TDSP Name	
>>	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
 	9		D-U-N-S+4, D-U-N-S Number with Four Character Suffix	
>>	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	TDSP D-U-N-S Number or D-U-N-S + 4 Number	
X	N105	706	Entity Relationship Code	O		ID 2/2	
	Code describing entity relationship	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
D	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
	Condition: Required if TDSP is the receiver, otherwise not used.	
 	40		Receiver	

	Segment:	N1 Name (ERCOT)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required
	
		N1~AY~ERCOT~1~183529049~~41 (ERCOT to Current CR)
N1~AY~ERCOT~1~183529049~~41 (ERCOT to TDSP)
N1~AY~ERCOT~1~183529049~~41 (ERCOT to New CR)
N1~AY~ERCOT~1~183529049~~40 (Current CR to ERCOT)	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	AY		Clearinghouse	
	ERCOT	
>>	N102	93	Name	X		AN 1/60	
	Free-form name	
	ERCOT Name	
>>	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
>>	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	ERCOT D-U-N-S Number	
X	N105	706	Entity Relationship Code	O		ID 2/2	
	Code describing entity relationship	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
>>	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	40		Receiver	
 	41		Submitter	

	Segment:	N1 Name (Competitive Retailer)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Optional when sent from ERCOT to the TDSP	
		N1~SJ~CURRENT CR NAME~1~007909422~~40 (ERCOT to Current CR)
N1~SJ~CURRENT CR NAME~1~007909422 (ERCOT to TDSP when premise is active)
N1~SJ~NEW CR NAME~1~007909422~~40 (ERCOT to New CR)
N1~SJ~CURRENT CR NAME~1~007909422~~41 (Current CR to ERCOT)	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	SJ		Service Provider	
	Competitive Retailer (CR)	
>>	N102	93	Name	X		AN 1/60	
	Free-form name	
	CR Name	
>>	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
 	9		D-U-N-S+4, D-U-N-S Number with Four Character Suffix	
>>	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	CR D-U-N-S Number or D-U-N-S + 4 Number	
X	N105	706	Entity Relationship Code	O		ID 2/2	
	Code describing entity relationship	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
D	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
	Condition: Required if CR is the sender or receiver, otherwise not used.	
 	40		Receiver	
 	41		Submitter	

	Segment:	LIN Item Identification
	Position:	010
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify basic item identification data
	Syntax Notes:	1	If either LIN04 or LIN05 is present, then the other is required.
		2	If either LIN06 or LIN07 is present, then the other is required.
		3	If either LIN08 or LIN09 is present, then the other is required.
		4	If either LIN10 or LIN11 is present, then the other is required.
		5	If either LIN12 or LIN13 is present, then the other is required.
		6	If either LIN14 or LIN15 is present, then the other is required.
		7	If either LIN16 or LIN17 is present, then the other is required.
		8	If either LIN18 or LIN19 is present, then the other is required.
		9	If either LIN20 or LIN21 is present, then the other is required.
		10	If either LIN22 or LIN23 is present, then the other is required.
		11	If either LIN24 or LIN25 is present, then the other is required.
		12	If either LIN26 or LIN27 is present, then the other is required.
		13	If either LIN28 or LIN29 is present, then the other is required.
		14	If either LIN30 or LIN31 is present, then the other is required.
	Semantic Notes:	1	LIN01 is the line item identification
	Comments:	1	See the Data Dictionary for a complete list of IDs.
		2	LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Notes:		Required

Only 1 LIN Loop per EDI transaction is accepted in the Texas Market	
		LIN~1~SH~EL~SH~CE	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
>>	LIN01	350	Assigned Identification	O		AN 1/20	
	Alphanumeric characters assigned for differentiation within a transaction set	
M	LIN02	235	Product/Service ID Qualifier	M		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	SH		Service Requested	
M	LIN03	234	Product/Service ID	M		AN 1/48	
	Identifying number for a product or service	
	Commodity	
 	EL		Electric Service	
>>	LIN04	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	SH		Service Requested	
>>	LIN05	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
 	CE		Energy Services	
X	LIN06	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	SH		Service Requested	
X	LIN07	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
 	CE		Energy Services	
 	HI		Historical Interval Usage	
 	HU		Historical Monthly Usage	
 	SW		Special Read for Off-cycle Switch	
X	LIN08	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	SH		Service Requested	
X	LIN09	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
 	CE		Energy Services	
 	HI		Historical Interval Usage	
 	HU		Historical Monthly Usage	
 	SW		Special Read for Off-cycle Switch	
X	LIN10	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN11	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
 	CE		Energy Services	
 	HI		Historical Interval Usage	
 	HU		Historical Monthly Usage	
 	SW		Special Read for Off-cycle Switch	
X	LIN12	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN13	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN14	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN15	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN16	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN17	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN18	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN19	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN20	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN21	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN22	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN23	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN24	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN25	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN26	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN27	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN28	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN29	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
X	LIN30	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN31	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	

	Segment:	ASI Action or Status Indicator
	Position:	020
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To indicate the action to be taken with the information provided or the status of the entity described
	Syntax Notes:
	Semantic Notes:
	Comments:
Notes:		Identifies the action to be taken or the status of a requested action for the service identified in the LIN segment.
	
		Required
	
		ASI~7~024	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	ASI01	306	Action Code	M		ID 1/2	
	Code indicating type of action	
 	7		Request	
 	RL		Reschedule	
	Required for Mass Transition when MVO or MVI is future dated.
Otherwise not used. 
Code used to notify POLR to submit a MVI or MVO, POLR must resubmit pending transaction for future date per customer request.	
M	ASI02	875	Maintenance Type Code	M		ID 3/3	
	Code identifying the specific type of item maintenance	
 	024		Cancellation or Termination	
	Rescind	
X	ASI03	641	Status Reason Code	O		ID 3/3	
	Code indicating the status reason	
	Refer to 004010 Data Element Dictionary for acceptable code values.	

	Segment:	REF Reference Identification (Status Reason)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Required

Only 1 REF~1P segment may be sent.
	
		REF~1P~B40~CANCELLED BY CUSTOMER REQUEST
REF~1P~PNR	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	1P		Accessorial Status Code	
	Used on the response when the request is accepted, and additional status information must be provided.	
>>	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
 	A13		Other	
	Explanation Required in REF03. 	
 	A81		Item or Service Not Available on Requested Date	
	Request can not be performed within the scheduled window MIMO Rules, ERCOT 3, TDSP 3
Not valid for CR cancellations	
 	A95		Past Cutoff Time	
	Review period expired. MIMO Rules, ERCOT 23, TDSP 3.  Not valid for CR cancellations	
 	ANL		Agent Not Listed	
	Submitting CR is not, or is not scheduled to be the Rep of Record at date of request.  MIMO Rules, ERCOT 6, TDSP 3.  Not valid for CR cancellations	
 	B40		Dropped by Customer Request	
	Cancelled by Customer Request	
 	CCA		Competition	
	Cancelled due to Move In MIMO Rules, ERCOT 7, TDSP 3.  Not valid for CR Cancellations.	
 	CCE		Contract Details	
	Cancelled due to Move Out MIMO Rules, ERCOT 7, TDSP 3.  Not valid for CR cancellations	
 	CHA		Changed Agent	
	Customer switched to new CR. MIMO Rules, ERCOT 9, TDSP 3.  Not valid for CR cancellations.
ERCOT Cancel due to Mass Transition. 	
 	COV		Conflicting Authorizations	
	Evaluation conflict while 'Cancel Pending' MIMO Cancellation Rules, ERCOT 15, TDSP 3
Not valid for CR cancellations	
 	EB3		Withdrawn	
	Customer Rescinds Enrollment Request.  Not valid for CR cancellations	
 	MAN		Manual Cancel	
	Cancellation received has been manually cancelled in ERCOTs system.  For ERCOT use only.  	
 	MOX		Move In Same Day	
	Same date as Move In / Force off MIMO Rules, ERCOT 8, TDSP 3
Not valid for CR cancellations	
 	MPC		Past Date Conflict	
	MVI with later requested date completed while permit pending. MIMO Rules, ERCOT 10, TDSP 2, 3.  Not valid for CR cancellations	
 	PNR		Permit Not Received	
	If a Move In in "Permit Pending" status is not scheduled within 20 days of the requested MVI date, ERCOT can cancel the Move In  

Not valid for CR cancellations. For ERCOT Use Only	
 	TWO		Two Party	
	Two Move In's,  two Move Out's, two Switches, or two Drops are requested for "same date" MIMO Rules, ERCOT 6, TDSP 3
Not valid for CR cancellations	
D	REF03	352	Description	X		AN 1/80	
	A free-form description to clarify the related data elements and their content	
	Used to further describe the reason code sent in REF02. Code "A13" requires a text explanation in this element.	
X	REF04	C040	Reference Identifier	O			
	To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier	
X	C04001	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	C04002	127	Reference Identification	M		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
X	C04003	128	Reference Identification Qualifier	X		ID 2/3	
	Code qualifying the Reference Identification	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	C04004	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
X	C04005	128	Reference Identification Qualifier	X		ID 2/3	
	Code qualifying the Reference Identification	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	C04006	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	

	Segment:	REF Reference Identification (ESI ID)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Required
	
		REF~Q5~~10111111234567890ABCDEFGHIJKLMNOPQRS	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	Q5		Property Control Number	
	Electric Service Identifier (ESI ID)	
X	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	ESI ID	
>>	REF03	352	Description	X		AN 1/80	
	A free-form description to clarify the related data elements and their content	
	ESI ID	
X	REF04	C040	Reference Identifier	O			
	To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier	
X	C04001	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	C04002	127	Reference Identification	M		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
X	C04003	128	Reference Identification Qualifier	X		ID 2/3	
	Code qualifying the Reference Identification	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	C04004	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
X	C04005	128	Reference Identification Qualifier	X		ID 2/3	
	Code qualifying the Reference Identification	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	C04006	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	

	Segment:	SE Transaction Set Trailer
	Position:	150
	Loop:
	Level:	Detail
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
	Syntax Notes:
	Semantic Notes:
	Comments:	1	SE is the last segment of each transaction set.
Notes:		Required	
		SE~11~000000001	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	SE01	96	Number of Included Segments	M		N0 1/10	
	Total number of segments included in a transaction set including ST and SE segments	
M	SE02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set