7004DD05

Due Date Less Than Current Date @

A due date cannot be less then the current date.

Ensure that the value populated on the DDD field on the LSR Form is equal to, or greater than today's date. In short: you may not request that your LSR be completed on a day that has already past. Please check the Interval Guidelines for the appropriate due date.

back to top

7020BL02

Invalid Blocking Option@ - LSR in query

This error message is advising that the Blocking option on the Local Service Request is invalid. Block value does not have a corresponding Blocking USOC on the matrix for that REQTYP, jurisdiction, and TOS.

Ensure that the Blocking FID is a valid blocking option. Please refer to the Business Rules. The Business Rules/Blocking Matrix (Appendix 3.4) will indicate the valid options and conditions for correct field entry based on REQTYP and jurisdiction.

back to top

7020BL03

Block option to be added is already present on CSR@ - LSR in Query

This error message is advising that the Block being requested on the Local Service Request is currently on the Customer Service Record.

You will need to obtain a current CSR and compare the information to the Blocking FID on your LSR. You should ensure that the Blocking information on your LSR is not duplicated.

To help you identify the correct Blocking FID, refer to the Business Rules Appendices Section. The Blocking Matrices are located in Section 3.4 of the Order Appendices.

back to top

7020BL04

Invalid BLKD FIDS Combo

This error message is advising that the Block option, identified on the Local Service Request, to be deleted is not on the Customer Service Record.

Obtain a current CSR to validate if the correct USOC for the blocking option is populated on the LSR. If the correct USOC is on the LSR a SUP must be issued to correct or cancel the LSR. To ensure that the Blocking FID is a valid blocking option. Please refer to the Business Rules. The Business Rules/Blocking Matrix (Appendix 3.4) will indicate the valid options and conditions for correct field entry based on REQTYP and jurisdiction.

back to top

7020BL07

INVALID BLKD FIDS COMBO

This error code will indicate an invalid Blocking FID combo on the order.

You will need to obtain a current CSR and compare the information to the Blocking FID on your LSR. Ensure that the Blocking FID is not duplicated or mutually exclusive to another Block.

To help you identify the correct Blocking FID, please refer to the Business Rules. The Business Rules/Blocking Matrix (SEC 3.4) will indicate the valid options and conditions for correct field entry.

back to top

7020BT06

EATN does not equal the BTN

This error message is advising that the Existing Account Telephone Number on EU Form of the Local Service Request does not match the Billing Telephone Number.

You will need to obtain a current CSR to validate the BTN and/or the EATN on the CSR to ensure it has been correctly populated on the LSR.

back to top

7020CT04

This Service is not eligible to be Migrated to UNE-Pal

@ Not valid for migration to UNE-PAL

Check the LSR to validate that the correct TOS (class of service) has been issued on the LSR. The TOS submitted cannot be migrated to UNE-Pal. A Sup may need to be issued to cancel the LSR.

back to top

7020FU02

USOC: XXXXX already exists on TN: XXX XXX-XXXX

The USOC identified in the error message is already on the Telephone Number populated on the Local Service Request.

Obtain a current CSR. Validate if the correct USOC is populated on the FA field on the RS/PS Form. If the correct USOC is being ordered validate if the USOC already exists on the account.

back to top

7020FU03

USOC: XXXXX already exists on TN: XXX XXX-XXXX

The error message will identify the feature is invalid for the New Market Segment.

When an order is being issued to change the Account Structure, you should validate that the features being retained on the new Class of Service are valid for that type of service. For example, when changing from a residence service to a business service account, the feature @ is not offered on a business account.

back to top

7020HT07

@' Not found @'

The error code will identify what is not found on the Local Service Request.

The feature or service being ordered is not valid or compatible with product being ordered.

Obtain applicable USOC for features and services being ordered. The USOC guide will identify if another feature or FID is required or prohibited.

You should also reference your local Tariff for additional feature requirements.

back to top

7020HT08

USOC XXX only allowed on last line of hunt group - LSR in Query

The USOC identified in the error message is only allowed on the last line of the Hunt Group of the Local Service Request

Check the LSR and determine if the product or service is in conflict with the hunt feature. Check to make sure that the USOC is on the last line of the TN with the hunt group.

back to top

7020HT09

USOC XXX only allowed on last line of hunt group - LSR in Query

This error message is advising that the USOC noted in the error description cannot be ordered with Circular Hunting.

Check the central office equipment to determine if circular hunt is being ordered in a 1A/5ess central office. If a circular hunting arrangement exists the USOC for CF2 cannot be added to the same account and the LSR has to be resubmitted/cancelled.

back to top

7020HT10

USOC XXX not allowed on any line with hunting - LSR IN QUERY

This error message is advising that the USOC identified in the error message is not allowed on any line with hunting.

Obtain a CSR to identify if the account telephone number on this LSR has hunting. If a hunting arrangement exists the USOC XXX cannot be added to the account and the LSR has to be resubmitted/cancelled.

back to top

7020HT13

HTN not found in Hunt Group on CSR

This error message indicates that the Hunting Telephone Number on the Local Service Request is invalid or doesn't exist.

You will need to obtain a current CSR and compare the information with your LSR. You should ensure that the hunting information on your LSR is correct. A SUP is required to correct the Hunting Telephone Number.

back to top

7020HT16

HID on LSR not on CSR

This error message indicates that the Hunt ID on the Local Service Request is not on the End User's Customer Service Record

Check the End Users CSR to validate that the hunting ID number is on the CSR. If the hunting ID number is not on the CSR, issue a SUP to correct the change to the hunting Id.

back to top

7020HT19

HTSEQ IS INVALID

This error message indicates that the Hunting Sequence field on the (LSR) Local Service Request Form (LSOG 5) or on the (HGI) Hunt Group Information Form (LSOG 6) is invalid.

You should check the LSR to make sure that the lines on the account are placed in sequential order for the hunting sequence. A SUP may need to be issued to correct the hunting.

back to top

7020HT20

@ @ Prohibited in multiple HID

The error message will indicate what telephone numbers are prohibited in multiple Hunt Ids. Verify the values populated on the HT Field on the (LSR) Local Service Request Form (LSOG 5), HTN Field on the (HGI) Hunt Group Information Form (LSOG 6).

You should perform the Pre-Order transaction Products and Services Availability to determine the products and services available in the central office.

back to top

7020HT08

USOC XXX only allowed on last line of hunt group - LSR in Query

The USOC identified in the error message is only allowed on the last line of the Hunt Group of the Local Service Request.

Check the LSR and determine if the product or service is in conflict with the hunt feature. Check to make sure that the USOC is on the last line of the TN with the hunt group.

back to top

7020HT10

USOC XXX not allowed on any line with hunting - LSR IN QUERY

This error message is advising that the USOC identified in the error message is not allowed on any line with hunting.

Obtain a CSR to identify if the account telephone number on this LSR has hunting. If a hunting arrangement exists the USOC XXX cannot be added to the account and the LSR has to be resubmitted/cancelled.

back to top

7020HT16

HID on LSR not on CSR

This error message indicates that the Hunt ID on the Local Service Request is not on the End User's Customer Service Record

Check the End User's CSR to validate that the hunting ID number is on the CSR. If the hunting ID number is not on the CSR, issue a SUP to correct the change to the hunting Id.

back to top

7020LC11

Invalid block combo - LSR in query

This error message indicates that the Blocking combination on the Local Service Request is invalid.

Obtain a current CSR. Validate if the correct USOC for the blocking option is populated on the LSR. If the correct USOC is on the LSR, validate to make sure the USOC for the blocking option matches the USOC on the account. If the USOC does not match a Sup must be issued.

back to top

7020LN01

C/S &X_VAR1 cannot be changed to C/S: &X_VAR2

The error message is advising that the Class of Service and product cannot be changed to the Class of Service and product identified on the Local Service Request.

You will need to obtain a current CSR and determine that the Class of Service information populated on your LSR and the product/service being ordered are compatible.
Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

back to top

7020LN03

Mixed Class of Service on Account is Invalid

This error message indicates the COS cannot be mixed on an Account. As an example, you cannot populate the TOS field as a Business when the End User's account is Residential.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the applicable COS.

You will need to verify that the TOS and USOC(s) on your LSR are compatible with your COS.

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

back to top

7020LN10

LN SHARE exists on TN specified, not eligible for migration

This error message is informing you that Line Share exists on the TN and migration is not eligible.

Check the CSR to validate that the Line Share arrangement exists on the TN. The Line Share arrangement must be removed from the TN in order to place a migration order.

back to top

7020LN27

Invalid Market Segment Change @ CLS on CSR is Bus.

This error message is advising that the order has an invalid Market Segment Change. The Class of Service on the Customer Service Record is for Business.

When processing this LSR, you will need to obtain a current CSR to identify the applicable Class of Service (COS).

You will need to verify that the TOS and USOC(s) on your LSR are compatible with your CSR.

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

Note: This will occur when the AC Field = C (to indicate Residence to Business migration) and the current CSR indicates Business Acct.

back to top

7020LN28

AC FIELD REQUIRED FOR TOS CHANGE - LSR IN QUERY

This error message is advising that the Account Structure Change field is required for the Type of Service change on the Local Service Request.

When submitting an LSR and it is indicated on the TOS field that it is a restructor of the Account, then CLEC needs to ensure that the AC field on the LSR Form is populated. Check the Business Rules for the valid entry values.

back to top

7020SC10

DISTINCTIVE RING USOC @

This error message is indicating that there is a problem with the Distinctive Ring USOC.

The Distinctive Ring feature or service being ordered is not valid or compatible with product being ordered. Obtain correct USOC for features and services being ordered. The USOC guide will identify if another feature or FID is required or prohibited.

You should also reference your local Tariff for additional feature requirements.

back to top

7020SC11

@ REQUIRED WITH @

The error message will indicate If LSR REQTYP = DB & LSR ACT = T & PS FEATURE DETAIL field contains the MWI or MSS FID

NORTH PON: There is no other occurrence of the PS FEATURE for the same TN that contains one of the following Call forwarding features: CFZ, GCZ, EKM, ELM

SOUTH PON: There is no other occurrence of the PS FEATURE for the same TN that contains one of the following Call forwarding features: EVB, EVD, EKM

Certain fields are required on specific forms. Check the Business Rules to determine what fields are required with what forms when placing a LSR request.

back to top

7020SC12

Invalid Disposition of @

If LSR REQTYP = DB & LSR ACT = T, Then the PS Feature Detail Field can not contain MWI OUT (FID and Code Set)

This error message is returned because on an ACT of T the customer must indicate only the features requested at the new address, all features at the old address are assumed to be disconnected. The appearance of MWI OUT is invalid since a service cannot be removed that is not currently working or installed at the new address.

Review PS Form of the LSR Request and Send SUP 3 after removing the entry on the Feature Detail field for the MWI OUT.

back to top

7020SC18

PIC/LPIC REQUIRED WHEN CHANGING FROM OR TO REMOTELINE

This error message is advising that a PIC/LPIC selection is required when changing the end user's account from or to Remoteline service.

You will need to issue a SUP on your LSR and populate the "PIC" and "LPIC" Fields if you are changing the account from or to Remoteline, otherwise change the values on the "TOS" Field on the LSR Form.

back to top

7020SC42

LSR Loop type is different from existing account

