Technical documentation for this interface is available on the left-hand side of the screen. The information listed below is general ordering information related to this interface.
Ordering Functions
Documentation
Description
Transaction Sets
Process Flow
Error Types
Responses
EDI Element Separator/Segment
Terminators
Basic EDI/Business
Rules
The following ordering forms are supported on this Page:
Inbound forms (CLEC to AT&T)
LSR End User
Loop Service
Number Portability
Loop Service w/Number Portability
Resale
Resale Private Line
Port Service
Resale ISDN PRI
UNE ISDN PRI
CENTREX Resale
CENTREX UNE
DID/PBX Resale
DID/PBX UNE
Digital Trunking Resale
Digital Trunking UNE
Directory Listing/Captioning Request
Hunt Group Information
Outbound forms (AT&T to CLEC)
Local Response Confirmation
Local Response Completion
Directory Only Completion
Jeopardy Notification
Reject Notification
Post to Bill Notification
Provider Notification
The following documentation is available from the
left-hand side of the screen:
Mapping/Segment Charts – Provide sample EDI Mappings for each field on
a form in the proper X12 Segment order. LSOR field names are designated in italics.
SEF Files – Transaction Set documentation
generated out of EDISIM in both .sef and .htm format. These files list all of
the AT&T supported EDI Segments, Elements and Qualifiers in transaction set order
for the 850, 855, 860, 865, 836, 997 and ICS.
OBF/X12 Conversion Tables – OBF to X12 conversion tables that
are supported by AT&T
PO1 Loop Designators – A list of the codes
to be used with the A6 qualifier in the PO1 segment to identify the detail level
data being passed in a PO1 loop
DE751 Code Lists – AT&T supported qualifiers/phrase codes for DE751, as
well as OBF to X12 translations where applicable
EDI Response Code Matrix – Tables listing
the valid BAK01/02, BCA01/02, RT and EC VER combinations on responses sent from
AT&T to CLECs
LSOR – Link to the 13-State Local Service Ordering Requirements (LSOR)
document
EDI utilizes the following transaction sets to process requests:
Following is the basic process flow for EDI:
Note – See Responses section below for additional responses that may be sent from AT&T to the CLEC.
SUPER FATAL ERRORS:
The following errors are identified as Super Fatal.
Must send another Record Type 850 (initial)
When a Super Fatal error is detected, editing of the request will cease
FATAL ERRORS:
AT&T will be sending a variety of responses to the CLECs relating to Local Service Requests. Following are the responses which may be received:
Acknowledgment Response - This response will be provided to CLECs that submit requests via Electronic Data Transfer. This response utilizes the 997 transaction and will indicate that the file was either successfully received or that problems were encountered.
Local Response Confirmation - This response provides information associated with the customer's request for service. It will be provided to indicate that the requests received are complete and accurate and have been processed by AT&T as a firm order. This response can utilize either an 855 transaction (for initial request) or an 865 transaction (for supplement to a request). Also see Provider Initiated Activity Response which utilizes this process.
Provider Initiated Response - This response
utilizes the Local Response Confirmation to convey a provider (AT&T) initiated
change to the original confirmation. The Provider Initiated Activity field will
contain an indicator that advises the CLECs what data has been changed. A Provider
Initiated Activity response is merely an update of the previous Local Response
Confirmation to either an original request or a supplement to a request and
does not take the place of those confirmations.
The original confirmation will be fully refreshed and the updated (PIA) confirmation
will include all unchanged data as well as the data that has been changed from
the original confirmation, as identified by the PIA indicator. This response
utilizes the 865 transaction. (See the Local Response Confirmation section for
field abbreviations, data characteristics and data names utilized in this response
in addition to the PIA related fields.)
Directory Service Request Completion - A Directory Service Completion is the completion notice sent when a Directory Only (DSR REQTYP J) has been processed by the Directory Publishing company, is posted to the white pages data base, and available to Directory Assistance (DA). One completion is sent per LSR. This notification utilizes the 865 transaction.
Local Service Request Completion - This response notifies the customer that their request for service is complete. The notice is sent once all orders associated with the request have been marked as completed in AT&T systems. This notification utilizes the 865 transaction.
Local Response Jeopardy - This response will be sent to CLECs to indicate that the service requested may not be completed by the confirmed due date. This is an informational message and may require CLEC action. This notification utilizes the 865 transaction.
Local Response Reject - Upon receipt of the initial or supplement LSR, the request will be edited. If the LSR failed edits and cannot be processed, a response will be sent to the CLEC along with error messages indicating why the request failed. This response can utilize either an 855 transaction (for error responses on the initial request) or an 865 transaction (for error responses on a supplement to a request).
Provider Notification - This response will be provided to the losing CLEC when an end user chooses to change from one CLEC to another CLEC. It alerts the losing CLEC that a change requested by another CLEC has been completed and the end user is no longer theirs. This notification utilizes the 836 transaction.
AT&T recommends the use of the following characters on responses sent from AT&T to CLECs. These are the default characters that will be used unless otherwise requested by the customer.