Virginia Implementation Standard For Electronic Data Interchange - - - TRANSACTION SET 814 Enrollment Request and Response Ver/Rel 004010 VA 814 Enrollment 1 814e-stan2-3.doc
Summary of Changes August 27, 2001 Version 2-1FINAL February 20, 2002 Version 2-11 FINAL August 14, 2002 Version 2-12 FINAL December 1, 2002 Version 2.2 FINAL January 16, 2003 Version 2.2.1 Issue final version 2.1 for 1/1/2002 Open Access Added AP to the VA Use greybox for REF*SPL In Notes section bullet Historical Usage Requests for Interval Data Accounts, removed comment about AEP honoring requests only at the point of enrollment. For REF*SPL, changed VA Use for responses to Required only for PJM participants. Inserted REF*17 (Summary Interval) needed by AEP. For Data Dictionary, made necessary revisions to be in sync with IG. Made Revisions to N4 (Customer Service Address) and REF segments for CSP Consolidated Billing. Added note for certain participating Electric Cooperatives. February 24, 2003 Added note for BARC, CVEC, C-BEC, MEC, NNEC, SVEC, and SEC- LIN01=05 not Draft Version 2.2.2 supported; changed several NM1 data elements to conditional ; changed AMT01=7N and AMT01=QY to conditional. Approved Draft Version 2.2.2 Version 2.3 VA 814 Enrollment 2 814e-stan2-3.doc
Notes One 814 per Account Multiple LINs Response per LIN Unknown LIN05 codes Secondary Service Request - LIN05=HU Rejection vs. Acceptance with Status Reason code Historical Usage Requests for Interval Data Accounts CSP Account Numbers Each 814 can only be used for one customer account For AEP, each 814 can only be used for one Service Delivery Identification Number (SDID). A customer account may have multiple SDIDs. SDID is used in place of LDC Customer Account Number There may be multiple detail LIN loops for each customer account. It is important that the sender order the LIN loops in the order they would like them processed for all primary services. Refer to the LIN segment within this document for a better understanding of primary and secondary services. The sender may opt to send one service per 814 instead of using multiple LIN segments. There must be one response LIN for each request LIN. Note that DVP does not send 814HU response if the requested 867 is sent. These responses may be created and sent at different times in different 814 transactions, but all LINs must be responded to within the time limits set by the VAEDT. If an LDC receives a request for a code they do not support (or is not defined by these standards), the LDC will respond. They will reject the code with an SNP (Service Not Provided) BARC, CVEC, C-BEC, MEC, NNEC, SVEC, and SEC requests (and responses) are made outside of EDI. A Status Reason code is different than a Rejection Reason code in that it is used to give additional information to the receiving party (an FYI). For example, if a request for Historical Usage is sent and the transaction is valid, but historical usage is not available for that customer, the transaction is accepted and a status reason code is provided to explain that the historical usage would not be sent. Generally, if a transaction is rejected, the sender is expected to follow up and resubmit; whereas if a transaction is accepted with a status reason code, the sender is not expected to take any further action. DVP, Conectiv, NOVEC, REC, BARC, CVEC, C-BEC, MEC, NNEC, SVEC, and SEC requests are made outside of EDI. AEP and AP send 814HU to request summary level, send 814HI to request detail level, send 814HU and HI to request both levels. The only time a LDC will update a CSP account number is from an 814E or 814C. Offcycle Enrollments Un-metered Accounts VA Definitions VA LDC s do not support off cycle enrollment requests. BARC, CVEC, C-BEC, MEC, NNEC, SVEC, and SEC - un-metered accounts are not eligible for CSP services. In Virginia the term LDC means Local Distribution Company and refers to the incumbent utility. In Virginia the term CSP means Competitive Service Provider and refers to the entity that provides a competitive service. An end use customer is a legal entity that receives electric or gas service at one or several service locations, each of which will have a customer account. VA 814 Enrollment 3 814e-stan2-3.doc
How to Use the Implementation Guideline Segment: REF Reference Identification Position: 030 This section is Loop: LIN used to show the Level: Detail X12 Rules for this segment. Max Use: >1 You must look Purpose: To specify identifying information further into the Syntax Notes: 1 At least one of REF02 or REF03 is required. grayboxes below 2 If either C04003 or C04004 is present, then the other is required. for State Rules. 3 If either C04005 or C04006 is present, then the other is required. 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: VA Use: Recommended by UIG Must be identical to account number as it appears on the customer s bill, excluding punctuation (spaces, dashes, etc.). Significant leading and trailing zeros must be included. }~I_I The Notes: section generally contains notes by the Utility Industry Group (UIG). This section is used to show the Request: Required individual State s Rules for Accept Response: Required implementation of this segment. Reject Response: Required I Example: REF*12*2931839200 One or more examples. Des. Element Name X12 Attributes Must Use REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 12 Billing Account LDC-assigned account number for end use customer. Must Use REF02 127 Reference Identificatio n X AN 1/30 Reference information as d efined for a particular Transaction Set or as specified by t he Reference Identification Qualifier I This column shows the use of each data element. If state rules differ, this will show Conditional and the conditions will be explained in the appropriate grayboxes. These are X12 code descriptions, which often do not relate to the information we are trying to send. Unfortunately, X12 cannot keep up with our code needs so we often change the meanings of existing codes. See graybox for the UIG or state definitions. This column shows the X12 attributes for each data element. Please refer to Data Dictionary for individual state rules. M = Mandatory, O= Optional, X = Conditional AN = Alphanumeric, N# = Decimal value, ID = Identification, R = Real VA 814 Enrollment 4 814e-stan2-3.doc
814 General Request, Response or Confirmation Heading Functional Group ID=GE Pos. Seg. Req. Loop Notes and No. ID Name Des. Max. Use Repeat Comments Must Use 010 ST Transaction Set Header M 1 Must Use 020 BGN Beginning Segment M 1 LOOP ID - N1 >1 Must Use 040 N1 Name O 1 n1 060 N3 Address Information O 2 070 N4 Geographic Location O 1 080 PER Administrative Communications Contact O >1 Detail Pos. Seg. Req. Loop Notes and No. ID Name Des. Max. Use Repeat Comments LOOP ID LIN >1 Must Use 010 LIN Item Identification O 1 Must Use 020 ASI Action or Status Indicator O 1 030 REF Reference Identification O >1 040 DTM Date/Time Reference O >1 060 AMT Monetary Amount O >1 LOOP ID - NM1 >1 080 NM1 Individual or Organizational Name O 1 n2 130 REF Reference Identification O >1 Summary Pos. Seg. Req. Loop Notes and No. ID Name Des. Max. Use Repeat Comments Must Use 150 SE Transaction Set Trailer M 1 Transaction Set Notes: 1. The N1 loop is used to identify the transaction sender and receiver, LDC, CSP(s), Customer, and meter owner. The NM1 is used to provide meter level information. VA 814 Enrollment 5 814e-stan2-3.doc
Data Dictionary for Generation Services (LIN05=CE) Appl Field Generation Services (CE) Request and Response Data Dictionary Field Name Description EDI Segment 1 Transaction Set Purpose Code 2 Transaction Reference Number Request = 13 BGN01 Response = 11 A unique transaction identification BGN02 number assigned by the originator of this transaction. This number must be unique over time. Loop / Related EDI Qualifier Data Type X(30) 3 System Date Date that the data was processed by the BGN03 9(8) sender s application system. 4 Original Transaction Transaction Reference Number echoed BGN06 X(30) Reference Number from the Original Request Transaction (BGN02). 5 LDC Name identifier LDC Name identifier N101 = 8S 6 LDC Name LDC Name N102 N1: N101 = 8S X(60) 7 LDC Duns identifier Identifier to indicate DUNS or DUNS+4 N103 = 1 or 9 8 LDC Duns LDC DUNS Number or DUNS+4 Number N104 N1: N101 = 8S N103 = 1 or 9 N106 = 40 or 41 X(1) X(13) 9 LDC Sender / Receiver Indicates whether LDC was sender or N106 = 40 indicator receiver or 41 10 ESP Name code Code to indicate ESP Name N101 = SJ 11 ESP Name ESP s Name N102 N1: N101 = SJ X(60) 12 ESP Duns identifier Identifier to indicate DUNS or DUNS+4 N103 = 1 or 9 13 ESP Duns ESP s DUNS Number or DUNS+4 Number 14 ESP Sender / Receiver indicator Indicates whether ESP was sender or receiver N104 N106 = 40 or 41 N1: N101 = SJ N103 = 1 or 9 N106 = 40 or 41 15 Customer Name code Code to indicate Customer Name N101 = 8R 16 Customer Name Customer Name as it appears on the Customer s Bill 17 Customer Reference Number identifier 18 Customer Reference Number N102 N1: N101 = 8R X(1) X(13) X(35) Customer Reference Number identifier N103 = 92 N1: A reference number assigned by and meaningful to the customer. An example would be Store number N104 N1: N101 = 8R N103 = 92 X(30) 19 Service Address Customer Service Address N301 & N302 N1: N101 = 8R 20 City Customer Service Address N401 N1: N101 = 8R X(55) X(30) VA 814 Enrollment 6 814e-stan2-3.doc
21 State Customer Service Address N402 N1: N101 = 8R 22 Zip Code Customer Service Address N403 N1: N101 = 8R 23 Location Code Service Address County N405 = CO N1: N101 = 8R 24 Location Code Identifier Service Address County Name N406 N1: N101 = 8R 25 Customer Contact identifier Customer contact identifier Note that PER05 through 08 are available for sending more than one communication number. PER01 = IC X(9) X(30) 26 Customer Contact Name Customer Contact Name PER02 PER01=IC X(60) 27 Communication number indicator 28 Customer Communication Number Communication number indicator PER03 = TE, FX or EM Contact Telephone Number (TE), Fax Number (FX) or Email Address (EM) for the customer PER04 N1: N101 = 8R PER01 = IC PER03 = TE, FX or EM 29 Customer Billing Address Code to indicate Customer Billing N101 = BT code Address 30 Customer Billing Name Name on Billing Address N102 N1: N101 = BT 31 Customer Billing Street Address Customer Billing Address N301 & N302 N1: N101 = BT 32 Billing City Customer Billing Address N401 N1: N101 = BT 33 Billing State Customer Billing Address N402 N1: N101 = BT 34 Billing Zip Code Customer Billing Address N403 N1: N101 = BT 35 Billing Country Code Customer Billing Address N404 N1: N101 = BT X(80) X(35) X(55) X(30) 36 Billing Contact identifier Billing contact identifier Note that PER05 through 08 are available for sending more than one communication number. PER01 = IC 37 Billing Contact Name Billing Contact Name PER02 PER01=IC X(60) 38 Communication number indicator 39 Billing Communication Number 40 Third Party Name for copies of notices code Communication number indicator PER03 = TE, FX or EM Contact Telephone Number (TE), Fax Number (FX) or Email Address (EM) related to this billing address Code to indicate Third party Name for copies of notices 41 Third Party Name for copies of notices Name for Third Party to receive copies of notices 42 Street Address Address for Third Party to receive copies of notices 43 Street Address Address for Third Party to receive copies of notices PER04 N1: N101 = BT PER01 = IC PER03 = TE, FX or EM N101 = PK N102 N1: N101 = PK N301 N1: N101 = PK N302 N1: N101 = PK X(9) X(3) X(80) X(35) X(55) X(55) VA 814 Enrollment 7 814e-stan2-3.doc
44 City Address for Third Party to receive copies N401 N1: N101 = X(30) of notices PK 45 State Address for Third Party to receive copies N402 N1: N101 = of notices PK 46 Zip Code Address for Third Party to receive copies N403 N1: N101 = X(9) of notices PK 47 Country Code Address for Third Party to receive copies N404 N1: N101 = X(3) of notices PK 48 Customer Contact identifier Customer contact identifier Note that PER05 through 08 are available for sending more than one PER01 = IC 49 Third Party Name for Contact for Copies of Notices 50 Communication number indicator communication number. Third Party Name for Contact for Copies of Notices Communication number indicator PER03 = TE, FX or EM 51 Communication Number Contact Telephone Number (TE), Fax Number (FX) or Email Address (EM) related to this Third Party. 52 Third Party Name for copies of bills code Code to indicate Third party Name for copies of bills PER02 PER01=IC X(60) PER04 N1: N101 = PK PER01 = IC PER03 = TE, FX or EM N101 = 2C 53 Third Party Name for copies of bills Name for Third Party to receive copies of bills 54 Street Address Address for Third Party to receive copies of bills 55 Street Address Address for Third Party to receive copies of bills 56 City Address for Third Party to receive copies of bills 57 State Address for Third Party to receive copies of bills 58 Zip Code Address for Third Party to receive copies of bills 59 Country Code Address for Third Party to receive copies of bills 60 Customer Contact PER01 = IC identifier 61 Third Party Contact Name for copies of bills 62 Communication number indicator Customer contact identifier Note that PER05 through 08 are available for sending more than one communication number. Name for Third Party Contact to receive copies of bills Communication number indicator PER03 = TE, FX or EM 63 Communication Number Contact Telephone Number (TE), Fax Number (FX) or Email Address (EM) related to this Third Party 64 Line Item Transaction Reference Number Unique Tracking Number for each line item in this transaction. This number must be unique over time. N102 N1: N101 = 2C N301 N1: N101 = 2C N302 N1: N101 = 2C N401 N1: N101 = 2C N402 N1: N101 = 2C N403 N1: N101 = 2C N404 N1: N101 = 2C PER02 N1: N101 = 2C PER04 LIN01 N1: N101= 2C PER01 = IC PER03 = TE, FX or EM X(80) X(35) X(55) X(55) X(30) X(9) X(3) X(60) X(80) X(20) VA 814 Enrollment 8 814e-stan2-3.doc
65 Product / Service ID Qualifier Qualifier indicating product / service LIN02 = SH 66 Product / Service ID Product / Service ID LIN03 = EL 67 Product / Service ID Qualifier 68 Generation Services Indicator Qualifier indicating product / service LIN04 = SH Indicates a customer request to switch to the designated ESP with which he or she has signed a contract for generation services. 69 Action Code Indicates that the transaction is a request, or whether this transaction has been accepted or rejected. LIN05 = CE LIN02 = SH LIN03 = EL LIN04 = SH ASI01= Request: 7 Accept Response: WQ Reject Response: U 70 Maintenance Type Code Maintenance Type Code ASI02 = 021 LIN: ASI02= 021 LIN: X(3) Note that the following REF segments may appear in any order on the actual EDI transaction. 71 Rejection Code identifier Rejection Code identifier REF01 = 7G 72 Rejection Reason Code Code explaining reason for rejection. REF02 LIN: REF01= 7G 73 Rejection Reason Text Text explaining rejection. REF03 LIN: REF01= 7G LIN: X(3) X(80) 74 ESP Account number identifier ESP Account number identifier REF01 = 11 LIN: 75 ESP Account Number ESP Customer Account Number REF02 LIN: REF01= 11 X(30) 76 LDC Account number identifier LDC Account number identifier REF01 = 12 LIN: 77 LDC Account Number LDC Customer Account Number REF02 LIN: REF01= 12 X(30) 78 Service Delivery Identification (SDID) SDID identifier REF01 = Q5 LIN: identifier 79 SDID SDID used by AEP instead of LDC Customer Account Number 80 Old LDC Account number identifier REF03 LIN: REF01 = Q5 X(80) Old LDC Account number identifier REF01 = 45 LIN: 81 Old Account Number Previous LDC Customer Account Number REF02 LIN: REF01= 45 X(30) 82 Payment arrangement identifier Payment arrangement identifier REF01 = 4N LIN: 83 Payment Arrangement Used to indicate whether customer has an active payment arrangement with the LDC. 84 LDC Billing Cycle identifier REF02= Y or N LDC Billing Cycle identifier REF01 = BF 85 LDC Billing Cycle LDC Cycle on which the bill will be rendered REF02 LIN: REF01= 4N LIN: LIN: REF01= BF VA 814 Enrollment 9 814e-stan2-3.doc X(1)
86 LDC Billing Cycle special condition Indicates LDC Bill Cycle has frequency other than monthly REF03 87 Billing Type identifier Billing Type identifier REF01 = BLT 88 Billing Type Indicates type of billing REF02 LDC consolidated Billing (REF02=LDC) ESP consolidated Billing (REF02=ESP) Dual bills (REF02=DUAL) 89 Billing Calculator identifier 90 Billing Calculation Method 91 LDC Budget Billing Status identifier 92 LDC Budget Billing Status Billing Calculator identifier REF01 = PC Indicates party to calculate bill. REF02 LDC calculates bill (REF02=LDC) - Each party calculates its portion of the bill (REF02=DUAL) LDC Budget Billing Status identifier REF01 = NR Transmits the current budget billing status shown for this customer on the LDC system. REF02= Y or N 93 PJM LMP Bus identifier PJM LMP Bus identifier REF01 = SPL 94 PJM LMP Bus Point at which the customer is connected REF03 to the transmission grid 95 Customer Contract Customer Contract Effective Date/Time DTM01 = Effective Date/Time identifier 129 identifier 96 Customer Contract Effective Date/Time 97 Service Period Start identifier Date/Time ESP entered into contract with customer used to determine which supplier is the last one in. CCYYMMDD HHMM ZZ DTM02, DTM03 & DTM04 Service Period Start identifier DTM01 = 150 98 Service Period Start Date on which energy is expected to flow to this customer for the designated ESP. DTM02 LIN: REF01= X(3) BF LIN: LIN: REF01= BLT LIN: LIN: REF01= PC LIN: LIN: REF01= NR LIN: LIN: REF01= SPL LIN: LIN: DTM01 = 129 LIN: LIN: DTM01 = 150 X(3) X(4) X(4) X(1) X(3) X(80) X(3) See EDI Guide X(3) 9(8) Note that the following AMT segments may appear in any order on the actual EDI transaction. 99 Participating Interest identifier Participating Interest identifier AMT01 = 7N 100 Participating Interest Percent of the customer s load the ESP is requesting service for. If an ESP is only responsible for half of the customer s eligible load, the amount.5 will be returned. 101 Eligible Load Percentage identifier AMT02 Eligible Load Percentage identifier AMT01 = QY 102 Eligible Load Percentage Percent of the customer s load that is eligible for competition. For example, if 2/3 of the customer s load is eligible, the amount.66667 will be returned. AMT02 LIN: LIN: AMT01= 7N LIN: LIN: AMT01= QY 9(1).9999 9 9(1).9999 9 VA 814 Enrollment 10 814e-stan2-3.doc
103 Percent Tax Exemption identifier Percent Tax Exemption identifier AMT01 = DP 104 Percent Tax Exemption Customer s Tax Exemption Percentage Residential usually 100% (send 1), Commercial/Industrial anything other than 0% requires you secure tax exemption certificate. (e.g., if 50% send.5) 105 Capacity Obligation identifier AMT02 Capacity Obligation identifier AMT01 = KC 106 Capacity Obligation Peak load contributions provided to PJM AMT02 for Installed Capacity calculation (coincident with PJM s peak) 107 Transmission Obligation Transmission Obligation identifier AMT01 = identifier KZ 108 Transmission Obligation Customer s peak load contribution AMT02 provided to PJM for the transmission service calculation (coincident with LDC peak) 109 Number of Months identifier Number of Months identifier AMT01 = LD 110 Number of Months Number of Months over which the Total kwh (AMT*TA) and/or Peak Demand (AMT*MA) are calculated. AMT02 111 Peak Demand identifier Peak Demand identifier AMT01 = LIN: LIN: AMT01= DP LIN: LIN: AMT01= KC LIN: LIN: AMT01= KZ LIN: LIN: AMT01= LD MA 112 Peak Demand (12 mo) Highest usage in the last 12 months (kw). AMT02 LIN: AMT01= MA 113 Total kwh identifier Total kwh identifier AMT01 = TA 114 Total kwh Total kwh for the number of months specified in the AMT*LD segment (actual or estimated). AMT02 LIN: LIN: AMT01= TA 9(1).9(4) 9(9).99 9(9).99 9(2) 9(11).999 115 Load Mgt - AC Identifier Load Mgt. AC Identifier AMT01 =5J 116 Load Mgt - AC Indicates number of air conditioners on this account that are on load management program AMT02 LIN: AMT01 = 5J 117 Load Mgt - WH Identifier Load Mgt - WH Identifier AMT01=L0 118 Load Mgt - WH Indicates number of water heaters on this account that are on load management program 119 Entity Type Code Entity Type Code NM101= MQ LIN: AMT01 = L0 NM101= MQ NM102= 3 NM108= 32 120 Entity Type Qualifier Entity Type Qualifier NM102= 3 NM101= MQ NM102= 3 NM108= 32 121 Identification Code Qualifier Identification Code Qualifier NM108= 32 NM101= MQ NM102= 3 NM108= 32 9(15) 9(2) 9(2) X(1) VA 814 Enrollment 11 814e-stan2-3.doc
122 Meter Number Number which identifies meter Request: NM109= ALL Response: NM109= [meter number] or UNMETER ED NM101= MQ NM102= 3 NM108= 32 X(30) Note that the following REF segments may appear in any order on the actual EDI transaction. 123 Profile Group identifier Profile Group identifier REF01= LO NM1: 124 Profile Group A code for the Load Profile used for this customer. Differs by LDC. Codes posted on LDC s Web site. REF02 NM1: REF01= LO X(30) 125 LDC Rate Code identifier LDC Rate Code identifier REF01= NH NM1: 126 LDC Rate Code Code indicating the rate a customer is being charged by LDC per tariff. Codes posted on LDC s Web site REF02 NM1: REF01= NH X(30) 127 LDC Rate Subclass Code LDC Rate Subclass Code identifier REF01= PR NM1: identifier 128 LDC Rate Subclass Code Used to provide further classification of a REF02 NM1: REF01= X(30) rate. PR 129 ESP Rate Code identifier ESP Rate Code identifier REF01= RB NM1: 130 ESP Rate Code ESP rate code for customer REF02 NM1: REF01= X(30) RB 131 LDC Meter Cycle LDC Meter Cycle identifier REF01= TZ NM1: identifier 132 LDC Meter Cycle LDC Cycle on which the meter will be REF02 NM1: REF01= read TZ 133 Meter Type identifier Meter Type identifier REF01= MT NM1: 134 Meter Type Type of Meter REF02 NM1: REF01= MT X(5) The following three fields each require that the Meter Type be shown in REF03: 135 Meter Constant/Meter Multiplier identifier 136 Meter Constant/Meter Multiplier 137 Number of Dials / Digits identifier 138 Number of Dials / Digits and related decimal positions 139 Type of metering identifier Meter Constant/Meter Multiplier identifier Some factor multiplied by the meter reading to give billed usage. REF01= 4P NM1: REF02 NM1: REF01= 4P REF03 = Meter Type (See REF*MT) 9(9).99 Number of Dials / Digits identifier REF01= IX NM1: Needed to determine usage if meter reading rolls over during the billing period. Number of dials on the meter displayed as the number of dials to the left of the decimal, a decimal point, and number of dials to the right of the decimal. REF02 NM1: REF01= IX REF03 = Meter Type (See REF*MT) Type of metering identifier REF01= TU NM1: 9.9 VA 814 Enrollment 12 814e-stan2-3.doc
140 Type of metering used for billing Indicates the type of metering information that will be sent on the 867 transaction. Example: 41 = Off Peak REF02 NM1: REF01 = TU REF03 = Meter Type (See REF*MT) 141 Time Zone for Meter Identifier Time Zone for Meter Identifier REF01 = GE NM1: 142 Time Zone for Meter Indicates time zone in which meter is located REF02 NM1: REF01 = GE VA 814 Enrollment 13 814e-stan2-3.doc
Data Dictionary for Historical Usage Requests (LIN05=HU) Appl Field Request for Historical Usage (HU) Request and Response Data Dictionary Field Name Description EDI Segment Loop / Related EDI Qualifier 1 Transaction Set Purpose Code Request = 13 Response = 11 BGN01 2 Transaction Reference A unique transaction identification BGN02 Number number assigned by the originator of this transaction. This number must be unique over time. 3 System Date Date that the data was processed by the sender s application system. 4 Original Transaction Reference Number Transaction Reference Number echoed from the Original Request Transaction (BGN02). Data Type X(30) BGN03 9(8) BGN06 X(30) 5 LDC Name identifier LDC Name identifier N101 = 8S 6 LDC Name LDC Name N102 N1: N101 = 8S X(60) 7 LDC Duns identifier Identifier to indicate DUNS or DUNS+4 8 LDC Duns LDC DUNS Number or DUNS+4 Number 9 LDC Sender / Receiver indicator Indicates whether LDC was sender or receiver N103 = 1 or 9 N104 N106 = 40 or 41 X(1) N1: N101 = 8S X(13) N103 = 1 or 9 N106 = 40 or 41 N1: 10 ESP Name code Code to indicate ESP Name N101 = SJ 11 ESP Name ESP s Name N102 N1: N101 = SJ X(60) 12 ESP Duns identifier Identifier to indicate DUNS or DUNS+4 13 ESP Duns ESP s DUNS Number or DUNS+4 Number N103 = 1 or 9 N1: X(1) N104 N1: N101 = SJ X(13) N103 = 1 or 9 N106 = 40 or 41 N1: 14 ESP Sender / Receiver Indicates whether ESP was sender or N106 = 40 or indicator receiver 41 15 Customer Name code Code to indicate Customer Name N101 = 8R 16 Customer Name Customer Name as it appears on the N102 N1: N101 = 8R X(35) Customer s Bill 17 Line Item Transaction Reference Number 18 Product / Service ID Qualifier Unique Tracking Number for each line item in this transaction. This number must be unique over time. LIN01 Qualifier indicating product / service LIN02 = SH X(20) 19 Product / Service ID Product / Service ID LIN03 = EL 20 Product / Service ID Qualifier Qualifier indicating product / service LIN04 = SH VA 814 Enrollment 14 814e-stan2-3.doc
21 Historical Usage Indicates an ESP request to obtain historical usage information for this customer. Historical Usage will be returned on an EDI 867 transaction. 22 Action Code Indicates that the transaction is a request, or whether this transaction has been accepted or rejected. LIN05 = HU ASI01= Request: 7 Accept Response: WQ Reject Response: U LIN02 = SH LIN03 = EL LIN04 = SH LIN: ASI02= 029 23 Maintenance Type Maintenance Type Code ASI02 = 029 LIN: X(3) Code 24 Rejection Code identifier Rejection Code identifier REF01 = 7G LIN: 25 Rejection Reason Code Code explaining reason for rejection. REF02 LIN: REF01= 7G X(3) 26 Rejection Reason Text Text explaining rejection. REF03 LIN: REF01= 7G X(80) 27 Status Reason Code Status Reason Code identifier REF01 = 1P LIN: identifier 28 Status Reason Code Code to provide status information for a secondary service. REF02 LIN: REF01= 1P X(3) 29 Status Reason Text Text to provide status information. REF03 LIN: REF01= 1P X(80) 30 ESP Account number ESP Account number identifier REF01 = 11 LIN: identifier 31 ESP Account Number ESP Customer Account Number REF02 LIN: REF01= X(30) 11 32 LDC Account number identifier LDC Account number identifier REF01 = 12 LIN: 33 LDC Account Number LDC Customer Account Number REF02 LIN: REF01= 12 X(30) 34 Service Delivery Identification (SDID) SDID identifier REF01 = Q5 LIN: identifier 35 SDID SDID used by AEP instead of LDC Customer Account Number 36 Old LDC Account Number identifier REF03 LIN: REF01 = Q5 X(80) Old LDC Account Number identifier REF01 = 45 LIN: 37 Old Account Number Previous LDC Customer Account Number REF02 LIN: REF01= 45 X(30) 38 URL identifier URL identifier REF01 = URL LIN: X(3) 39 URL LDC s URL (web address) for REF03 LIN: REF01= X(80) Historical Interval Data URL VA 814 Enrollment 15 814e-stan2-3.doc
Data Dictionary for Summary Interval (LIN05=SI) Appl Field Request for Summary Interval Information (SI) Request and Response Data Dictionary Field Name Description EDI Segment 1 Transaction Set Purpose Code 2 Transaction Reference Number Request = 13 Response = 11 A unique transaction identification number assigned by the originator of this transaction. This number must be unique over time. 3 System Date Date that the data was processed by the sender s application system. 4 Original Transaction Reference Number Transaction Reference Number echoed from the Original Request Transaction (BGN02). BGN01 BGN02 Loop / Related EDI Qualifier Data Type X(30) BGN03 9(8) BGN06 X(30) 5 LDC Name identifier LDC Name identifier N101 = 8S 6 LDC Name LDC Name N102 N1: N101 = 8S X(60) 7 LDC Duns identifier Identifier to indicate DUNS N103 = 1 or 9 X(1) or DUNS+4 8 LDC Duns LDC DUNS Number or DUNS+4 Number N104 X(13) N1: N101 = 8S N103 = 1 or 9 N106 = 40 or 41 9 LDC Sender / Indicates whether LDC was N106 = 40 or Receiver indicator sender or receiver 41 10 ESP Name code Code to indicate ESP Name N101 = SJ 11 ESP Name ESP s Name N102 N1: N101 = SJ X(60) 12 ESP Duns identifier Identifier to indicate DUNS or DUNS+4 13 ESP Duns ESP s DUNS Number or DUNS+4 Number 14 ESP Sender / Receiver Indicates whether ESP was indicator sender or receiver 15 Customer Name code Code to indicate Customer Name 16 Customer Name Customer Name as it appears on the Customer s Bill 17 Line Item Transaction Reference Number 18 Product / Service ID Qualifier Unique Tracking Number for each line item in this transaction. This number must be unique over time. Qualifier indicating product / service N103 = 1 or 9 N104 N106 = 40 or 41 N101 = 8R N102 LIN01 LIN02 = SH N1: N101 = SJ N103 = 1 or 9 N106 = 40 or 41 X(1) X(13) N1: N101 = 8R X(35) X(20) 19 Product / Service ID Product / Service ID LIN03 = EL 20 Product / Service ID Qualifier indicating product / LIN04 = SH Qualifier service VA 814 Enrollment 16 814e-stan2-3.doc
21 Summary Interval Information Indicates an ESP request to obtain interval data at the summary level only. 22 Action Code Indicates that the transaction is a request, or whether this transaction has been accepted or rejected. LIN05 = SI ASI01= Request: 7 Accept Response: WQ Reject Response: U LIN02 = SH LIN03 = EL LIN04 = SH LIN: ASI02= 021 23 Maintenance Type Maintenance Type Code ASI02 = 021 LIN: X(3) Code 24 Rejection Code identifier Rejection Code identifier REF01 = 7G LIN: 25 Rejection Reason Code Code explaining reason for rejection. REF02 LIN: REF01= 7G X(3) 26 Rejection Reason Text Text explaining rejection. REF03 LIN: REF01= 7G X(80) 27 Status Reason Code identifier Status Reason Code identifier REF01 = 1P LIN: 28 Status Reason Code Code to provide status REF02 LIN: REF01= X(3) information for a secondary service. 1P 29 Status Reason Text Text to provide status REF03 LIN: REF01= X(80) information. 1P 30 ESP Account number identifier ESP Account number identifier REF01 = 11 LIN: 31 ESP Account Number ESP Customer Account REF02 LIN: REF01= X(30) Number 11 32 LDC Account number LDC Account number REF01 = 12 LIN: identifier identifier 33 LDC Account Number LDC Customer Account Number 34 Service Delivery Identification (SDID) identifier 35 SDID SDID used by AEP instead of LDC Customer Account Number 36 Old LDC Account Old LDC Account Number Number identifier identifier 37 Old Account Number Previous LDC Customer Account Number 38 Interval Reporting Level identifier 39 Interval Reporting Level REF02 LIN: REF01= 12 X(30) SDID identifier REF01 = Q5 LIN: Interval Reporting Level identifier Indicates that interval data will be reported at the summary level. REF03 LIN: REF01 = Q5 X(80) REF01 = 45 LIN: REF02 LIN: REF01= 45 X(30) REF01 = 17 LIN: REF02= SUMMARY LIN: REF01= 17 X(30) VA 814 Enrollment 17 814e-stan2-3.doc
Data Dictionary for Special Meter Read (LIN05=SR) Appl Field Special Meter Read (SR) Request and Response Data Dictionary Field Name Description EDI Segment 1 Transaction Set Purpose Code 2 Transaction Reference Number Loop / Related EDI Qualifier Data Type Request = 13 Response = 11 BGN01 A unique transaction identification BGN02 X(30) number assigned by the originator of this transaction. This number must be unique over time. BGN03 9(8) 3 System Date Date that the data was processed by the sender s application system. 4 Original Transaction Reference Number Transaction Reference Number echoed from the Original Request Transaction (BGN02). BGN06 X(30) 5 LDC Name identifier LDC Name identifier N101 = 8S 6 LDC Name LDC Name N102 N1: N101 = 8S X(60) 7 LDC Duns identifier Identifier to indicate DUNS or DUNS+4 N103 = 1 or 9 X(1) 8 LDC Duns LDC DUNS Number or DUNS+4 Number N104 X(13) 9 LDC Sender / Receiver indicator Indicates whether LDC was sender or receiver N106 = 40 or 41 N1: N101 = 8S N103 = 1 or 9 N106 = 40 or 41 10 ESP Name code Code to indicate ESP Name N101 = SJ 11 ESP Name ESP s Name N102 N1: N101 = SJ X(60) 12 ESP Duns identifier Identifier to indicate DUNS or DUNS+4 13 ESP Duns ESP s DUNS Number or DUNS+4 Number N103 = 1 or 9 N104 N1: N101 = SJ N103 = 1 or 9 N106 = 40 or 41 X(1) X(13) 14 ESP Sender / Indicates whether ESP was sender N106 = 40 Receiver indicator or receiver or 41 15 Customer Name Code to indicate Customer Name N101 = 8R code 16 Customer Name Customer Name as it appears on the Customer s Bill N102 N1: N101 = 8R X(35) 17 Line Item Unique Tracking Number for each LIN01 X(20) Transaction Reference Number line item in this transaction. This number must be unique over time. 18 Product / Service ID Qualifier Qualifier indicating product / service LIN02 = SH 19 Product / Service ID Product / Service ID LIN03 = EL 20 Product / Service ID Qualifier indicating product / LIN04 = SH Qualifier service 21 Special Read Request Indicator Indicates an ESP request to obtain special meter reading. LIN05 = SR LIN02 = SH LIN03 = EL LIN04 = SH VA 814 Enrollment 18 814e-stan2-3.doc
22 Action Code Indicates that the transaction is a request, or whether this transaction has been accepted or rejected. ASI01= Request: 7 LIN: ASI02= 021 Accept Response: WQ Reject Response: U Maintenance Type Code ASI02 = 021 LIN: X(3) 23 Maintenance Type Code 24 Rejection Code identifier 25 Rejection Reason Code 26 Rejection Reason Text 27 Status Reason Code identifier 28 Status Reason Code Code to provide status information for a secondary service. Rejection Code identifier REF01 = 7G LIN: Code explaining reason for rejection. REF02 LIN: REF01= 7G Text explaining rejection. REF03 LIN: REF01= 7G X(3) X(80) Status Reason Code identifier REF01 = 1P LIN: REF02 LIN: REF01= 1P 29 Status Reason Text Text to provide status information. REF03 LIN: REF01= 1P 30 ESP Account number identifier 31 ESP Account Number 32 LDC Account number identifier 33 LDC Account Number 34 Service Delivery Identification (SDID) identifier 35 SDID SDID used by AEP instead of LDC Customer Account Number 36 Old LDC Account Number identifier 37 Old Account Number 38 Requested Read Date identifier 39 Requested Read Date X(3) X(80) ESP Account number identifier REF01 = 11 LIN: ESP Customer Account Number REF02 LIN: REF01= 11 X(30) LDC Account number identifier REF01 = 12 LIN: LDC Customer Account Number REF02 LIN: REF01= 12 X(30) SDID identifier REF01 = Q5 LIN: Old LDC Account Number identifier Previous LDC Customer Account Number REF03 LIN: REF01 = Q5 REF01 = 45 LIN: REF02 Requested Read Date identifier DTM01 = MRR Date ESP is requesting special DTM02 / meter read to be made. DTM03 / CCYYMMDD (optionally HHMM DTM04 Zone) LIN: REF01= 45 LIN: DTM01 = MRR X(80) X(30) X(3) 9(8) VA 814 Enrollment 19 814e-stan2-3.doc
Data Dictionary for Meter Information (LIN05=MI) Appl Field Request for Meter Information (MI) Request and Response Data Dictionary Field Name Description EDI Segment 1 Transaction Set Purpose Code Request = 13 Response = 11 BGN01 2 Transaction Reference A unique transaction BGN02 Number identification number assigned by the originator of this transaction. This number must be unique over time. 3 System Date Date that the data was processed by the sender s application system. 4 Original Transaction Reference Number Transaction Reference Number echoed from the Original Request Transaction (BGN02). Loop / Related EDI Qualifier Data Type X(30) BGN03 9(8) BGN06 X(30) 5 LDC Name identifier LDC Name identifier N101 = 8S 6 LDC Name LDC Name N102 N1: N101 = 8S X(60) 7 LDC Duns identifier Identifier to indicate DUNS N103 = 1 or X(1) or DUNS+4 9 8 LDC Duns LDC DUNS Number or DUNS+4 Number N104 X(13) 9 LDC Sender / Receiver indicator Indicates whether LDC was sender or receiver N106 = 40 or 41 N1: N101 = 8S N103 = 1 or 9 N106 = 40 or 41 10 ESP Name code Code to indicate ESP Name N101 = SJ 11 ESP Name ESP s Name N102 N1: N101 = SJ X(60) 12 ESP Duns identifier Identifier to indicate DUNS or DUNS+4 13 ESP Duns ESP s DUNS Number or DUNS+4 Number 14 ESP Sender / Receiver Indicates whether ESP was indicator sender or receiver 15 Customer Name code Code to indicate Customer Name 16 Customer Name Customer Name as it appears on the Customer s Bill 17 Line Item Transaction Unique Tracking Number for Reference Number each line item in this transaction. This number must be unique over time. 18 Product / Service ID Qualifier Qualifier indicating product / service N103 = 1 or 9 N104 N106 = 40 or 41 N101 = 8R N1: N101 = SJ N103 = 1 or 9 N106 = 40 or 41 N102 N1: N101 = 8R LIN01 LIN02 = SH X(1) X(13) X(35) X(20) 19 Product / Service ID Product / Service ID LIN03 = EL VA 814 Enrollment 20 814e-stan2-3.doc
20 Product / Service ID Qualifier 21 Meter Data Request Indicator Qualifier indicating product / LIN04 = SH service Indicates an ESP request to LIN05 =MI LIN02 = SH obtain meter information for LIN03 = EL this customer. The meter LIN04 = SH information will be returned on the transaction set 650. 22 Action Code Indicates that the transaction is a request, or whether this transaction has been accepted or rejected. ASI01= LIN: ASI02= Request: 7 029 Accept Response: WQ Reject Response: U 23 Maintenance Type Maintenance Type Code ASI02 = 029 LIN: X(3) Code 24 Rejection Code identifier Rejection Code identifier REF01 = 7G LIN: 25 Rejection Reason Code Code explaining reason for rejection. REF02 LIN: REF01= 7G X(3) 26 Rejection Reason Text Text explaining rejection. REF03 LIN: REF01= 7G X(80) 27 Status Reason Code identifier Status Reason Code identifier REF01 = 1P LIN: 28 Status Reason Code Code to provide status REF02 LIN: REF01= information for a secondary 1P service. 29 Status Reason Text Text to provide status REF03 LIN: REF01= information. 1P 30 ESP Account number ESP Account number REF01 = 11 LIN: identifier identifier 31 ESP Account Number ESP Customer Account REF02 LIN: REF01= Number 11 32 LDC Account number identifier LDC Account number identifier REF01 = 12 LIN: X(3) X(80) X(30) 33 LDC Account Number LDC Customer Account Number REF02 LIN: REF01= 12 X(30) 34 Service Delivery Identification (SDID) identifier SDID identifier REF01 = Q5 LIN: 35 SDID SDID used by AEP instead REF03 LIN: REF01 = X(80) of LDC Customer Account Number Q5 36 Old LDC Account Number identifier Old LDC Account Number identifier 37 Old Account Number Previous LDC Customer Account Number REF01 = 45 LIN: REF02 LIN: REF01= 45 X(30) VA 814 Enrollment 21 814e-stan2-3.doc
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: 1 The transaction set identifier (ST01) 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: VA Use: Required Example: ST*814*000000001 Must Use ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 814 General Request, Response or Confirmation Must Use 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 VA 814 Enrollment 22 814e-stan2-3.doc
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. 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: VA Use: Required Request Example: BGN*13*199904011956531*19990401** (Note: BGN06 not used in the request.) Response Example: BGN*11*199904020830531*19990402***199904011956531 (Note: BGN06 is optional on the response.) Must Use BGN01 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 11 Response Signifies that the requested service will be addressed as described in this transaction. 13 Request Must Use 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 should be unique over all time. Must Use BGN03 373 Date M DT 8/8 Date (CCYYMMDD) The transaction creation date the date that the data was processed by the application system. Optional 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 If used, refers to the BGN02 identification number of the original Request. Not used on the request. Optional on the response. VA 814 Enrollment 23 814e-stan2-3.doc
Segment: N1 Name Position: 040 Loop: N1 Level: Heading: 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. 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. VA Use: Request: Required Response: Required Request Example: N1*8S*LDC COMPANY*1*007909411**40 (as Receiver) Response Example: N1*8S*LDC COMPANY*1*007909411**41 (as Sender) Must Use 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) Used to identify the LDC Must Use N102 93 Name X AN 1/60 Free-form name LDC Company Name Must Use 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 Must Use N104 67 Identification Code X AN 2/80 Code identifying a party or other code LDC D-U-N-S Number or D-U-N-S + 4 Number Optional N106 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or an individual. Used in addition to the N103 and N104 to identify the transaction sender and receiver when more than two parties are identified by N1 loops. 40 Receiver Entity to accept transmission 41 Submitter Entity transmitting transaction set VA 814 Enrollment 24 814e-stan2-3.doc
Segment: N1 Name Position: 040 Loop: N1 Level: Heading: 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. 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. VA Use: Request: Required Response: Required Request Example: N1*SJ*ESP COMPANY*9*007909422ESP1**41 (as Sender) Response Example: N1*SJ*ESP COMPANY*9*007909422ESP1**40 (as Receiver) Must Use N101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual SJ Service Provider ESP Must Use N102 93 Name X AN 1/60 Free-form name ESP Company Name Must Use N103 66 Identification Code Qualifier X ID ½ 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 Must Use N104 67 Identification Code X AN 2/80 Code identifying a party or other code ESP D-U-N-S Number or D-U-N-S + 4 Number Optional N106 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or an individual. Used in addition to the N103 and N104 to identify the transaction sender and receiver when more than two parties are identified by N1 loops. 40 Receiver Entity to accept transmission 41 Submitter Entity transmitting transaction set VA 814 Enrollment 25 814e-stan2-3.doc
Segment: N1 Name Position: 040 Loop: N1 Level: Heading: 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. 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. VA Use: Request: Required Response: Required Example: N1*8R*JONES,JOHN,B*92*1210 Must Use 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 Used to identify the customer associated with the LDC service account Must Use N102 93 Name X AN 1/60 Free-form name Customer Name as found on the customer bill. For individual name populate as last, first, middle, prefix, suffix with comma as delimiter. Allegheny and DVP will validate on first 4 characters of last name or company name, as found on the customer bill. Conditional N103 66 Identification Code Qualifier X ID ½ Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent Reference Number assigned by and meaningful to the customer. Note that this number is assigned to the LDC and may or may not be applicable to the ESP. Condition: The N103 and N104 are optional only on the Accept Response transaction. This information is provided at the point of time in the enrollment; an 814 change will not be processed if this data changes. Conditional N104 67 Identification Code X AN 2/80 Code identifying a party or other code Reference Number assigned by and meaningful to the customer. Note that this number is assigned to the LDC and may or may not be applicable to the ESP. Condition: The N103 and N104 are optional only on the Accept Response transaction. This information is provided at the point of time in the enrollment; an 814 change will not be processed if this data changes. This information may also appear on a Rate Ready 810. VA 814 Enrollment 26 814e-stan2-3.doc
Segment: N3 Address Information Position: 060 Loop: N1 Level: Heading: Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Comments: VA Use: Request: Not Used CE Accept Response: Required for Customer Service Address All Other Responses: Not Used VA Use: For a freeflow address, place entirely within N301-02, leaving N4 empty Example: N3*123 N MAIN ST*MS FLR13 Must Use N301 166 Address Information M AN 1/55 Address information Optional N302 166 Address Information O AN 1/55 Address information VA 814 Enrollment 27 814e-stan2-3.doc
Segment: N4 Geographic Location Position: 070 Loop: N1 Level: Heading: Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. 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. VA Use: Request: CE Accept Response: All Other Responses: Not Used Required for Customer Service Address Not Used Example: N4*ANYTOWN*VA*18111 Must Use N401 19 City Name O AN 2/30 Free-form text for city name Must Use N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency Must Use N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) Conditional N405 309 Location Qualifier X ID ½ Code identifying type of location Condition: N405 and N406 are required for CSP Consolidated Billing; otherwise, they are optional. CO County/Parish and State Service Address County / Parish Conditional N406 310 Location Identifier O AN 1/30 Code which identifies a specific location Service Address County / Parish Condition: N405 and N406 are required for CSP Consolidated Billing; otherwise, they are optional. VA 814 Enrollment 28 814e-stan2-3.doc
Segment: PER Administrative Communications Contact Position: 080 Loop: N1 Level: Heading: Max Use: >1 Purpose: To identify a person or office to which administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Comments: VA Use: Example: Request: CE Accept Response: All Other Responses: PER*IC**TE*8005559876 Not Used Optional for Service Address Not Used Must Use PER01 366 Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named IC Information Contact Optional PER02 93 Name O AN 1/60 Free-form name Must Use PER03 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number EM Electronic Mail FX Facsimile TE Telephone Must Use PER04 364 Communication Number X AN 1/80 Complete communications number including country or area code when applicable Optional PER05 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number EM Electronic Mail FX Facsimile TE Telephone Optional PER06 364 Communication Number X AN 1/80 Complete communications number including country or area code when applicable Optional PER07 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number EM Electronic Mail FX Facsimile TE Telephone Optional PER08 364 Communication Number X AN 1/80 Complete communications number including country or area code when applicable VA 814 Enrollment 29 814e-stan2-3.doc