This error message is advising that the Loop Type on the Local Service Request is different from that which is identified on the Customer Service Record.

Validate the 2nd character of the TOS against the NC/NCI Table located in the Appendices of the Verizon Business Rules and compare against the customers CSR that the loop types are the same.

back to top

7020SC45

TOT Lines greater than or equal to 4, Unable to process UNE request.

This Local Service Request cannot process 4 or more line according to the UNE-P Carve Out conditions.

Check the LSR to validate the number of telephone numbers entered. You will need to review Verizon's Business Rules and Platform Services to determine the procedures for UNE-P Carve Out.

back to top

7020SC51

Circuit @ not eligible for TOS/NC/NCI code combination where @ is the circuit number in the OECCKT field

If LSR TOS 2nd Character "F" and LSR NC/NCI codes are equal to worksheet "Loop Share Migrations" column "D", "E" and "F" and LS:OECCKT 4 character string = SWXX then the CSR NC/NCI codes must be equal to worksheet "Loop Share Migrations" column "I", "J" and "K".

If this is a Loop share migration and the selected NC/NCI code matches the worksheet columns D, E, and F, and the Out Exchange Company Circuit ID (OECCKT) is 4 characters = SWXX then the NC/NCI codes from the CSR must match the Loop Share Migration worksheet columns I, J and K. To help you identify the correct NC/NCI and TOS combination, please refer to the Business Rules Appendix 3.2.

back to top

7020SL01

Line assignable USOC is not eligible for Line Splitting.

This error message is advising that the Line Assignable USOC on the End User's account is not eligible for Line Splitting.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the USOC(s) currently on the account to identify if additions and/or changes are eligible for Line splitting.

back to top

7020UA31

USOC OR FID NOT AVAILABLE IN END USER'S CENTRAL OFFICE @

This error message indicates the designated USOC or FID is not available in the End User's Central Office.

The error will identify what USOC or FID is not available.

Access the Pre-Order transaction to obtain available Products and Services Availability for the applicable central office to identify if the USOC or FID on your LSR is valid.

back to top

7020V018

No specialized routing contract

This error message is advising that the End User does not have a Specialized Routing Contract.

The End User does not have a specialized routing contract. The CLEC should contact the end user to verify/ensure that a contract is in place.

back to top

7020WT02

USOC: &X_VAR1 not found on TN:&TN

This error message indicates that the USOC on the LSR is not found on the Telephone Number (TN).

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the applicable TNs and USOCs on the End User's account.

Ensure that the USOC/TN combination on your LSR is on the CSR.

back to top

7020WT03

Response Description TN ON LSR NOT ON CSR - LSR IN QUERY

This error message indicates that the Telephone Number populated on the TNS field of the PS/RS Form is not on the End User's Customer Service Record.

Obtain a current CSR to identify and validate that the applicable TNs on the LSR are listed on the End User's account. Ensure that the TNs on your LSR are on the CSR. Resubmit a correction to the LSR.

back to top

7020WT07

Invalid Circuit ID on LSR" not on CSR

The identified Circuit ID is not listed on the Customer Service Record for this End User.

Validate the 2^nd character of the TOS against the NC/NCI Table located in the Appendices of the Verizon Business Rules and compare against the customers CSR that the circuit number on the service specific form has been recorded correctly and is a valid circuit number.

back to top

7020WT08

PS Form with all TNS on account or TNS value =A Req for full Disc

This request is for a full disconnect of the acct, not a partial. All lines listed on LSR need to match all lines on the CSR. The CLEC cannot leave any lines behind on the End User's account

When processing a complete disconnect of an End User's account check the CSR to make sure that all lines on the End User's account are on this LSR.

back to top

7020WT16

NPA NXX not valid

This error message is advising that the NPA NXX of the TN on the LSR is not valid.

Access the Pre-Order transaction to obtain Products and Services Availability for the applicable central office to identify if the area code and exchange has been entered correctly on your LSR and that the codes are valid. (If this is a CLEC NPA NXX then the EXKEY field must also be populated)

back to top

7020WT19

Partial move of a Remoteline not in scope.

This error message is advising that a partial move of a Remoteline is not in scope.

When processing a move order or migrating the end user, you will need to obtain a current CSR to validate that the all of the telephone numbers associated with the Remoteline account was submitted correctly your LSR. An order cannot be placed to move a part of the account.

back to top

7020WT26

Multi-line account, not applicable for migration at this time.

This indicates that there are multiple lines on the CSR.

Please check the CSR to verify if there are multiple lines on the account. If multi-lines exist on the account, then the account is not eligible for this type of migration at this time. A SUPP 1 must be issued to cancel the LSR or have the additional lines separated from this account first.

back to top

FORM: LS TN: &X_VAR1 not found or FORM: LSNP TN: &X_VAR1 not found

This error message is advising that the Telephone Number on the Loop Service form or Loop Service with Number Portability form is not valid.

back to top

There are (2) possible variations of text: SBN &X_VAR1 not found on the SBN table or SBN &X_VAR1 not found on the CRIS database.

This error message is advising that the Summary Billing Number is not on the Summary Billing Number table or not in the CRIS database.

back to top

Service cannot be ordered for Fiber only address

back to top

7030UA16

CSR shows no/different CLEC for Acc

The error message is advising that the Customer Service Record CSR indicates that there is no CLEC or a different CLEC name for the End User's account

When processing a change order or migrating the end user, you will need to obtain a current CSR to validate that the CLEC Name was submitted correctly your LSR.

If a new install, verify that the CLEC Name populated on the CCNA Field on the LSR is authorized to submit requests for the TN populated in the ATN field on the LSR Form.

back to top

7030V014

Invalid LPIC, No ACNA code found

This error message is indicates that the IntraLATA Pre-subscription Indicator Code is invalid, and the Access Customer Name Abbreviation is not found on the Local Service Request. .

Check the LSR to validate that the PIC/LPIC Carrier Code and the Access Customer Name Abbreviation (ACNA) has been input correctly or that it is valid for that telephone number. If the Carrier Code has been input correctly, contact the WCCC to issue a trouble ticket.

back to top

7030V015

Carrier Code is invalid

This error message is advising that the PIC/LPIC on the PS or RS Form of the Local Service Request is invalid.

Check the LSR to validate that the PIC/LPIC Carrier Code has been input correctly or that it is valid for that telephone number. If the Carrier Code has been input correctly, contact the WCCC to issue a trouble ticket.

back to top

7030V018

Invalid Branding option: XX for RSID: XXXX

The error message is advising that an invalid Branding option for the Reseller ID was provided.

You will need to obtain a current CSR to validate the RSID on the CSR to ensure it has been correctly populated on the LSR. If the RSID on the CSR is the same as your order, you will need to contact the WCCC to issue a trouble ticket.

back to top

Delete Action invalid for Main Listing

The Line Activity (LACT) of Delete (D) is invalid for the Main Listing (LML) on an account.

back to top

Different TNS found in ATN and EATN - LSR in query

This error message is advising that the Telephone Number keyed in the Account Telephone Number field and the Existing Account Telephone Number field is different.

When processing a change order or migrating the end user, you will need to obtain a current CSR to validate that the CLEC Name was submitted correctly your LSR.

If a new install, verify that the CLEC Name populated on the CCNA Field on the LSR is authorized to submit requests for the TN populated in the ATN field on the LSR Form.

back to top

TN IN ATN OR EATN NOT FOUND ON RS OR PS FORM - LSR IN QUERY

Error message indicates that the Account Telephone Number populated on the LSR Form or Existing Account Telephone Number populated on the EU Form is not found on the Resale Service form or Port Service form.

For Resale and Platform New Connects one WTN must = the BTN

back to top

TN &X_VAR1 to be added already sent - Check for duplicate TNs

This error message indicates that the TN being added on your order is currently on the end user's account.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the applicable TN(s) on the End User's account.

Ensure that the TN on your LSR is not on the current CSR and/or that the TN on the LSR has not been duplicated.

back to top

Call Forwarding II USOC (&X_VAR2) requires &X_VAR1 FID

This error message is advising that a Feature Identification code is required for the Call Forwarding II Uniform Service Order Code (USOC) on the Local Service Request, such as "CFN", "CFND", "CFNB" fid Required on Call Forwarding USOC ("E5E", "XCBRG", "EVD", "EVB") with Feature ACT = 'N' or 'C'.

The Call Forwarding II feature requires a feature identification code be added when the USOC is added to the account. To obtain applicable USOCs and required feature identification codes for products, access the Verizon Business Rules Appendices. The USOC guide will identify if another feature or FID is required or prohibited. You may also reference your local Tariff for additional feature requirements.

back to top

Only one Port Form allowed on Platform "AS IS" -LSR in query.

This error message is advising that only one Port Form is allowed on a UNE-Platform order with an Activity of AS IS.

End User must check to make sure that only one Port Service Form has be issued with the associated telephone number when the ACT Field on the LSR Form = W

back to top

Class of Service XXXXX Invalid

This error message is advising that the Class of Service is Invalid.

When processing a LSR you will need to obtain a current CSR to identify the applicable Class of Service (COS).

You will need to verify that the TOS and USOC(s) on your LSR are compatible with your COS.

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

back to top

7030V163

ALI code is required - LSR in query

The error code is advising that an Alpha/Numeric Listing Identifier Code is required for this type of ACT or LACT value.

Obtain a current CSR to determine the Alpha/Numeric Listing Identifier. Issue a SUP to add the ALI code to the LSR.

back to top

7030V174

Invalid RTY/LTY Combination - LSR in query

This error message indicates that the combination of the "RTY" (Record Type) on the DL Form and "LTY" (Line Type) on the DL Form is invalid.

You will need to review Verizon's Business Rules to determine the correct combination of listing types.

back to top

Invalid USOC

This error message indicates that an invalid USOC is on your order.

back to top

ATN must be on N on New Loop requests - LSR in query

If REQTYP = "AB", LSR ACT = "N", then the LSR ATN must = N or blank

back to top

Feature Activity is required with Feature - LSR in query

This error message indicates that you cannot have a Feature USOC without a Feature Activity provided on the Local Service Request.

back to top

ATN TN Should only appear once on RS Form -LSR in query

This error message is advising that the Account Telephone Number should only appear on the Resale Service Form one time.

If LSR ACT = T, none of the TNS = LSR ATN, and LSR ATN is not = EU EATN then it causes an error.

back to top

Feature is required with Feature Activity - LSR in query

Cannot have Feature Activity w/o a Feature USOC/FID.

Review customer's current CSR to determine what services exist and what line they exist on so that the TN is identified for the FID. Check the LSR to make sure that the feature activity and feature Field are populated on the LSR.

back to top

DDDO prohibited for ACT other than T - LSR IN QUERY

This error message is advising that populating the Desired Due Date Out field is prohibited unless the end user's address is being moved, this is done with an ACT = "T".

back to top

Incorrect data in the feature field - LSR in query

This error message indicates that the data populated in the Feature Field of the PS or RS Form is incorrect.

You will need to obtain a current CSR and compare the information on your LSR, to ensure that the services being requested is available or compatible with the class of service for this end user.

You may need to issue a SUP 3 to correct the data in the FEATURE field of the PS or RS Form or a SUP 1 to cancel the LSR.

back to top

DL fields must be in mixed case - LSR in query

This error message is advising that the Directory Listing fields on the DL Form must be entered in Upper and Lower Case.

