Update all of the TX SET Implementation Guides to allow the receiver of the transaction containing Special Characters to determine to either accept the transaction or to respond with a valid rejection.
ERCOT to add the list of the actual characters from 3.3.2 section 4 into each of the guides. Update all language to remove the ‘may accept the transaction’. TDSP’s will go back and review to make sure it is only the items in section 4 and no other characters missing from this list. Proposed: if we implement a transactional solution, we need to add a specific reject code for the select language characters.
Background
Status:
Withdrawn
Date Submitted:
01/09/2017
Submitter Name:
Kathryn Thurman
Submitter Company:
ERCOT
Emergency:
No
Sections:
All transactions
Description:
Update the all TX SET Implementation Guides to allow the receiver of the transaction containing Special Characters to determine to either accept the transaction or to respond with a valid rejection.
The structure page of every Implementation Guide will be updated to have the following language.
Transaction Set Notes:
For use on an alphanumeric field, TX SET recognizes all characters within the Basic Character Set. Within the Extended Character Set, TX SET recognizes all character sets except all Select Language Characters found in Section 3.3.2 item (4) of X12 Application Control Structure. Exceptions to ANSI Standards for alphanumeric fields are noted in gray box of this Implementation Guide.
Recipients of a transaction(s) containing characters found in item (4) as referenced above may make the determination to accept the transaction(s) or respond with a valid reject.
Reason:
This Change Control will align the Implementation Guides with NPRR 796