back to top

Invalid TITLE1 value - LSR in query

The error message is advising that theTitle1field value is invalid.

back to top

&X_VAR1 not eligible for &X_VAR2 in state: &X_State, X=UNE, UNE Coin or Resale.

This error code tells you that a feature is not valid for the state that your End User resides in. For example: NST not eligible for UNE in state:NY

back to top

Incorrect format for fixed CL FWDG TN - LSR in query

This error message indicates that the format of the Fixed Call Forwarding Telephone Number is incorrect. If USOC=E5E, EVD, EVB following CFN, CFND, CFNB must have a space and a valid TN format

back to top

RTY Invalid with Toll Free Telephone Numbers

This error message is advising that the selection in the "RTY" (Record Type) Field on the DL Form is invalid with Toll Free Telephone Numbers

back to top

@ @ PROHIBITED IN MULTIPLE HID

The error code will identify what is prohibited in a multiple Hunt Group ID.

back to top

Grandfathered USOC not valid @

This error message will indicate that the USOC has been grandfathered. It is not allowed to be ordered via the Local Service Request

back to top

7030V511

Market Seg does not agree with Bell Atlantic records (ZI)

This error message indicates that the Type of Service (TOS) on your order does not match the CSR.

You will need to obtain a current CSR and compare the information to the TOS on your LSR.

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

back to top

7030V534

Blocking must be added to all lines in Hunt Group

This error message is advising that blocking must be added to all lines within the Hunt Group.

You should ensure that the Blocking FID is a valid blocking option. Please refer to the Verizon Business Rules. The Business Rules/Blocking Matrix (Appendix 3.4) will indicate the valid options and conditions for correct field entry based on REQTYP and jurisdiction. Blocking must be added to all line in this hunt group.

back to top

7030V576

FID: &X_VAR1 required with USOC: &X_VAR2' (used with SIT FID)

This error message is advising that a Feature ID is required with the USOC on the order.

Access the Pre-Order transaction to obtain Products and Service Availability to identify if the USOC or FID on your LSR is valid.

back to top

7030V593

Can only select 1 Call Answering USOC

This error message is advising that only one Call Answering USOC can be selected.

Obtain a current CSR. Validate if the correct USOC for Call Answering is populated on the LSR. If the correct USOC is being ordered, validate to make sure the USOC does not already exist on the account. If the USOC already exists on the account, you should issue a SUP to remove the duplicate USOC.

back to top

7030V619

This is a co carrier account - ineligible for reseller

This error message is advising that the co carrier account is ineligible for the reseller.

Check the LSR to validate that the Customer Carrier Name Abbreviation (CCNA) field has been input correctly. If the CCNA has been input correctly, contact the WCCC to issue a trouble ticket.

back to top

7030V639

Full restoral not valid-account not suspended

This error message is advising that the End User's account is not suspended. A restoral is not valid.

Review a current copy of the CSR. Validate if the account is suspended, if so validate that the ATN was submitted correctly on your LSR. If you are unable to obtain a CSR, it is possible the End User may have migrated to another provider. Review your Provider Notification report. If you are able to review a CSR and it shows that the account is suspended then you will need to contact the WCCC to issue a trouble ticket.

back to top

7030V660

CF2 invalid with Circular Hunting in 1A/5ESS office

The error message is advising that "CF2" is invalid with Circular Hunting in a 1A/5ESS Central Office.

Check the central office equipment to determine if CF2 is being ordered in a 1A/5ess central office. If a circular hunting arrangement exists the USOC for CF2 cannot be added to the same account and the LSR has to be resubmitted/cancelled.

back to top

7030V675

USOC: &X_VAR1 already exists on TN: &X_VAR2 (used for Selective Calling)

The USOC in question already exists on the telephone number. Therefore, the USOC may not be requested.

Obtain a current CSR to ensure that the correct USOC is populated on the LSR. You should validate that the USOC being ordered does not already exist on this account. If the USOC already exists on the account you should issue a SUP to remove the duplicate USOC.

back to top

7030V697

Invalid Area Code/Exchange (NPA/NXX) combination.

This error message is advising that the Area Code/Exchange (NPA/NXX) combination used on the Local Service Request (LSR) is invalid.

Access the Pre-Order transaction to obtain Products and Services Availability for the applicable central office to identify if the area code and exchange has been entered correctly on your LSR and that the codes are valid.

back to top

7030V725

Can Only select one Caller ID feature.

This error message is advising that only one Caller ID feature may be selected for the End User's account.

Obtain a current CSR. Validate if the correct USOC for Caller ID is populated on the LSR. If the correct USOC is being ordered validate to ensure that the USOC does not already exist on the account or that duplicates are being requested on the LSR.

back to top

7030V736

X_VAR1 USOC: &X_VAR1 n/a in NPANXX: &X_VAR2 / Phonesmart USOC: &X_VAR1 n/a in NPANXX: &X_VAR2

This error message will identify the Uniform Service Order Code that is not applicable in the End User's Numbering Plan Area/Network Exchange serving area.

You should perform the Product and Service Availability Pre-Order Transaction to determine the products and services available for the NPA/NXX.

back to top

7030V740

Pre-designated Carrier Arrangement data is invalid.

This error indicates that the TN(s) on the Service Specific form (Resale, Port, etc.) is invalid.

Validate that the TN on the Service Specific form has a valid Verizon NPA/NXX.

Obtain a current CSR to verify the TN(s) on the end user's account.

back to top

7030V811

Service Is Incompatible With Service. Service Is Required With Service. Service is Not Available or Service is Not Available in Switch Type. Service is Only Available in Switch Type. USOC: XXXXX not Available with Class of Service: XXXXX.

This error message indicates that a service or feature is required or incompatible with another service or feature or not compatible or available in the switch type on the Local Service Request. The error message will identify the service.

Obtain a current CSR to ensure that the correct USOC is populated on the LSR. You should validate that the USOC being ordered does not already exist on this account. If the USOC already exists on the account, you should issue a SUP to remove the duplicate USOC.

back to top

7030V826

FID &X_VAR1 not found- cannot assign DD - Verify data entered in correct fields

This error message will identify the FID being asked for is not valid therefore a due date cannot be assigned to the request submitted.

The FID entered in the Feature field of the PS or RS Form may not be valid. Check the LSR and the Port Service or Resale Service Form to ensure the services being ordered are correct.

back to top

7030V830

Form &X_VAR1 Data for Tag &X_VAR2 is Invalid

This error message will identify the form that is required based on the population of certain fields that are identified in the edit.

You will need to identify the correct forms to use on your LSR, refer to the Business Rules Appendices. The Ordering Matrix is located in Section 3.3 of the Order Appendices.

back to top

7030V852

&X_VAR1: Tag &X_VAR2 - &X_VAR3 invalid when &X_VAR4 Tag &X_VAR5

This error message indicates that a field on your LSR is invalid with another field on the LSR or CSR.

As an example, LSR: Tag ACT = W invalid when AECN Tag (your AECN) on the account.

You will need to obtain a current CSR to validate the AECN on the CSR. It is possible that the account has already been converted to you.

back to top

7030V855

&X_VAR1: Tag &X_VAR2 - &X_VAR3 invalid when &X_VAR4 Tag &X_VAR5&X_VAR1. Tag &X_VAR2. =&X_VAR3 only valid when Tag &X_VAR4. =&X_VAR5

This error message will indicate what variable is only valid with another variable provided on the Local Service Request. This could apply to multiple invalid combinations provided on your request

As an example, LSR: Tag ACT = W invalid when AECN Tag = (your AECN) on the account.

You will need to obtain a current CSR to validate the AECN on the CSR. It is possible that the account has already been converted to your company. Therefore ACT = W (conversion as is) is an invalid request.

NOTE: TAG replaces the specific assigned Name to fields or forms on a LSR.

back to top

7030V866

Form LSR: ACT = &X VAR1 requires Form RS: TNS = BTN, FEATURE - C/S or Form RS: LNA = &X VAR1 requires TNS = AUX, Feature = C/S (used for AUX line)

This error indicates that per your ACT on the LSR or LNA on the Resale Service (RS) form, you are missing features.

The error reason will identify what form has incorrect data or example: Form LSR:ACT = T requires Form RS:TNS=BTN, FEATURE = C/S.

When processing a move or change order for the end user, you will need to obtain a current CSR to identify the applicable features needed on the Resale form.

Certain transactions require that the feature field be populated on the Resale form.

To help you identify the correct forms to use on your LSR, please refer to the Business Rules. The Ordering Matrix (SEC 3.3) found in the Business Rules will identify the required forms for your LSR request type (REQTYP) and Activity (ACT).

back to top

7030V879

Invalid Action Code - Listing does not exist

This error message is advising that the Action Code populated on the LACT field on the DL Form is invalid. The Listing provided does not exist.

Check the LSR to make sure that the correct action code or listing was entered on the DL Form also check the CSR or directory assistance to ensure that it is a valid listing. A SUP may need to be issued to cancel the LSR.

back to top

7030V889

YPH prohibited

This error message is advising that the Yellow Page Header in prohibited. This occurs when the customer populates "YPHV" field of the DL form with valid entry value of "None", if the valid value is "None" then the "YPH" field can't be populated.

You should check the Verizon Business Rules and the DL form to ensure that the YPHV field is correctly populated

back to top

7030V900

Floating FID TN required in S&E section

This error message is advising that a Floating FID Telephone Number is required in the Service Details Section of the Local Service Request.

Review customer's current CSR to view what services exist and what line they exist on, the TN must be identified for the FID.

back to top

7030V906

&VAR_1 INVALID

Invalid AC_CR Flag in Position 3 of Listing Type (DZ tag)

Access the Pre-Order transaction to obtain available Products and Services Availability to identify if the USOC and FID on your LSR is valid. This must be corrected on the LSR by issuing a SUP.

back to top

7030V959

Main Listing telephone number must equal Main Line TN

The Main Listing TN must equal the Main Line TN on your LSR.

Validate that the Main Listing and Main Line TN(s) are entered correctly on your LSR.

When processing a change order or migrating the end user, you will need to obtain a current CSR to validate the TN was submitted correctly on your LSR.

If a new install, verify that the TN on the DL form matches the ATN on the LSR form.

back to top

7030V963

Listing Required for Main Number

This error message is advising that a Directory Listing is required for the Main Number.

Validate that a Main Listing and Main Line TN(s) are entered correctly on your LSR. Refer to the Business Rules Ordering Matrix for the required forms based on the REQTYP, ACT & LNA. A Sup may need to be issued to add the main listing.

back to top

7030WT07

Listing &X_VAR1 not found on account &X_VAR2 or Circuit &X_VAR1 not found on account &X_VAR2 - format example 74/TXNU/410008//NY where &X_VAR1 is the input circuit delimited by slash Example: Circuit 74/SWXX/419936//NY not found on account 7184476945 - format example 74/TXNU/410008//NY

This error message is advising that the Listing or Circuit is not on the account.

You should review the CSR to identify and validate the Listing and/or Circuit and issue a SUP to correct.

back to top

7030Z574

Switch Incompatible w/Ringmate Telephone Number

This error message indicates that the Ringmate TN on your order is not compatible with the end user's central office.

back to top

7030Z604

Form tag: DD has invalid data: X (i.e. LSR tag: C9 has invalid data: N)

This error message will identify the data populated on a specific field is invalid within the identified form (i.e. LSR).

Check the LSR to validate that the Due Date has been entered properly.

back to top

7030Z616

BTN: & X_VAR1(1,3) &X_VAR1(4,3)-&X_VAR1(7) not found

Your Local Service Request has incorrect information populated in the Billing Telephone Number Field.

You will need to review the customer's CSR and match it against the LSR and verify that the Billing Telephone Number populated on the "ATN" Field on the LSR Form or the "EATN" Field on the EU Form is a valid TN. A SUP will need to be sent to correct the information.

back to top

Request cannot be processed-Account already converted to Company Code: XXXX

This error message is used for Migration requests when the Company Code on LSR form equals the AECN on the CSR-account is already converted to that AECN

Prior to submitting an LSR request (Examples: Records, Change, Disconnect, Suspension or Restoral) obtain a current CSR to identify if the account is active. Validate that the ATN was submitted correctly on your LSR. If you are unable to obtain a CSR, it is possible the End User may have another provider. Review your Provider Notification report found in Wise Order. If you are able to review a CSR, you will need to contact the WCCC to issue a trouble ticket.

back to top

is prohibited when is present

This error occurs when a Field is populated and the usage is Prohibited when the other Field is populated also.

Review LSR to validate which Fields are being referred to or populated. Submit a SUP to remove the data from one of the fields and ensure that the values are correct by checking the Verizon Business Rules.

back to top

1. EATN must = Verizon retail customer BTN
2. EATN does not equal the BTN

You will need to obtain a current CSR to validate that the EATN is a Verizon Customer and is the main billing number of the account that the LSR is being issued under. If the CSR reflects different information and the modifications are actually a change to the existing CSR, you will need to contact the WCCC to issue a trouble ticket.

If you have determined there are no changes to be made to the account you will need to issue a supplement (SUP 1) to cancel your Purchase Order Number (PON).

back to top

with value of is required when is present with value of

The error message will identify the field and the field value(s) that are required.

Review LSR to see which fields are being referred. Submit a SUP to remove the data from one of the fields or ensure that the values are correct.

back to top

Request AECN does not equal account AECN

This error message indicates that the Alternate Exchange Carrier Name (AECN) on the LSR does not equal the AECN on the CSR.

You will need to obtain a current CSR to validate the AECN on the CSR to ensure it has been correctly populated on the LSR.

If you are unable to obtain the CSR, it is possible that the end user is with another provider.

If the AECN on the CSR is the same as your order, you will need to contact the WCCC to issue a trouble ticket.

If you have submitted recent activity for the End User and you have received the BCN, please allow 72 hours for the CSR to update.

back to top

AUX line TN: XXXXXXXXXX not in same CO as BTN: XXXXXXXXXX --or-- New BTN: XXXXXXXXXX not in same CO as Old BTN: XXXXXXXXXX

This error message is advising that the Auxiliary Telephone Number being asked for is not in the same Central Office as the Billing Telephone Number; or, the new Billing Telephone Number is not in the came Central Office as the old Billing Telephone Number.

Check the CSR and the LSR being issued to make sure that the NXX is from the same Central Office by using the Pre-Order Address Validation transaction. Access the Pre-Order transaction to obtain available Products and Services Availability for applicable central office. You will need to obtain a current CSR to validate the BTN on the CSR to ensure it has been correctly populated on the LSR.

back to top

USOC: &X_VAR1 already exists on TN:&TN

The USOC identified in the error message is already on the TN populated on the LSR.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify if the USOC is currently on the End User's account under the applicable TN.

If the USOC on the LSR is not on the current CSR, you will need to contact the WCCC to issue a trouble ticket.

back to top

NC/NCI/SECNCI Class of Service does not match SBN: XXXXXXXXXX Class of Service

Check the CSR to validate that the Special Billing Number (SBN) is valid for the TOS indicated on the LSR and match the Class of Service on the End User's account. Validate the data entered on the NC/NCI/SECNCI Fields on the LSR and submit the correct code. Refer to the Business Rules NC/NCI/SECNCI/ Matrix for the valid codes based on the TOS entries.

back to top

Invalid request - TN: XXXXXXXXXX is suspended 1-way

This error message is advising that the ordering activity is invalid, as the Telephone Number is on a 1-way suspension.

The End Users account is suspended one way. A restoral order must be issued before subsequent changes are allowed. Obtain a current CSR and check the Business Rules before reissuing the LSR.

back to top

Tag: &X_VAR2 on Form &X_VAR1 required for UNE request.

The error code will identify the field and form that is required for the UNE request.

Check the Order Business Rules Ordering Matrix to determine what forms and fields are required to place a LSR for a UNE change or migration.

back to top

Class of Service for Tag: XX is: XXX-cannot process request

The error code has to do with the End User Listing Accounts.

1. Class of Service for Tag: zh is: not NWP, LWR or LYB -cannot process request (a Directory Listing SBN was given in tag ZH but the Class of Service for that SBN on the CSR is not NWP, LWR or LYB, which is the Directory Listing Class of Service).

2. Class of Service for Tag: AJ is: NWP-cannot process request (An SBN was given in tag AJ but the Class of Service for that SBN on the CSR is NWP, which is only used as a Class of Service for a Directory Listing SBN)

3. "Class of Service for Tag: AJ is: 1MB-cannot process request" 1MB is just an example of a non-SBN Class of Service. This variable could be filled in with any non-SBN Class of Service USOC) (A valid TN was given in tag AJ but the Class of Service for that TN is not an SBN Class of Service)

The feature or service being ordered is not valid or compatible with Class of Service being ordered.

You will need to obtain a current CSR and compare the information to the TOS on your LSR.

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

back to top

Ringmate TN not in same switch as BTN

This error message indicates that the Ringmate TN for the BTN on your LSR is not in the same central office.

Access the Pre-Order transaction to obtain available Products and Services Availability for applicable central office. Ensure that Ringmate is compatible and in the same central office as the end user's BTN.

You will need to obtain a current CSR to validate the BTN and/or Ringmate TN on the CSR to ensure it has been correctly populated on the LSR.

back to top

Invalid format/value for FID XXX

This error message indicates what FID has an invalid format or value.

Access the Pre-Order transaction to obtain available Products and Services Availability to identify if the USOC and FID on your LSR is valid. The format must be corrected on the LSR by issuing a SUP.

back to top

Exchange Carrier not authorized for Platform NPANXX

This error message indicates that the Exchange Carrier is not authorized for the exchange for Platform service.

Check the LSR to validate that the PIC/LPIC or Carrier Code has been input correctly or that it is valid for that telephone number. If the Carrier Code has been input correctly, contact the WCCC to issue a trouble ticket.

back to top

Invalid Reseller ID (VJ Tag) Variation #2, or Invalid AECN.

This error message indicates that the Reseller ID used on the Local Service Request is invalid.

You will need to obtain a current CSR to ensure that the RSID/AECM has been correctly populated on the LSR. If the RSID on the LSR is the same as your order, you will need to contact the WCCC to issue a trouble ticket.

back to top

LTOS = P required for Line Splitting

This error message indicates that the line being migrated has Line Share or Line Splitting on it.

back to top

7030Z812

Centrex Class of Service must equal 2 lines or more

The error message is advising that in order for it to be considered a Centrex Class of Service, a minimum amount of 2 lines is required.

Resubmit the LSR with a SUP to either add more lines to the account or a SUP to change the class of service for the account; otherwise a SUP 1 is required to cancel the request.

back to top

Account contains fid: XXXX not eligible for Migration or add another X.

This error message indicates that the FID identified is not eligible for Migration.

back to top

RESELLER BILLING ACCT NUMBER NOT FOUND - LSR IN QUERY

The Account Telephone Number cannot be found.

You will need to review the LSR and verify that the Reseller's Billing Account Telephone Number populated on the BAN1 or BAN2 Field of the LSR Form is a valid TN. If it is correct, you will need to contact the WCCC to issue a trouble ticket.

back to top

LOCAL SVC PROVIDER FREEZE IN EFFECT

This error code indicates that the current provider has a local service provider freeze on the end user's account.

The end user is with another provider; you need to supplement (SUP) your order to cancel it, or contact the end user to have them contact their current provider to have the Local Service Provider Freeze removed from the account.

When the freeze is removed from the end user's account, you will need to submit a (SUP) to update your order. Don't forget to add Remarks to identify the changes.

back to top

Account Not Live-LSR in Query

This error code indicates order activity is being requested for an End User's account that is no longer working.

You will need to obtain a current CSR. If the CSR reflects a working account, you will need to contact the WCCC to issue a trouble ticket.

If you cannot retrieve a CSR, and have received a BCN, you will need to contact the WCCC and issue a trouble ticket in order for the CSR to be updated.

If you have not received a BCN, we recommend that a trouble ticket be issued for a BCN on or after the 3rd business day following receipt of the PCN. You will receive a PCN two business days from provisioning completion.

If you have determined the account is not live you will need to issue a supplement (SUP) to cancel your Purchase Order Number (PON).

back to top

Response Description Invalid ACT Type LSR in query

This error message is advising that the Activity on the Local Service Request is invalid.

You will need to obtain a current CSR and compare the information on your LSR.

To identify the REQTYP and ACT to issue on your LSR, please refer to the Business Rules ordering matrix (SEC 3.3) which will identify the required forms for your LSR Request Type (REQTYP) and Activity (ACT). You will need to issue a SUP to correct the ACT type on your LSR.

back to top

Requested Listing account TN already exists. (FTP initiative new code)

When REQTYP = "AB", "BB", "CB" or "JB", ACT = N", BAN = "N" (BAN1 or BAN2) and there is an existing listing account under the requested BTN.

You will need to obtain a current CSR and compare the REQTYP, and BAN information. Blocking FID, refer to the Business Rules Appendices Section.

back to top

Invalid CCNA

This error message is advising that the Customer Carrier Name Abbreviation provided on the Local Service Request is invalid.

Check the LSR to validate that the Customer Carrier Name Abbreviation has been input correctly. If the CCNA has been input correctly, contact the WCCC to issue a trouble ticket.

back to top

SUS PRESENT - CANNOT FLOWTHRU

This error message is advising that currently the End User's account is suspended. Type of request being submitted can't be processed until the account is Restored first.

The end users account is suspended. A restoral order must be issued before subsequent changes are allowed. Obtain a current CSR and check the business rules before reissuing the LSR.

back to top

7070UA03

Request RSID/AECN does not equal account RSID/AECN CSR

This error message is advising that the Reseller ID/Alternate Exchange Carrier Name does not equal the account Reseller ID/Alternate Exchange Carrier Name on the Customer Service Record. RSID value doesn't match OCN value in LSP. TB for this acct (CLEC) doesn't own this acct, or there is none on the acct.

You will need to obtain a current CSR to validate the RSID and AECN on the CSR to ensure it has been correctly populated on the LSR. If the AECN on the CSR is the same as your order, you will need to contact the WCCC to issue a trouble ticket.

back to top

7070UA06

No RSID - AECN on End User CSR -LSR in Query.

There is a discrepancy between the Customer Service Record and the Local Service Request regarding the RSID/AECN.

This Error Code is returned when there is no RSID or AECN found on the End User's Account or at times when the RSID/AECN found on the Local Service Request does not match the one on the Customer Service Record.

back to top

7070UA09

LNA=P: NO PIC, LPIC or FPI change found - LSR in query.

This error message is indicating that the Line Number Activity = "P", and the InterLATA Pre-subscription Indicator Code, IntraLATA Pre-subscription Indicator Code or Freeze PIC Indicator change was not found on the Local Service Request.

Check the LSR to validate that the PIC/LPIC or FPI Code has been populated or input correctly or that it is valid for that telephone number and line number activity. If the Carrier Code has been input correctly, contact the WCCC to issue a trouble ticket.

back to top

7070UA10

/BLKD A/CAS 94 RQD IN FEA-DTL ON LN USOC w/DHL-LSR IN QUERY

This error code indicates that the Feature Detail, /BLKD A/CAS 94, is required with the Line USOC on the Local Service Request.

If you are ordering the DHL Block, you will need to issue a SUP and add "/BLKD A/CAS 94" in the Feature Detail Field.

To help you identify the correct Blocking FID, refer to the Business Rules Blocking Matrix Appendices Section. The Blocking Matrices are located in Section 3.4 of the Order Appendices.

back to top

7070UA18

Cannot change PIC/LPIC with dual service - LSR in query

This error message is advising that the InterLATA Pre-subscription Indicator Code and/or IntraLATA Pre-subscription Indicator Code cannot be changed while dual service exists.

The End User has dual service and must have all services working identical in both locations. You will need to issue a SUP on your LSR to change the "PIC" and "LPIC" Fields so that both the main and alternate End User location has the same PIC/LPIC codes or submit a SUP 1 to cancel the LSR in it's entirety. All services must be identical in both locations.

back to top

7070UA32

@ REQUIRES @ - LSR IN QUERY

This error code indicates what feature or services require another feature or service. For example: Feature FRM requires Feature ESM - LSR in Query.

Certain features are dependent on other features being added also.

To obtain applicable USOCs for products, access the Business Rules. The USOC guide will identify if another feature or FID is required or prohibited.

You may also reference your local Tariff for additional feature requirements.

back to top

7070UA34

@ Not valid with @ - LSR in query

The error message advises that the USOC/FID or service is not compatible or available with the other USOC/FID or service being ordered on the Local Service Request.

The feature or service being ordered is not valid or compatible with product being ordered.

Obtain applicable USOCs for features and services being ordered.

The USOC guide will identify if another feature or FID is required or prohibited.

You should also reference your local Tariff for additional feature requirements.

back to top

NO CHANGES FROM LSR & CSR - LSR IN QUERY

This error code indicates that the modifications requested on the LSR are no different than what is on the current CSR.

You will need to obtain a current CSR to validate that the modifications being requested on the LSR are not on the CSR.

If the CSR reflects different information and the modifications are actually a change to the existing CSR, you will need to contact the WCCC to issue a trouble ticket.

If you have determined there are no changes to be made to the account you will need to issue a supplement (SUP) to cancel your Purchase Order Number (PON).

back to top

Minimum of 3 products required for Worksmart

User must add at least three products when ordering Worksmart

Obtain a current CSR. Validate if the correct USOC for Worksmart is populated on the LSR. If the correct USOC is being ordered, validate to make sure that three product USOCs are included on the LSR. If three product USOCs do not exist on the account, you should issue a SUP to add the additional products requested by the End User.

back to top

TN/Service Address Mismatch

This error code indicates the address used, based on the Pre-Order validation, does not match the entry on the LSR.

The address used to reserve the TN will need to be the entire address including supplemental address information such as Unit, Room, Apt, Lot, Slip, Suite, Floor (FL), Building, Wing or Pier. Also, if applicable, include Service Address Directional Prefix and/or Service Address Directional Suffix.

If the TN originally reserved was using a nearby address or an address without supplemental information, such as the Apartment, you will need to reserve a new number using the entire address. You will need to submit a supplement (SUP) to update your order with the new reserved TN. Don't forget to add Remarks to identify the changes.

If the requested address is in a new location where working service has never existed, or if an Assigned House Number is required, the house number range will not appear in the Address Validation Pre-Order transaction. You will need to populate the TN fields with the NPA/NXX of a nearby address and 4 zeros in the last 4 characters of the TN (for example 6162430000). In the AAI field on the End User form populate "NEW ADDR". In the Remarks field, provide a nearby TN and indicate that you need a TN assigned.

If the house number or supplemental address information needs to be added to Verizon's database, you will need to contact the WCCC. In this situation, the house range will appear in the Address Validation Pre-Order transaction.

When submitting the LSR the address used to reserve the TN must match exactly what is used on the End User form.

back to top

Service Address Mismatch LSR

This error message is advising that the data populated on any of the following fields of the EU Form doesn't match: Service Address Number Prefix, Service Address Number, Service Address Number Suffix, Service Address Street Directional Prefix, Service Address Street Name, Service Address Street Type, Service Address Street Directional Suffix, Location Designator 1, Location Value 1, Location Designator 2, Location Value 2, Location Designator 3, Location Value 3, City and/or Zip

Address validation has to be a match. Obtain a current CSR to ensure the address has been correctly populated on the LSR.

The service address on the End User form must match the address on the CSR or the address returned on the Address Validation Pre-Order transaction for new service. This may include supplemental address information such as: Unit, Room, Apartment, Lot, Slip, Suite, Floor, Building, Wing, or Pier, also, if applicable the service address directional Prefix and/or Suffix.

back to top

NEW/CHANGE TN @

This error code indicates that the TN on the LSR was entered incorrectly.

You will need to obtain a current CSR to validate the TN was correctly submitted on your LSR.

Ensure that the TN on the LSR has not been transposed and the NXX is correct.

If you reserved a new TN, validate the TN returned from the Pre-Order Reservation transaction matches the TN submitted on your LSR.

back to top

7071LW45

TN disconnect more than 30 days assign new TN

The error message is advising that the Telephone Number has been disconnected for more than 30 days and that a new Telephone Number will need to be assigned.

Since the number has been disconnected for more than 30 days, there is a possibility that it may no longer be available. You will need to go through the normal TN Reservation process and possibly choose a different number.

back to top

New LML is required for partial conversions, which do not include the BTN.

This error code indicates that a Main Listing (LML) is required on a partial conversion of an end user's account, which does not include the Billing Telephone Number (BTN).

back to top

Invalid LSR/DL form - ALI/TN combination

This error code indicates that the TN and ALI Code combination are invalid.

back to top

New LML needed, existing listing cannot be used

New LML needed, existing listing cannot be used

back to top

LML is required - LSR in query

This error message is advising that the "LTY" Field on the DL Form requires to be populated with "LML" (new Local Main Listing) for this end user's account.

back to top

(Field) required when ACT is V, N or T, otherwise optional, (Field) prohibited when ACT=W or S or LNA=D, W, B or P.

The error message will identify the FA Field on the PS or RS Form is required when the Activity field on the LSR Form is V, N, or T; otherwise entry in the FA field is optional; or, identify the FA field is prohibited when the Activity field (ACT) on the LSR Form is W or S or the Line Activity (LNA) field on the PS or RS Form is D, W, B.

Review LSR that the entry in these fields matches the combination value populated on the ACT or LNA field. A Sup may be required to change this information.

back to top

(SUP Field) prohibited on initial requests

The error message will identify the field that is prohibited on initial requests.

Population of this field is invalid for this transaction. Check the Business Rules for conditions on when to populate the field.

back to top

Duplicate SR

This error message is advising that a duplicate LSR already exists for the same exact request against the End User's account

Check to validate if there is a duplicate service request pending for the account telephone number. If a duplicate service request exists, a SUP has to be issued to cancel this LSR.

back to top

Directory activity invalid for convert "AS IS" requests.

The Directory Listing information as populated on the LSR is incompatible with a Conversion "AS Is" Request, there should not be any directory changes requested.

On an "As Is" conversion, these types of changes are not permitted, refer to the business rules Order Matrix for the REQTYP, ACT & LNA combinations and what Forms are permitted/required.

back to top

8016

(Field) required form missing for this REQTYP

This error code indicates that a required form is missing for the REQTYP on the LSR.

As an example, Port Service (PS) form missing for REQTYP "DB".

To identify the correct forms to use on your LSR, please refer to the Business Rules ordering matrix (SEC 3.3) will identify the required forms for your LSR Request Type (REQTYP) and Activity (ACT).

back to top

DL form is prohibited for Line Sharing and Line Splitting.

This error code indicates that the Directory Listing (DL) form is a prohibited form for this service.

back to top

The CHC field on the SUP 4 cannot be different than original LSR.

The CHC field on the SUP 4 cannot be different than original LSR.

back to top

State invalid or missing; or ACNA not certified in state

This error message indicates that the State is missing on the LSR, or you are not certified for the State identified.

back to top

The NNSP value provided does not match CLEC profile - LSR in query

This error message is advising that the New Network Service Provider Identification value does not match the CLEC profile. The Local Service Request is in query.

back to top

Valid Value B, 4th Char of TOS is only valid with REQTYP = D, F or M; otherwise prohibited (4th char = B is valid only for PA)

This error message is advising that the 4th character of "B" in the Type of Service field is only valid when the Request Type on the Local Service Request form is D, F, or M, and the state is PA. Otherwise the entry of "B" in the 4th character of the Type of Service.

When processing a LSR you will need to obtain a current CSR to identify the applicable Class of Service (COS). You will need to verify that the TOS and USOC(s) on your LSR are compatible with your COS.

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

back to top

Invalid BLOCK for State.

This error message is advising that the Block is invalid for the State on the Local Service Request.

back to top

(Field) prohibited when LACT = Z, otherwise required

This error message will identify the field that is prohibited when the Listing Activity Field (LACT) equals Z (No listing changes) on the DL Form; otherwise, the identified field will be required.

Check your LSR and determine if the LACT Field on the DL Form has a value of "Z" (which means No listing changes). If so, then the LTY Field in this case is prohibited from being populated,

If changes are needed, issue a SUP to correct the DL Form to either remove any entry on the LTY Field, or change the value on the LACT Field and populate the LTY Field.

back to top

Prohibited when the LACT field = "D" or "Z", otherwise required.

The error message will indicate that the STYC Field on the DL Form normally required in this case is prohibited because the Line Activity (LACT) field is populated with a value of "D" or "Z" on the DL Form, otherwise the Field identified will be required.

Determine if the directory listings on the end user's account are being disconnected or are remaining on the account. If the Line Activity Field indicates a "D" for disconnect or "Z" no change to listing, then there is no need to provide a Style Code for the listings. See Ordering Directory Services: Directory Listing for correct information on ordering directory listings.

back to top

Required in Verizon North, PA, DE and NJ, when ADI not equal to 0 and LACT = "N" or "I"

This error code indicates the required field(s) to be populated on the Directory Listing (DL) form when the Address Indicator (ADI) is not equal to "0" and the Line Activity (LACT) is equal to "N" or "I".

As an example, Listed Address Locality (LALOC) required when ADI not equal to 0 and Line Activity (LACT) = "N" or "I". The LALOC field will need to be populated.

To identify the correct field entries, please refer to the Business Rules.

back to top

(Field) required when SO is A and the PLS field is N, otherwise prohibited.

The error message will identify the field that is required when the Sequence Override (SO) 1 field is equal to "A" and the Prior Level Status (PLS) field is equal to "N"; otherwise the field identified is prohibited.

The "FAINFO" field on the DL Form must be populated when the "SO" field = A& the PLS Field = N. You should validate the DL Form to ensure that the fields are populated accordingly. If the fields are not populated correctly a SUP may need to be issued to correct the fields.

back to top

DL132

The 2nd and 3rd characters of "AM" are only valid for the States of CT, MA, ME, NH, NY, PS, RI or VT.

This error message is advising that the 2nd and 3rd characters of "AM" in the Record Type field on the Directory Listing Form is only valid for the States of CT, MA, ME, NH, NY, PA, RI or VT.

If the 2nd and 3rd characters of the RTY field is populated with "AM", then you need to validate that the STATE/SAST field (Location and Access Section) on the EU form is for one of the following states "CT", "MA","ME","NH","NY","PA","RI", or "VT".

back to top

DL139

(Field) optional for NY orders and VT secondary Orders when the STYC = SL

The error message will indicate the "OMSD" (Omit from Secondary Directory) Field on the DL Form is optional for NY orders and VT secondary orders when the "STYC" (Style Code) Field on the DL Form equals "SL."

For NY and VT LSRs, you will need to look at the "STYC" (Style Code) Field on the Directory Listing Form of the LSR. If it is not populated with "SL," you will need to issue a SUP and remove the entry in the "OMSD" Field.

back to top

DL194

Contact Verizon Information Services for Yellow Page Heading changes to existing listings.

The end user through Verizon Information Services must negotiate all changes to existing Yellow Page Headings. See the Verizon Customer Support website. Prohibited when LACT = "I" and the AC Field on the LSR is not populated with a value of "C" for a regrade from residence to business.

Requests for changes to Yellow Page Headings (free or contracted) on existing listings can only be accomplished by referring the end user to Verizon Information Services at 1-800-555-4833.

back to top

EU007

(Field) optional when AFT = C and ROUTE is populated.

The "SASN" Field on the EU Form becomes optional when the "AFT" (Address Format Type) Field is "C" Provider Assigned House Number (valid address where no House Number exists), and the "ROUTE" Field is populated.

If you choose to populate the "SASN Field," verify that the "AFT" Field = C and "ROUTE" Field is populated.

back to top

EU044

(Field) Required when the DISC NBR field is populated, otherwise prohibited.

This applies to the DNUM Field on the EU Form, advising that it is required when the DISC NBR Field is populated.

To identify the correct field entries, please refer to the Business Rules.

back to top

(Field) required when REQTYP = EB and ACT = T or D

This error message will identify the required field(s) to be populated on the End User (EU) form when the Request Type (REQTYP) is equal to EB and the LSR Activity (ACT) is equal to T or D.

back to top

(Note: When ACT = T, the first iteration of DISC NBR must equal the EATN)

The error message is advising that when the Activity on the Local Service Request is a "T", the first iteration on the DISC NBR field (Disconnect Telephone Number) on the EU Form must equal the data populated on the EATN Field (Existing Account Telephone Number) on the End User form.

back to top

Required when ((REQTYP = EB, FB, JB, MB, PB, BB, CB, NB) or (REQTYP = DB and the EATN field is populated)) and ACT=V. Optional when the 1st char of the REQTYP on the LSR form=A, and the ACT field on the LSR form=V.Optional when the 1st character of the REQTYP on the LSR Form = "D" and the ACT field on the LSR Form = "V" and the EATN field is not populated.Otherwise Prohibited.

This error message is advising that the End User Retaining Listing field (ERL/ELT) is required when the 1st character of the Request Type = "B", "C", "F", "M", "E", "P", "N" or REQTYP = D and the Existing Account Telephone Number (EATN) Field is populated and the Activity field on the Local Service Request = "V"; and Optional when the 1st character of REQTYP Field = "A" and the ACT Field = V, or Optional when 1st character of the REQTYP Field = "D" and the ACT Field = V and the Existing Account Telephone Number Field (EATN) on the End User Form is not populated, otherwise this field is prohibited.

back to top

(Field) optional when the SASN field is populated.

The error message will identify that the "AAI" Field on the EU Form is optional when the "SASN" (Service Address Street Name) Field is populated.

If you choose to populate the "AAI" Field, verify that you have the "SASN" Field populated also.

back to top

Required when (((the first position of the LSR.REQTYP = "J" and the DL.LACT = "N" or "I") or (the LSR.ACT = "N" or "T")) and (the 2nd character of the TOS field does not equal "F", "P", "R" or "Y".)))

This error message will indicate what field is required when the first Position of the REQTYP is = "J" and the DL LACT = "N" or "I" or, what field is required when the 2nd character of the TOS does not equal "F", "P", "R" OR "Y".

The Address Format Type (AFT) is required for your LSR. An example the AFT field would be required when the first position of the LSR REQTYP = "J" and the DL LACT = "N" or "I".

To identify the correct field entries, please refer to the Business Rules.

back to top

DL form is prohibited when ERL = "Y" or "N" (LSOG 5) ELT = "A" or "B" (LSOG 6).

DL form is prohibited when ERL = "Y" or "N".

The DL form is prohibited when the Retain end user listings (ERL/ELT) field on the EU Form is populated on the LSR with those values in both directory and/or directory assistance

back to top

Required when the 1ST character of the LSR REQTYP = "E" or "D" and the LSR ACT = "N" or "T" or the LNA on the PS & RS Forms = "T" and the 1ST character of the TOS field = "2", otherwise prohibited.

The error message will identify that the WSOP field on the EU Form is required when the 1st character of the Local Service Request Type field equals E or D and the Local Service Request Activity field equals N or T, or the Line Number Activity field on the Port Service or Resale Service form equals T and the 1st character of the Type of Service field equals 2, otherwise the field identified is prohibited.

You should validate that the PS and RS forms are populated correctly. A SUP 3 may need to be to ensure that because of the conditions listed above the WSOP field must be populated.

back to top

Required when the HTQTY field on the LSR Form is populated, otherwise optional.

The "HLA" (Line Hunt Group Activity) Field on the Local Service Request Form (for LSOG 5) or on the HGI Form (for LSOG 6) is required when the "HTQTY" (Hunt Quantity) Field is populated.

You will need to review the Hunt Group Information on the LSR Form and if the "HTQTY" Field is populated you will need to issue a SUP and populate the "HLA" Field on the LSR or HGI Forms.

back to top

(Field) required when HTQTY is populated, otherwise prohibited

The HNUM field is required when the HTQTY Field on the LSR Form is populated.

Check the End User's CSR to validate that the Hunting Quantity is correct on the LSR. If the hunting QTY (HTQTYP) field is populated then need to ensure that the HNUM Field is also populated, a SUP may be needed to correct or change the quantity. To ensure that the submitted LSR is correct for Hunt Groups, see the Select Service Offering: Hunting.

back to top

A SUP 3 is received and a previous SUP 6 or SUP 7 exists, and LTQ on SUP 3 does not=LQTY on previous version of LSR.

A SUP 3 is received and a previous SUP 6 or SUP 7 exists, and LQTY on SUP 3 does not =LQTY on previous version of LSR.

You should populate the LQTY with the same LQTY that was on the previous LS form.

Note: The Engineering Analysis is based on the LQTY that was originally submitted for the LSR and SUP 6. If the LQTY is greater than or less than what was originally submitted then it could result in inaccurate billing for the initial analysis returned to the CLEC

back to top

A SUP 3 is received and a previous SUP 6 or SUP 7 exists, and LTQ on SUP 3 does not=LQTY on previous version of LSR.

A SUP 3 is received and a previous SUP 6 or SUP 7 exists, and LQTY on SUP 3 does not =LQTY on previous version of LSR.

You should populate the LQTY with the same LQTY that was on the previous LSNP form.

Note: The Engineering Analysis is based on the LQTY that was originally submitted for the LSR and SUP 6. If the LQTY is greater than or less than what was originally submitted then it could result in inaccurate billing for the initial analysis returned to the CLEC

back to top

PO001

MPO - Pending Migration with Due Date = (DD from Pending Order) [this error code is returned under the following scenario CLEC-to-CLEC Migration Overlap: Different CLEC]

This error message is advising that there is a pending order, migrating the End User.

Prior to submitting an LSR request (Examples: Records, Change, Disconnect, Suspension or Restoral) obtain a current CSR to identify if the account is active. Validate that the ATN was submitted correctly on your LSR. If you are unable to obtain a CSR, it is possible the End User may have migrated to another provider. Review your Provider Notification report. If you are able to review a CSR, you will need to contact the WCCC to issue a trouble ticket.

back to top

PO004

DPO - Pending Disconnect with Due Date = (DD from Pending Order) [this error code is returned under the following scenario CLEC-to-CLEC Migration Overlap: Different CLEC]

This error message is advising that there is a Pending Disconnect Order with a different CLEC that is pending. The Due Date of the Pending Order will be reflected in the error message.

When placing a CLEC to CLEC migration, an entry must be made to the LSR indicating that there is a pending order from a different CLEC. A SUP 1 may need to be issued to cancel this LSR pending completion of the prior order.

back to top

PO006

CPO - Pending Change Due Date = (DD from Pending Order) [this error code is returned under the following scenario CLEC-to-CLEC Migration Overlap: Different CLEC]

This error message is advising that another Purchase Order from a different CLEC is pending for the same End User.

When placing a CLEC to CLEC migration, an entry must be made to the LSR indicating that there is a pending order from a different CLEC. A SUP 1 may need to be issued to cancel this LSR pending completion of the prior order.

back to top

PO007

SPO - Pending Suspend Due Date = (DD from Pending Order) [this error code is returned under the following scenario Migration Overlap - Suspend/Restore: Different CLEC]

There is a conflict with the due date on a Local Service Request to migrate an end user and another Local Service Request from another CLEC to Suspend/Restore the same end user.

You will need to issue a SUP 1 to cancel the request or re-submit the LSR with the Date Due on the "DDD" Field on the LSR Form after the date of the pending order.

back to top

PO009

XPO - Duplicate Request of PON (PON from Pending Order) [this error code is returned under the following scenario Change, Disconnect or Migration Overlap - Duplicate Request: Same CLEC]

This error message is advising that the same CLEC had previously submitted another Purchase Order for the same activity being requested on this Local Service Request, resulting in a duplicate.

Validate that a duplicate LSR is not pending for the same order activity. If a duplicate order exists issue a SUP 1 to cancel this LSR.

back to top

PO010

XPO - Duplicate Request of PON (PON from Pending Order) [this error code is returned under the following scenario Duplicate Suspend/Restore Issued: Same CLEC]

This error message is advising that a duplicate Purchase Order (PON) currently exists from the same CLEC.

Validate that a duplicate LSR is not pending for the same order activity. If a duplicate order exists issue a SUP 1 to cancel this LSR.

back to top

PO017

MPO - Customer Migrating Resubmit after Post Migration completes with Due Date = (DD from Pending Order) [this error code is returned under the following scenario Change Received - Pending Migration: Same or Different CLEC

This error message is advising that a Pending Order exists against the End User's account, and to resubmit after the date provided.

Either submit a SUP 2 on the LSR with a date later then the date from the pending order or submit a SUP 1 to cancel the LSR.

back to top

PO019

MPO - Pending Migration with Due Date = (DD from Pending Order)) [this error code is returned under the following scenario Change Received - Pending Migration: Same or Different CLEC]

This error message is advising that a pending migration exists against the End User's account.

You will need to issue a SUP to cancel the request or re-submit the LSR with the Date Due after that of the pending order.

back to top

PS005

When the 1st position of the REQTYP field on the LSR form = "D" or "F" and the 2nd character of the TOS field on the LSR form is not = "Y" and the ACT field on the LSR form = "C", then the LNA field must be populated with "C", "N", "D", "P", "T" or "X".

When the 1st position of the Request Type is Retail/Bundled *(Combined Loop & Port without Cage-Platform) or Unbundled Local Switching (Port) and the 2nd character of the TOS on the Local Service Request is not "Y" (TR008 Port Arrangement), and the Activity field on the Local Service Request form is "C" (Change), then the Line Activity must have a value of C, N, D, P, T, or X.

If the 1^st position of the "REQTYP" Field on the LSR Form equals "D" or "F" and the 2nd character of the "TOS" Field on the LSR form is not equal to a "Y," and the "ACT" Field equals a "C," you will need to review the Port Service form. If the "LNA" Field does not have a value of either "C", "N", "D", "P", "T" or "X" you will need to issue a SUP.

back to top

PS013

(Field) prohibited when (the 1st character of the TOS field on the LSR form = "4") or (the 2nd character of the TOS field on the LSR form = "P").

This error message is advising that the combination for the "LTOS" Field on the PS Form and the "TOS" Field on the LSR Form is invalid.

You will need to verify you have populated the correct values in the "TOS" Field on the LSR Form as well as the "LTOS" Field on the PS Form. See Verizon's Business Rules for the correct entries.

back to top

PS026

(Field) optional when LNA = C

The error message will indicate that the TC Field is optional when the Line Activity equals "C".

Populating the Transfer of Calls Field on the Port Service (PS) form is Optional, when the LNA Field on the PS Form = "C". Issue a Supp to remove the transfer of calls if it is not needed.

back to top

PS060

When ((the LNA field = "N" or "T") or (the LNA field= "V" and the RL field is populated)), only an entry of "N" is applicable.

The error message is advising that when the Line Activity field = "N" or "T" or the LNA Field = "V" and the RL Field is populated, then only an entry of "N" is applicable in the Feature Activity field (FA) of the PS Form.

If the LSR is for a new line service or a line move, the feature activity field must also be populated with an "N" for new service.

back to top

PS066

(Field) prohibited when the 2nd char. of the TOS = Y, otherwise required

The error message will identify the TNS field on the PS Form is prohibited when the 2nd character of the Type Of Service = Y; otherwise, the identified field is required.

Check your LSR and determine if the "TOS" Field on the LSR Form has the 2^nd character equal to "Y," then the TNS Field on the PS Form must not be populated. If it is, issue a SUP to correct the Port Service Form by removing the entry in the specified field.

back to top

PS100

Prohibited when the ACTs = W, D, I, J, S, B, or Y

The error message is advising that the "SSIG" Field on the PS Form is prohibited when the Activity field is populated with W, D, I, J, S, B or Y.

Issue a SUP and remove the entry in the "SSIG" Field on REQTYP "DB" if the "ACT" on the LSR is W, D, I, J, S, B, or Y.

back to top

PS110

When REQTYP=DB and ACT=D, if TNS does not = "A" then one of the TNS must = EATN.

The error message is advising that on a disconnect of a Platform account, if the TNS field on the PS Form is not populated with a Value of "A" (for all lines) then one of the Telephone Numbers on the TNS Field must equal the value on the Existing Account Telephone Number (EATN) field.

If the Telephone Number field does not equal "A", then one of the Telephone Numbers must equal the Existing Account Telephone Number field.

back to top

PS119

Invalid LNA value for AC value

The error message is advising that the Line Activity value is invalid for the Account Structure Change.

You will need to review Verizon's Business Rules for the correct LNA value when you are doing an Account Structure Change. When the AC = "A" then there needs to be at least one LNA = "Z."

back to top

PS123

Required when the PS form NPI field = "C" or "E" or "F"

When the Number Portability Indicator on the Port Service Form has a value of C (Port In Working TN), E (Port in a Wireless TN), or F (Not Applicable) then the EXKEY (Exchange Key) Field on the PS Form is required.

You will need to issue a SUP and enter a value in the "EXKEY" Field on the PS Form if the "NPI" Field on the Port Service Form contains a "C" or "E" or "F."

back to top

PS125

Out Exchange Company circuit id will be required when the RL field on the PS form is populated, otherwise prohibited

Out Exchange Company Circuit ID (OECCKT) Field on the Port Service Form is required when the reuse loop (RL) field on the Port Service (PS) form is populated, otherwise prohibited.

You will need to ensure if the end user's loop is going to be re-used (which will be indicated on the RL Field) if so, the CKT ID that is going to be used must be populated on the OECCKT Field on the PS Form of the LSR Request.

back to top

PS127

NO CHANGES REQUESTED ON PS FORM-LSR IN QUERY

When a value of "C" is used on the Line Activity, then one or more of the following fields on the PS Form must be populated: FPI, PIC, LPIC, OTN, BLOCK, LSCP, TSP or FA.

You will need to check the LSR and populate one or more of the following fields: "FPI," "PIC," "LPIC," "OTN," "BLOCK," "TSP" or "FA" on the PS Form if you have a value of "C" in the "LNA" Field.

back to top

Invalid Field Data-Field Name-Reason

This error message indicates that a field on your LSR contains invalid data. The error message will provide the Field Name and Reason.

This example is for invalid data in the TOS field of the LSR.

Example: Q1002: Invalid Field Data - TOS - Incorrect Information

Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered.
• The 4th character is a Characterization of the Product being ordered.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the applicable TOS.

back to top

Address Invalid-Field Name

The Field identified in the error message is missing.

You will need to perform the Address Validation/TN Selection and Reservation Pre-Order Transaction and verify the address on your LSR.

back to top

Required Field Missing - Field Name

The Field identified in the error message has missing information.

The error reason will identify what Field is missing. As an example, the Class of Service USOC is missing or invalid.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the applicable USOCs.

back to top

Feature Invalid - Reason

The error will specify the reason that the Feature is invalid on your LSR.

back to top

Required Form Missing-Form Name

This error message is advising that a specific required form is missing from the Local Service Request (LSR).

You will need to submit a SUP for the LSR and submit the required missing form.

To help you identify the required forms, refer to the Business Rules Ordering Matrix in the Appendices Section. The Ordering Matrices are located in Section 3.3 of the Order Appendices.

back to top

Account ineligible for migration-Reason

This Manual error message will indicate the reason that the end user's account is not eligible for migration.

back to top

TN Invalid - Reason

The error will specify the reason that the TN is invalid on your LSR.

Validate that the TN is entered correctly on your LSR.

You will need to obtain a current CSR to validate the TN was submitted correctly on your LSR.

If you reserved a new TN, validate the TN returned from the Pre-Order Reservation transaction matches the TN submitted on your LSR.

back to top

Pending Order-Resubmit after MMDDYYYY

This error message is advising that a Pending Order exists against the End User's account, and to resubmit after the date provided.

The CLEC should submit either a SUP 2 with a date subsequent to the pending order date or a cancellation of the LSR and send a new LSR after the date provided in the error message. This error applies to all LSR REQTYP

back to top

Other-Reason

This error message indicates there is missing or invalid data on the LSR.

The error reason will identify what information is missing or invalid. As an example, Circuit ID not found on CSR.

You should check that all information matches by obtaining a current CSR.To help you identify the correct format of the Circuit ID, please refer to the Business Rules.

back to top

(Field) optional when LNA =C

This error message will identify the ECCKT field on the RS Form is optional when the Line Activity field on the LSR Form = C.

If you choose to populate the ECCKT field on the RS Form for this Activity Type ensure that the field is populated correctly. All components of the CKT must be delimited by virgules.

back to top

Invalid LNA value for ACT value.

The Line Activity is not compatible with the Activity on the Local Service Request.

If you have populated the "LNA" Field with a "Z" on the Resale Services Form, then you must populate the "AC" Field on the LSR Form with a value of "A." A SUP may need to be submitted to ensure these fields have the appropriate values.

back to top

NO CHANGES REQUESTED ON RS FORM-LSR IN QUERY

When a value of "C" is used on the Line Activity field then one or more of the following fields on the RS Form must be populated: FPI, PIC, LPIC, OTN, BLOCK, TSP, RSCP or FA.

You will need to check the LSR and populate one or more of the following fields: "FPI," "PIC," "LPIC," "OTN," "BLOCK," "TSP," "RSCP" or "FA" on the RS Form if you have a value of "C" in the "LNA" Field of the same form.

back to top

SR009

DFDT is Required if CHC = "A", "B" or "Y" OR NPT on the LSNP or NP form = "D" and the SLI field on the LSR form is not equal to "B", otherwise prohibited.

The error message will identify the Desired Frame Date & Time DFDT field on the LSR Form is prohibited when the CHC field on the LSR Form = A, B or Y or when the NPT field on the LSNP or NP Forms = D and the SLI Field on the LSR Form is not populated with "B".

This field should not be populated when a Coordinated Frame Down Time is on the order or when issuing an LSR to Disconnect service.

back to top

SR077

(Field) required when CHC = Y

The Implementation Contact (IMPCON) field is required when the Coordinated Hot Cut (CHC) field is equal to "Y"

Check the Local Service Request (LSR) to validate that the Implementation contact (IMPCON) field on the LSR Form is populated when the CHC field on the LSR Form is populated with a value of Y. This person is the customer contact that will be informed/contacted by the provider installer when the end user requires a coordination of activity from both sides.

back to top

SPEC field required for Platform Product

This error message is advising that the Service Specific Ordering Code is required when ordering a Platform ISDN BRI Product.

When processing a platform ISDN BRI. You will need to ensure that the SPEC Field on the LSR Form is populated and that the TOS and USOC(s) values on the PS Form are correct.

back to top

(Field) required when REQTYP =, EB, FB, KB, LB, MB, NB, PB, RB, or SB and ACT does not = N or on REQTYP DB when ACT = V & no RL Field on the PS Form is populated.

The field identified in the error message is required when the REQTYP Field on the LSR Form = DB, ED, FB, KB, LB, MB, NB, PB, or SB and the ACT Field on the LSR Form does not equal N.

Check the End User Form to validate that the EATN field is populated correctly. This field must be populated when the following conditions are met:

Required when (((the first position of the REQTYP field = "D") and ((the ACT field on the LSR Form does not equal "N") or (the ACT field on the LSR Form equals "V" and no RL field on the PS form is populated))) or (the first position of the REQTYP field = "E", "F", "K", "L", "M", "N", "P" or "R") and (the ACT field on the LSR Form does not equal " N ")).

back to top

A value of "N" is prohibited when any TNS field on the PS or RS form is not equal to "N".

The error message is saying that the ATN Field on the LSR Form cannot = "N" when at least one entry of the TNS Field on the PS or RS Form is not populated with "N".

Review the entries on the LSR. If one of the TN values on the PS or RS then the ATN Field cannot have an "N" also, a SUP may need to be submitted to correct the value on one of the fields.

back to top

3rd char valid entry (("A") or ("B" EXCEPT when fGTE = PA) is required when REQTYP = "DB","FB", "MB" & ACT NOT = "J", & 2nd char of TOS = "A", "B", "E", "-" & 4th char of TOS not = "F" or "R" & EU.SAST Field = PA. Otherwise the 3rd char valid entry "A" or "B" is prohibited.

This error message is advising that if the 1st position of the Request Type = D, F, or M and the ACT is not equal to "J" and the 2nd character of the Type of Service = "A", "B", "E" or "-" & 4th character does not equal "F" or "R", and the SAST/STATE Field on the EU Form on the Local Service Request is PA, then the 3rd character of the Type Of Service should be an "A" or ("B" except when PA=fGTE); otherwise it is prohibited.

When processing a change order or migrating the end user, you will need to obtain a current CSR to identify the applicable REQTYP.

You will need to verify that the TOS and USOC(s) on your LSR are compatible with your REQTYP. Check all the characters of the TOS field -

• The 1st character is the Type of Service.
• The 2nd character identifies the Product being ordered.
• The 3rd character identifies the Class of the Product being ordered. (Platform option A & B are only available in PA (B except when fGTE=PA)
• The 4th character is a Characterization of the Product being ordered.

back to top

SR197

Required when ((the first position of the REQTYP field = "B" or "C") or ((the first position of the REQTYP field = "D", "E", "F", "P" or "N") and (at least one occurrence of the NPI field on the PS, RS, CRS or DDPS Form = "C" or "E"))), otherwise prohibit

This error code will identify the NPDI field on the LSR Form is required if the first position of the Request Type field is equal to "B" or "C"; or the first position of the Request Type field is equal to "D", "E", "F", "P" or "N" and at least one occurrence of the NPI field on the Port Service, Resale Form, CRS or DDPS Forms = C or E, otherwise it is prohibited.

When processing a Request for porting of a number then, the type of Port needs to be indicated, such as
B = Wireless to Wireline,
C= Wireline to Wireless or
D = Wireline to Wireline

back to top

SR204

Required when ((the 1st position of the REQTYP field = "A" or "B") and (ACT field = "V") and (the LS.LNA or LSNP.LNA = "V")) and ((2nd character of the TOS field = "2") and (the 3rd character of the TOS field = "1", "2", "3", "4", "6" or "R")) or (2nd character of the TOS field = "F")).

Population of the Network Channel (NC) Field on the LSR Form is required when the REQTYP Field on the LSR = A or B with the appropriate ACT/TOS/LNA combinations.

back to top

SR222

AENG field required for this SUP type

AENG field is not populated with "Y" when SUP =6 submitted

You should issue a SUP to populate the AENG field with a "Y" when a SUP 6 is issued.

back to top

SR223

SUP Type prohibited for ACT/REQTYP

REQTYP, ACT, LNA field values are not valid for SUP 6.

You should issue a SUP to populate the appropriate value in the REQTYP and/or ACT fields

Note: AB, BB, DB are the only valid REQTYP's for a SUP 6 depending on the REQTYP, N, C, V or T are the only valid ACT types.

back to top

SR224

Product not Available, unable to process request.

A SUP 7 is prohibited when the previous SUP 6 has not had any activity for greater than 30 days.

You should submit a SUP 1 to cancel the previous LSR and issue a new LSR.

Note: Verizon automatically cancels an LSR after 30 days of non-activity, but Verizon cannot cancel the PON.

back to top

SR226

SCA field required for this SUP type

SCA field is not populated with "Y" when SUP 7 = submitted.

You should review the LSR and the SUP 7 and issue a SUP to populate the SCA field with a "Y" when a SUP 7 is issued.

back to top

SR228

Product not available, unable to process request.

If REQTYP = "DB" or "FB" and ACT = "N," "T," "V" or "W" and 2nd character of TOS - "K" or if REQTYP = "DB" or "FB" and ACT = "C" and 2nd character of TOS = "K" and LNA = "N" or "T," the CLEC is ineligible to order this product.

You have received this error message for 1 of 2 reasons:

1. Verizon does not accept any orders for new, moves or migrations to mass market UNE-P arrangements. You can only send orders to suspend, restore, disconnect, add or delete features, change TN, make directory changes, and cancel (SUP 1). You should check to see if your company has entered into a commercial agreement for UNE-P replacement service.
   
   If your company has not entered into a commercial agreement for UNE-P replacement service, Platform services cannot be offered. Resale Services or Loop Services can be ordered.
   
   
2. Verizon does not offer unbundled switching arrangements or unbundled shared transport at packet switch central office locations. Before submitting an order for these services, you should review the Packet Switch Deployment List for Verizon.
   
   Use the Address Validation/TN Selection and Reservation Pre-Order Transaction to identify the CLLI code. Compare the CLLI code next to the Packet Switch Deployment List for Verizon found on Ordering Local Services.
   
   If the CLLI code is found on this list, Platform services cannot be offered. Resale Services can be ordered in packet switching central office locations.

back to top

SR231

Product not available, unable to process request.

-Facility Modification, Validation Check criteria: If REQTYP = "AB", or "DB" and SUP = "6" and AENG = "Y" Agreement data source check by CLEC, by State and effective date---: Match on CLEC, STATE and Validate Contract Product Effective Date.

Product is only available to CLECs who have a signed contract agreement for this type of request. All steps in the validation process must be met before request can be accepted.

back to top

SR232

Product not available, unable to process request.

If REQTYP = "AB" and ACT = "C", "N", or "V" and 2nd character of the TOS = "R" and SLI = "S", "B" and LNA = "N" or "W" Or If REQTYP = "BB" and ACT = "V" and 2nd character of the TOS = "R" and SLI = "B" and LNA = "V" CLEC is ineligible to order this product.

This product is only available to CLECs who have a signed contract agreement for this type of request. All steps in the validation process must be met before request can be accepted.

back to top

SR240

Invalid REQTYP and ACT field combination for AC field.

Optional when the LSR REQTYP = "DB" or "EB" & the LSR ACT = "C" or "V", otherwise prohibited.

You should check the LSR to ensure that the REQTYP is for a Platform (DB) or a Resale (EB) Firm Order and that the ACT is for a Post Migration Change (C) or a Migration "As Specified" (V).

back to top

SR253

Number of Requests LM Duplication of characters in first two positions of the NOR field for one RPON group is prohibited.

This error message is advising that duplication of characters in the first two positions of the Number of Requests field, for one Related Purchase Order Number group, is prohibited.

Check the Number of Requests (NOR) entered for a RPON Group. Make sure that the values on the NOR field is not duplicated on any of the LSRs for that group.

back to top

RPON Version XX Required if RPON is populated Otherwise prohibited.

This new field will identify the version of a RPON group for tracking and distribution of all related orders (all PONS within a RPON group must be submitted within 24 hrs) when a CLEC submits a supplemental change (Each PON has a VER; each RPON group has a RPVER.).

RPVER -RPON Version on the LSR form. This new field will identify the sequence of a RPON group for tracking and distribution of all related orders (Each PON has a VER; each RPON group has a RPVER.).

back to top

-(LSR:wW) RPON VERSION wW SUBSEQUENT VERSIONS MUST BE INCREMENTED BY 1

If (the SUP field is equal to "1" or "2") or (the SUP field is = to "3", "4" or "5" and the DDD field has changed from the prior version of the LSR), then the RPVER field must be incremented by 1 across LSR's (RPVER of SUP = RPVER of prior version +1).Example: Initial PON is received with RPVER = "00". SUP 3 PON with DDD change is then received. RPVER of the SUP 3 PON must equal "01"

This field will identify the sequence of a RPON group for tracking and distribution of all related orders (Each PON has a VER; each RPON group has a RPVER.) RPVER Field must increase by 1 on subsequent versions. Check the LSR to make sure that the version number has been increased on all the PONs within the RPON batch. RPVER -RPON Version on the LSR form.

back to top

Subsequent versions must be incremented by 1

This error message is advising that subsequent versions of the Local Service Request must be incremented by 1

If the SUP field is equal to "3", "4" or "5" and the DDD field has not changed from the prior version of the LSR, then the RPVER field must remain the same across LSRs (RPVER of SUP = RPVER of the prior version).

Example: Initial PON is received with RPVER = "00". SUP 3 PON with no DDD change is then received. RPVER of the SUP 3 PON must equal "00"

Related Purchase Order Number P3 Related PONS not all received within 24 hours.

back to top

Related Purchase Order Number P3 Related PONS not all received within 24 hours.

This error message is advising that all of the Related Purchase Orders were not received within 24 hours.

If the entire sequence of related Service Orders (RPON group) is NOT received within 24 hours, system will reject all Service Requests for the RPON group received to that point for the related sequence in question

Check the LSR to make sure that all related service orders were submitted. If the entire sequence of related Service Orders (RPON group) is NOT received within 24 hours, system will reject all Service Requests for the RPON group received to that point for the related sequence in question.

back to top

SR261

XXXX-"Related PON XXXXX (X denotes RPON value) unable to pass edits resubmit all PONs."

The error message will identify the Related Purchase Order Number that is unable to pass the system edits. All related orders will need to be resubmitted.

If one PON within the RPON group does not pass all system edits and a SUP needs to be issued for the one PON, then all PONs within that RPON Group require SUPs.

back to top

SR312

Duplicate transaction SUP 6 already in process.

A SUP 6 was submitted and a SUP 6 for the same PON already exists.

A SUP 6 is already pending for this account. Issue a SUP to cancel this request. There can only be one SUP 6 pending for an account at a time.

back to top

SR317

SUP 6 prohibited for this request.

A SUP 6 (which is for engineering query request) is only valid when a previous LSR is in a Jeopardy state and if it was for a reason other than "no facilities are available". If a SUP 6 is received and a previous LSR is in a Jeopardy state for a no facilities condition, then send a new error message back to CLEC.

Review the Jeopardy reason code to determine why the LSR was returned. If the LSR was returned for "no facilities available" a Sup 6 can be issued by the CLEC to request the Engineer to provide facilities for the order. If the LSR was returned for a reason other than "no facilities available" a new error message will be sent back to the CLEC and a Sup 1 will need to be issued to cancel this LSR.

back to top

SR318

A SUP 6 is prohibited for this request

A SUP 6 is received and the previous LSR does not have any Jeopardy conditions.

Review the Jeopardy reason code to determine why the LSR was returned. If the LSR was returned for "no facilities available" a SUP 6 can be issued by the CLEC to request the Engineer to provide facilities for the order. If the LSR was returned for a reason other than "no facilities available" a new error message will be sent back to the CLEC and a SUP 1 will need to be issued to cancel this LSR. A SUP cannot be issued unless the LSR has been returned for no facilities available.

back to top

SR319

Product not available, unable to process request

A SUP 7 is prohibited if SUP 6 response had not been returned populated with ECI and NMR and a value of K in the RT field.

You should wait 72 hours for the SUP 6 response before submitting the SUP 7. If the SUP 6 response is not received after 72 hours, then you will need to contact the WCCC to issue a trouble ticket. Note: This is primarily a system edit to ensure that all fields are populated and returned with in 72 hours for the SUP 6.

back to top

Duplicate USOC or FD for TN on LSR

This error message is advising that the same USOC or Feature Detail already exists for a particular telephone number on the Local Service Request.

Obtain a current CSR. Validate if the correct USOC or Feature Detail is populated on the LSR. If the correct USOC is being ordered validate to make sure the USOC does not already exists on the account

back to top