WO1999052264A1 - Transaction sets for automated electronic ordering of telecommunications products and services - Google Patents

Transaction sets for automated electronic ordering of telecommunications products and services Download PDF

Info

Publication number
WO1999052264A1
WO1999052264A1 PCT/US1999/004215 US9904215W WO9952264A1 WO 1999052264 A1 WO1999052264 A1 WO 1999052264A1 US 9904215 W US9904215 W US 9904215W WO 9952264 A1 WO9952264 A1 WO 9952264A1
Authority
WO
WIPO (PCT)
Prior art keywords
code
service
data
segment
transaction set
Prior art date
Application number
PCT/US1999/004215
Other languages
French (fr)
Inventor
Timothy M. Gilles
Therese A. Wierzbicki
Donna J. M. Motto
Original Assignee
Ameritech Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ameritech Corporation filed Critical Ameritech Corporation
Priority to AU27926/99A priority Critical patent/AU2792699A/en
Publication of WO1999052264A1 publication Critical patent/WO1999052264A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/202—Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification
    • G06Q50/60—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal

Definitions

  • the present invention relates to electronic ordering of telecommunications services and products . - 2 -
  • EDI has been developed to provide a standard format for exchanging basic business data among firms that regularly conduct business with one another. EDI may be used to replace a wide variety of common business forms including purchase orders, invoices, shipping and packing slips, and numerous others, to eliminate costs associated with handling paper documents resulting in more efficient utilization of resources and increased accuracy.
  • transaction sets Similar to their physical counterparts, standard transaction sets include line items, referred to as data segments, and specific items, referred to as data elements. For example, data elements in an invoice might include quantity, product identification, unit price, and extended price.
  • data elements in an invoice might include quantity, product identification, unit price, and extended price.
  • Telecommunications services and products are currently ordered from wholesalers primarily in a manual fashion, either by voice contact or exchange of paper forms. Where electronic methods are in use, they are generally batch-oriented, form-based file exchange -3 - processes, or utilize proprietary interfaces which may include Internet browser technology, for example. While some telecommunication companies have implemented EDI ordering systems, these systems typically require manual intervention to enter received EDI orders into the company's internal order system. Although EDI has been proposed for ordering of telecommunication products and services for several years, there has not yet been a significant implementation of EDI for this purpose.
  • Telephone Local Exchange Carriers are now required to provide some type of system and method for Telecommunications Carriers to electronically place orders with an LEC for wholesale bundled exchange products and/or services m addition to unbundled elements of the telecommunications network.
  • the various LECs have developed differing solutions such as providing direct access to their internal ordering systems, creating Internet browser forms for order entry, or creating proprietary application-to- application interface protocols.
  • FIGURE 1 is a diagram illustrating a Public Switched Telephone Network (PSTN) for application of - 4 - automated electronic telecommunications product/service ordering according to the present invention
  • PSTN Public Switched Telephone Network
  • FIGURE 2 is a flow chart illustrating one embodiment of a process for automated electronic ordering of telecommunication products and/or services according to the present invention
  • FIGURE 3 is a transaction flow diagram illustrating a pre-ordermg exchange between a telecommunications provider and a telecommunications reseller as implemented m one embodiment of the present invention
  • FIGURE 4 is a block diagram illustrating one embodiment of an address validation interface for automated electronic telecommunications ordering according to the present invention
  • FIGURE 5 is a block diagram illustrating one embodiment of a feature availability file for automated electronic telecommunications ordering according to the present invention
  • FIGURE 6 is a flow chart illustrating one embodiment for feature availability processing for automated electronic telecommunications ordering according to the present invention
  • FIGURE 7 is a block diagram illustrating one embodiment of a Customer Service Record (CSR) interface for automated electronic telecommunications ordering according to the present invention
  • FIGURE 8 is a block diagram illustrating one embodiment of a telephone number interface for automated electronic telecommunications ordering according to the present invention
  • FIGURE 9 is a block diagram illustrating one embodiment of a due date interface for automated electronic telecommunications ordering according to the present invention.
  • FIGURE 10 is a block diagram illustrating mapping and translation functions of one embodiment for automated electronic telecommunications ordering according to the present invention.
  • Automated electronic processing of orders for telecommunications products and services minimizes or eliminates human intervention to reduce or eliminate costs associated with handling paper documents.
  • the present invention provides a real -time, interactive interface for telecommunications resellers to increase accuracy and reduce turn-around time.
  • the development of transaction sets particularly suited for telecommunications services and products provides a standard method for electronic ordering where external access to dynamic data is required.
  • Automated translation to and from unique or proprietary interfaces used by individual resellers to standard transaction sets further reduces manual intervention while providing increased flexibility for telecommunication product/services resellers. - 6 -
  • FIG. 1 is a diagram illustrating a Public Switched Telephone Network (PSTN) for application of automated electronic telecommunications product/service ordering according to the present invention.
  • PSTN Public Switched Telephone Network
  • LEC Local Exchange Carriers
  • Each LEC 22 owns and/or manages one or more Central Offices (CO) , indicated generally by reference numeral 24, such as Central Offices 26-36.
  • CO Central Offices
  • each CO 24 typically serves a particular geographic area and includes various hardware and software to deliver telecommunication services.
  • Such hardware includes one or more switches 38, 40 to provide a communication path for a telephone call.
  • the various COs 24 are typically connected using one or more circuits 42 which are classified based on bandwidth capability, signal protocol, or the like, as also well known in the art .
  • a telecommunications reseller 50 interfaces with end users or customers 52, 54 to provide various retail telecommunications products and services 56 such as caller ID 58, remote access call forwarding 60, and call waiting 62, for example.
  • Reseller 50 provides the customer service functions including invoicing, collections, service inquiries, new telephone numbers, directory listings, and the like.
  • Each customer 52, 54 may have one or more telecommunications devices 64 such as a computer 66 or telephone 68, sometimes referred to as premises equipment (PE) .
  • PE premises equipment
  • Customers typically include both residential customers, such as customer 52, and business or commercial customers, such as customer 54.
  • Business customer 54 may have a Private Branch exchange (PBX) which interfaces with a switch such as switch 42 in the local CO 34.
  • the PBX provides connections between and among internal PE in addition to coordinating access to external lines (circuits) .
  • reseller 50 preferably utilizes automated electronic ordering according to the present invention to provide telecommunications products/services 64 to customers 52, 54.
  • Reseller 50 employs customer service agents 70 which process requests from customers 52, 54 relative to telecommunications products and services.
  • Customer service agents 70 preferably utilize one or more computers 72 to enter information received from customers 52, 54 which is then communicated to a message server 74 which preforms two primary functions.
  • Message server 74 manages communications between itself and computers (clients) 72 while also providing a single access point for communication with telecommunications wholesaler 22.
  • Message server 74 communicates with a router 76 which preferably permits only messages conforming to the Transmission Control Protocol/Internet Protocol (TCP/IP) between reseller 50 and wholesaler 22.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • Router 76 communicates with DSU/CSU (Digital Service Unit/Customer Service Unit) 78 to facilitate digital communications.
  • DSU/CSU Digital Service Unit/Customer Service Unit
  • a particular class of circuit 42 is selected and installed. This may include DS0 (Digital Service Level 0 - 56Kbps) /DS1 (Digital Service Level 1 - 1.5Mbps) 90, Tl 92, frame relay 94, or the like.
  • DS0 Digital Service Level 0 - 56Kbps
  • DS1 Digital Service Level 1 - 1.5Mbps
  • Wholesaler 22 includes similar equipment such as a message server 100, router 102, and DSU/CSU 104. Messaging between reseller 50 and wholesaler 22 is preferably accomplished using a dedicated connection which may be facilitated by one or more of the circuits described above.
  • reseller 50 may communicate with wholesaler 22 via a Value Added Network (VAN) provider 110 operated by a third party.
  • VAN Value Added Network
  • server 100 of wholesaler 22 and server 74 of reseller 50 is performed using a simple character protocol, such as the Enterprise Access Protocol (EAP) .
  • EAP commands are sent from the server 74 of reseller 50 to server 100 of wholesaler 22 over a TCP/IP socket connection.
  • the EAP commands are used to establish an application session to exchange electronic information between reseller 50 and wholesaler 22.
  • Each message preferably includes a sender's reference (SNRF) which is generated by reseller 50 and used for routing purposes. This facilitates the distribution of messages by server 74 to customer service agents 70 via computers 72.
  • SNRF sender's reference
  • the SNRF contains a unique identification code in the first six characters corresponding to a particular reseller 50. The last six characters of the SNRF are reserved for assignment by reseller 50 to uniquely identify a particular customer service agent 70 or computer 72. This enables reseller 50 to appropriately route messages received from wholesaler 22 through message server 74.
  • each message server 74 which interacts with message server 100 of wholesaler 22 has a unique identification and password.
  • passwords are required only at the start of a particular session and are not required for each transaction set or electronic document exchanged.
  • a packet filter firewall is used which permits only packets destined for a correctly defined static IP address and service port to further improve security.
  • the connection established between reseller 50 and wholesaler 22 may be used to transfer files in addition to the defined transaction sets as described in greater detail below.
  • all transaction sets are approved by a recognized standards organization such as the American National Standards Institute (ANSI), or the International Standards Organization (ISO) .
  • ANSI American National Standards Institute
  • ISO International Standards Organization
  • the transaction sets conform to the ANSI Accredited Standards Committee (ASC) X12 , the committee that develops and maintains generic requirements for EDI in the United States .
  • ASC ANSI Accredited Standards Committee
  • the electronic reseller notification transaction set is used to convey advance notice of a change of local service provider, confirmation when that - 11 - change is completed, and notice if the planned change is cancelled.
  • This transaction set is referred to as a contract award by ANSI .
  • the purchase order transaction set (850) may be used to provide for customary and established business and industry practice relative to the placement of purchase orders for telecommunications goods and services.
  • the reseller would use this transaction set to request telecommunications services from the wholesaler.
  • the purchase order is used to request any of the following types of services, each based on unique transaction identifiers contained within the transaction set: telephone number inquiries, reservations, reservation cancellations, and reservation confirmations; due date inquiries, reservations, reservation cancellations, and reservation confirmations; customer service record requests; and service requests.
  • the purchase order acknowledgment transaction set (855) is preferably used as an acknowledgment from the wholesaler to the reseller.
  • This transaction set provides scheduling information, telephone and circuit number information, and the like, in response to receipt of a purchase order transaction (850) for one of the transactions identified above.
  • Purchase order changes are preferably communicated using the Purchase Order
  • the reseller would use this transaction set to request a change to a previously submitted purchase order. - 12 -
  • the Text Message transaction set (864) is intended to provide electronic communication for people, not necessarily for computer processing as with the other transaction sets.
  • the use of this transaction set requires that the sender have certain detailed information about the recipient in some human-readable form.
  • the recipient's network dictates the available capabilities for delivery of the information contained within the transaction. It is the responsibility of the sender to obtain this information and include it in the transmission.
  • This transaction set may be used to respond to a customer service record request to provide information about an existing customer of the wholesaler to the reseller.
  • the Purchase Order Change Acknowledgment transaction set (865) is used to convey acceptance or rejection of changes to a previously submitted purchase order by the wholesaler or to notify the reseller of changes initiated by the wholesaler to a previously submitted purchase order by the wholesaler. This transaction is also used to notivy the wholesaler that an order has been completed.
  • the reseller order status transaction set may be used to convey jeopardies which occur on an order after the 855 transaction set has been communicated. This transaction set may be used to provide status on individual line items of a purchase order or on the entire order.
  • the Functional Acknowledgment transaction set (997) is used to define the control structures for a set of acknowledgments to indicate the results of the - 13 - syntactical analysis of the electronically encoded documents using other transaction sets.
  • This transaction set includes data segments used to identify which electronic document (transaction set) contains an error and where the error occurred within the document.
  • Figure 2 is a flow chart illustrating one embodiment of a process for automated electronic ordering of telecommunication products and/or services according to the present invention.
  • the various steps, tasks, or functions illustrated are not necessarily sequential in nature.
  • the present invention is generally independent of the particular sequence or order m which the tasks or steps are completed.
  • Various steps, tasks, or functions may be completed simultaneously, virtually simultaneously, or may be separated by minutes, hours, or days without departing from the spirit or scope of the present invention.
  • the present invention performs automatic electronic ordering of telecommunications using computer- o-computer communications exclusively, meaning that no human intervention is required to reduce or eliminate keying errors, mishandled or lost forms, and the like.
  • the present invention incorporates exception processing which may include some level of human intervention to process unique or as yet undefined transactions.
  • Computer readable storage media may include various types of volatile and non-volatile storage media including but not limited to random access memory (RAM) , read-only memory (ROM) , programmable read-only memory (PROM) , electrically programmable read-only memory (EPROM) , electrically erasable read-only memory (EEPROM) , flash memory, magnetic tape or disk, optical media, and the like.
  • RAM random access memory
  • ROM read-only memory
  • PROM programmable read-only memory
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable read-only memory
  • flash memory magnetic tape or disk, optical media, and the like.
  • Block 120 of Figure 2 represents gathering customer information during a pre-orde ⁇ ng process. This is typically performed by the reseller in response to a customer inquiry or request for a service.
  • this step may also be initiated by the reseller or wholesaler under particular circumstances, such as in the event of termination of service for non-payment, area code changes, feature availability changes, and the like.
  • the reseller gathers appropriate information depending upon the particular telecommunications service or product .
  • the resellers use internal computing systems, such as computers 72, and/or databases to collect the appropriate items which constitute a particular transaction set for an electronic exchange of information.
  • the information necessary for a particular transaction set may be scattered about - 15 - va ⁇ ous fields and/or databases depending upon the particular reseller's implementation.
  • the information or data is collected or mapped to a particular transaction set to form an electronic "document" as indicated by reference numeral 122.
  • the gathered information is validated as represented by block 124 using an address validation file 126 (illustrated and described with reference to Figure 4) and a feature availability file 128 (illustrated and described with reference to Figures 5- 6) .
  • the information is translated into a standard EDI format as represented by block 130.
  • block 130 represents the reciprocal function of translating an EDI transaction received by the reseller back to the reseller's internal format.
  • the translation function 130 allows the reseller to format the data conveniently for the customer service representatives rather than being forced to conform to the pre-defined EDI format.
  • Automatic translation according to the present invention reduces or eliminates human intervention to transfer the data contained in an EDI transaction into the reseller's internal forms and format.
  • the standardized EDI format allows the reseller and/or wholesaler to conduct business with other wholesalers and resellers who conform to the standard, respectively.
  • the information is communicated from the reseller to the wholesaler (or vice versa) as represented by block 132. This may be accomplished using a dedicated or direct connection between the reseller and the wholesaler, or by using a - 16 -
  • VAN as described above. While this communication may be completed in a batch mode 134, it is preferably communicated using a TCP/IP socket connection during an interactive, substantially real-time session, i.e., while the reseller is "on-line" as represented by reference numeral 136. While batch processing may be used to take advantage of lower volume traffic during off-peak times, it delays processing and reduces efficiency, especially if any errors are present m the electronic data, regardless of their source.
  • the information communicated to the wholesaler is processed by the message server, preferably interactively as indicated by block 138.
  • This processing may include negotiating products and services 140, negotiating due dates 142, and exception processing 134.
  • the processing by the wholesaler is facilitated by a customer service record interface 146, a telephone number interface 148, and a due date interface 150. These interfaces are illustrated and described m detail with reference to Figures 7-9, respectively.
  • Batch processing may include processing orders 154, in addition to transferring files to update feature availability, represented by block 156, and to update the address validation file, represented by block 158.
  • a commercial electronic file transfer program is used to transfer the address and feature availability files such as the Connect Direct software which is commercially available . - 17 -
  • FIG. 3 is a transaction flow diagram illustrating a pre-ordering exchange between a telecommunications provider and a telecommunications reseller as implemented in one embodiment of the present invention.
  • Reseller 50 uses the feature availability file and address validation file which was previously transmitted to verify the availability of the requested feature for a particular address and to authenticate or validate the address as indicated at reference numerals 208 and 210.
  • a telephone number inquiry may be initiated by reseller 50 and sent to wholesaler 22 using purchase order transaction set (850) with a transaction code of T10, for example, as indicated by reference numeral 212.
  • Wholesaler 22 generates a response using purchase order acknowledgment transaction set (855) as indicated by reference numeral 214.
  • a telephone number reservation may then be - 18 - mitiated by reseller 50 and transmitted to wholesaler 22 using purchase order transaction set (850) with a transaction code or type of T20 as indicated by reference numeral (216) .
  • wholesaler 22 confirms the telephone number reservation to reseller 50 using purchase order acknowledgment transaction set (855) as indicated by reference numeral 218.
  • a due date inquiry, initiated by reseller 50 is sent to wholesaler 22 using purchase order transaction set (850) with a transaction type of R10 as indicated by reference numeral 220.
  • Wholesaler 22 responds using purchase order acknowledgment transaction set (855) as indicated by reference numeral 222.
  • This is followed by a due date reservation initiated by reseller 50 and forwarded to wholesaler 22 using purchase order transaction set (850) indicating a transaction type of R20 as indicated by reference numeral 224.
  • the purchase order acknowledgment transaction set (855) is again used to confirm the due date reservation as indicated by reference numeral 226.
  • Various other transaction pairs utilizing the purchase order transaction set (850) and purchase order acknowledgment transaction set (855) may also be exchanged.
  • a telephone number reservation cancellation may be initiated by reseller 50 and then confirmed by wholesaler 22.
  • a telephone number reservation inquiry may be initiated by reseller 50 with an appropriate transaction code or type, such as T40 and confirmed by wholesaler 22 when appropriate.
  • due date reservation cancellations and confirmations may be initiated and confirmed by reseller 50 and wholesaler 22, respectively.
  • FIG. 4 is a block diagram illustrating one embodiment of an address validation interface for automated electronic telecommunications ordering according to the present invention.
  • Address validation interface 250 provides regular address validation information updates from the wholesaler to the reseller.
  • the reseller is provided with a text file having fixed length fields for a particular geographic area, such as one address file for each state. This allows the reseller to determine which central office
  • each set of address records is retrieved from the address file as represented by block 254.
  • Each set of records is selected by matching one or more of the data fields including street, direction, zip code, state, and community name, as represented by block 256.
  • the house or building number is compared to determine whether it is within a valid range for the particular street and direction as represented by block 258. Subsequently, an odd/even check may be performed where appropriate as represented by block 260. Any remarks which may provide additional information to be submitted on the service order are represented by block 262.
  • the system determines a unique central office code corresponding to the address information to identify the particular central office which services that address as represented by block 264. This information is then used to identify a rate band and access area information for the customer's address as represented by block 266. -20 -
  • Figure 5 is a block diagram illustrating one embodiment of a feature availability file for automated electronic telecommunications ordering according to the present invention.
  • feature availability interface 280 provides regular feature availability information updates to resellers from the wholesalers as described above.
  • the reseller is provided with three types of text files having fixed length fields including a central office feature file 282, a prefix feature file 284, and a prefix cross-reference file 286.
  • each geographic region such as a state, has associated feature files 282, 284, and 286.
  • Central office feature file 282 contains feature information for each central office in a particular area code and one or more exchanges. Where a central office includes more than one switch, central office feature file 282 contains information about which switch provides each feature as represented by reference numeral 290. Feature file 282 may include information relative to features such as remote access call forwarding 292, call waiting 294, caller ID 296 and voicemail 298. Preferably, data elements within feature file 282 include the Numbering Plan Area (NPA) , commonly known as the area code, the exchange which serves the customer, the central office code, the date on which the most recent changes became effective, the feature Universal Service Ordering Code (USOC) , the switch identification, a feature exception indicator, an additional exception indicator, and a call-waiting exception indicator. - 21 -
  • NPA Numbering Plan Area
  • USOC feature Universal Service Ordering Code
  • Prefix feature file 284 preferably contains feature information 300 for each prefix within the NPA, while also identifying the central office that the prefix belongs to as represented by reference numeral 302.
  • prefix file 284 includes data fields for the NPA, exchange, central office ID, prefix, the date on which the most recent changes became effective, and indicators for: exception call-waiting, remote access call forwarding, feature exception, additional exceptions, and the USOC .
  • Prefix cross-reference file 286 preferably provides a cross-reference between the prefix 304 and central office 306 containing the prefix in addition to the switches 308 which service the prefix.
  • the information in this file is not required for standard processing of a customer order, unless specific prefixes are requested.
  • FIG. 6 is a flow chart illustrating one embodiment for feature availability processing for automated electronic telecommunications ordering according to the present invention. This process is preferably used in determining available features in a particular CO as well as determining switch identifica ion for COs serviced by more than one switch.
  • the CO code or switch identification may be used in a telephone number request.
  • the system retrieves the feature record from the central office feature file by matching with the central office field as represented by block 310.
  • the feature exception indicator is examined to determine whether the particular CO is serviced by more than one - 22 - switch as represented by block 312. If the CO is not serviced by more than one switch with differing features, the USOC table will contain all of the available features for that particular CO. Using this list, the system verifies that the requested features are available within the identified CO as represented by block 314. If any feature is not available, an appropriate message may be generated before submitting the request for a telephone number using the CO code as represented by block 326.
  • the additional exception indicator field is examined as represented by block 318. If none of the desired features contain an appropriate code in the additional exception indicator field, the desired features are available for all switches within the CO so the telephone number request is submitted with the CO code as represented by block 326. If any of the desired features do contain an appropriate code in the additional exception indicator field, not all of the desired features are available in each switch servicing the CO. In th s case, the USOC table is examined to determine if all of the desired features are provided by any one switch as represented by block 320. If any one switch provides all of the desired features, then the switch ID is added to the telephone number request as represented by block 322.
  • each feature may be assigned a code indicating its relative importance. The code may be determined by the reseller, the wholesaler, or the ultimate customer depending upon the particular application.
  • the switch ID which satisfies a greater number of selection criteria is then added to the telephone number request as represented by block 322.
  • the telephone number request is then submitted with the CO code and the switch ID (where appropriate) as represented by block 326.
  • the telecommunications reseller can ensure that the desired features are available for the serving CO retrieved through the address validation process.
  • the feature availability interface determines the switch which contains the desired features, or selects the switch which contains the most features based on quantity or importance.
  • the reseller can use the various feature files to determine all of the areas in which a particular feature is offered, determine which features are offered for a particular prefix (exchange) , and determine valid prefixes for a particular CO.
  • FIG. 7 is a block diagram illustrating one embodiment of a Customer Service Record (CSR) interface for automated electronic telecommunications ordering according to the present invention.
  • CSR Customer Service Record
  • the CSR provides the reseller with on-line customer service records.
  • the reseller obtains customer account information by submitting EDI transactions and receiving EDI responses.
  • the reseller transmits a request for a Customer Service Record using the appropriate transaction set (preferably 850-ASCX12 version 003030) which is received by the wholesaler as represented by block 350.
  • the wholesaler processes the request as represented by block 352 and generates one of three responses represented by blocks 354, 356, and 358.
  • the responses are returned using a different transaction set, such as the 864-ASCX2 version 003030.
  • the request will result in forwarding of the appropriate CSR to the reseller as represented by block 354. However, the request may be rejected with an appropriate message as represented by block 356.
  • a letter of authorization is required as represented by block 358. If the transaction requires a letter of authorization, exception processing is performed by the wholesaler as represented by blocks 360-368.
  • An immediate reply is generated using the appropriate transaction set (preferably 864) and forwarded to the reseller to indicate that a letter of authorization is required as represented by block 360.
  • the appropriate CSR is then held in temporary storage as represented by block 362 for a predetermined time, preferably about 48 hours, as represented by block 364. If a letter of authorization is received within the predetermined time period, the CSR is released to the reseller as represented by block 366. Otherwise, the CSR is deleted from temporary storage as represented by block 368.
  • the CSR interface also accommodates requests received by E-mail. Resellers can send CSR data - 25 - requests to the wholesaler and receive either the desired CSR or error messages in return.
  • the CSR data and error messages have a text format and are meant to be read by people rather than computers.
  • the CSR interface uses the Flexible Communication Interface Format (FCIF) developed by Bellcore. This format uses a tag value methodology. Each request starts with an asterisk (*) followed by a code indicating the type of request. Braces ( ⁇ ) are used to enclose pairs of tag values and associated ASCII characters which provide the value for each data element. Data elements are separated by a semicolon. The percent sign (%) is used to denote the end of a request.
  • FCIF Flexible Communication Interface Format
  • CSR requests can be made within one e- mail by incorporating them into the text of a single e- mail message. However, each request is returned separately to avoid any negative impact on the e-mail network. Likewise, if the retrieved CSR data is particularly sizable, a response is sent indicating that the CSR has been retrieved but will be delayed for off- peak delivery.
  • FIG. 8 is a block diagram illustrating one embodiment of a telephone number interface for automated electronic telecommunications ordering according to the present invention.
  • Telephone number interface 380 provides interactive, on-line telephone number inquiry and reservation features to the reseller. In one embodiment of the present invention, four transactions are provided and handled on a real-time basis. Communications between the reseller and wholesaler are preferably based on EDI message formats with 850-ASCX12 version 003030 used for submissions by the reseller and - 26 -
  • a telephone number inquiry as represented by block 384 may be submitted as a Purchase Order (850) with a transaction type of T10. The corresponding response is issued as a Purchase Order Acknowledgment (855) .
  • the telephone number inquiry 384 may be used to determine the availability of a specific telephone number. Given a specific telephone number, the system will respond with a message indicating whether or not the telephone number is available as represented by block 386. Given a particular NPA and prefix, the system will return a predetermined or requested number of available telephone numbers as represented by block 388. Given a preferred telephone number pattern, the system will attempt to match the available numbers to the requested pattern and return a list of available numbers that match the desired pattern as represented by block 390.
  • the telephone number inquiry does not reserve telephone numbers for subsequent use in a service order. A separate transaction must be submitted to guarantee that the number will be held for a requester's service order as explained in greater detail below.
  • Telephone number interface 380 may also be used to assign a telephone number for use by a reseller in subsequent order processing as represented by block 392.
  • This transaction is submitted as a purchase order with a transaction type of T20. The response is issued using the purchase order acknowledgment transaction set.
  • the telephone number is reserved for a -27 - certain period of time as represented by block 394. In one embodiment of the present invention, the period of time is two hours. If a service order is not received within the predetermined time interval, the reservation is canceled and the telephone number will be returned to the available telephone number pool for use by other resellers and representatives.
  • a telephone number assignment cancellation request represented by block 396, is submitted using the purchase order transaction set with a transaction type of T30.
  • the response from the wholesaler to the reseller is issued using the purchase order acknowledgment transaction set.
  • the system determines whether the request came from the same reseller that initially reserved the telephone number as represented by block 398. If the reseller ID matches, the reservation is cancelled as represented by block 400 and the previously assigned telephone number is returned to the pool of available telephone numbers. Each request cancels only one telephone number reservation.
  • a telephone number assignment confirmation is transmitted using the purchase order transaction set with a transaction type of T40 as represented by block 402.
  • the response is issued using the purchase order acknowledgment transaction set.
  • This request is used to confirm that a telephone number is still assigned to a particular reseller. Confirmations for telephone number assignments can be made only by the reseller making the initial reservation. As such, the reseller - 28 - identification code is checked against the previously submitted assignment as represented by block 404.
  • FIG. 9 is a block diagram illustrating one embodiment of a due date interface for automated electronic telecommunications ordering according to the present invention.
  • Due date interface 410 provides online due date inquiry and reservation features.
  • due date interface 410 provides four transactions which are handled on a real-time basis. Preferably, all transactions are submitted using the purchase order transaction set (850-ASCX12 version 003030) with responses from the wholesaler using the purchase order acknowledgment transaction set (855-ASCX12 version 003030) .
  • a due date inquiry is submitted with a transaction type of R10 as represented by block 412. This transaction may be used to determine the availability of a specific due date as represented by block 414. Given a requested due date, the system will respond by indicating whether or not the due date is available and can be met based on the required service order activity. A due date inquiry may also be used to obtain a list of available due dates when a premises visit is required as represented by block 416. Given a description of the requested service order activity, the system provides the earliest possible due date in addition to a list of other available due dates. The due date inquiry does not reserve due dates for subsequent use in a service order. A separate due date assignment transaction 418 must be submitted to - 29 - guarantee that the due date will be held for a particular service order.
  • Due date assignment transaction 418 is submitted using the purchase order transaction set with a transaction type of R20. A response is issued using the purchase order acknowledgment transaction set . Due date transaction 418 allows the reseller to reserve a specific due date for use in subsequent order processing as represented by block 420. This transaction contains the same information as the inquire transaction 412 with the exception that the reseller submits a specific due date and a time-of-day preference, such as morning, afternoon, or all day. A due date assignment may be attempted without a previously submitted due date inquiry.
  • the due date Upon receipt of a due date assignment transaction 418, the due date is reserved for a predetermined period of time, such as two hours, as represented by block 420.
  • the reseller must submit a service order for the reserved due date within this time period or the reservation is automatically canceled. All requested products and services should be accurately represented on a due date assignment transaction. If the subsequently submitted service order contains information different from the due date assignment which impacts the due date, the service order may be rejected.
  • FIG 10 is a block diagram illustrating mapping and translation functions of one embodiment for automated electronic telecommunications ordering according to the present invention.
  • the mapping and translation functions being performed by the reseller, indicated generally by reference numeral 450, cooperate with similar mapping and translation functions of the wholesaler, indicated generally by reference numeral 452, preferably using a TCP/IP connection, indicated by reference numeral 454.
  • the mapping and translation functions are performed by software executing on one or more computers, such as the customer - 3 1 - service agent computers and message servers described and illustrated with reference to Figure 1.
  • the data gathered by the reseller is entered into one or more databases or forms 456 which include various data fields 458.
  • Forms 456 preferably represent various data entry screens on a computer operated by a customer service representative.
  • a mapping function is performed as indicated generally by reference numeral 460 to collect the information related to a particular electronic "document" 462.
  • a translator 464 also implemented in software, translates the data from electronic document 462 into an electronic message 466 using a standard transaction set.
  • Message 466 includes several segments 468 each having a segment identifier 470, a data segment identifier 472, and a data segment value 474.
  • the segments of a transaction set must occur in a particular sequence for proper processing.
  • a single electronic message 466 may contain multiple electronic documents 462 which are concatenated in a single data stream. Additional information is added to electronic message 466 for transmission via the TCP/IP link 454 to the wholesaler, such as routing information, error detection information, and the like, as well known in the art.
  • Translator 480 parses electronic message 466 to identify one or more transaction sets. Message syntax is examined and error messages are generated when appropriate. The received data is temporarily stored in electronic document 482 having data fields 484. The appropriate information is - 32 - then automatically transferred to the wholesaler's internal order system as represented by blocks 486 and 488. The order is processed and a response is generated, translated using the standard transaction set, and transmitted to the reseller. By reducing manual intervention, this system reduces operating expenses and increases accuracy. Furthermore, a realtime response is generated and communicated to reduce turn-around time.
  • This ordering section addresses use of TCIF-defined EDI standards for the purpose of providing a method of requesting telecommunication services.
  • This guide is intended to be a supplement to the information provided in the TCIF EDI Guidelines, Telecommunications Carrier Services, Issue 5.
  • the TCIF guidelines should be consulted for specific detail when necessary.
  • Envelopes provide the interchange control structure for transmuting business transactions.
  • the interchange control header (ISA) and interchange control trailer (IEA) envelope one or more functional group header/trailer pairs (GS/GE). They identify the sender and receiver, provide function group control header (GS) information, and allow for authorization and security information.
  • the ISA is transmitted first, followed by the data in functional groups with the interchange trailer at the end. The sequence for the transaction sets follows:
  • More than one ST/SE pair, each representing a transaction set, may be used within one functional group.
  • envelope layouts for Preorde ⁇ ng and Ordering are included to illustrate the different identifications required m the ISA08 element for documents sent to the wholesaler and the ISA06 element for documents sent from the wholesaler.
  • This standard provides the interchange envelope of a header and trailer for the electronic interchange through a data transmission, and it provides a structure to acknowledge the receipt and processing of tins envelope.
  • Authonzation Information M AN 10/10 Information used for additional identification or authonzation of the sender or the data in the interchange.
  • the type of information is set by the Authonzation Information Qualifier (101).
  • Qualifier to designate the system method of code structure used to designate the sender or receiver ID element bemg qualified 01 Duns (Dun & Bradstreet)
  • ICNs should only be reused once the full 100,000,000 possible combmations have been exhausted and should not be reused when resubmitting a revised order using the same purchase order number.
  • Test Indicator M ID 1/1 Code to indicate whether data enclosed by this interchange envelope is test or production
  • Subelement separator hexidecimal Al Element separator, hexidecimal 4C Segment separator, hexidecimal 15
  • a functional group of related transaction sets withm the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
  • CA Purchase Order iange Acknowledgement (865) PC Purchase Order Change (860) PO Purchase Order (850) PR Purchase Order Acknowledgement (855) RQ Reseller Notification (836) RS Order Status Information (870) TX Text Message (864)
  • HHMMSS 24-hour clock time
  • Semantic Notes 1
  • the transaction set identifier (STOl) used by the translation routines of the interchange partners to select the approp ⁇ ate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
  • Max Use 1 Purpose: To indicate the beginning of the Contract Award Transaction Set and to transmit identifying numbers and dates.
  • This section contains the format and establishes the data contents of the Procurement Notices Transaction Set (836) for use withm the context of an Electronic Data Interchange (EDI) environment. Only the segments used by AIIS for the reseller notification are listed.
  • PIC/LPIC changes is an optional offe ⁇ ng
  • Semantic Notes 1
  • the transaction set identifier (STO 1 ) used by the translation routmes of the interchange partners to select the approp ⁇ ate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
  • Alphanumenc characters assigned for differentiation withm a transaction set Must be equal 1 or higher; do not use 0
  • P9 Pnmary Interexchange Carner P9 Pnmary Interexchange Carner (PIC)
  • the transaction set can be used to provide for customary and established busmess and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
  • CTTOl The number of line items
  • Semantic Notes 1
  • the transaction set identifier (STOl) used by the translation routmes of die interchange partners to select the approp ⁇ ate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
  • Number identifies a telecommunications industry account
  • Billing account telephone number (telecommunication earners for billing of unbundled product orders)
  • SI02 A A A/Establish new account C/Change existing account D/Disconnect account T/Outside move V/ Assume as specified W/ Assume as is
  • Service Characte ⁇ stic Qualifier and Product Service ID may be repeated ten times m segment.
  • At least one of PID04 or PID05 is required.
  • PID07 is present, then PID03 is required.
  • PID08 is present, then PID03 is required.
  • Semantic Notes 1 Use PID03 to indicate the organization that publishes die code list being referred to.
  • PID08 desc ⁇ bes the physical charactenstics of die product identified in PID04.
  • a " Y” indicates that the specified att ⁇ bute applies to this item.
  • a "N” indicates it does not apply. Any other value is indeterminate.
  • 3 PID07 specifies the mdividual code list of the agency specified m PID03
  • a reference diat indicates die table or text maintamed by the Source Qualifier
  • DI Directory Code indicating die title or contents of a document, report or supporting item DI Directory
  • Reports diat provide information about a subject, name, product, etc.
  • N402 is required only if city name (N401) is m the USA or Canada.
  • NX201 defines me type of address component.
  • NX202 defines the address component identified in NX201.
  • a walled room or partitioned area of a building 36 Slip
  • NX202 166 Address Information AN 1/35 Address information Floor, room, building, etc.
  • Item Identifier e.g., Lme USOC, HTY, ML, CLT, etc.

Abstract

A system and method for electronically exchanging information related to telecommunication services (20) includes separating data representing the information to be exchanged into predefined segments corresponding to telecommunication services (124), associating a segment identification code with each segment, and grouping each segment identification code with corresponding data (122). The system and method also include concatenating the segment identification codes and associated data according to a predefined sequence to form an electronic transaction (130) and transmitting the electronic message to a telecommunications wholesaler or reseller (132). Preferably, the information is exchanged over a TCP/IP connection (136) in an interactive, transaction-based exchange (138).

Description

- 1 -
TRANSACTION SETS FOR AUTOMATED
ELECTRO C ORDERING OF TELECOMMUNICATIONS
PRODUCTS AND SERVICES
Copyright Notice
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Cross-Reference To Related Applications
This application is related to commonly owned applications Serial No. 09/056,023 titled "Automated Electronic Telecommunications Order Translation And Processing" and application Serial No. 09/056,001 titled "Interactive Electronic Ordering For Telecommunication Products And Services" all filed the same day, April 6, 1998, the disclosures of which are hereby incorporated by reference in their entirety.
Technical Field
The present invention relates to electronic ordering of telecommunications services and products . - 2 -
Background Art
Businesses of all sizes rely on computers and communication systems now more than ever before.
However, the widespread use of computers has not brought about the paperless office anticipated by the visionaries of the 1970s. Electronic Data Interchange
(EDI) has been developed to provide a standard format for exchanging basic business data among firms that regularly conduct business with one another. EDI may be used to replace a wide variety of common business forms including purchase orders, invoices, shipping and packing slips, and numerous others, to eliminate costs associated with handling paper documents resulting in more efficient utilization of resources and increased accuracy.
The structure and content of electronic documents are defined by transaction sets. Similar to their physical counterparts, standard transaction sets include line items, referred to as data segments, and specific items, referred to as data elements. For example, data elements in an invoice might include quantity, product identification, unit price, and extended price. Hundreds of approved (standardized) transaction sets have been published by standards committees for various industries.
Telecommunications services and products are currently ordered from wholesalers primarily in a manual fashion, either by voice contact or exchange of paper forms. Where electronic methods are in use, they are generally batch-oriented, form-based file exchange -3 - processes, or utilize proprietary interfaces which may include Internet browser technology, for example. While some telecommunication companies have implemented EDI ordering systems, these systems typically require manual intervention to enter received EDI orders into the company's internal order system. Although EDI has been proposed for ordering of telecommunication products and services for several years, there has not yet been a significant implementation of EDI for this purpose.
Telephone Local Exchange Carriers (LEC) are now required to provide some type of system and method for Telecommunications Carriers to electronically place orders with an LEC for wholesale bundled exchange products and/or services m addition to unbundled elements of the telecommunications network. The various LECs have developed differing solutions such as providing direct access to their internal ordering systems, creating Internet browser forms for order entry, or creating proprietary application-to- application interface protocols.
The various objects, advantages, and features of the present invention will be readily apparent from the following detailed description of the best mode for carrying out the invention when taken in connection with the accompanying drawings.
Brief Description Of The Drawings
FIGURE 1 is a diagram illustrating a Public Switched Telephone Network (PSTN) for application of - 4 - automated electronic telecommunications product/service ordering according to the present invention;
FIGURE 2 is a flow chart illustrating one embodiment of a process for automated electronic ordering of telecommunication products and/or services according to the present invention;
FIGURE 3 is a transaction flow diagram illustrating a pre-ordermg exchange between a telecommunications provider and a telecommunications reseller as implemented m one embodiment of the present invention;
FIGURE 4 is a block diagram illustrating one embodiment of an address validation interface for automated electronic telecommunications ordering according to the present invention;
FIGURE 5 is a block diagram illustrating one embodiment of a feature availability file for automated electronic telecommunications ordering according to the present invention;
FIGURE 6 is a flow chart illustrating one embodiment for feature availability processing for automated electronic telecommunications ordering according to the present invention;
FIGURE 7 is a block diagram illustrating one embodiment of a Customer Service Record (CSR) interface for automated electronic telecommunications ordering according to the present invention; FIGURE 8 is a block diagram illustrating one embodiment of a telephone number interface for automated electronic telecommunications ordering according to the present invention;
FIGURE 9 is a block diagram illustrating one embodiment of a due date interface for automated electronic telecommunications ordering according to the present invention; and
FIGURE 10 is a block diagram illustrating mapping and translation functions of one embodiment for automated electronic telecommunications ordering according to the present invention.
Detailed Description Of Preferred Embodiments
Automated electronic processing of orders for telecommunications products and services according to the present invention minimizes or eliminates human intervention to reduce or eliminate costs associated with handling paper documents. The present invention provides a real -time, interactive interface for telecommunications resellers to increase accuracy and reduce turn-around time. The development of transaction sets particularly suited for telecommunications services and products provides a standard method for electronic ordering where external access to dynamic data is required. Automated translation to and from unique or proprietary interfaces used by individual resellers to standard transaction sets further reduces manual intervention while providing increased flexibility for telecommunication product/services resellers. - 6 -
Figure 1 is a diagram illustrating a Public Switched Telephone Network (PSTN) for application of automated electronic telecommunications product/service ordering according to the present invention. The PSTN, indicated generally by reference numeral 20, includes a number of Local Exchange Carriers (LEC) , such as LEC 22, which function as wholesalers for telecommunication products and services. Each LEC 22 owns and/or manages one or more Central Offices (CO) , indicated generally by reference numeral 24, such as Central Offices 26-36. As is known, each CO 24 typically serves a particular geographic area and includes various hardware and software to deliver telecommunication services. Such hardware includes one or more switches 38, 40 to provide a communication path for a telephone call. The various COs 24 are typically connected using one or more circuits 42 which are classified based on bandwidth capability, signal protocol, or the like, as also well known in the art .
A telecommunications reseller 50 interfaces with end users or customers 52, 54 to provide various retail telecommunications products and services 56 such as caller ID 58, remote access call forwarding 60, and call waiting 62, for example. Reseller 50 provides the customer service functions including invoicing, collections, service inquiries, new telephone numbers, directory listings, and the like. Each customer 52, 54 may have one or more telecommunications devices 64 such as a computer 66 or telephone 68, sometimes referred to as premises equipment (PE) . Customers typically include both residential customers, such as customer 52, and business or commercial customers, such as customer 54. Business customer 54 may have a Private Branch exchange (PBX) which interfaces with a switch such as switch 42 in the local CO 34. The PBX provides connections between and among internal PE in addition to coordinating access to external lines (circuits) .
To provide prompt and efficient customer support, reseller 50 preferably utilizes automated electronic ordering according to the present invention to provide telecommunications products/services 64 to customers 52, 54. Reseller 50 employs customer service agents 70 which process requests from customers 52, 54 relative to telecommunications products and services. Customer service agents 70 preferably utilize one or more computers 72 to enter information received from customers 52, 54 which is then communicated to a message server 74 which preforms two primary functions. Message server 74 manages communications between itself and computers (clients) 72 while also providing a single access point for communication with telecommunications wholesaler 22. Message server 74 communicates with a router 76 which preferably permits only messages conforming to the Transmission Control Protocol/Internet Protocol (TCP/IP) between reseller 50 and wholesaler 22. Router 76 communicates with DSU/CSU (Digital Service Unit/Customer Service Unit) 78 to facilitate digital communications. Depending upon the particular bandwidth requirement of reseller 50, i.e., the quantity, complexity, and frequency of transactions between reseller 50 and wholesaler 22, a particular class of circuit 42 is selected and installed. This may include DS0 (Digital Service Level 0 - 56Kbps) /DS1 (Digital Service Level 1 - 1.5Mbps) 90, Tl 92, frame relay 94, or the like. - 8 -
Wholesaler 22 includes similar equipment such as a message server 100, router 102, and DSU/CSU 104. Messaging between reseller 50 and wholesaler 22 is preferably accomplished using a dedicated connection which may be facilitated by one or more of the circuits described above. In an alternative embodiment, reseller 50 may communicate with wholesaler 22 via a Value Added Network (VAN) provider 110 operated by a third party. Preferably, messaging between server 100 of wholesaler 22 and server 74 of reseller 50 is performed using a simple character protocol, such as the Enterprise Access Protocol (EAP) . In a preferred embodiment, EAP commands are sent from the server 74 of reseller 50 to server 100 of wholesaler 22 over a TCP/IP socket connection. The EAP commands are used to establish an application session to exchange electronic information between reseller 50 and wholesaler 22. Each message preferably includes a sender's reference (SNRF) which is generated by reseller 50 and used for routing purposes. This facilitates the distribution of messages by server 74 to customer service agents 70 via computers 72. In a preferred embodimen , the SNRF contains a unique identification code in the first six characters corresponding to a particular reseller 50. The last six characters of the SNRF are reserved for assignment by reseller 50 to uniquely identify a particular customer service agent 70 or computer 72. This enables reseller 50 to appropriately route messages received from wholesaler 22 through message server 74.
Preferably, each message server 74 which interacts with message server 100 of wholesaler 22 has a unique identification and password. To improve configuration flexibility, in one embodiment of the - 9 - present invention passwords are required only at the start of a particular session and are not required for each transaction set or electronic document exchanged. Also preferably, a packet filter firewall is used which permits only packets destined for a correctly defined static IP address and service port to further improve security. The connection established between reseller 50 and wholesaler 22 may be used to transfer files in addition to the defined transaction sets as described in greater detail below.
Functional descriptions for representative transaction sets applicable to automated electronic telecommunications ordering according to the present invention are set forth in Table 1 below. Detailed specifications for the transaction sets along with examples of use for representative transactions are provided in the Appendix preceding the claims.
■ 10 -
Transaction Description Set
836 Reseller notification (Contract Award)
850 Purchase order
855 Purchaser order acknowledgment
860 Buyer initiated purchaser order change request
864 Text message
865 Purchase order change acknowledgment
870 Reseller order status
997 Functional acknowledgment
Figure imgf000012_0001
Tabie 1. Telecommunications Transaction Sets
Preferably, all transaction sets are approved by a recognized standards organization such as the American National Standards Institute (ANSI), or the International Standards Organization (ISO) . In one preferred embodiment of the present invention the transaction sets conform to the ANSI Accredited Standards Committee (ASC) X12 , the committee that develops and maintains generic requirements for EDI in the United States .
The electronic reseller notification transaction set is used to convey advance notice of a change of local service provider, confirmation when that - 11 - change is completed, and notice if the planned change is cancelled. This transaction set is referred to as a contract award by ANSI .
The purchase order transaction set (850) may be used to provide for customary and established business and industry practice relative to the placement of purchase orders for telecommunications goods and services. For example, the reseller would use this transaction set to request telecommunications services from the wholesaler. Preferably, the purchase order is used to request any of the following types of services, each based on unique transaction identifiers contained within the transaction set: telephone number inquiries, reservations, reservation cancellations, and reservation confirmations; due date inquiries, reservations, reservation cancellations, and reservation confirmations; customer service record requests; and service requests.
The purchase order acknowledgment transaction set (855) is preferably used as an acknowledgment from the wholesaler to the reseller. This transaction set provides scheduling information, telephone and circuit number information, and the like, in response to receipt of a purchase order transaction (850) for one of the transactions identified above. Purchase order changes are preferably communicated using the Purchase Order
Change Request - Buyer Initiated transaction set (860) .
For example, the reseller would use this transaction set to request a change to a previously submitted purchase order. - 12 -
The Text Message transaction set (864) is intended to provide electronic communication for people, not necessarily for computer processing as with the other transaction sets. The use of this transaction set requires that the sender have certain detailed information about the recipient in some human-readable form. The recipient's network dictates the available capabilities for delivery of the information contained within the transaction. It is the responsibility of the sender to obtain this information and include it in the transmission. This transaction set may be used to respond to a customer service record request to provide information about an existing customer of the wholesaler to the reseller.
The Purchase Order Change Acknowledgment transaction set (865) is used to convey acceptance or rejection of changes to a previously submitted purchase order by the wholesaler or to notify the reseller of changes initiated by the wholesaler to a previously submitted purchase order by the wholesaler. This transaction is also used to notivy the wholesaler that an order has been completed.
The reseller order status transaction set may be used to convey jeopardies which occur on an order after the 855 transaction set has been communicated. This transaction set may be used to provide status on individual line items of a purchase order or on the entire order.
The Functional Acknowledgment transaction set (997) is used to define the control structures for a set of acknowledgments to indicate the results of the - 13 - syntactical analysis of the electronically encoded documents using other transaction sets. This transaction set includes data segments used to identify which electronic document (transaction set) contains an error and where the error occurred within the document.
Figure 2 is a flow chart illustrating one embodiment of a process for automated electronic ordering of telecommunication products and/or services according to the present invention. As will be appreciated by one of ordinary skill in the art, the various steps, tasks, or functions illustrated are not necessarily sequential in nature. As such, the present invention is generally independent of the particular sequence or order m which the tasks or steps are completed. Various steps, tasks, or functions may be completed simultaneously, virtually simultaneously, or may be separated by minutes, hours, or days without departing from the spirit or scope of the present invention. Preferably, the present invention performs automatic electronic ordering of telecommunications using computer- o-computer communications exclusively, meaning that no human intervention is required to reduce or eliminate keying errors, mishandled or lost forms, and the like. However, the present invention incorporates exception processing which may include some level of human intervention to process unique or as yet undefined transactions.
The functions, steps, or tasks illustrated m the figures are preferably performed by a programmed microprocessor executing instructions stored in or on a computer readable storage medium. One of ordinary skill in this art will recognize that the functions, steps, or - 14 - tasks are independent of the particular type of instruction set, storage medium, microprocessor, or processing strategy and may be performed by software, hardware, integrated circuits, firmware, microcode, and the like, operating alone or in combination. Likewise, processing strategies may include multi-processing, multi-tasking, parallel processing, and the like without departing from the spirit or scope of the present invention. Computer readable storage media may include various types of volatile and non-volatile storage media including but not limited to random access memory (RAM) , read-only memory (ROM) , programmable read-only memory (PROM) , electrically programmable read-only memory (EPROM) , electrically erasable read-only memory (EEPROM) , flash memory, magnetic tape or disk, optical media, and the like.
Block 120 of Figure 2 represents gathering customer information during a pre-ordeπng process. This is typically performed by the reseller in response to a customer inquiry or request for a service.
However, this step may also be initiated by the reseller or wholesaler under particular circumstances, such as in the event of termination of service for non-payment, area code changes, feature availability changes, and the like. For a representative transaction, the reseller gathers appropriate information depending upon the particular telecommunications service or product . The resellers use internal computing systems, such as computers 72, and/or databases to collect the appropriate items which constitute a particular transaction set for an electronic exchange of information. However, the information necessary for a particular transaction set may be scattered about - 15 - vaπous fields and/or databases depending upon the particular reseller's implementation. As such, the information or data is collected or mapped to a particular transaction set to form an electronic "document" as indicated by reference numeral 122.
The gathered information is validated as represented by block 124 using an address validation file 126 (illustrated and described with reference to Figure 4) and a feature availability file 128 (illustrated and described with reference to Figures 5- 6) .
The information is translated into a standard EDI format as represented by block 130. Likewise, block 130 represents the reciprocal function of translating an EDI transaction received by the reseller back to the reseller's internal format. The translation function 130 allows the reseller to format the data conveniently for the customer service representatives rather than being forced to conform to the pre-defined EDI format. Automatic translation according to the present invention reduces or eliminates human intervention to transfer the data contained in an EDI transaction into the reseller's internal forms and format. However, the standardized EDI format allows the reseller and/or wholesaler to conduct business with other wholesalers and resellers who conform to the standard, respectively.
Once validated, the information is communicated from the reseller to the wholesaler (or vice versa) as represented by block 132. This may be accomplished using a dedicated or direct connection between the reseller and the wholesaler, or by using a - 16 -
VAN as described above. While this communication may be completed in a batch mode 134, it is preferably communicated using a TCP/IP socket connection during an interactive, substantially real-time session, i.e., while the reseller is "on-line" as represented by reference numeral 136. While batch processing may be used to take advantage of lower volume traffic during off-peak times, it delays processing and reduces efficiency, especially if any errors are present m the electronic data, regardless of their source.
The information communicated to the wholesaler is processed by the message server, preferably interactively as indicated by block 138. This processing may include negotiating products and services 140, negotiating due dates 142, and exception processing 134. Preferably, the processing by the wholesaler is facilitated by a customer service record interface 146, a telephone number interface 148, and a due date interface 150. These interfaces are illustrated and described m detail with reference to Figures 7-9, respectively.
Batch processing, represented by block 152, may include processing orders 154, in addition to transferring files to update feature availability, represented by block 156, and to update the address validation file, represented by block 158. In one preferred embodiment of the present invention, a commercial electronic file transfer program is used to transfer the address and feature availability files such as the Connect Direct software which is commercially available . - 17 -
Figure 3 is a transaction flow diagram illustrating a pre-ordering exchange between a telecommunications provider and a telecommunications reseller as implemented in one embodiment of the present invention. Once a relationship has been established between reseller 50 and wholesaler 22, reseller 50 receives regular transmissions of a feature availability file 200 and address validation file 202 for subsequent use in processing customer orders. When reseller 50 receives an order or inquiry from a customer, reseller 50 initiates an electronic request for customer service record information and transmits the request to wholesaler 22 using either the purchaser order transaction set (850) as indicated by reference numeral 204. If the customer service record request has appropriate authorization, the corresponding customer service record is forwarded to the reseller using the customer service record response transaction set (864) as indicated by reference numeral 206.
Reseller 50 uses the feature availability file and address validation file which was previously transmitted to verify the availability of the requested feature for a particular address and to authenticate or validate the address as indicated at reference numerals 208 and 210. As part of the same transaction, or as part of a separate transaction, a telephone number inquiry may be initiated by reseller 50 and sent to wholesaler 22 using purchase order transaction set (850) with a transaction code of T10, for example, as indicated by reference numeral 212. Wholesaler 22 generates a response using purchase order acknowledgment transaction set (855) as indicated by reference numeral 214. A telephone number reservation may then be - 18 - mitiated by reseller 50 and transmitted to wholesaler 22 using purchase order transaction set (850) with a transaction code or type of T20 as indicated by reference numeral (216) . In response, wholesaler 22 confirms the telephone number reservation to reseller 50 using purchase order acknowledgment transaction set (855) as indicated by reference numeral 218.
A due date inquiry, initiated by reseller 50 is sent to wholesaler 22 using purchase order transaction set (850) with a transaction type of R10 as indicated by reference numeral 220. Wholesaler 22 responds using purchase order acknowledgment transaction set (855) as indicated by reference numeral 222. This is followed by a due date reservation initiated by reseller 50 and forwarded to wholesaler 22 using purchase order transaction set (850) indicating a transaction type of R20 as indicated by reference numeral 224. The purchase order acknowledgment transaction set (855) is again used to confirm the due date reservation as indicated by reference numeral 226.
Various other transaction pairs utilizing the purchase order transaction set (850) and purchase order acknowledgment transaction set (855) may also be exchanged. For example, a telephone number reservation cancellation may be initiated by reseller 50 and then confirmed by wholesaler 22. Likewise, a telephone number reservation inquiry may be initiated by reseller 50 with an appropriate transaction code or type, such as T40 and confirmed by wholesaler 22 when appropriate. In a similar fashion, due date reservation cancellations and confirmations may be initiated and confirmed by reseller 50 and wholesaler 22, respectively. - 19 -
Figure 4 is a block diagram illustrating one embodiment of an address validation interface for automated electronic telecommunications ordering according to the present invention. Address validation interface 250 provides regular address validation information updates from the wholesaler to the reseller.
Preferably, the reseller is provided with a text file having fixed length fields for a particular geographic area, such as one address file for each state. This allows the reseller to determine which central office
(CO) services a particular customer's address or Living
Unit (LU) . This information is validated as represented by block 252.
Using the address information provided by the customer and transmitted by the reseller, each set of address records is retrieved from the address file as represented by block 254. Each set of records is selected by matching one or more of the data fields including street, direction, zip code, state, and community name, as represented by block 256. The house or building number is compared to determine whether it is within a valid range for the particular street and direction as represented by block 258. Subsequently, an odd/even check may be performed where appropriate as represented by block 260. Any remarks which may provide additional information to be submitted on the service order are represented by block 262. The system determines a unique central office code corresponding to the address information to identify the particular central office which services that address as represented by block 264. This information is then used to identify a rate band and access area information for the customer's address as represented by block 266. -20 -
Figure 5 is a block diagram illustrating one embodiment of a feature availability file for automated electronic telecommunications ordering according to the present invention. In a preferred embodiment, feature availability interface 280 provides regular feature availability information updates to resellers from the wholesalers as described above. In this embodiment, the reseller is provided with three types of text files having fixed length fields including a central office feature file 282, a prefix feature file 284, and a prefix cross-reference file 286. Preferably, each geographic region, such as a state, has associated feature files 282, 284, and 286.
Central office feature file 282 contains feature information for each central office in a particular area code and one or more exchanges. Where a central office includes more than one switch, central office feature file 282 contains information about which switch provides each feature as represented by reference numeral 290. Feature file 282 may include information relative to features such as remote access call forwarding 292, call waiting 294, caller ID 296 and voicemail 298. Preferably, data elements within feature file 282 include the Numbering Plan Area (NPA) , commonly known as the area code, the exchange which serves the customer, the central office code, the date on which the most recent changes became effective, the feature Universal Service Ordering Code (USOC) , the switch identification, a feature exception indicator, an additional exception indicator, and a call-waiting exception indicator. - 21 -
Prefix feature file 284 preferably contains feature information 300 for each prefix within the NPA, while also identifying the central office that the prefix belongs to as represented by reference numeral 302. In one preferred embodiment, prefix file 284 includes data fields for the NPA, exchange, central office ID, prefix, the date on which the most recent changes became effective, and indicators for: exception call-waiting, remote access call forwarding, feature exception, additional exceptions, and the USOC .
Prefix cross-reference file 286 preferably provides a cross-reference between the prefix 304 and central office 306 containing the prefix in addition to the switches 308 which service the prefix. The information in this file is not required for standard processing of a customer order, unless specific prefixes are requested.
Figure 6 is a flow chart illustrating one embodiment for feature availability processing for automated electronic telecommunications ordering according to the present invention. This process is preferably used in determining available features in a particular CO as well as determining switch identifica ion for COs serviced by more than one switch. When necessary, the CO code or switch identification may be used in a telephone number request. Using the CO code retrieved from the address validation process described above, the system retrieves the feature record from the central office feature file by matching with the central office field as represented by block 310. The feature exception indicator is examined to determine whether the particular CO is serviced by more than one - 22 - switch as represented by block 312. If the CO is not serviced by more than one switch with differing features, the USOC table will contain all of the available features for that particular CO. Using this list, the system verifies that the requested features are available within the identified CO as represented by block 314. If any feature is not available, an appropriate message may be generated before submitting the request for a telephone number using the CO code as represented by block 326.
If the CO is serviced by more than one switch with varying features as determined by block 312, then the additional exception indicator field is examined as represented by block 318. If none of the desired features contain an appropriate code in the additional exception indicator field, the desired features are available for all switches within the CO so the telephone number request is submitted with the CO code as represented by block 326. If any of the desired features do contain an appropriate code in the additional exception indicator field, not all of the desired features are available in each switch servicing the CO. In th s case, the USOC table is examined to determine if all of the desired features are provided by any one switch as represented by block 320. If any one switch provides all of the desired features, then the switch ID is added to the telephone number request as represented by block 322.
If all of the desired features are not provided by any one switch, all of the requirements will not be able to be met and the system (or a service representative) must select the switch which provides - 23 - either the greatest number of features, or the most important features. For this process, each feature may be assigned a code indicating its relative importance. The code may be determined by the reseller, the wholesaler, or the ultimate customer depending upon the particular application. The switch ID which satisfies a greater number of selection criteria is then added to the telephone number request as represented by block 322. The telephone number request is then submitted with the CO code and the switch ID (where appropriate) as represented by block 326.
Using the feature availability interface m an interactive mode, the telecommunications reseller can ensure that the desired features are available for the serving CO retrieved through the address validation process. Where the CO serving the customer includes more than one switch, the feature availability interface determines the switch which contains the desired features, or selects the switch which contains the most features based on quantity or importance. The reseller can use the various feature files to determine all of the areas in which a particular feature is offered, determine which features are offered for a particular prefix (exchange) , and determine valid prefixes for a particular CO.
Figure 7 is a block diagram illustrating one embodiment of a Customer Service Record (CSR) interface for automated electronic telecommunications ordering according to the present invention. The CSR provides the reseller with on-line customer service records. The reseller obtains customer account information by submitting EDI transactions and receiving EDI responses. -24 -
The reseller transmits a request for a Customer Service Record using the appropriate transaction set (preferably 850-ASCX12 version 003030) which is received by the wholesaler as represented by block 350. The wholesaler processes the request as represented by block 352 and generates one of three responses represented by blocks 354, 356, and 358. Preferably, the responses are returned using a different transaction set, such as the 864-ASCX2 version 003030.
Typically, the request will result in forwarding of the appropriate CSR to the reseller as represented by block 354. However, the request may be rejected with an appropriate message as represented by block 356. For some transactions, a letter of authorization is required as represented by block 358. If the transaction requires a letter of authorization, exception processing is performed by the wholesaler as represented by blocks 360-368. An immediate reply is generated using the appropriate transaction set (preferably 864) and forwarded to the reseller to indicate that a letter of authorization is required as represented by block 360. The appropriate CSR is then held in temporary storage as represented by block 362 for a predetermined time, preferably about 48 hours, as represented by block 364. If a letter of authorization is received within the predetermined time period, the CSR is released to the reseller as represented by block 366. Otherwise, the CSR is deleted from temporary storage as represented by block 368.
In one preferred embodiment of the present invention, the CSR interface also accommodates requests received by E-mail. Resellers can send CSR data - 25 - requests to the wholesaler and receive either the desired CSR or error messages in return. The CSR data and error messages have a text format and are meant to be read by people rather than computers. In this embodiment, the CSR interface uses the Flexible Communication Interface Format (FCIF) developed by Bellcore. This format uses a tag value methodology. Each request starts with an asterisk (*) followed by a code indicating the type of request. Braces ({}) are used to enclose pairs of tag values and associated ASCII characters which provide the value for each data element. Data elements are separated by a semicolon. The percent sign (%) is used to denote the end of a request. Several CSR requests can be made within one e- mail by incorporating them into the text of a single e- mail message. However, each request is returned separately to avoid any negative impact on the e-mail network. Likewise, if the retrieved CSR data is particularly sizable, a response is sent indicating that the CSR has been retrieved but will be delayed for off- peak delivery.
Figure 8 is a block diagram illustrating one embodiment of a telephone number interface for automated electronic telecommunications ordering according to the present invention. Telephone number interface 380 provides interactive, on-line telephone number inquiry and reservation features to the reseller. In one embodiment of the present invention, four transactions are provided and handled on a real-time basis. Communications between the reseller and wholesaler are preferably based on EDI message formats with 850-ASCX12 version 003030 used for submissions by the reseller and - 26 -
855-ASCX12 version 003030 used for responses from the wholesaler.
A telephone number inquiry as represented by block 384 may be submitted as a Purchase Order (850) with a transaction type of T10. The corresponding response is issued as a Purchase Order Acknowledgment (855) . The telephone number inquiry 384 may be used to determine the availability of a specific telephone number. Given a specific telephone number, the system will respond with a message indicating whether or not the telephone number is available as represented by block 386. Given a particular NPA and prefix, the system will return a predetermined or requested number of available telephone numbers as represented by block 388. Given a preferred telephone number pattern, the system will attempt to match the available numbers to the requested pattern and return a list of available numbers that match the desired pattern as represented by block 390. The telephone number inquiry does not reserve telephone numbers for subsequent use in a service order. A separate transaction must be submitted to guarantee that the number will be held for a requester's service order as explained in greater detail below.
Telephone number interface 380 may also be used to assign a telephone number for use by a reseller in subsequent order processing as represented by block 392. This transaction is submitted as a purchase order with a transaction type of T20. The response is issued using the purchase order acknowledgment transaction set. Upon receipt of the telephone number assignment transaction, the telephone number is reserved for a -27 - certain period of time as represented by block 394. In one embodiment of the present invention, the period of time is two hours. If a service order is not received within the predetermined time interval, the reservation is canceled and the telephone number will be returned to the available telephone number pool for use by other resellers and representatives.
A telephone number assignment cancellation request, represented by block 396, is submitted using the purchase order transaction set with a transaction type of T30. The response from the wholesaler to the reseller is issued using the purchase order acknowledgment transaction set. Upon receipt, the system determines whether the request came from the same reseller that initially reserved the telephone number as represented by block 398. If the reseller ID matches, the reservation is cancelled as represented by block 400 and the previously assigned telephone number is returned to the pool of available telephone numbers. Each request cancels only one telephone number reservation.
Multiple telephone number requests are preferably not allowed.
A telephone number assignment confirmation is transmitted using the purchase order transaction set with a transaction type of T40 as represented by block 402. The response is issued using the purchase order acknowledgment transaction set. This request is used to confirm that a telephone number is still assigned to a particular reseller. Confirmations for telephone number assignments can be made only by the reseller making the initial reservation. As such, the reseller - 28 - identification code is checked against the previously submitted assignment as represented by block 404.
Figure 9 is a block diagram illustrating one embodiment of a due date interface for automated electronic telecommunications ordering according to the present invention. Due date interface 410 provides online due date inquiry and reservation features. In one preferred embodiment of the present invention, due date interface 410 provides four transactions which are handled on a real-time basis. Preferably, all transactions are submitted using the purchase order transaction set (850-ASCX12 version 003030) with responses from the wholesaler using the purchase order acknowledgment transaction set (855-ASCX12 version 003030) .
A due date inquiry is submitted with a transaction type of R10 as represented by block 412. This transaction may be used to determine the availability of a specific due date as represented by block 414. Given a requested due date, the system will respond by indicating whether or not the due date is available and can be met based on the required service order activity. A due date inquiry may also be used to obtain a list of available due dates when a premises visit is required as represented by block 416. Given a description of the requested service order activity, the system provides the earliest possible due date in addition to a list of other available due dates. The due date inquiry does not reserve due dates for subsequent use in a service order. A separate due date assignment transaction 418 must be submitted to - 29 - guarantee that the due date will be held for a particular service order.
Due date assignment transaction 418 is submitted using the purchase order transaction set with a transaction type of R20. A response is issued using the purchase order acknowledgment transaction set . Due date transaction 418 allows the reseller to reserve a specific due date for use in subsequent order processing as represented by block 420. This transaction contains the same information as the inquire transaction 412 with the exception that the reseller submits a specific due date and a time-of-day preference, such as morning, afternoon, or all day. A due date assignment may be attempted without a previously submitted due date inquiry.
Upon receipt of a due date assignment transaction 418, the due date is reserved for a predetermined period of time, such as two hours, as represented by block 420. The reseller must submit a service order for the reserved due date within this time period or the reservation is automatically canceled. All requested products and services should be accurately represented on a due date assignment transaction. If the subsequently submitted service order contains information different from the due date assignment which impacts the due date, the service order may be rejected.
A due date assignment cancellation transaction
422 is submitted by the reseller as a purchase order using transaction set 850 with a transaction type of R30. A response is issued using the purchase order acknowledgmen . This transaction is used to cancel a - 30 - previously assigned due date. The reseller identification is checked against the previously submitted due date assignment transaction as represented by block 424 so that only the reseller who initially made the assignment may submit a cancellation request for that assignment. Each due date assignment cancellation transaction cancels exactly one due date reservation. Multiple due date cancellations in one transaction are preferably not permitted.
A due date assignment confirmation transaction
426 is submitted by the reseller using the purchase order transaction set with a transaction type of R40. A response is generated by the wholesaler using the purchase order acknowledgment transaction set . This transaction is used to confirm that a due date is still m assigned status. The identification of the reseller is compared against the previously submitted assignment transaction as represented by block 428. Confirmations of due date assignments are preferably only permitted for the reseller who made the initial reservation.
Figure 10 is a block diagram illustrating mapping and translation functions of one embodiment for automated electronic telecommunications ordering according to the present invention. The mapping and translation functions being performed by the reseller, indicated generally by reference numeral 450, cooperate with similar mapping and translation functions of the wholesaler, indicated generally by reference numeral 452, preferably using a TCP/IP connection, indicated by reference numeral 454. Preferably, the mapping and translation functions are performed by software executing on one or more computers, such as the customer - 3 1 - service agent computers and message servers described and illustrated with reference to Figure 1.
The data gathered by the reseller is entered into one or more databases or forms 456 which include various data fields 458. Forms 456 preferably represent various data entry screens on a computer operated by a customer service representative. A mapping function is performed as indicated generally by reference numeral 460 to collect the information related to a particular electronic "document" 462. A translator 464, also implemented in software, translates the data from electronic document 462 into an electronic message 466 using a standard transaction set. Message 466 includes several segments 468 each having a segment identifier 470, a data segment identifier 472, and a data segment value 474. In one preferred embodiment of the present invention, the segments of a transaction set must occur in a particular sequence for proper processing. A single electronic message 466 may contain multiple electronic documents 462 which are concatenated in a single data stream. Additional information is added to electronic message 466 for transmission via the TCP/IP link 454 to the wholesaler, such as routing information, error detection information, and the like, as well known in the art.
An analogous reciprocal process occurs when the message reaches the wholesaler 452. Translator 480 parses electronic message 466 to identify one or more transaction sets. Message syntax is examined and error messages are generated when appropriate. The received data is temporarily stored in electronic document 482 having data fields 484. The appropriate information is - 32 - then automatically transferred to the wholesaler's internal order system as represented by blocks 486 and 488. The order is processed and a response is generated, translated using the standard transaction set, and transmitted to the reseller. By reducing manual intervention, this system reduces operating expenses and increases accuracy. Furthermore, a realtime response is generated and communicated to reduce turn-around time.
While the best mode for carrying out the invention has been described in detail, those familiar with the art to which this invention relates will recognize various alternative designs and embodiments for practicing the invention as defined by the following claims.
-33-
APPENDIX Transaction Set Specifications
34
General Ordering Overview
This ordering section addresses use of TCIF-defined EDI standards for the purpose of providing a method of requesting telecommunication services. This guide is intended to be a supplement to the information provided in the TCIF EDI Guidelines, Telecommunications Carrier Services, Issue 5. The TCIF guidelines should be consulted for specific detail when necessary.
Please note that in the following transactions all qualifiers, data, etc., are shown in UPPER CASE letters, with the exception of the qualifiers, data, etc., in the Nl loops, which are shown in Mixed Case.
This section of the ESO Guide details the use of the following transaction sets:
• 836 Electronic Notification
Losing Reseller Notification
PIC/LPIC
• 850 Purchase Order
• 855 Purchase Order Acknowledgment
• 860 Purchase Order Change Request — Buyer Initiated
• 865 Purchase Order Completion Notification — Seller Initiated
• 870 Order Status (Jeopardy)
• 997 Functional Acknowledgment
35
EDI Envelope — Ordering
Introduction
Envelopes provide the interchange control structure for transmuting business transactions. The interchange control header (ISA) and interchange control trailer (IEA) envelope one or more functional group header/trailer pairs (GS/GE). They identify the sender and receiver, provide function group control header (GS) information, and allow for authorization and security information. The ISA is transmitted first, followed by the data in functional groups with the interchange trailer at the end. The sequence for the transaction sets follows:
ISA Interchange Control Header
Starts and identifies an interchange of one or more functional groups.
GS Functional Group Header starts a group of related transactions
ST Transaction Set Header starts a transaction set
Transaction Set (for example. 850. 860)
SE Transaction Set trailer ends a transaction set
GE Functional Group Trailer ends a group of related transactions
IEA Interchange Control Trailer ends the interchange of one or more functional groups
More than one ST/SE pair, each representing a transaction set, may be used within one functional group.
Included in the following pages are envelope layouts for Preordeπng and Ordering. Both are included to illustrate the different identifications required m the ISA08 element for documents sent to the wholesaler and the ISA06 element for documents sent from the wholesaler.
ICS Interchange Control Structures
Functional Group ID=
Introduction:
The purpose of this standard is to define the control structures for the electronic interchange of one or more encoded business transactions including the EDI (Electronic Data Interchange) encoded transactions of Accredited Standards Committee X12. This standard provides the interchange envelope of a header and trailer for the electronic interchange through a data transmission, and it provides a structure to acknowledge the receipt and processing of tins envelope. 36
Pθ!. Seg. Req. Loop Notes and
So. ID Dei. M-l.Lie Repeat Comments
Must L se 010 IS A Interchange Control Header M 1
Must L se 030 GS Functional Group Header M 1
Must L se 040 GE Funcuonal Group Trailer .M 1
Must L se 050 IEA Interchange Control Trailer
Figure imgf000038_0001
M 1
Segment: ISA Interchange Control Header
Position: 010
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use ISA01 101 Authonzation Information Qualifier M ID 2/2 Code to identify the type of information in the Authorization Information
00 No Authonzation Information Present (No Meaningful
Information in 102)
Must Use ISA02 102 Authonzation Information M AN 10/10 Information used for additional identification or authonzation of the sender or the data in the interchange. The type of information is set by the Authonzation Information Qualifier (101).
Blanks
Must Use ISA03 103 Secunty Information Qualifier M ID 2/2 Code to identify the type of information in the Secunty Information
00 No Secunty Information Present (No Meaningful Information in 104)
Must Use ISA04 104 Secunty Information M AN 10/10 This is used for identifying the secunty information about the sender or the data m the interchange. The type of information is set by the Secunty Information Qualifier (103).
Blanks
Must Use ISA05 105 Interchange ID Qualifier M ID 2/2 Qualifier to designate the system method of code structure used to designate the sender or receiver ID element bemg qualified
01 Duns (Dun & Bradstreet)
Must Use ISA06 106 Interchange Sender ID M AN 15/15 Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Must Use ISA07 105 Interchange ID Qualifier M ID 2/2
Qualifier to designate the system method of code structure used to designate the sender or receiver ID element bemg qualified 01 Duns (Dun & Bradstreet)
Must Use ISA08 107 Interchange Receiver ID M AN 15/15 Identification code published by the receiver of the data; When sending, it t used by the sender as their sending ID, thus other paπies sending to them will use this as a receiving ID to route data to them 37
023044759MOR Ordenng only
Must Use ISA09 108 Interchange Date M DT 6 6 Date of the interchange
Must Use ISA10 109 Interchange Time M TM 4/4 Time of the interchange
Must Use ISA11 110 Interchange Control Standards Identifier M ID 1/1 Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
Refer to 003030 Data Element Dictionary for acceptable code values.
Must Use ISA12 111 Interchange Control Version Number M ID 5/5 This version number covers the interchange control segments
00303 Draft Standard for Tnal Use Approved for Publication by ASC XI 2 Procedures Review Board Through October 1992
Must Use ISA13 112 Interchange Control Number M NO 9/9 A control number assigned by the interchange sender.
ICNs should only be reused once the full 100,000,000 possible combmations have been exhausted and should not be reused when resubmitting a revised order using the same purchase order number.
Must Use ISAM 113 Acknowledgment Requested M ID 1/1 Code sent by the sender to request an interchange acknowledgment (TA1)
0 No Acknowledgment Requested
Must Use ISA15 114 Test Indicator M ID 1/1 Code to indicate whether data enclosed by this interchange envelope is test or production
T/Test Data
P/Production Data
Refer to 003030 Data Element Dictionary for acceptable code values.
Must Use ISA16 115 Component Element Separator M AN 1/1 This is a field provides the de meter used to separate component data elements withm a composite data structure; this value must be different than the data element separator and the segment terminator
Subelement separator, hexidecimal Al Element separator, hexidecimal 4C Segment separator, hexidecimal 15
Segment: GS Functional Group Header
Position: 030
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of a functional group and to provide control information
Syntax Notes:
Semantic Notes:
Comments: A functional group of related transaction sets, withm the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use GS01 479 Functional Identifier Code M ID 2/2
Code ιdentιt>ιng a group of application related transaction sets 38
CA Purchase Order iange Acknowledgement (865) PC Purchase Order Change (860) PO Purchase Order (850) PR Purchase Order Acknowledgement (855) RQ Reseller Notification (836) RS Order Status Information (870) TX Text Message (864)
Must Use GS02 142 Application Sender's Code M AN 2/15
Code identifying party sending transmission; codes agreed to by trading partners
Must Use GS03 124 Application Receiver's Code M AN 2/15
Code identifying party receiving transmission. Codes agreed to by trading partners
023044759MOR
Ordenng only
Must Use GS04 373 Date M DT 6/6
Date (YYMMDD)
Must Use GS05 337 Time M TM 4/6
Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through 235959) uses HHMM format
Must Use GS06 28 Group Control Number M NO 1/9
Assigned number ongmated and maintained by the sender
Must Use GS07 455 Responsible Agency Code M ID 1/2
Code used in conjunction with Data Element 480 to identify the issuer of the standard
X Accredited Standards Committee X 12
Must Use GS08 480 Version / Release / Industry Identifier Code M AN 1/12
Code indicating the version, release, subrelease and industry identifier ot the EDI standard bemg used. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).
003030 Draft Standards Approved for Publication by ASC X 12
Procedures Review Board Through October 1 92
Segment: GE Functional Group Trailer
Position: 040
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of a functional group and to provide control information
Syntax Notes:
Semantic Notes:
Comments: 1 The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integπty. The control number is the same as that used in the corresponding header.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use GE01 97 Number of Transaction Sets Included M NO 1/6
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing thi-, d.u.i 39
element
Must Use GE02 28 Group Control Number M NO 1/9
Assigned number oπginated and maintained by the sender
Segment: IEA Interchange Control Trailer
Position: 050
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control segments
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use IEA01 116 Number of Included Functional Groups M NO 1/5
A count of the number of functional groups mcluded m an interchange
Must Use IEA02 112 Interchange Control Number M NO 9/9
A control number assigned by the interchange sender.
836 Contract Award- Losing Reseller Notification
Functional Group ID=RQ
Introduction:
This contains the format and establishes the data contents of the Procurement Notices Transaction Set (836) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set will be for Reseller Notification.
Pos. Seg. Req. Loop Notes and No ID Name Des Max. Use Repeat Comments
Must L se 010 ST Transaction Set Header M 1 Must Lse 020 BCO Beginning Segment For Contract Award M 1
LOOP ID - Nl >1
021 M Name O 1
LOOP ID - POl >1
Must L se 030 POl Baseline Item Data M 1 090 REF
Figure imgf000041_0001
Reference Numbers O >1
Must L se 190 SE Transacuon Set Trailer
Segment: ST Transaction Set Header
Position: 010
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes: 40
Semantic Notes: 1 The transaction set identifier (STOl) used by the translation routines of the interchange partners to select the appropπate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set 836 X12.54 Contract Award
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the oπgmator for a transaction set Mist match value in SE02
Segment: BCO Beginning Segment For Contract Award
Position: 020
Usage: Mandatory
Max Use: 1 Purpose: To indicate the beginning of the Contract Award Transaction Set and to transmit identifying numbers and dates.
Syntax Notes: Semantic Notes: 1 BCO04 is the contract number.
2 BCO06 is the contract beginning date.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use BCO01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set 47 Transfer
Must Use BCO02 586 Request for Quote Reference Number M AN 1/45
Number assigned by the purchaser to identify his request for quote
Account number
Must Use BCO03 652 Request Quotation Control Date M DT 6/6
Date to be used for reference purposes in an RFQ and a response to RFQ.
Date issued
BCO04 127 Reference Number O AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Purchase order number
Must Use BCO05 846 Contract Status Code M ID 2/2
Code designating the current status of the contract TR Contract Transferred
Must Use BCO06 373 Date M DT 6/6
Date (YYMMDD)
Order due date
Segment: 1 Name
Position: 021
Loop: Nl
Level:
Usage: Optional
Figure imgf000042_0001
Max Use: 1 41
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N 102 is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method o providing organizational identification.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N101 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
MA Party for whom item is ultimately intended
N102 93 Name X AN 1/35
Free-form name ZXX Placeholder for ACNA
Segment: P01 Baseline Item Data
Position: 030
Loop: POl
Level:
Usage: Mandatory
Max Use: 1
Purpose: To specify basic and most frequently used lme item data
Syntax Notes: 1 If PO103 is present, en PO102 is required.
Semantic Notes:
Comments: 1 PO101 is the line item identification.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PO101 350 Assigned Identification M AN 1/11
Alphanumenc characters assigned for differentiation withm a transaction set
Must be equal 1 or higher; do not use 0
Must Use PO102 330 Quantity Ordered M R 1/9
Quantity ordered
Presently, always 1
Must Use PO103 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the umts in which a value is bemg expressed, or manner in which a measurement has been taken EA Each
Segment: REF Reference Numbers
Position: 090
Loop: POl
Level:
Usage: Optional
Max Use: >1
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 is required.
Semantic Notes:
Figure imgf000043_0001
Comments: 42
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying the reference number QQ Umt number
Must Use REF02 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier Telephone number of circuit ID
Segment: SE Transaction Set Trailer
Position: 190
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (includmg the beginnmg (ST) and endmg (SE) segments).
Syntax Notes:
Semantic Notes:
Comments: 1 SE is the last segment of each transaction set.
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included m a transaction set including ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the onginator for a transaction set Must match value in ST02
836 Contract Award— PIC/LPIC
Functional Group ID=RQ
Introduction:
This section contains the format and establishes the data contents of the Procurement Notices Transaction Set (836) for use withm the context of an Electronic Data Interchange (EDI) environment. Only the segments used by AIIS for the reseller notification are listed.
PIC/LPIC changes is an optional offeπng
Pot. Seg. Req. Loop Notts and
No. ID Name Dei Mai.Use Repeat Commend
Must L se 010 ST Transacuon Set Header M 43
Must L se 020 BCO Beginning Segment For Contract Award
LOOP ID - Nl
021 \ 1 Name O 025 REF Reference Numbers O
LOOP ID - POl
Must L se O?0 PO l Baseline Item Data M
090 REF Reference Numbers O
LOOP ID - Nl
!?0 \ 1 Name Must L se 190 SE Transacuon Set Trailer M
Segment: ST Transaction Set Header
Position: 010
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (STO 1 ) used by the translation routmes of the interchange partners to select the appropπate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set 836 X12.54 contract award
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be umque withm the transaction set functional group assigned by the onginator for a transaction set Must match value m SE02
Segment: BCO Beginning Segment For Contract Award
Position: 020
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Contract Award Transaction Set and to transmit identifying numbers and dates.
Syntax Notes:
Semantic Notes: 1 BCO04 is the contract number.
Comments:
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use BCO01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set
13 Request
Must Use BCO02 586 Request for Quote Reference Number M AN 1/45 44
Number assigned by the purchaser to identify his request for quote
Account number
Must Use BCO03 652 Request Quotation Control Date M DT 6/6
Date to be used for reference purposes in an RFQ and a response to RFQ
Date issued
Must Use BCO04 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Purchase order number
Must Use BCO06 373 Date M DT 6/6
Date (YYMMDD)
Order due date
Segment: N 1 Name
Position: 021
Loop: Nl
Level:
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N 102 is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providmg organizational identification.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N101 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
MA Party for whom Item is Ultimately Intended
N102 93 Name X AN 1/35
Free-form name ZXX
Segment: REF Reference Numbers
Position: 025
Loop: Nl
Level:
Usage: Optional
Max Use: >1
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use REF01 128 Reference Number Qualifiei M ID 2/2
Code qualifying the Referenc mber.
Figure imgf000046_0001
Must Use REF02 127 Reference Number M AN 1/30 Reference number or identification number as defined for a particular 45
Transaction Set, or as specified b> the Reference Number Qualifier.
* If REF01=l l
End user account telephone number
* IfREF01=12
Billing account telephone number mutually exclusive use
Segment: P01 Baseline Item Data
Position: 030
Loop: POl
Level:
Usage: Mandatory
Max Use: 1
Purpose: To specify basic and most frequently used lme item data
Syntax Notes: 1 If PO103 is present, then PO102 is required.
2 If POl 06 is present, then PO107 is required.
Semantic Notes: Comments: 1 POl 01 is the line item identification.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PO101 350 Assigned Identification M AN 1/11
Alphanumenc characters assigned for differentiation withm a transaction set Must be equal 1 or higher; do not use 0
Must Use PO102 330 Quantity Ordered M R 1/9
Quantity ordered Presently, always 1
Must Use PO103 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the umts in which a value is being expressed, or manner in which a measurement has been taken EA Each
PO106 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type source of the descπptive number used m Product Service ID (234)
TY Telecommunications industry service code
POl 07 234 Product/Service ID X AN 1/30
Identifying number for a product or service PC01 PIC change
PC02 LPIC change
PC03 Change of both PIC and LPIC
Segment: REF Reference Numbers
Position: 090
Loop: POl
Level:
Usage: Optional
Max Use: >1
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 is required.
Semantic Notes:
Figure imgf000047_0001
Comments: 46
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number.
7J Code for toll billing reference number
Must Use REF02 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Telephone number or circuit ID
Segment: 1 Name
Position: 130
Loop: Nl
Level:
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N103 is required.
2 If either N103 or N104 ιs present, then the other is required.
Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N101 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
IK Intermediate earner
P9 Pnmary Interexchange Carner (PIC)
Identifies the earner who will handle the interexchange calls
N103 66 Identification Code Qualifier X ID 1/2 Code designatmg the system method of code structure used for Identification Code (67)
41 Telecommunications earner identification code
Identifies the interexchange earner for the charges bemg billed
N104 67 Identification Code X AN 2/17 Code identifying a party or other code
Value of CIC for interexchange earners
Segment: SE Transaction Set Trailer
Position: 190
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginmng (ST) and ending (SE) segments).
Syntax Notes: Semantic Notes: 47
Comments: 1 SE is the last segment of each transaction set.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included m a transaction set including ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique with the transaction set functional group assigned by the onginator for a transaction set Must match value in ST02
850 Purchase Order
Functional Group ID=PO
Introduction:
This contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established busmess and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
Heading:
Pos. Seg. Req. Loop Notes and
No. ID N me Des. Max.L'se Repeat Comments ust L se 010 ST Transacuon Set Header M 1
Must L se 020 BEG Beginning Segment for Purchase Order M 1 Must L se 050 REF Reference Numbers M 12
060 PER Admirustrauve Commumcauons Contact O 3
120 ITA Allowance. Charge or Service O 10 150 DTM Date Time Peπod O 10
Must Use 185 SI Service CharacteπsUc Idenuficauon M 2
190 PID Product Item Descnpuon 0 200 210 PWK Paperwork 0 25
LOOP ID - N l 200
Must L se 310 Nl Name M 1
320 N2 Λddiuona! Name Inlormation O 2
330 N3 Address lnformauon O 2
340 N4 Geographic Location O 1 345 NX2 Real Estate Property ID Component O 3
Figure imgf000049_0001
360 PER Admimstrauve Commumcauons Contact O 3
Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Mai.Uie Repeat Comments
LOOP ID - PO l 100000
Must Use 010 PO l Baseline Item Data M 1 nl Must L se 018 SI Service CharacteπsUc Idcntiht-alion M 5
Figure imgf000049_0002
LOOP ID - PID 1000 1 48
050 PID Product/Item Descπpuon O 1 1
100 REF Reference Numbers O 12 110 PER Admimstrauve Commumcauons Contact O J 210 DTM Date/Time Penod O 10
LOOP ID - SLN 1000
470 SL\ Subhne Item Detail 0 1 480 SI Service Characleπsuc Idenuficatton 0 5 490 PID Product item Descπpuon 0 1000 520 DTM Date Time/Peπod 0 10
LOOP ID - N 1 10
530 N l Name 0 1 540 \2 Addiuonal Name Information 0 2 550 N3 Address Intormation 0 2 560 \'4 Geographic Location 0 1 570 NX2 Real Estate Property ID Component 0 3 590 PER
Figure imgf000050_0001
Administrative Commumcauons Contact 0 3
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Mal.Uie Repeat Comments
Must L se 010 CTT Transacuon Totals M n2 Must Use 030 SE Transacuon Set Trailer M
Transaction Set Notes
1. POl 02 is required.
2. The number of line items (CTTOl) is the accumulation of the number of POl segments.
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (STOl) used by the translation routmes of die interchange partners to select the appropπate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set 850 XI 2.1 purchase order
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be umque withm the transaction set functional group assigned by die onginator for a transaction set Must match value in SE02
Segment: BEG Beginning Segment for Purchase Order
Position: 020
Loop:
Level: Heading 49
Usage: Mandatory Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use BEG01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set 00 Oπginal
Must Use BEG02 92 Purchase Order Type Code M ID 2/2
Code specifying the type of Purchase Order SS Supply or service order
US Urgent service request
Must Use BEG03 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser BEG04 328 Release Number O AN 1/4
Number identifying a release against a Purchase Order previously placed by die parties mvolved m the transaction Version number must remain below 9000
Must Use BEG05 323 Purchase Order Date M DT 6/6
Date assigned by the purchaser to Purchase Order BEG07 587 Acknowledgment Type O ID 2/2
Code specifying the type of acknowledgment
AE Acknowledge with exception detail only
Segment: REF Reference Numbers
Position: 050
Loop:
Level: Heading
Usage: Mandatory
Max Use: 12
Purpose: To specify identifying numbers.
Svntax Notes: 1 At least one of REF02 is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying die Reference Number.
11 Account number
Number identifies a telecommunications industry account
12 Billing account number
Account number under which billing is rendered
AN Associated purchase orders
BB Authonzation Number
Proves that permission was obtained to provide a service
CO Related orders
JB Project code
P3 Reservation number
Must Use REF02 127
Figure imgf000051_0001
Reference Number M AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. 50
♦ IfREFOl = 1 1
End user account telephone number (format=7082482314)
* IfREFOl = 12
Billing account telephone number (telecommunication earners for billing of unbundled product orders)
IfREFOl = AN
Associated Purchase Orders - orders that need to be worked together but not with the same due date requirement
IfREFOl = BB Authonzation number
IfREFOl = CO
Related PON orders - orders that have the same desired due date
IfREFOl = JB Project code
IfREFOl = P3 Reservation number
♦mutually exclusive use
Segment: PER Administrative Communications Contact
Position: 060
Loop:
Level: Headmg
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom admmistrative commumcations should be directed
Svntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use PER01 366 Contact Function Code M ID 2/2
Code identif ing the major duty or responsibility of the person or group named
DE Design contact
SU Supplier contact
Must Use PER02 93 Name M AN 1/35
Free-form name Contact name
Must Use PER03 365 Communication Number Qualifier M ID 2/2
Code identifying the type of communication number
FX Facsimile
TE Telephone
Must Use PER04 364 Communication Number M AN 1/25
Complete communications number includmg country or area code when applicable If PER03 = FX 51
Fax number (format = 2167666740)
If PER03 = TE
Telephone number (format = 2167666740) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
If PER03 = FX
Fax number (format = 2167666740)
IfPER03 = TE
Telephone number (format = 2167666740)
Segment: ITA Allowance, Charge or Service
Position: 120 Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify allowances, charges, or services
Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 or ITA14 is required. 2 If ITA 10 is present, then ITA 11 is required.
Semantic Notes: 1 ITA 12 is die quantity of free goods.
Comments: 1 IT A02 identifies the source of the code value m IT A03.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use ITA01 248 Allowance or Charge Indicator M ID 1/1
Code which indicates an allowance or charge for tie service specified N No Allowance or Charge
ITA02 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values
TI Telecommunications Industry
ITA03 560 Special Services Code X ID 2/10 Code identifying die special service
CT Count and Recount
Must Use ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2
Code indicating method of handling for an allowance or charge 06 Charge to be Paid by Customer
ITA10 339 Allowance or Charge Quantity O R 1/10
Quantity basis when allowance or charge quantity is different from the purchase order or mvoice quantity
ITA11 355 Unit or Basis for Measurement Code X ID 2/2
Code specifying the umts in which a value is bemg expressed, or manner in which a measurement has been taken MO Months
ITA12 380 Quantity O R 1/15
Numenc value of quantity ITA14 150 Special Charge or Allowance Code X ID 3/3
Code identifying type of special charge or allowance
Segment: DTM Date/Time/Period 52
Position: 150
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify peπinent dates and times
Syntax Notes: 1 At least one of DTM02 or DTM03 is required.
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000054_0001
Attributes
Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time 092 Contract Effective
150 Service period start (install/change) Date service requested to start
151 Service penod end (disconnect) Date service requested to end
Must Use DTM02 373 Date M DT 6/6
Date (YYMMDD) Requested due date
DTM03 337 Time O TM 4/6
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359) 0900/AM 1300/PM
Absence indicates all day
Requested due date time (local time to service address)
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 19 Century code
Segment: SI Service Characteristic Identification
Position: 185
Loop:
Level: Heading
Usage: Mandatory
Max Use: 2
Purpose: To specify service characteristic data
Syntax Notes:
Semantic Notes:
Comments: 1 SIOl defines the source for each of the service charactenstics qualifiers.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning me code values
TI Telecommunications industry
Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualifying the type of service charactenstics
AA Account activity code
DR Disconnect reason 53
RO Requested local office
SC Service category code
SF Service features; options
TC Transfer of calls
Z4 Mutually defined (prohibit PIC change)
Z6 Mutually defined (exchange)
Must Use SI03 234 Product/Service ID M AN 1/30
Identifying number for a product or service
If SI02 = A A A/Establish new account C/Change existing account D/Disconnect account T/Outside move V/ Assume as specified W/ Assume as is
If SI02 = DR Disconnect reason UB/Unbundled CO/Competitive NF/No further use SU/Supersede
If SI02 = RO
Name of requested local office
This is required on remote call forwardmg and foreign exchange (FX) requests
If SI02 = SC
Account Class of Service
Code values are available through your account manager
If SI02=SF
RCU/Retain current listing
If SI02=TC
Telephone number to which calls should be transferred
If SI02 = Z4 Prohibit PIC Change Y/Yes N No
IfSI02 = Z6 Exchange value
Service Characteπstic Qualifier and Product Service ID may be repeated ten times m segment.
Segment: PID Product/Item Description
Position: 190 Loop:
Level: Headmg
Usage: Optional
Max Use: 200
Purpose: To descnbe a product or process in coded or free-form format
Syntax Notes: 1 If PID04 is present, then PID03 is required. 54
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the organization that publishes die code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
3 PID08 descπbes the physical charactenstics of die product identified in PID04. A " Y" indicates that the specified attπbute applies to this item. A "N" indicates it does not apply. Any other value is indeterminate.
Comments: 1 If PID01 = "F", then PID05 is used. If PID01 = "S", then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being descnbed in the segment.
3 PID07 specifies the mdividual code list of the agency specified m PID03
Data Element Summary
Ref. Data Des. Element Name Attributes PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
S Structured (From Industry Code List)
X Semi-structured (Code and Text)
PID03 559 Agency Qualifier Code O ID 2/2
Code identifying the agency assigning the code values
AS Assigned by Seller
TI Telecommunications Industry
PID04 751 Product Description Code O AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
ACC Access instructions
CFA Connecting facility assignment
DIR Directory instructions
EXP Expedite reason
FAC Facilities available
LOA Letter of authonzation
LP Associated loop order
ORI Order instructions
UB Unbundled order
PID05 352 Description C AN 1/80
A free-form descnption to clanfy the related data elements and their content IfPID04 = ACC
Use PID05 for instructions which should be supplied to technician who will do die premises work
If PID04 = CFA
Connecting facility assignment
Use PID05 for supplymg CFA information
If PID04 = DIR
Use PID04 for directory instructions
IfPID04 = EXP
Use PID05 for expedite reason
If PID04 = LOA 55
Use on end user disconnect for unbundling orders
If PID04 = LP
Use with number portability orders
IfPID04=ORI
Use PID05 for instructions to service center
IfPID04=UB Unbundling order
PID07 822 Source Subqualifier O AN 1/15
A reference diat indicates die table or text maintamed by the Source Qualifier
AMT01 list for PID
PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response This data element is yes no response to the PID04 question in a structured PID segment
N No
Y Yes
Segment: PWK Paperwork
Position: 210
Loop:
Level: Heading
Usage: Optional
Max Use: 25
Purpose: To identify die type and transmission of paperwork or supportmg information
Comments:
Notes: Required on new orders, oώerwise prohibited.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use PWK01 755 Report Type Code M ID 2/2
Code indicating die title or contents of a document, report or supporting item DI Directory
Reports diat provide information about a subject, name, product, etc.
PWK02 756 Report Transmission Code O ID 2/2 Code defining timing, transmission method or format by which reports are to be sent
BM By mail
PWK03 757 Report Copies Needed O NO 1/2
The number of copies of a report that should be sent to the addressee Quantity of directoπes requested
Segment: N 1 Name
Position: 310
Loop: Nl
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by type of organization, name, and code.
Syntax Notes: 1 At least one of N 102 or N 103 is required.
2 If either N 103 or N 104 is present, then the other is required.
Semantic Notes: 56
Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain mis efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. Notes: If business account and mere is no yellow page listing requested, send 'ZZ' in NlOl and ■NONE' m N 102
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use NlOl 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an mdividual
33 Inquiry address
Used to provide a nearby address to actual installation sue AN Authonzation name
Name of mdividual authonzing service BT Party to be billed
Required on new order DA Delivery address
On a new order used to show umque delivery address for telephone book delivery IT Installation on site (service)
PS Previous address
Used on move order XI Final bill address
An address to which a specified item is to be mailed
N102 93 Name O AN 1/35
Free-form name Customer name
N103 66 Identification Code Qualifier O ID 1/2
Code designatmg the system/method of code structure used for Identification Code (67)
Code to indicate correct address but not on street address guide 92 Assigned by buyer or buyer's agent
BE Common Language Location Identification (CLLI)
The standard address location code for a specific equipment location as used in ie telephone industry ZZ Mutually Defined
Code to indicate correct address but not on street address guide
N104 67 Identification Code O AN 2/17
Code identifying a party or other code If N103 = 92 ACNA
If N103 = BE N104= CLLI code
IfN103 = ZZ
N104 = ADDR
Segment: 2 Additional Name Information
Position: 320
Loop: Nl
Figure imgf000058_0001
Level: Heading 57
Usage: Optional Max Use: 2 Purpose: To specify additional names or those longer than 35 characters in length
Data Element Summary
Ref. Data
Des. Element Name
Attributes t Use N201 93 Name M AN 1/35
Free-form name
N202 93 Name O AN 1/35
Free-form name
Segment: 3 Address Information
Position: 330
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Notes: Street address
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000059_0001
Attributes
Must Use N301 166 Address Information M AN 1/35
Address information Street address
N302 166 Address Information O AN 1/35
Address information Additional address information
Segment: N4 Geographic Location
Position: 340
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 At least one of N401 is required.
Semantic Notes:
Comments: 1 N402 is required only if city name (N401) is m the USA or Canada.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N401 19 City Name M AN 2/30
Free-form text for city name
Must Use N402 156 State or Province Code M ID 2/2
Code (Standard State) as defined by appropπate government agency
Must Use N403 116 Postal Code M ID 3/9
Code defining international postal zone code excludmg punctuation and blanks (zip code for United States) 58
Segment: NX2 Real Estate Property ID Component
Position: 345
Loop: Nl
Level: Headmg
Usage: Optional
Max Use: 3
Purpose: To define types and values for geographic location of real estate property
Syntax Notes:
Semantic Notes: 1 NX201 defines me type of address component.
2 NX202 defines the address component identified in NX201.
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000060_0001
Attributes
NX201 1106 Address Component Qualifier O ID 2/2
Code qualifying the type of address component TCIF values
12 Building name 13 Apartment number 14 Suite number 30 Pier
The pier at which a ship or boat is docked
31 Wmg
The particular w g of a building
32 Floor
A particular floor or level of a building
33 Dπveway
The dπveway or pπvate road connecting a house, garage, or another building with the street
34 Lot
A particular lot or piece of land 35 Room
A walled room or partitioned area of a building 36 Slip
The slip or location on a pier at which a ship or boat is docked
37 Unit
A unit or separate structure
NX202 166 Address Information AN 1/35 Address information Floor, room, building, etc.
Segment: PER Administrative Communications Contact
Position: 360
Loop: Nl
Level: Headmg
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom admmistrative commumcations should be directed
Svntax Notes: 1 If eidier PER03 or PER04 is present, then the oώer is required.
2 If eidier PER05 or PER06 is present, then the other is required.
Data Element Summary
Ref. Data 59
Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifymg the major duty or responsibility of the person or group named
OC Order contact
PER02 93 Name O AN 1/35
Free-form name Contact name
Must Use PER03 365 Communication Number Qualifier M ID 2/2
Code identifying the type of communication number
FX Facsimile
TE Telephone
Must Use PER04 364 Communication Number M AN 1/25
Complete commumcations number including country or area code when applicable If PER03 = FX Fax number (format = 7082482333)
If PER03 = TE
Telephone number (format = 7082482314) PER05 365 Communication Number Qualifier X ID 2/2
Code identifymg the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete commumcations number mcludmg country or area code when applicable
If PER03 = FX
Fax number (format = 2167666740)
If PER03 = TE
Telephone number (format = 2167666740)
Segment: P01 Baseline Item Data
Position: 010
Loop: POl
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To specify basic and most frequently used lme item data
Syntax Notes: 1 If PO103 is present, men PO102 is required.
2 IfPO106 is present, then PO107 is required.
Semantic Notes: Comments: 2 POl 01 is the lme item identification.
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use PO101 350 Assigned Identification M AN 1/3
Numenc characters assigned for differentiation withm a transaction set Line item number; must equal value of 1 or higher; do not use 0
Must Use PO102 330 Quantity Ordered M R 1/9
Quantity ordered Presently, always 1 60
Must Use PO103 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken EA Each
Must Use PO106 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type source of the descnptive number used m
Product Service ID (234)
TY Telecommunications industry service code
Must Use POl 07 234 Product Service ID O AN 1/30
Identifying number for a product or service
Item Identifier (e.g., Lme USOC, HTY, ML, CLT, etc.); see Valid Item
Identifier Table later in mis section
Segment: SI Service Characteristic Identification
Position: 018
Loop: POl
Level: Detail
Usage: Optional
Max Use: 5
Purpose: To specify service characteπstic data
Syntax Notes:
Semantic Notes:
Comments: 1 SIOl defines the source for each of die service charactenstics qualifiers.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying die agency assigning the code values TI Telecommunications industry
Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualifying the type of service charactenstics Need exit routine. Can be up to 10 occurrences of Service Qualifier/Service ID combination.
BN Billing telephone number
Cl Circuit location drop code
CK Code for circuit location code
CL Residence / busmess listing
CN Code for network provider circuit ID
DD Digits outpulsed
DN Code for directory name
FI Code for facility interface code
FS Foreign serving office
LF Code for line class
LN Code for listed telephone number
LO Serving central office
LS Code for local serving office (required on circuits)
NC Code for network channel code
PE Code for type of pulsing
PT Preassigned telephone number
PX Code for Centrex or DID station
RI Code for route index
RO Foreign serving central office
SA Service activity code
SF Service feature code
SG Service group 61
SI Terminal type
T5 Terminal number
TB Code for call blocking
TC Transfer of calls
TH Code for trunk group number
TL Connecting to CO
TN Code for telephone number
TS Type of signaling
WC Code for wire count
Z5 Dial access code
Must Use SI03 234 Product/Service ID M AN 1/30
Identifymg number for a product or service IfSI02 = BN Billing telephone number
IfSI02 = CI
Circuit location drop code
IfSI02 = CK
Circuit location code (numenc, beginnmg with 1)
If SI02 = CL B /busmess C/residence
IfSI02 = CN
Network provider circuit ID
IfSI02 = LO
CLLI code of die serving central office
IfSI02 = DD Digits outpulsed
If SI02 = DN
Name of directory foreign listmg is to be m
IfSI02 = FI For OS circmts: OL13A OL13B OL13C
For TL circuits: TL11M TL11E TL12M TL12E TL31M TL31E TL32M TL32E TC31M TC31E TC32M TC32E
If SI02 = FS
Foreign serving office NPA-NXX (required on circmts)
IfSI02 = LF Lme class code
IfSI02 = LN
Listed telephone number 62
If SI02 = LO Serving central office
If SI02 = LS
Local service office NPA-NXX (required on circuits)
If SI02 = NC Network channel code
IfSI02 = PE DP/Dial pulse MF/Multifrequency DTMF/Dual tone multifrequency
IfSI02 = PT
Preassigned telephone number
If SI02 = PX
Centrex station number
If SI02 = RI Route mdex
IfSI02 = RO Serving central office
If SI02 = SA
A/Add
C/Change
CF/Change from
CT/Change to
D/Delete
V/ Assume as specified
W/ Assume as is
If SI02 = SF
USOC of feature requested
If SI02 = SG Hunt group number
If SI02 = SI
Terminal type (A, B, C, D, E)
If SI02 = TB
A/No collect or third number calls B/No third number calls accepted C/No collect calls accepted
IfSI02 = TC
Telephone number to which calls should be transferred
IfSI02 = TH
DID trunk group number
If SI02 = TL 63
Connecting to CO
IfSI02 = TN Telephone number
IfSI02 = TS DST/Delay dial GST/Ground start IST/Immediate dial LPS/Loop start WST/Wink start
IfSI02 = WC 2/2 wire 4/4 wire
IfSI02 = Z5
Dial access code USOC
Segment: PID Product/Item Description
Position: 050
Loop: PID
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To descnbe a product or process in coded or free-form format
Svntax Notes: 1 If PID04 is present, men PID03 is required.
At least one of PID04 or PID05 is required.
If PID07 is present, then PID03 is required.
If PID08 is present, ώen PID03 is required.
Semantic Notes: Use PID03 to mdicate the orgamzation that publishes the code list bemg referred to.
PID04 should be used for industry-specific product descnption codes.
PID08 descnbes die physical charactenstics of the product identified in
PID04. A "Y" indicates that the specified attnbute applies to this item. A
"N" mdicates it does not apply. Any other value is indeterminate.
Comments: 1 If PID01 = "P, then PID05 is used. If PID01 = "S", then PID04 is used. If
PID01 = "X", then both PID04 and PID05 are used.
PID07 specifies die mdividual code list of die agency specified m PID03.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PIDOl 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
S Structured (from industry code list)
X Semi-structured (code and text)
Must Use PID03 559 Agency Qualifier Code M ID 2/2
Code identifying the agency aligning the code values
AS Assigned by seller
TI Telecommunications industry
Must Use PID04 751 Product Description Code M AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
ACC Access instructions
AK Extended distance 64
CFA Connect facility assignment
CPE Text manufacturer and model
To be used for both text manufacturer and model
DIR Directory instructions
EUFT End user kilofeet maximum
ISDN Point-to-point or multipoint
MCPE EKTS or CACH
MIL Extended mileage
ORJ Order instructions
OVRFLW Trunk group number assigned to Pπme
TRAK Use of service
Must Use PID05 352 Description M AN 1/80
A free-form descnption to clanfy the related data elements and their content IfPID04 = ACC Use PID05 for access remarks for multipoint circuits
If PID04 = AK Extended distance
IfPID04 = CFA
Use PID05 for connect facility assignment
If PID04 = CPE
Use PID05 for CPE Manufacturer and model
If PID04 = DIR
Use PID05 for directory instructions
If PID04 = EUFT
End user kilofeet maximum
IfPID04 = ISDN
Set PID08 to N to indicate pomt-to-pomt
Set PID08 to Y to indicate multipoint
IfPID04 = MCPE Use PID05 for: 1/EKTS 2/CACH
IfPID04 = MIL Extended mileage
IfPID04 = ORl
Use PID05 for order remarks
IfPID04 = OVRFLW
Use PID05 for trunk group overflow
IfPID04 = TRAK Use PID05 for FID
Must Use PID07 822 Source Subqualifier M AN 1/15
A reference that indicates the table or text mamtamed by the Source Qualifier AMT01 list for PID
SORSQ Service order resale question
PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response This data element is yes/no response to the PID04 question in a structured 65
PID segment
N No
Y Yes
Segment: REF Reference Numbers
Position: 100
Loop: POl
Level: Detail
Usage: Optional
Max Use: 12
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000067_0001
Attributes
REF01 128 Reference Number Qualifier O ID 2/2
Code qualifying the Reference Number.
GP Government pnoπty number
Code for telecommunications service pnonty
REF02 127 Reference Number O AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by die Reference Number Qualifier. Telecommunications service pnonty number (TSP123456-E1)
Segment: PER Administrative Communications Contact
Position: 110
Loop: POl
Level: Detail
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Svntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named
CA Customer contact granting appomtment
PER02 93 Name O AN 1/35
Free-form name Contact name
PER03 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number
FX Facsimile
TE Telephone
PER04 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable 66
IfPER03 = FX Fax number (format : 7082482333)
If PER03 = TE
Telephone number (format = 7082482314) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
IfPER03 = FX
Fax number (format = 2167666740)
If PER03 = TE
Telephone number (format = 2167666741
Segment: DTM Date/Time/Period
Position: 210
Loop: POl
Level: Detail
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DT 02 or DTM03 is required.
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000068_0001
Attributes t Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time End date for transfer of calls 376 Delivery end
The date that delivenes will end
Use DTM02 373 Date M DT 6/6
Date (YY MDD) Requested due date DTM03 337 Time O TM 4/6
Time expressed m 24-hour clock time (HHM ) (Time range: 0000 through 2359) 0900/ AM 1 00/PM
Absence indicates all day
Requested due date time (local time to service address)
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 19 Century code
Segment: SLN Subline Item Detail
Position: 470
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify product subline detail item data
Svntax Notes: 1 If SLN09 is present, then SLN10 is required 67
Semantic Notes: SLNOl is the identifying number for the sublme item.
SLN02 is the identifying number for the subline level. The sublme level is analogous to the level code used in a bill of mateπals.
Comments: SLNOl is related to (but not necessanly equivalent to) the baseline item number. Example: 1.1 or 1 A might be used as a subl e number to relate to baseline number 1.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use SLNOl 350 Assigned Identification M AN 1/11
Numeπc characters assigned for differentiation widun a transaction set
Same value as line item POl 01
SLN02 350 Assigned Identification O AN 1/11
Numenc characters assigned for differentiation within a transaction set
Alpha character identifying action number, i.e.
A/first action
B/second action
C/third action
Must Use SLN03 661 Configuration Code M ID 1/1
Code indicating the relationship of the sublme item to the baseline item.
A Added
I Included
Must Use SLN04 380 Quantity M R 1/15
Numeπc value of quantity Always 1
Must Use SLN05 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying die umts in which a value is being expressed, or manner m which a measurement has been taken EA Each
SLN09 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descnptive number used in
Product/Service ID (234)
TY Telecommunications industry service code
SLN10 234 Product/Service ID X AN 1/30
Identifying number for a product or service
Item identifier, e.g., NLT, NPU, SF8; see Valid Item Identifier Table later tn this section
Segment: SI Service Characteristic Identification
Position: 480
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 5
Purpose: To specify service characteπstic data
Syntax Notes:
Semantic Notes:
Comments: 1 SIOl defines the source for each of the service charactenstics qualifiers.
Data Element Summary
Ref. Data
Des. Element Name
Attributes 68
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values
TI Telecommunications industry Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualify'ing the type of service charactenstics
AT Code for customer access treatment
Cl Channel number
C Code for circuit location
CN Code for circuit number
CQ Centrex group number
DD Digits dialed
DN Directory name
FI Code for facility interface
LF Code for lme class
LN Listed number
LS Local serving office
NC Code for network channel
Nl Code for network channel interface
PT Preassigned telephone number
PX DID station number
Rl Code for route index
SA Service activity code
SF Service feature code
SM Speed call number
T5 Terminal number
TB Code for toll blocking
TC Transfer of calls
TH Trunk group number
TN Telephone number
TS Type of signaling
Must Use SI03 234 Product/Service ID M AN 1/30
Identifying number for a product or service
If SI02 = AT
Customer access treatment
If SI02 = Cl
Channel number
If SI02 = C . Circuit location code
IfSI02 = CN Circuit ID
IfSI02 = CQ Centrex group number
If SI02 = DD Digits dialed
IfSI02 = DN
Code for directory name
If SI02 = FI
For OS circuits:
OL13A
OL13B 69
0L13C
For TL circuits:
TL11M TL11E
TL12M TL12E
TL31M TL 1E
TL32M TL32E
TC31M TC31E
TC32M TC32E
If SI02 = LF Line class code
If SI02=LN Listed number
If SI02 = LS Local serving office
If SI02 = NC Network channel code
IfSI02 = NI
Network channel interface code
If SI02 = PT
Preassigned telephone number
If SI02 = PX
DID station number
If SI02 = RI Route index
If SI02 = SA A/ Add C/Change CF/Change from CT/Change to D/Delete
If SI02 = SF
USOC of Feature requested
If SI02 = SM Speed call number
If SI02 = T5
Terminal number of hunt group
If SI02 = TB
A/No collect or third number calls B/No third number calls accepted C/No collect calls accepted
If SI02 = TC
Telephone number calls are to be transferred to or NONE 70
If SI02 = TH Trunk group number
IfSI02 = TN Telephone number
IfSI02 = TS DST/Delay dial EM1/E&M I EM2/E&M II EM3/E&M III GST/Ground start IST/Immediate dial LPS/Loop start WST/Wink start
In addition to always transmitting an SA Service Activity Code, send additional Service Characteπstic Qualifiers and Product/Service IDs as appropπate to customer's order. The combination of Service Characteπstic Qualifier and Product/Service ID may be repeated 10 times.
Rules: When transmuting more than one extension number and there is a senes of numbers, use a comma with no spaces to separate the entnes. If there is a range of number, separate the first and last number with a hyphen.
Example: SKTKSA<C<PX<2230,2234,2235-2239 n/1
When using EDI gateway, features are ordered using Universal Service Order Codes, or USOCs. These USOCs are listed m the subline detail in the SI segment following a Service Characteπstic Qualifier of SF. The USOCs, which may be found the Local Exchange Resale Product Catalog, are listed separated by commas. For example, to order 3-Way Calling and Caller ID to be added to an Illinois business line, the SI segment would be:
Example: SI<TI<SA<A<SF<ESC,NSD n/1
In some cases, information in addition to the feature USOC is required. For instance, if Busy Line Transfer is added, a forward-to number is required. This additional information should follow the feature USOC separated by a slash (/) character. To order Busy Lme Transfer and Alternate Answer added to a line with different forward-to numbers, the SI segment would be as follows:
Example: SKTKSA<A<SF<EVB/3125551212,EVD/3125558888/3 n 1
If the element length is not large enough to accommodate the information required, use a qualifier of 99 followed by the remainder of the information.
Example: SI<TKSA<A<SF<EVB/3125551212,EVB/3125558888/<99<3 n/1
The USOC section shows those USOCs that require additional information and what information is required when adding a feature or changing the value of a data item associated with the feature, all additional data items must be present in the order shown. When deleting a feature, only the USOC need be listed. 71
Segment: PID Product/Item Description
Position: 490
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 1000
Purpose: To descnbe a product or process in coded or free-form format
Svntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the orgamzation that publishes the code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
3 PID08 descnbes the physical charactenstics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this item. A "N" indicates it does not apply. Any other value is indeterminate.
Comments: 1 If PID01 = "F", then PID05 is used. If PID01 = "S", then PID04 is used. If PID01 = "X", then bom PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being descπbed m the segment.
3 PID07 specifies the individual code list of the agency specified m PID03.
Data Element Summary
Ref. Data Des. Element Name Attributes PID01 349 Item Description Type O ID 1/1
Code indicating the format of a descnption
S Structured (from industry code list)
X Semi-structured (code and text)
PID03 559 Agency Qualifier Code O ID 2/2
Code identifying the agency assigning the code values
AS Assigned by seller
TI Telecommunications industry
PID04 751 Product Description Code O AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
ACC Access instructions
AJ Assume dial 9
CALLID Caller ID
CFA Connecting facility assignment
COY GLARE - central office yields
DIDR DID numbers new or reuse
DIR Directory instructions
DP Digits prefixed
DR Digits received
ORI Order instructions
SGNL D channel signaling
STAID PBX station ID feature
TRHJ DID trunk hunt sequence
PID05 352 Description O AN 1/80
A free-form descnption to clanfy the related data elements and their content IfPID04 = ACC Use PID05 for access instructions
IfPID04 = AJ 72
Dial 9
IfPID04 = CALLID
Use PID08 to indicate Y or N caller ID
If PID04 = CFA
Use PID05 for connecting facility assignment
If PID04 = COY
GLARE - Use PID08 to indicate Y or N if Central Office yields
If PID04 = DIDR Use PID08 to indicate: N/new Y/reuse
If PID04 = DIR Directory instructions
IfPID04 = DP
Use PID05 for digits prefixed
IfPID04 = DR
Use PID05 for digits received
IfPID04 = ORI
Use PID05 for instructions to service center
IfPID04 = SGNL
D channel signaling
IfPID04 = STAID
Use PID08 to mdicate Y or N PBX station ID feature
If PID04 = TRHJ
Use PID05 for:
2WF/ascendιng
2WB/descendιng,
MIDL/most idle (DMS only)
LIDL/least idle (DMS only)
PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier
SO-RSQ/Resale questions
AMT01 list for PID
PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response
This data element is yes/no response to the PID04 question in a structured
PID segment
N No
Y Yes
Segment: DTM Date/Time/Period
Position: 520
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 or DTM03 is required. 73
Semantic Notes: Comments:
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000075_0001
Attributes
DTM01 374 Date/Time Qualifier O ID 3/3
Code specifying type of date or time, or both date and time 376 Delivery end
The date that dehveπes will end End date for transfer of calls
DTM02 373 Date O DT 6/6
Date (YYMMDD) Requested due date
DTM03 337 Time O TM 4/6
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359) 0900/ AM 1300/PM
Absence indicates all day
Requested due date time (local time to service address)
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 19 Century code
Segment: N1 Name
Position: 530
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N 102 or N 103 is required.
2 If either N 103 or N 104 is present, then the other is required.
Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing orgamzational identification. To obta this efficiency the "ID Code" (N104) must provide a key to the table mamtamed by the transaction processing party.
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use NlOl 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
B4 Parent company (caption heading)
The orgamzational entity which, by virtue of organization, ownership, and/or management, exercises control over a subordinate but separate business entity B5 Affiliated company (subcaption listing)
An organizational entity that shares a business affiliation with another business entity C3 Circuit location identifier identifies the address information as that which is 74
assigned to a circuit location address DH Doing business as (listing)
DI Different premise address (DP A)
Provides the different premise address when the associated equipment, or services, or both, are located at an address different from the main address IK Intermediate earner (LPIC)
IT Installation on sue (service)
P9 Pπmary Interexchange Camer (PIC)
Identifies the earner who will handle the interexchange calls SK Secondary Location Address (SLA)
Identifies a physical address location in which a telecommunications circuit terminates this address is in addition to a mam service address TR Interexchange earner address
YE Independent telco / third party
ZZ Mutually defined (Yellow Pages)
N102 93 Name O AN 1/35
Free-form name
Last name, first name, M.I. (White Page listing) N103 66 Identification Code Qualifier O ID 1/2
Code designating the system/method of code structure used for Identification Code (67)
BE Common Language Location Identification (CLLI)
The standard address location code for a specific equipment location as used m the telephone industry ZZ Mutually defined
Code to indicate correct address but not on street address guide N104 67 Identification Code O AN 2/17
Code identifying a party or odier code If N103 = BE N104 = CLLI Code
IfN103 = ZZ N104 = ADDR
Segment: N2 Additional Name Information
Position: 540
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 2
Purpose: To specify additional names or those longer than 35 characters in length
Syntax Notes:
Semantic Notes:
Comments:
Notes: Title or Titles in order of display. If listing has a designation and no title, populate N201 with TMONE'
Data Element Summary Ref. Data
Des. Element Name
Attributes Must Use N201 93 Name M AN 1/35
Free-form name Title or titles in order of display 75
N202 93 Name O AN 1/3:
Free-form name Designation
Segment: N3 Address Information
Position: 550
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N301 166 Address Information M AN 1/35
Address information Street address
N302 166 Address Information O AN 1/35
Address information Additional address information
Segment: N4 Geographic Location
Position: 560
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 At least one of N401 is required.
Semantic Notes:
Comments: 1 N402 is required only if city name (N401) is in the USA or Canada.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N401 19 City Name M AN 2/30
Free-form text for city name
Must Use N402 156 State or Province Code M ID 2/2
Code (Standard State) as defined by appropπate government agency
Figure imgf000077_0001
Must Use N403 116 Postal Code M ID 3/9
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Segment: NX2 Real Estate Property ID Component
Position: 570
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 3
Purpose: To define types and values for geographic location of real estate property
Semantic Notes: 1 NX201 defines the type of address component.
2 NX202 defines the address component identified NX201.
Data Element Summary
Ref. Data 76
Des. Element Name Attributes Must Use NX201 1 1110066 Address C omponent Qualifier M ID 2/2
Code qualifying the type of address component
TCIF values
12 Building name
13 Apartment number
14 Suite number
30 Pier
The pier at which a ship or boat is docked
31 Wing
The particular wmg of a building
32 Floor
A particular floor or level of a building
33 Dπveway
The dπveway or pπvate road connecting a house. garage, or another building with the street
34 Lot
A particular lot or piece of land
35 Room
A walled room or partitioned area of a building
36 Slip
The slip or location on a pier at which a ship or boat is docked
37 Unit
A unit or separate structure
Must Use NX202 166 Address Information M AN 1/35
Address in formation
Floor, room, building, etc.
Segment: PER Administrative Communications Contact
Position: 590
Loop: Nl
Level: Detail
Usage: Optional
Max Use:
Purpose: To identify a person or office to whom administrative commumcations should be directed
Svntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
Figure imgf000078_0001
2 If either PER05 or PER06 is present, then die other is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named
CA Customer contact granting appointment
PER02 93 Name O AN 1/35
Free-form name Contact name
PER03 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER04 364 Communication Number X AN 1/25
Complete communications number including country or area code when 77
applicable
If PER03 = FX
Fax number (format = 2167666740)
IfPER03 = TE
Telephone number (format = 2167666740) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
IfPER03 = FX
Fax number (format = 2167666740)
IfPER03 = TE
Telephone number (format = 2167666740)
Segment: CTT Transaction Totals
Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes:
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use CTTOl 354 Number of Line Items M NO 1/6
Total number of line items m the transaction set
Segment: SE Transaction Set Trailer
Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of me transmitted segments (includmg the beginnmg (ST) and endmg (SE) segments).
Comments: 1 SE is the last segment of each transaction set.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the onginator for a transaction set Must match value in ST02 78
855 Purchase Order Acknowledgment
Functional Group ID=PR
Introduction:
This contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in u eir partnership.
This transaction set is used to acknowledge and confirm an order received from a customer via the 850 or 860 transaction sets. Only selected segments are listed.
Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des Max.lse Bϊfiϋ! Comments
Musi L se 010 ST Transacuon Set Header M 1
Must L se 020 B AK Beginning Segment tor Purchase Order M 1 Acknowledgment
050 REF Reterence Numbers O 12
060 PER Admimstrauve Commumcauons Contact O ?
150 DTM Date/Time/Peπod 0 10
190 PID Product Item Descπpuon 0 200
LOOP ID - N9 1000
Figure imgf000080_0001
280 \9 Reference Number 0 1
Detail:
Pos. Sag. Raq. Loop Notes and
No ID Name Des Max.L se Repeat Comments
LOOP ID - POl looouo
010 PO l Baseline Item Data O 1 nl 018 S! Service Characteπstic Identification O 5 100 REF Reference Numbers O 12 200 DTM Date/Time/Peπod 0 10
LOOP ID - N9 1000
350 \9 Reterence Number O 1
LOOP ID - SLN 1000
490 SL\ Subline Item Detail O 1 500 SI Service Characteπstic Identilicauon n
Summary:
Pos Seg. Req Loop Notes and No. ID Name Des Max.l se Repeat Comments
Must L se 010 CTT Transacuon Totals M 1 n2
Figure imgf000080_0002
Must L se 030 SE Transacuon Set Trailer M 1
Transaction Set Notes
1. POl 02 is required 79
2. The number of line items (CTTOl) is the accumulation of the number of POl segments.
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (STOl) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
855 X12.9 purchase order acknowledgment
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be umque withm the transaction set functional group assigned by the oπgmator for a transaction set Must match value m SE02
Segment: B AK Beginning Segment for Purchase Order Acknowledgment
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction
Set and transmit identifying numbers and dates
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use BAK01 353 Transaction Set Purpose Code ID 2/2
Code identifying purpose of transaction set
00 Oπginal
05 Replace
Must Use BAK02 587 Acknowledgment Type M ID 2/2
Code specif} mg the type of acknowledgment
AE Acknowledge with exception detail only
RD Reject with detail
Must Use BAK03 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
Must Use BAK04 323 Purchase Order Date M DT 6/6
Date assigned bv the purchaser to purchase order
BAK05 328 Release Number O AN 1/30
Number identifying a release against a purchase order previously placed by the parties involved in the transaction
Used in response to 850 version (if value is 9000 or greater it is an unsolicited seller initiated 855). Version number must remain below 9000.
BAK06 326 Request Reference Number O AN 1/45
Reference number or RFQ number to use to identify a particular transaction 80
set and query (additional reference number or descnption which can be used with comract number)
Returned as a result of receipt of 860 element BCH05
BAK09 588 Acknowledgment Date O DT 6/6
Date assigned by the sender to the acknowledgment.
Segment: Kfcr Reference Numbers
Position: 050
Loop:
Level: Headmg
Usage: Optional
Max Use: 12
Purpose: To specify identifymg numbers.
Syntax Notes: 1 At least one of REF02 is required.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Figure imgf000082_0001
Must Use REF01 128 Reference Number Qualifie M ID 2/2
Code qualifying the reference number. 11 Account number
Number identifies a telecommunications ιndustr\ account
12 Billing account
Account number under which billing is rendered
BB Authonzation number
Proves that permission was obtained to provide a service
CO Customer order number
JB Job (project) number
OW Service order number
Number assigned when a customer orders service and equipment and which appears on bill
P3 Reservation number
Must Use REF02 127 Reference Number M AN 1/30
Reference number or identification number as defined for a panicular Transaction Set, or as specified by the Reference Number Qualifier IfREF01=U
End user account telephone number (format= 7082482314) Mutually exclusive use
IfREF01=12
Billmg account telephone number (telecommumcation earners for billing ol unbundled product orders)
Mutually exclusive use
If REFOl = BB Authonzation number
IfREFOl = CO Customer order number
IfREFOl = JB
Job (project) number
IfREFOl = OW service order number 81
IfREFOl = P3 Reservation number
Segment: PER Administrative Communications Contact
Position: 060
Loop:
Level: Headmg
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Svntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, men the other is required.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named
SR sales representative or department
Must Use PER02 93 Name M AN 1/35
Free-form name Contact name
Must Use PER03 365 Communication Number Qualifier M ID 2/2
Code identifying the type of communication number
FX Facsimile
TE Telephone
Must Use PER04 364 Communication Number M AN 1/25
Complete communications number including country or area code when applicable If PER03 = FX Fax number (format = 7082482314)
If PER0^ = TE
Telephone number (format = 7082482314)
PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
If PER03 = FX
Fax number ( tormat = 7082482314)
If PER03 = TE Telephone number (format : 7082482314)
Segment: DTM Date/Time/Period
Position: 150
Loop:
Level: Headmg
Usage: Optional
Max Use: 10
Purpose: To specify pertinent .ii and times
Svntax Notes: 1 At least one of DT\lιι2 or DTM03 is required. 82
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
150 Service peπod start (install/change) Date service was requested to start
151 Service peπod end (disconnect) Date service was requested to end
Must Use DTM02 373 Date M DT 6/6
Date (YYMMDD)
Assigned due date
DTM03 337 Time O TM 4/6
Time expressed in 24-hour clock time (HHMM)
(Time range: 0000 through 2359)
0900/AM
1300/PM
Absence indicates all day
DTM05 624 Century O NO 2/2
The first two characters in the designation of die year 19 Century code
Segment: PID Product/Item Description
Position: 190
Loop:
Level: Heading
Usage: Optional
Max Use: 200
Purpose: To descnbe a product or process m coded or free-form format
Syntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the organization ώat publishes the code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
3 PID08 descnbes the physical charactenstics of the product identified in PID04. A "Y" indicates mat the specified attribute applies to dus item. A "N" indicates it does not apply. Any other value is indeterminate.
Comments: 1 If PID01 = "F", then PID05 is used. If PID01 = "S", then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being descnbed in the segment.
3 PID07 specifies the individual code list of the agency specified in PID03
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
S Structured (from industry code IList)
X Semi -structured (code and text)
Must Use PID03 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values AS Assigned by seller 83
TI Telecommunications industry
Must Use PID04 751 Product Description Code M AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
DDR Due date requested
PV Premise visit
PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier AMT06 See List for PID
PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response IfPID = DDR Y/Due Date is the requested due date
IfPID = PV
Y/Premise visit is required
Segment: N9 Reference Number
Position: 280
Loop: N9
Level: Headmg
Usage: Optional
Max Use: 1
Purpose: To transmit identifying numbers and descπptive information as specified by the reference number qualifier
Syntax Notes: 1 At least one of N902 or N903 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N901 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number. R9 Rejection number
Must Use N902 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by die Reference Number Qualifier.
N903 369 Free-form Description O AN 1/45
Free-form descnptive text
See Reject Messages in section 6
Segment: POl Baseline Item Data
Position: 010
Loop: POl
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify basic and most frequently used lme item data
Syntax Notes : 1 If PO 103 is present, men PO 102 is required. Semantic Notes:
Comments: 1 See the Data Dictionary for a complete list of ID's. 2 PO101 is the line item identification.
Data Element Summary
Ref. Data 84
Des. Element Name Attributes
Must Use PO101 350 Assigned Identification M AN 1/3
Alphanumenc characters assigned for differentiation withm a transaction set
Line item number of supplier issued purchase order
Must Use PO102 330 Quantity Ordered M R 1/9
Quantity ordered
Quantity associated with line item
Figure imgf000086_0001
Must Use POl 03 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner m which a measurement has been taken EA Each
Segment: SI Service Characteristic Identification
Position: 018
Loop: POl
Level: Detail
Usage: Optional
Max Use: 5
Purpose: To specify service charactenstic data
Syntax Notes:
Semantic Notes:
Comments: 1 SIOl defines the source for each of the service charactenstics qualifiers.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values
TI Telecommunications industry
Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualifying the type of service charactenstics
CN Circuit number identification code CQ Centrex group number PX Code for Centrex station RJ Code for route index SG Hunt group number SM Speed call group number T5 Terminal number TH Code for trunk group number TN Telephone number Z2 Customer's temporary placeholder assigned Z5 Dial access code
Must Use SI03 234 Product/Service ID M AN 1/30
Identifying number for a product or service
Telephone/circuit number/group number, etc.
Service Charactenstic Qualifier and Product/Service ID may be repeated ten times in segment.
Segment: REF Reference Numbers
Position: 100
Loop: POl
Level: Detail
Usage: Optional
Max Use: 12
Purpose: To specify identifying numbers. 85
Syntax Notes: 1 At least one of REF02 is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number. OW Service order number
Number assigned when a customer orders service and equipment and which appears on bill
Must Use REF02 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier, service order number
Segment: DTM Date/Time/Period
Position: 200
Loop: POl
Level: Detail
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 or DTM03 is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
150 Service Penod Start (install/change) Date service was requested to start
151 Service Peπod End (disconnect) Date service was requested to end
Must Use DTM02 373 Date M DT 6/6
Date (YYMMDD) DTM03 337 Time O TM 4/6
Time expressed in 24-hour clock time (HHMM)
(Time range: 0000 through 2359)
0900/AM
1300/PM
Absence indicates all day
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 19 Century code
Segment: N9 Reference Number
Position: 350
Loop: N9
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To transmit identifying numbers and descπptive information as specified by the reference number qualifier
Syntax Notes: 1 At least one of N902 or N903 is required.
Semantic Notes:
Comments: 86
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N901 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number. R9 Rejection number
Must Use N902 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
N903 369 Free-form Description O AN 1/45
Free-form descnptive text
See Rejection Messages section
Segment: SLN Subline Item Detail
Position: 490
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify product sublme detail item data
Syntax Notes: 1 If SLN09 is present, then SLN 10 is required.
Semantic Notes: 1 SLNOl is the identifying number for the sublme item.
2 SLN02 is the identifying number for the sublme level. The subline level is analogous to the level code used m a bill of matenals.
Comments: 1 See the Data Dictionary for a conjplete list of ID's.
2 SLNO 1 is related to (but not necessaπly equivalent to) the baseline item number. Example: 1.1 or 1 A might be used as a sublme number to relate to baseline number 1.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use SLNOl 350 Assigned Identification M AN 1/11
Alphanumenc characters assigned for differentiation within a transaction set
Same value as line item PO101
Must Use SLN02 350 Assigned Identification M AN 1/11
Alphanumenc characters assigned for differentiation withm a transaction set
Alpha character identifying action number, i.e.
A/First action
B/Second action
C/Third action
Must Lse SLN03 661 Configuration Code M ID 1/1
Code indicating the relationship of the subline item to die baseline item.
A Added
I Included
Must Use SLN04 380 Quantity M R 1/15
Numeπc value of quantity Quantity of stations (extensions)
Must Use SLN05 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
EA Each
Must Use SLN09 235 Product/Service ID Qualifier M ID 2/2
Code identifying the type/source of the descπptive number used in Product/Service ID (234) 87
TY Telecommunications industrv service code
Must Use SLN10 234 Product/Service ID M AN 1/30
Identifying number for a product or service Telephone/circuit number/group number, etc. Item identifier (NLT,NPU)
Segment: SI Service Characteristic Identification
Position: 500
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 5
Purpose: To specify service charactenstic data
Syntax Notes:
Semantic Notes:
Comments: 1 SIOl defines the source for each of the service charactenstics qualifiers.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values
TI Telecommunications industry
Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualifying the type of service charactenstics
CN Circuit number
CQ Centrex group number
PX DID station number
SG Hunt group number
SM Speed call group number
Must Use SI03 234 Product/Service ID M AN 1/30
Identifying number for a product or service Telephone/circuit number/group number, etc. If SI02=CN Circuit number
If SI02=CQ
Centrex group number
IfSI02=PX DID station
If SI02=SG
Hunt group number
If SI02=SM
Speed call group number
Segment: CTT Transaction Totals
Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total lor a specific element in the transaction set
Syntax Notes:
Semantic Notes: 88
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and coπectness.
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use CTTOl 354 Number of Line Items M NO 1/6
Total number of line items in the transaction set
Segment: SE Transaction Set Trailer
Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of me transaction set and provide the count of the transmitted segments (including the beginmng (ST) and ending (SE) segments)
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Figure imgf000090_0001
Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set includmg ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique withm the transaction set functional group assigned by the onginator for a transaction set Must match value in ST02
860 Purchase Order Change Request — Buyer Initiated
Functional Group ID=PC
Introduction:
This contains the format and establishes the data contents of the Purchase Order Change Request - Buyer Initiated Transaction Set (860) for use withm the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide ihe information required for die customary and established business and industry practice relative to a purchase order change. This transaction can be used: ( 1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.
Notes:
Preferably, the 860 will be used to submit changes. Segments in the header should be sent as they should appear after a change. Changes to the item detail will be sent by replacing the oπginal POl segments with the POC segment identified by the same number used on ihe oπginal request. For example, if you want to add Call W aiiinn to the line contained in PO103, send the 860 with a POC03 showing the lme as it appeared in PO103 with the addition of Call Waiting. The 860 mirrors the 850 in much of the segment and code usage. This section onl} documents those segments and codes where the i wo transaction sets differ. If adding a new POC item, use v alue m CA m BCH02; see 850 documentation for valid values 89
Heading: Pos. Sag. Req. Loop Notes and
No. ID Name Des. Max .Ise Repeat Comments
Must L se 010 ST Transaction Set Header M 1
Must L sc 020 BCH Beginning Segment for Purchase Order Change M 1
050 REF Reference Numbers O 12
060 PER Administrative Commumcauons Contact O 3
150 DTM Daie Time Peπod 0 10
1 S5 SI Service Characteristic Identification 0 2
190 PID Product Item Descπpuon o 200
210 PUTC Paperwork o 25
LOOP ID - 1 200
300 N l Name o 1
310 N2 Addiuonal Name Informauon o 2
320 \? Address Information 0 2
330 N4 Geographic Locauon 0 1
335 NX2 Real Estate Property ID Component 0 3
Figure imgf000091_0001
350 PER Admimstrauve Commumcauons Contact o J
Detail:
Pos. Seg. Req. Notes and
No. ID Name Des. Max.Lse Comments
LOOP ID - POC 10000
010 POC Line Item Change 0
018 SI Service Characteπstic Identificauon o
LOOP ID - PID lO .l
050 PID Product/Item Descπpuon
100 REF Reference Numbers O 12
1 10 PER Admimstrauve Commumcauons Contact O 3
200 DTM Date/Time/Peπod O 10
LOOP ID - SLN 1000
460 SLN Subline Item Detail O 1
470 SI Service Charactenstic Idenuficauon O 5
480 PID Product/Item Description O 1000
510 DTM Date/Time/Peπod O 10
LOOP ID - Nl 10
520 l Name O 1
530 N2 Addiuonal Name Informauon O 2
540 N3 Address Informauon O 2
550 \4 Geographic Locauon O 1
560 NX2 Real Estate Property ID Component O }
580 PER
Figure imgf000091_0003
Admimstrauve Commumcauons Contact O J
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Lse Repeat omm nr
Must L se 010 CTT Transaction Totals M nl
Figure imgf000091_0002
Must se 030 SE Transacuon Set Trailer M
Transaction Set Notes
1. Number of line items (CTTOl) is the accumulation of the number of POC segments. Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Svntax Notes: 90
Semantic Notes: 1 The transaction set identifier (STOl) used by the translation routines ol the interchange partners to select the appropπate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
860 XI 2.15 Purchase Order Change Request - Buyer
Initiated
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the onginator for a transaction set Must match value in SE02
Segment: BCH Beginning Segment for Purchase Order Change
Position: 020
Loop:
Level: Headmg
Usage: Mandatory
Max Use: 1
Purpose: To mdicate die begmning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use BCH01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set 01 Cancellation
04 Change
Must Use BCH02 92 Purchase Order Type Code M ID 2/2
Code specifying die type of Purchase Order SS Supply or Service Order
Must Use BCH03 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
Customer issued oπginal order number
BCH05 327 Change Order Sequence Number O AN 1/4
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
860 version number must remain below 9000
Must Use BCH06 323 Purchase Order Date M DT 6/6
Date assigned by the purchaser to Purchase Order
Customer issued oπginal order date BCH11 279 Purchase Order Change Request Date O DT 6/6
Date of the purchase order change request.
Date of change order
Segment: REF Reference Numbers
Position: 050
Loop:
Level: Headmg
Usage: Optional 91
Max Use: 12
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Figure imgf000093_0001
Must Use REF01 128 Reference Number Qualifie M ID 2/2 Code qualifying the Reference Number. Refer to 850 transaction set for valid values.
REF02 127 Reference Number X AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier
Segment: PER Administrative Communications Contact
Position: 060
Loop:
Level: Heading
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom admimstrative communications should be directed
Svntax Notes: 1 If eidier PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of die person or group named
Refer to 850 transaction set for valid values.
PER02 93 Name O AN 1/35
Free-form name PER03 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER04 364 Communication Number X AN 1/25
Complete communications number includmg country or area code when applicable
If PER03=FX
Fax number (format=2167666740)
If PER03=TE
Telephone number (format=2166766740) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number includmg country or area code when applicable
IfPER03=FX 92
Fax number (format=2167666740)
IfPER03=TE
Telephone number (format=2166766740)
Segment: DTM Date/Time/Period
Position: 150
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 or DTM03 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Figure imgf000094_0001
Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time Refer to value codes in 850 transaction set.
193 Peπod start (install/change)
194 Peπod end (disconnect)
Must Use DTM02 373 Date M DT 6/6
Date (YYMMDD) Requested due date
DTM03 337 Time O TM 4/6
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359) 0900/ AM 1 00/PM
Absence indicates all day Requested due date time
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 19 Century code
Segment: 51 Service Chara
Position: 185
Loop: Level: Headmg
Usage: Optional Max Use: 2
Purpose: To specify service characteπstic data Syntax Notes: 1 If either SI04 ι or SI05 is present, then the other is required,
2 If either SI06 ι or SI07 is present, then the other is required,
3 If either SI08 < or SI09 is present, then the other is required,
4 If either SI 10 or SI 1 1 is present, then the other is reqmred.
5 If either SI 12 or SI 13 is present, then the other is required,
6 If either SI 14 or SI 15 is present, then the other is required,
7 If either SI 16 or SI 17 is present, then the other is required,
8 If either SI 18 or SI 19 is present, then the other is required,
Figure imgf000094_0002
9 If either SI20 or S 121 is present, then the other is required.
Data Element Summary
Ref. Data 93
Des. Elemenl Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2'2
Code identifying the agency assigning the code values
Refer to 850 transaction set lor valid values.
Must Use SI02 1000 Service Characteristics Qualifier M ID 2,2
Code from an industry code list qualifying the type of service characteπsti.s
Must Use SI03 234 Product/Service ID M AN 1,30
Identifying number for a product or service
SI04 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service charactenstiL s
SI05 234 Product/Service ID O AN 1/30
Identifying number for a product or service
SI06 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service charactenstics
SI07 234 Product/Service ID O AN 1/30
Identifying number for a product or service
SI08 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service haracteπsin.s
SI09 234 Product/Service ID O A 1/30
Identifying number for a product or service
SI10 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service charactenstiLs
Sill 234 Product Service ID O AN 1/30
Identifying number for a product or service
SI12 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service characterises
SI13 234 Product/Service ID O AN 1/30
Identifying number for a product or service
SI14 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service characicnsiiLs
SI15 234 Product/Service ID O AN 1/30
Identifying number for a product or service
SI16 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying die type of service charactcπsiics
SI17 234 Product/Service ID O AN 1/30
Identifying number for a product or service
SI18 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service charactcπsiRs
SI19 234 Product/Service ID O AN 1/30
Identifying number for a product or service
SI20 1000 Service Characteristics Qualifier O ID 2/2
Code from an industry code list qualifying the type of service charactcπsiKs
Figure imgf000095_0001
SI21 234 Product/Service ID O AN 1/30
Identifying number for a product or service 94
Segment: PID Product/Item Description
Position: 190
Loop:
Level: Heading
Usage: Optional
Max Use: 200
Purpose: To descnbe a product or process in coded or free-form format
Svntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
3 PID08 descnbes the physical charactenstics of the product identified in PID04. A "Y" indicates that the specified attπbute applies to this item. A "N" indicates it does not apply. Any other value is indeterminate.
Comments: 1 If PIDO 1 = ' ' F", then PID05 is used If PIDO 1 = " ' S", then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being descnbed m the segment.
3 PID07 specifies the individual code list of the agency specified in PID03.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
Refer to 850 transaction set for valid values.
PID02 750 Product/Process Characteristic Code O ID 2/3
Code identifying the general class of a product or process characteπstic
Refer to 850 transaction set for valid values.
PID03 559 Agency Qualifier Code O ID 2/2
Code identifying the agency assigning the code values
Refer to 850 transaction set for valid values.
PID04 751 Product Description Code O AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
PID05 352 Description O AN 1/80
A free-form descnption to clanfy the related data elements and their content PID06 752 Surface/Layer/Position Code O ID 2/2
Code indicating the product surface, layer or position that is being descnbed
Refer to 850 transaction set for valid values
PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response
This data element is yes/no response to the PID04 question in a structured
PID segment
N No
Y Yes
Segment: PWK Paperwork
Position: 210
Loop:
Level: Heading
Usage: Optional 95
Max Use: 25
Purpose: To identify the type and transmission ol paperwork or supporting information
Syntax Notes: 1 If either P WK05 or PW'K.06 is present, then the other is required.
Semantic Notes:
Comments: 1 PWK05 and PWK06 may be used to identify the addressee by a code number.
2 PWK07 may be used to indicate special information to be shown on the specified report.
3 PWK08 may be used to indicate action pertaining to a report.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PWK01 755 Report Type Code M ID 2/2
Code indicating the title or contents of a document, report or supporting item Refer to 850 transaction set for valid values
P K02 756 Report Transmission Code O ID 2/2 Code defining timing, transmission method or format by which reports are to be sent
Refer to 850 transaction set for valid values.
PWK03 757 Report Copies Needed O NO 1/2 The number of copies of a report that should be sent to the addressee PWK04 98 Entity Identifier Code O ID 2/2
Code identifying an orgamzational entity, a physical location, or an individual Refer to 850 transaction set for valid values.
PWK05 66 Identification Code Qualifier O ID 1/2 Code designating the system/method of code structure used for Identification Code (67)
Refer to 850 transaction set for valid values.
PWK06 67 Identification Code O AN 2/17 Code identifying a party or other code PWK07 352 Description O AN 1/80
A free-form descnption to clanfy the related data elements and their content PWK08 704 Paperwork/Report Action Code O ID 1/2
Code specifying how the paperwork or report that is identified in the PVVK segment relates to the transaction set or to identify the action diat is required Refer to 850 transaction set for valid values.
Segment: N1 Name
Position: 300
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N 103 or N 104 is present, then the other is required.
Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient mediod of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintamed by the transaction processing party
Data Element Summary 96
Ref. Data
Des. Element Name
Attributes
Must Use NlOl 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
Refer to 850 transaction set for valid values.
N102 93 Name X AN 1/35
Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67)"
Refer to 850 transaction set for valid values.
N104 67 Identification Code X AN 2/17 Code identifying a party or other code
Segment: N2 Additional Name Information
Position: 310
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify additional names or mose longer than 35 characters in length
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Use N201 93 Name M AN 1/35
Free-form name
N202 93 Name O AN 1/35
Free-form name
Segment: N3 Address Information
Position: 320
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify d e location of the named party
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000098_0001
Attributes
Must Use N301 166 Address Information M AN 1/35
Address information
N302 166 Address Information O AN 1/35
Address information
Segment: N4 Geographic Location
Position: 330
Loop: Nl
Level: Heading 97
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 At least one of N401 is required.
Semantic Notes:
Comments: 1 N402 is required only if city name (N401) is in the USA or Canada.
Data Element Summary
Ref. Data Des. Element Name Attributes N401 19 City Name X AN 2/30
Free-form text for city name
N402 156 State or Province Code O ID 2/2
Code (Standard State) as defined by appropnate government agency
N403 116 Postal Code O ID 3/9
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Segment: NX2 Real Estate Property ID Component
Position: 335
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 3
Purpose: To define types and values for geographic location of real estate property
Syntax Notes:
Semantic Notes: 1 NX201 defines the type of address component.
2 NX202 defines the address component identified NX201.
Comments:
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use NX201 1106 Address Component Qualifier M ID 2/2
Code qualifying the type of address component
12 Building name 13 Apartment number 14 Suite number 30 Pier
The pier at which a ship or boat is docked
31 Wing
The particular wmg of a building
32 Floor
A particular floor or level of a building
33 Dπveway
The dπveway or pπvate road connecting a house, garage, or another building with the street
34 Lot
A particular lot or piece of land 35 Room
A walled room or partitioned area of a building 36 Slip
The slip or location on a pier at which a ship or boat is docked 98
37 Unit
A unit or separate structure
Must Use NX202 166 Address Information M AN 1/35
Address information
Segment: PER Administrative Communications Contact
Position: 350
Loop: Nl
Level: Heading
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
Semantic Notes: Comments:
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifymg the major duty or responsibility of the person or group named
Refer to 850 transaction set for valid values.
PER02 93 Name O AN 1/35
Free-form name PER03 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER04 364 Communication Number X AN 1/25
Complete communications number mcludmg country or area code when applicable
If PER03 = FX
Fax number (iormat = 2167666740)
If PER03 = TE
Telephone number (format = 2166766740) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
If PER03 = FX
Fax number (format = 2167666740)
If PER03 = TE
Telephone number (format = 2166766740)
Segment: POC Line Item Change
Position: 010
Loop: POC
Level: Detail 99
Usage: Optional
Max Use: 1
Purpose: To specify changes to a line item
Syntax Notes: 1 If POC03 is present, then both POC04 and POC05 are required.
3 If POC08 is present, then POC09 is required.
Semantic Notes: 1 POC01 is the purchase order line item identification. Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
POC01 350 Assigned Identification O AN 1/3
Alphanumenc characters assigned for differentiation withm a transaction set Line item number to be changed; i.e.. if change is in P01<2 of oπginal order then POC is 2
POC02 670 Change or Response Type Code O ID 2/2
Code specifying die type of change to the line item
CA Changes to line items
To be used to add a new lme item
DI Delete ιtem(s) RE Replacement item
POC03 330 Quantity Ordered O R 1/9
Quantity ordered Presently, always 1
POC04 671 Quantity Left to Receive O R 1/9
Quantity left to receive as qualified by the unit of measure
Presently, always 1
POC05 355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken EA Each
Must Use POC08 235 Product Service ID Qualifier M ID 2/2
Code identifying the type/source of the descπptive number used in
Product Service ID (234)
TY Telecommunications industry service code
Must Use POC09 234 Product/Service ID M AN 1/30
Identifying number for a product or service
Item identifier (e.g., Line USOC, HML). See Valid Item Identifier Table Liter in this section
Segment: SI Service Characteristic Identification
Position: 018
Loop: POC
Level: Detail
Usage: Optional
Max Use: 5
Purpose: To specify service charactenstic data
Svntax Notes: 1 If either SI04 or SI05 is present, then the other is required.
2 If either SI06 or SI07 is present, then the other is required.
3 If either SI08 or SI 09 is present, then the other is required.
4 If eidier SI10 or SI 1 1 is present, then the other is required.
5 If either SI12 or SI 13 is present, then the other is required.
6 If either SI 14 or SI 15 is present, then the other is required.
7 If either SI16 or SI 17 is present, then the other is required.
8 If either SI 18 or SI 19 is present, then the other is required.
9 If either SI20 or SI 1 is present, then the other is required. 100
Semantic Notes: Comments: 1 SIOl defines the source for each of the service charactenstics qualifiers
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values
Refer to 850 transaction set for valid values.
Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualifying the type of service charactenstics Must Use SI03 234 Product/Service ID M AN 1/30
Identifying number for a product or service SI04 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactcπstiLs SI05 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI06 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics SI07 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI08 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics SI09 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI10 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics Sill 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI12 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics SI13 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI14 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service characteπstiLs SI15 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI16 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics SI17 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI18 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics SI19 234 Product/Service ID X AN 1/30
Identifying number for a product or service SI20 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics SI21 234 Product/Service ID X AN 1/30
Identifying number for a product or service
Segment: PID Product/Item Description
Position: 050
Loop: PID
Level: Detail
Usage: Optional
Max Use: 1 101
Purpose: To descnbe a product or process in coded or free-fomi fonnat Syntax Notes: If PID04 is present, then PID03 is required.
At least one of PID04 or PID05 is required.
Semantic Notes: Use PID03 to indicate the organization that publishes the code list being referred to.
PID04 should be used for industry-specific product descnption codes.
Comments: If PID01 = "F", then PID05 is used. If PID01 = " S". then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used. Use PID06 when necessary to refer to the product surface or layer being descnbed in the segment.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption Refer to 850 transaction set for valid values.
PID02 750 Product/Process Characteristic Code O ID 2/3 Code identifying the general class of a product or process charactenstic Refer to 850 transaction set for valid values.
PID03 559 Agency Qualifier Code X ID 2/2
Code identifying the agency assigning the code values Refer to 850 transaction set for valid values.
PID04 751 Product Description Code X AN 1/12 A code from an industry code list which provides specific data about a product charactenstic
PID05 352 Description X AN 1/80
A free-form description to clanfy the related data elements and their content PID06 752 Surface/Layer/Position Code O ID 2/2 Code indicating die product surface, layer or position that is being descnbed Refer to 850 transaction set for valid values.
PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response This data element is yes/no response to the PID04 question in a structured PID segment
N No
Y Yes
Segment: REF Reference Numbers
Position: 100
Loop: POC
Level: Detail
Usage: Optional
Max Use: 12
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 or REF03 is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reterence Number. Refer to 850 transaction set for valid values. 102
REF02 127 Reference Number X AN 1/30
Reference number or identification number as defined tor a particular Transaction Set. or as specified by the Reference Number Qualifier
REF03 352 Description X AN 1/80
A free-form descnption to clanfy the related data elements and their content
Segment: PER Administrative Communications Contact
Position: 110
Loop: POC
Level: Detail
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the ma]or duty or responsibility of the person or group named
CA Customer Contact Granting Appointment
PER02 93 Name O AN 1/35
Free-form name
Name of contact (customer location)
PER03 365 Communication Number Qualifier ID 2/2
Code identifying the type of communication number
FX Facsimile
TE Telephone
PER04 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
If PER03 = FX
Fax number (format = 2167666740)
If PER03 = TE
Fax number (format = 2167666740) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number AN 1/25
Complete commumcations number including country or area code when applicable
IfPER03 = FX
Fax number (format = 2167666740)
IfPER03 = TE
Telephone number (format = 2166766740)
Segment: DTM Date/Time/Period
Position: 200
Loop: POC
Level: Detail
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one ol DTM02 or DTM03 is required.
Figure imgf000104_0001
Semantic Notes: 103
Comments:
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
Refer to 850 transaction set for valid values.
DTM02 373 Date X DT 6/6
Date (YYMMDD) DTM03 337 Time X TM 4/6
Time expressed in 24-hour clock time (HHMM)
(Time range: 0000 through 2359)
0900/ AM
1300/PM
Absence indicates all day
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 19 Century code
Segment: SLN Subline Item Detail
Position: 460
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify product subline detail item data
Svntax Notes: 1 If SLN07 is present, men SLN06 is required.
2 If SLN08 is present, then SLN06 is required.
3 If SLN09 is present, en SLN 10 is required.
4 If SLN 11 is present, then SLN 12 is required.
5 If SLN 13 is present, then SLN 14 is required.
6 If SLN 15 is present, then SLN 16 is required.
7 If SLN17 is present, then SLN18 is required.
8 If SLN 19 is present, then SLN20 is required.
9 If SLN21 is present, dien SLN22 is required.
10 If SLN23 is present, dien SLN24 is required.
11 If SLN25 is present, dien SLN26 is required.
12 If SLN27 is present, then SLN28 is required.
Semantic Notes: 1 SLNOl is the identifying number for the subline item.
2 SLN02 is the identifying number for the sublme level. The subline level is analogous to the level code used in a bill of matenals.
Comments: 1 See the Data Dictionary for a complete list of ID's.
2 SLNOl is related to (but not necessanly equivalent to) the baseline item number. Example: 1.1 or 1 might be used as a subline number to relate to baseline number 1.
3 SLN09 dirough SLN28 provide for ten ( 10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No.. SKU.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use SLNOl 350 Assigned Identification M AN 1/1 1 104
Alphanumenc characters assigned for differentiation within a transaction s i
SLN02 350 Assigned Identification O AN 1/11
Alphanumenc characters assigned for differentiation within a transaction sd
Must Use SLN03 661 Configuration Code M ID 1/1
Code indicating the relationship of the subline item to the baseline item.
Refer to value codes in 850 transaction set.
Must Use SLN04 380 Quantity M R 1/15
Numeπc value of quantity
Figure imgf000106_0001
Must Use SLN05 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Refer to value codes in 850 transaction set.
SLN06 212 Unit Price X R 1/14
Pπce per unit of product, service, commodity, etc. SLN07 639 Basis of Unit Price Code O ID 2/2
Code identifying the type of unit pπce for an item
Refer to value codes in 850 transaction set.
SLN08 662 Relationship Code O ID 1/1
Code indicating the relationship of the pπce or amount to the associated segment.
Refer to value codes in 850 transaction set.
SLN09 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descπptive number used in
Product Service ID (234)
Refer to value codes in 850 transaction set.
SLN10 234 Product/Service ID X AN 1/30
Identifying number for a product or service SLN11 235 Product/Service ID Qualifier O ID 2/2
Code identifying die type/source of the descπptive number used in
Product Service ID (234)
Refer to value codes in 850 transaction set.
SLN12 234 Product/Service ID X AN 1/30
Identifying number for a product or service SLN13 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descπptive number used in
Product Service ID (234)
Refer to value codes in 850 transaction set.
SLN14 234 Product/Service ID X AN 1/30
Identifying number for a product or service
SLN15 235 Product Service ID Qualifier O ID 2/2
Code identifying the type/source of the descπptive number used in
Product/Service ID (234)
Refer to value codes in 850 transaction set.
SLN16 234 Product Service ID X AN 1/30
Identifying number for a product or service SLN17 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descπptive number used in
Product/Service ID (234)
Refer to value codes in 850 transaction set.
SLN18 234 Product Sen ice ID X AN 1/30
Identifying number for a product or service SLN19 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descπptive number used in
Product/Service ID (234)
Refer to value codes in 850 transaction set.
SLN20 234 Product Sei ice lD X AN 1/30
Identifying number tor a product or service SLN21 235 Product/Serv ice ID Qualifier O ID 2/2 105
Code identifying the type/source of the descπptive number used in
Product/Service ID (234)
Refer to value codes in 850 transaction set.
SLN22 234 Product/Service ID X AN 1/30 Identifying number tor a product or service SLN23 235 Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descπptive number used in Product Service ID (234)
Refer to value codes in 850 transaction set.
SLN24 234 Product/Service ID X AN 1/30 Identifying number for a product or service
SLN25 235 Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descπptive number used in Product Service ID (234)
Refer to value codes in 850 transaction set.
SLN26 234 Product/Service ID X AN 1/30 Identifying number for a product or service
SLN27 235 Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descπptive number used in Product/Service ID (234)
Refer to value codes m 850 transaction set.
SLN28 234 Product/Service ID X AN 1/30
Identifying number for a product or service
Segment: S I Service Characteristic Identification
Position: 470
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 5
Purpose: To specify service characteπstic data
Svntax Notes: 1 If either SI04 or SI05 is present, dien the other is required.
2 If either SI06 or SI07 is present, dien the other is required.
3 If either SI08 or SI09 is present, dien the other is required.
4 If either SI 10 or SI 11 is present, then the odier is required.
5 If either SI 12 or SIB is present, then the other is required.
6 If eidier SIM or SI 15 is present, then the other is required.
7 If either SI 16 or SI 17 is present, then the other is required.
8 If eiϋier SI 18 or SI 19 is present, dien the other is required.
9 If eidier SI20 or SI21 is present, then die other is required.
Semantic Notes: Comments: 1 SIOl defines the source for each of ώe service charactenstics qualifiers
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SIOl 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values
Refer to value codes in 850 transaction set.
Must Use SI02 1000 Service Characteristics Qualifier M ID 2/2
Code from an industry code list qualifying the type of service charactenstics
Must Use SI03 234 Product/Service ID M AN 1/30
Identifying number for a product or service
SI04 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service characteristics
SI05 234 Product/Service ID X AN 1/30
Identifying number for a product or service 106
5106 1000 Service Characteristics Qualifier X ID 2 2
Code from an industry code list qualifying the type of service charactenstics
5107 234 Product Serv ice ID X AN 1/30
Identify ing number for a product or service
5108 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics
5109 234 Product/Service ID X AN 1/30
Identifying number for a product or service
5110 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics Sil l 234 Product/Service ID X AN 1/30
Identifying number for a product or service
5112 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics
5113 234 Product/Service ID X AN 1/30
Identifying number for a product or service
5114 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics
5115 234 Product/Service ID X AN 1/30
Identifying number for a product or service
5116 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics
5117 234 Product/Service ID X AN 1/30
Identify ing number for a product or service
5118 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics
5119 234 Product Service ID X AN 1/30
Identifying number for a product or service
5120 1000 Service Characteristics Qualifier X ID 2/2
Code from an industry code list qualifying the type of service charactenstics
5121 234 Product Service ID X AN 1/30
Identifying number for a product or service
Segment: PID Product/Item Description
Position: 480
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 1000
Purpose: To descnbe a product or process in coded or free-form format
Svntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, ihen PID03 is required.
4 If PID08 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the orgamzation that publishes the code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
3 PID08 descnbes the physical charactenstics of the product identified in PID04. A "Y" indicates that the specified attribute applies to Uns item. A "N" indicates it does not apply. Any other value is indeterminate.
Comments: 1 If PID01 = " F", then PID05 is used. If PID01 = - ' S", then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being descnbed in the segment.
3 PID07 specifies the individual code list of the agency specified in PID03. 107
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
Refer to value codes in 850 transaction set
PID02 750 Product/Process Characteristic Code O ID 2/3
Code identifying the general class of a product or process characteπstic
Refer to value codes in 850 transaction set
PID03 559 Agency Qualifier Code X ID 2/2
Code identifying the agency assigning the code values
Refer to value codes in 850 transaction set
PID04 751 Product Description Code X AN 1/12
A code from an industry code list which provides specific data about a product charactenstic
Refer to value codes in 850 transaction set
PID05 352 Description X AN 1/80
A free-form descnption to clanfy the related data elements and their content
PID06 752 Surface/Layer/Position Code O ID 2/2
Code indicating the product surface, layer or position diat is being descnbed
Refer to value codes m 850 transaction set
PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text mamtamed by the Source Qualifier PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response
This data element is yes/no response to the PID04 question in a structured
PID segment
N No
Y Yes
Segment: DTM Date/Time/Period
Position: 510
Loop: SLN
Level: Detail
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Svntax Notes: 1 At least one of DTM02 or DTM03 is required.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
Refer to value codes in 850 transaction set.
DTM02 373 Date X DT 6/6
Date (YYMMDD) DTM03 337 Time X TM 4/6
Time expressed in 24-hour clock time (HHMM)
(Time range: 0000 through 2359)
0900/ AM
1300/PM
Absence indicates all day
DTM05 624 Century O NO 2/2
The first two characters in the designation of the year 108
19 Centurv code
Segment: N 1 Name Position: 520 Loop: Nl Level: Detail Usage: Optional Max Use: 1
Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required.
2 If eidier N103 or N104 is present, then the other is required. Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use NlOl 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
Refer to value codes in 850 transaction set.
N102 93 Name X AN 1/35
Free-form name N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
Refer to value codes in 850 transaction set.
N104 67 Identification Code X AN 2/17
Code identifying a parry or other code
Segment: IV Add itional Name Information
Position: 530
Loop: Nl Level: Detail
Usage: Optional Max Use: 2
Purpose: To specify additional names or ϋiose longei
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use N201 93 Name M AN 1/35
Free-form name
N202 93 Name O AN 1/35
Free-form name
Segment: N3 Address Information
Position: 540
Loop: Nl Level: Detail
Usage: Optional Max Use: 2
Figure imgf000110_0001
Purpose: To specify the location of the named party 109
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use N301 166 Address Information M AN 1/35
Address information
N302 166 Address Information O AN 1/35
Address information
Segment: N4 Geographic Location
Position: 550
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 At least one of N401 is required.
Semantic Notes:
Comments: 1 N402 is required only if city name (N401) is m the USA or Canada.
Data Element Summary
Ref. Data Des. Element Name Attributes N401 19 City Name X AN 2/30
Free-form text for city name
N402 156 State or Province Code O ID 2/2
Code (Standard State) as defined by appropπate government agency
N403 116 Postal Code O ID 3/9
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Segment: NX2 Real Estate Property ID Component
Position: 560
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 3
Purpose: To define types and values for geographic location of real estate property
Syntax Notes:
Semantic Notes: 1 NX201 defines the type of address component.
2 NX202 defines the address component identified in NX201.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use NX201 1106 Address Component Qualifier M ID 2/2
Code quali 1> ing the type of address component
12 Building name 13 Apartment number 14 Suite number 30 Pier
The pier at which a ship or boat is docked
3 1 Wmg
The particular wing of a building
32 Floor
A particular floor or level of a building 3 Dπveway 110
The dπveway or pπvate road connecting a house. garage, or another building with the street
34 Lot
A particular lot or piece of land
35 Room
A walled room or partitioned area of a building
36 Slip
The slip or location on a pier at which a ship or boat I docked
37 Unit
A unit or separate structure t Use NX202 166 Address Information M AN 1/35
Address information
Segment: PER Administrative Communications Contact
Position: 580
Loop: Nl
Level: Detail
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the odier is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000112_0001
Attributes
Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named
Refer to value codes in 850 transaction set.
PER02 93 Name AN 1/35
Free-form name PER03 365 Communication Number Qualifier ID 2/2
Code identifying die type of communication number
FX Facsimile
TE Telephone
PER04 364 Communication Number AN 1/25 Complete communications number including country or area code when applicable If PER03 = FX Fax number (format = 2167666740)
IfPER03 = TE
Telephone number (format = 2166766740) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1, 25
Complete communications number mcludmg country or area code when applicable If PER03 = FX 111
Fax number (format = 2167666740)
IfPER03 = TE
Telephone number (format = 2166766740)
Segment: CTT Transaction Totals
Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total for a specific element m the transaction set
Syntax Notes:
Semantic Notes:
Comments: This segment is intended to provide hash totals to validate transaction cnommnplleetteenneessss a anndd c coorrrreeccttnneessss-
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use CTTOl 354 Number of Line Items M NO 1/6
Total number of line items in "the transaction set
Segment: S E Transaction Set Trailer
Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and endmg (SE) segments).
Comments: 1 SE is the last segment of each transaction set.
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the onginator for a transaction set
Must match value in ST02
865 Purchase Order Change Acknowledgment/Request — Seller Initiated (Order Completion)
Functional Group ID=CA
Introduction:
This contains the format and establishes the data contents of the Purchase Order Change Acknowledgment/Request — Seller Initiated Transaction Set (865) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to convey acceptance or 112
rejection ot changes to a previously submitted purchase order by the seller or to notify the bu\ er ol" changes initiated by the seller to a previously submitted purchase order by the seller
Preferably, this transaction set is used as a Purchase Order Completion Notification. Onh selected segments are listed.
Heading:
Pos. Seg. Req Loop Notes and
No. ID Name Des Max L se Repeat Comments
Must L se 010 ST Transaction Set Header M 1
Must L se 020 BC A Beginning Segment tor Purchase Order Change M 1
Acknowledgment
050 REF Reference Numbers O 12
060 PER Admimstrauve Commumcauons Contact O
120 ITA Allowance, Charge or Service O 10
150 DTM Date/Time/Peπod O 10
190 PID Product Item Descπouon 0 200
LOOP ID - \9 1000
280 \9 Reterence Number 0 1
290 MSG Message Text 0 1000
Summ ary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max .Lse Repeat Comments
Must L se 010 CTT Transacuon Totals M 1 nl
Figure imgf000114_0001
Must L se O'O SE Transacuon Set Trailer M 1
Transaction Set Notes
1. Number of line items (CTTOl) is the accumulation of the number of POC segments
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Semantic Notes: 1 The transaction set identifier (STOl) used by the translation routines of the interchange partners to select the appropnate transaction set definition
(e.g., 810 selects the Invoice Transaction Set). Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
865 X12.16 Purchase Order Change
Acknowledgment Request - Seller Initiated
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique widun the transaction set functional group assigned by the onginator for a transaction set Must match value in ST02
Segment: BCA Beginning Segment for Purchase Order Change Acknowledgment
Position: 020
Loop:
Level: Heading 113
Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of the Purchase Order Change Acknowledgment
Transaction Set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes
Comments:
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use BCA01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set Completion notice
20 Final Transmission
BCA02 587 Acknowledgment Type O ID 2/2 Code specifying the type of acknowledgment
AE Acknowledge - With Exception Detail Only
Must Use BCA03 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
Customer issued oπgmal order number
BCA05 327 Change Order Sequence Number O AN 1/8
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
Indicates the version of die order completed
Must Use BCA06 323 Purchase Order Date M DT 6/6
Date assigned by the purchaser to Purchase Order
Customer issued onginal order date
BCA10 588 Acknowledgment Date O DT 6/6 Date assigned by the sender to the acknowledgment.
Date of acknowledgement
BCA11 279 Purchase Order Change Request Date O DT 6/6
Date of the purchase order change request Date of change order being acknowledged
Segment: REF Reference Numbers
Position: 050
Loop:
Level: Headmg
Usage: Optional
Max Use: 12
Purpose: To specify identifying numbers.
Syntax Notes: 1 At least one of REF02 is required.
Semantic Notes:
Figure imgf000115_0001
Comments:
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number. O W Service Order Number
Number assigned when a customer orders service and equipment and which appears on bill 114
Must Use REF02 127 Reference Number M AN 1.30
Reference number or identification number as defined for a particular Transaction Set. or as specified by the Reference Number Qualifier, assigned order number
Segment: PER Administrative Communications Contact
Position: 060
Loop:
Level: Heading
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Svntax Notes: 1 If eidier PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named
SR Sales Representative or Department
Must Use PER02 93 Name M AN 1/35
Free-form name
Contact name
Must Use PER03 365 Communication Number Qualifier M ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
Must Use PER04 364 Communication Number M AN 1/25
Complete communications number mcludmg country or area code when applicable lf PER03 = FX
Fax number (tormat = 7082222314)
If PER03 = TE
Telephone number (format = 7082222314) PER05 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number FX Facsimile
TE Telephone
PER06 364 Communication Number X AN 1/25
Complete communications number including country or area code when applicable
If PER03 = FX
Fax number ( tormat = 7082222314)
If PER03 = TE
Telephone number (format = 7082222314)
Segment: 1 I A Allowance, Cl
Position: 120
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Figure imgf000116_0001
Purpose: To specify allowanc Ls. diaraes. or services 115
Syntax Notes: 4 If ITA02 is present, then at least one of ITA03 or ITA 14 is required
Semantic Notes: 1 ITA12 is the quantity of free goods.
Comments: 1 If ITAOl = A- Allowance or C-Charge. then at least one of ITA06. ITA07. or ITA08 must be present.
2 ITA02 identifies the source of the code value in ITA03 or ITA15.
3 If ITA07 is present with either ITA06 or ITA08. then ITA07 takes precedence.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use ITAOl 248 Allowance or Charge Indicator M ID 1/1
Code which indicates an allowance or charge for the service specified C Charge
Must Use ITA02 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values TI Telecommunications Industry
Must Use ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2
Code indicating method of handling for an allowance or charge 06 Charge to be Paid by Customer
ITA07 360 Allowance or Charge Total Amount O N2 1/9
Total dollar amount for the allowance or charge ITA12 380 Quantity O R 1/15
Numenc value of quantity
Number of hours
Must Use ITA14 150 Special Charge or Allowance Code M ID 3/3
Code identifying type of special charge or allowance
580/Premιum deregulated time charges
ACL/Normal hours
LAA Normal deregulated time charges
OAC/Premium regulated time charges
PAD/Premium hours
PAR/Regulated mateπal charge
PAT/Deregulated matenal charge
STL/Normal regulated time charges
Segment: DTM Date/Time/Period
Position: 150
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 or DTM03 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
150 Service Peπod Start (install/change) Date service was requested to start
151 Service Peπod End (disconnect) Date service was requested to end 116
177 Cancellation
Date on which the coverage or service is no longer in force
Must Use DTM02 373 Date M DT 6/6
Date (YYMMDD) Assigned date
DTM03 337 Time O TM 4/6
Time expressed m 24-hour clock time (HHMM) (Time range: 0000 through 2359) 0900/ AM 1300/PM
Absence indicates all day Assigned time
DTM05 624 Century O NO 2/2
The first two characters in the designation of die year (CCYY) 19 Century code
Segment: PID Product/Item Description
Position: 190
Loop:
Level: Heading
Usage: Optional
Max Use: 200
Purpose: To descnbe a product or process in coded or free-form format
Svntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, u en PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
3 PID08 descnbes the physical charactenstics of the product identified in PID04. A "Y" indicates that die specified attribute applies to this item. A "N" indicates it does not apply. Any odier value is indeterminate.
Comments: 1 If PID01 = "F", ien PID05 is used. If PID01 = "S", then PID04 is used. If PID01 = "X", dien both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to die product surface or layer being descnbed m the segment.
3 PID07 specifies the individual code list of the agency specified in PID03.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
S Structured (From Industry Code List)
X Semi-structured (Code and Text)
Must Use PID03 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values AS Assigned by Seller
TI Telecommunications Industry
Must Use PID04 751 Product Description Code M AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
V1N Service call charge
PID07 822 Source Subqualifier O AN 1/15
A reference diat indicates die table or text mamtamed by the Source Qualifier 117
AMT02 list for PID
PID08 1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response
This data element is yes/no response to the PID04 question in a structured
PID segment
N No
Y Yes
Segment: N9 Reference Number
Position: 280
Loop: N9
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To transmit identifying numbers and descπptive information as specified by the reference number qualifier
Syntax Notes: 1 At least one of N902 or N903 is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use N901 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number.
LI Letters or Notes
Must Use N902 127 Reference Number M AN 1/30
Reference number or identification number as defined for a panicular Transaction Set, or as specified by the Reference Number Qualifier. Jack USOCs
Must Use N903 369 Free-form Description M AN 1/45
Free-form descnptive text
Segment: MSG Message Text
Position: 290
Loop: N9
Level: Headmg
Usage: Optional
Max Use: 1000
Purpose: To provide a free form format mat would allow the transmission of text information.
Syntax Notes:
Semantic Notes:
Comments: 1 MSG02 is not related to the specific charactenstics of a pnnter, but identifies top of page, advance a line, etc.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
MSG01 933 Free-Form Message Text M AN 1/264
Free-form message text
Phone jack USOCs information
Segment: CTT Transaction Totals
Position: 010
Loop:
Level: Summary
Figure imgf000119_0001
Usage: Mandatory 118
Max Use:
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes:
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and coπectness.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use CTTOl 354 Number of Line Items M NO 1/6
Total number of line items in the transaction set Will always be 0/zero
Segment: SE Transaction Set Trailer
Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginmng (ST) and ending (SE) segments).
Syntax Notes:
Semantic Notes:
Comments: 1 SE is the last segment of each transaction set.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set includmg ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number mat must be unique within the transaction set functional group assigned by the onginator for a transaction set Must match value in ST02
870 Order Status Report
Functional Group ID=RS Introduction:
This contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use widnn the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific customer in their entirety or on a selection basts. The transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners. Only selected segments are listed.
Notes:
The transaction set can be used to convey jeopardies which occur on an order after die 855 transaction set has been sent.
The number of line items (CTTOl) is the accumulation of the number of HL segments. 119
Headi ng:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.L se Repeat Comments
Must se 010 ST Transaction Set Header \l 1
Musi I se 020 BSR Beεinmnβ Segment for Order Staius Report 1
Figure imgf000121_0001
040 REF Reference Numbers. O 12
Detail:
Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Lse Repeat Comments
LOOP ID - HL 1000
Must I se 010 HL Hierarchical Level M 1
LOOP ID - ISR 104 |
0?0 ISR Item Status Report O 1 1 040 PID
Figure imgf000121_0002
Product Item Descnption O 6 1
080 DTM Date/Time/Peπod
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Lse Repeat Comments
Must L se 010 CTT Transaction Totals M n l ust L se 020 SE Transaction Set Trailer M
Transaction Set Notes
The number of line items (CTTOl) is the accumulation of the number of HL segments.
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (STOl) used by the translation routines of the interchange partners to select the appropπate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
870 X12.1 Order Status Report
Refer to value codes in 850 transaction set
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identify'ing control number that must be unique withm the transaction set functional group assigned by the onginator for a transaction set
Must match value in SE02
Segment: BSR Beginning Segment for Order Status Report
Position: 020
Loop:
Level: Heading
Usage: Mandatory 120
Max Use: 1
Purpose: To indicate the beginning of an Order Status Report.
Semantic Notes: 1 BSR03 indicates a status report document number assigned by the sender.
2 BSR04 indicates the date of this repoπ from the sender.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use BSR01 850 Status Report Code M ID 1/2
Code indicating the reason for sending the report 04 Response to Requisition
Current status data is provided based upon the processing of an outstanding requisition
Must Use BSR02 847 Order/Item Code M ID 1/2 Code identifying a group of orders and items
PA Selected Orders - All Items Must Use BSR03 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Service Order Number
Must Use BSR04 373 Date M DT 6/6
Date (YYMMDD)
Date of Status Repoπ BSR05 848 Product/Date Code O ID 1/2 Code indicating whether the inquiry is based on products and/or date parameters
PD Selected Products and Selected Date Parameters
BSR06 849 Location Code O ID 1/2 Code indicating the selection of a supplier's and/or buyer's locations or group of locations
SL Selected Buyer Locatιon(s)
Segment: Kfcr Reference Numbers
Position: 040
Loop:
Level: Heading
Usage: Optional
Max Use: 12
Purpose: To specify identifymg numbers.
Syntax Notes: 1 At least one of REF02 or REF03 is required.
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000122_0001
Attributes
Must Use REF01 128 Reference Number Qualifier M ID 2/2
Code qualify'ing the Reference Number.
PO Purchase Order Number
Must Use REF02 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Customer's Purchase Order Number
Segment: H L Hierarchical Level
Position: 010
Loop: HL
Level: Detail
Usage: Mandatory
Figure imgf000122_0002
Max Use: 1 121
Purpose: To identify dependencies among and the content of hierarchtcalh related groups of data segments
Syntax Notes:
Semantic Notes:
Comments: The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
HLOl shall contain a unique alphanumenc number for each occurrence of the HL segment in the transaction set. For example, HLOl could be used to indicate the number of occurrences of the HL segment, in which case the value of HLOl would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment with the transaction HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL03 mdicates the context of the senes of segments following the cuπent HL segment up to the next occurrence of an HL segment in the transaction For example, HL03 is used to mdicate diat subsequent segments in the HL loop form a logical grouping of data refemng to shipment, order, or item- level information.
HL04 indicates whedier or not there are subordinate (or child) HL segments related to the current HL segment.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use HLOl 628 Hierarchical ID Number M AN 1/12
A umque number assigned by die sender to identify a particular data segment in a hierarchical structure
Must Use HL03 735 Hierarchical Level Code M ID 1/2
Code defining the characteπstic of a level in a hierarchical structure
D Product Descnption
HL04 736 Hierarchical Child Code O ID 1/1
Code indicating whedier if there are hierarchical child data segments subordinate to die level being descnbed
0 No Additional Subordinates
Segment: ISR Item Status Report
Position: 030
Loop: ISR
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify detailed purchase order/item status
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use ISR01 368 Shipment/Order Status Code M ID 2/2
Code indicating the status of an order or shipment or the disposition of an difference between the quantity ordered and the quantity shipped lor a line item or transaction
PH Product On Hold
Segment: PID Product/Item Description Position: 040 122
Loop: ISR
Level: Detail
Usage: Optional
Max Use: 6
Purpose: To descnbe a product or process m coded or free-form format
Svntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the orgamzation that publishes the code list being referred to.
2 PID04 should be used for industry-specific product descnption codes.
Comments: 1 If PIDO 1 = ' " S", then PID04 is used. If PIDO 1 = " " X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being descnbed in the segment.
3 PID07 specifies the individual code list of the agency specified in PID03
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use PID01 349 Item Description Type M ID 1/1
Code indicating the format of a descnption
S Structured (From Industry Code List)
X Semi -structured (Code and Text)
Must Use PID03 559 Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values AS Assigned by Seller
Must Use PID04 751 Product Description Code M AN 1/12
A code from an industry code list which provides specific data about a product characteπstic
01 Facilities shortage
02 Assignment problems
04 End user not ready
05 Missed appomtment
06 No access
07 Other
08 Call to renegotiate the Due Date
PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier AMT05 Jeopardy List for 850 Transactions
Segment: DTM Date/Time/Period
Position: 080
Loop: HL
Level: Detail
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 or DTM03 is required.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use DTM01 374 Date/Time Qualifier M ID 3/3
Code specif} nig type of date or time, or both date and time 055 Confirmed 123
067 Current Schedule Delivery
Must Use DTM02 373 Date M DT 6/6
Date (YYMMDD)
DTM03 337 Time O TM 4/6
Time expressed in 24-hour clock time (HHMM)
(Time range: 0000 through 2359)
0900/ AM
1300/PM
Absence indicates all day
DTM05 624 Century O NO 2/2
The first two characters m the designation of the year (CCYY) 19 Century code
Segment: CTT Transaction Totals
Figure imgf000125_0001
Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total for a specific element m the transaction set
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use CTTOl 354 Number of Line Items M NO 1/6
Total number of line items in the transaction set
Segment: SE Transaction Set Trailer
Position: 020
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of die transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Comments: 1 SE is the last segment of each transaction set.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number mat must be unique widun die transaction set functional group assigned by the onginator for a transaction set Must match value in ST02
997 Functional Acknowledgment
Functional Group ID=FA Introduction:
This contams the format and establishes die data contents of the Functional Acknowledgment Transaction Set (997) for use withm the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electromcally encoded documents. The encoded documents are die transaction 124
sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max. e Repeat Comments:
Must L se oio ST Transaction Set Header M nl
Must L se 020 AK.1 Funcuonal Group Response Header M n2
LOOP ID - AK.2 999999
0?0 A .2 Transaction Set Response Header O 1 n?
LOOP ID • AK3 999999
040 AK.3 Data Seement Note O 1 c l
050 AK4
Figure imgf000126_0002
Data Element Note O 99
Must L se 060 AK5 Transaction Set Response Trailer M
Musi L se 070 A .9 Funcuonal Group Response Trailer M
Figure imgf000126_0001
Must L se 080 SE Transaction Set Trailer M
Transaction Set Notes
1. These acknowledgments shall not be acknowledged, ereby preventing an endless cycle of acknowledgments of acknowledgments.
2. The Functional Group Header Segment (GS) is used to start the envelope for the Functional Acknowledgment Transaction Sets. In prepaπng the functional group of acknowledgments, the application sender's code and the application receiver's code, taken from the functional group being acknowledged, are exchanged; therefore, one acknowledgment functional group responds to only those functional groups from one application receiver's code to one application sender's code.
3. There is only one Functional Acknowledgment Transaction Set per acknowledged functional group.
4. AK1 is used to respond to the functional group header and to start the acknowledgment for a functional group. There shall be one AK1 segment for the functional group tiiat is being acknowledged.
5. AK2 is used to start the acknowledgment of a transaction set withm the received functional group. The AK2 segments shall appear m the same order as the transaction sets in the functional group that has been received and is being acknowledged.
Transaction Set Comments
1. The data segments of this standard are used to repoπ the results of the syntactical analysis of the functional groups of transaction sets; they report the extent to which the syntax complies with the standards for transaction sets and functional groups. They do not repoπ on the semantic meaning of the transaction sets (for example, on the ability of the receiver to comply widi the request of the sender).
Segment: ST Transaction Set Header
Position: 010
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (STOl) used by die translation routines of die interchange partners to select the appropπate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Comments:
Data Element Summary
Ref. Data 125
Des. Element Name Attributes
Must Use STOl 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
997 X12.20 Functional Acknowledgment
Must Use ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique widnn the transaction set functional group assigned by the onginator for a transaction set
Segment: AK1 Functional Group Response Header
Position: 020
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To start acknowledgment of a functional group
Syntax Notes:
Semantic Notes: 1 AK101 is the functional ID found m the GS segment (GS01) m the functional group bemg acknowledged.
2 AK102 is die data mterchange control number found m the GS segment in the functional group being acknowledged.
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Figure imgf000127_0001
Must Use AK101 479 Functional Identifier Code M ID 2/2
Code identifying a group of application related transaction sets PC PO
Must Use AK102 28 Group Control Number M NO 1/9
Assigned number ongmated and maintamed by die sender
Segment: AK2 Transaction Set Response Header
Position: 030
Loop: AK2
Level:
Usage: Optional
Max Use: 1
Purpose: To start acknowledgment of a single transaction set
Syntax Notes:
Semantic Notes: 1 AK201 is the transaction set ID found m the ST segment (STOl) in the transaction set being acknowledged.
2 A 202 is the transaction set control number found in the ST segment in the transaction set being acknowledged.
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Figure imgf000127_0002
Must Use AK201 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set 850 X 12.1 Purchase Order
860 XI 2.15 Purchase Order Change Request - Buyer
Initiated 126
Must Use AK202 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique withm the transaction set functional group assigned by the onginator for a transaction set
Segment: Ar\ Data Segment Note
Position: 040
Loop: AK3
Level:
Usage: Optional
Max Use: 1
Purpose: To report errors in a data segment and u
Syntax Notes: maπtic Notes:
Comments:
Data Element Summary
Ref. Data
Des. Element Name
Figure imgf000128_0001
Attributes
Must Use AK301 721 Segment ED Code M ID 2/3
Code defining die segment ID of die data segment in error Must Use AK302 719 Segment Position in Transaction Set M NO 1/6
The numeπcal count position of this data segment from the start of the transaction set: the transaction- set header is count position 1
Segment: AK4 Data Element Note
Position: 050
Loop: AK3
Level:
Usage: Optional
Max Use: 99
Purpose: To report errors in a data element and identify the location of the data element
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use AK401 722 Element Position in Segment M NO 1/2
This is used to indicate die relative position of the data element in error in mis data segment. The count starts with 1 for the data element immediately following the segment ID. This value is 0 for an error in the segment ID.
AK402 725 Data Element Reference Number O NO 1/4
Reference number used to locate the Data Element Dictionary.
Must Use AK403 723 Data Element Syntax Error Code M ID 1/3 Code indicating the error found after syntax edits of a data element
AK404 724 Copy of Bad Data Element O AN 1/99 This is a copy of the data element in error
Segment: AK5 Transaction Set Response Trailer
Position: 060
Loop: AK2
Level:
Usage: Mandatory
Max Use: 1
Purpose: To acknowledge acceptance or rejection and report errors in a transaction set
Data Element Summary
Ref. Data 127
Des. Element Name Attributes Must Use AK501 717 Transaction Set Acknowledgment Code M ID 1/1
Code indicating accept or reject condition based on the syntax editing ot the transaction set
A Accepted
R Rejected
AK502 718 Transaction Set Syntax Error Code O ID 1/3 Code indicating error found based on the syntax editing of a transaction set
1 Transaction Set Not Supported
2 Transaction Set Trailer Missing
3 Transaction Set Control Number in Header and Trailer Do Not Match
4 Number of Included Segments Does Not Match Actual Count
5 One or More Segments m Error
6 Missing or Invalid Transaction Set Identifier
7 Missing or Invalid Transaction Set Control Number
AK503 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set
1 Transaction Set Not Supported
2 Transaction Set Trailer Missing
3 Transaction Set Control Number in Header and Trailer Do Not Match
4 Number of Included Segments Does Not Match Actual Count
5 One or More Segments in Error
6 Missing or Invalid Transaction Set Identifier
7 Missing or Invalid Transaction Set Control Number
AK504 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set
1 Transaction Set Not Supported
2 Transaction Set Trailer Missing
3 Transaction Set Control Number in Header and Trailer Do Not Match
4 Number of Included Segments Does Not Match Actual Count
5 One or More Segments in Error
6 Missing or Invalid Transaction Set Identifier
7 Missing or Invalid Transaction Set Control Number AK505 718 Transaction Set Syntax Error Code O ID 1/3
Code indicatmg error found based on the syntax editing of a transaction set
1 Transaction Set Not Supported
2 Transaction Set Trailer Missing
3 Transaction Set Control Number in Header and Trailer Do Not Match
4 Number of Included Segments Does Not Match Actual Count
5 One or More Segments in Error
6 Missing or Invalid Transaction Set Identifier
7 Missing or Invalid Transaction Set Control Number AK506 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set
1 Transaction Set Not Supported
2 Transaction Set Trailer Missing
3 Transaction Set Control Number in Header and Trailer Do Not Match 128
4 Number of Included Segments Does Not Match Actual Count
5 One or More Segments in Error
6 Missing or Invalid Transaction Set Identifier
7 Missing or Invalid Transaction Set Control Number
Segment: AK9 Functional Group Response Trailer
Position: 070
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To acknowledge acceptance or rejection of a functional group and report the number of included transaction sets from the oπgmal trailer, the accepted sets, and die received sets in this functional group
Syntax Notes:
Semantic Notes:
Comments: 1 If AK901 is 'A' or 'E', then the transmiπed functional group is accepted. If AK901 is 'R', then the transmitted group is rejected.
Data Element Summary
Ref. Data Des. Element Name Attributes Must Use AK901 715 Functional Group Acknowledge Code M ID 1/1
Code indicating accept or reject condition based on the syntax editing of the functional group
A Accepted
R Rejected
Must Use AK902 97 Number of Transaction Sets Included M NO 1/6
Total number of transaction sets mcluded in the functional group or interchange (transmission) group teπmnated by die trailer containing this data element
Value should equal the same data element m the Functional Group Trailer
(GE01) of the functional group being acknowledged.
Must Use AK903 123 Number of Received Transaction Sets M NO 1/6
Number of Transaction Sets received
Must Use AK904 2 Number of Accepted Transaction Sets M NO 1/6
Number of accepted Transaction Sets m a Functional Group
AK905 716 Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group header and or trailer
AK906 716 Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group header and/or trailer
AK907 716 Functional Group Syntax Error Code O ID 1/3
Code indicating eπor found based on die syntax editmg of the functional group header and/or trailer
AK908 716 Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on die syntax editmg of the functional group header and/or trailer
AK909 716 Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editmg of the functional group header and/or trailer
Segment: SE Transaction Set Trailer
Position: 080
Loop: 129
Level:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).
Comments: 1 SE is the last seament of each transaction set.
Data Element Summary
Ref. Data
Des. Element Name
Attributes
Must Use SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE segments
Must Use SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number mat must be unique withm the transaction set functional group assigned by the onginator for a transaction set

Claims

- 13 0 -What Is Claimed Is;
1. A method for electronically exchanging information related to telecommunication services, the method comprising: separating data representing the information to be exchanged into a plurality of predefined segments; associating a segment identification code with each of the plurality of predefined segments, at least one of the segments corresponding to one of the telecommunication services; grouping each of the plurality of predefined segment identification codes with corresponding data; concatenating the segment identification codes and associated data according to a predefined sequence to form an electronic transaction; and transmitting the electronic message.
2. The method of claim 1 wherein the predefined segment identification codes and the predefined sequence are determined by a standards organization.
3. The method of claim 1 wherein associating a segment identification code comprises associating a unique segment identification code for jeopardy notification, account loss notification, telephone number selection, due date selection, and customer service record retrieval.
4. The method of claim 1 wherein transmitting comprises transmitting the electronic message over a - 131 -
TCP/IP socket connection between a telecommunications reseller and a telecommunications wholesaler.
5. The method of claim 1 further comprising: parsing the electronic message to separate the segment identification codes and associated data; processing the associated data to identify a corresponding telecommunication service; and automatically generating an acknowledgment containing segment identification codes for the corresponding telecommunication service.
6. The method of claim 5 wherein processing the associated data comprises: retrieving customer service information; formatting the customer service information using the segment identification codes; and forwarding the formatted customer service information to a telecommunication services reseller.
7. The method of claim 5 wherein processing the associated data comprises: identifying a request related to telephone number selection based on the data associated with a telephone number selection segment; searching for available telephone numbers; and generating a response using a segment identification code having associated data including at least one available telephone number.
8. The method of claim 5 wherein processing the associated data comprises: - 132 - ldentifymg a request related to due date selection based on the data associated with a due date selection segment; searching for available due dates; and generating a response using a segment identification code having data including at least one available due date .
9. The method of claim 5 wherein processing the associated data comprises: generating a response indicating an error corresponding to unavailability of a requested service.
10. A computer readable storage medium having stored therein data representing instructions executable by a programmed microprocessor for electronically exchanging information related to telecommunication services, the storage medium comprising instructions for: separating data representing the information to be exchanged into a plurality of predefined segments, associating a segment identification code with each of the plurality of predefined segments, at least one of the segments corresponding to one of the telecommunication services; grouping each of the plurality of predefined segment identification codes with corresponding data; concatenating the segment identification codes and associated data according to a predefined sequence to form an electronic transaction; and transmitting the electronic message.
11. The computer readable storage medium of claim 10 wherein the instructions associate a unique - 133 - segment identification code for jeopardy notification, account loss notification, telephone number selection, due date selection, and customer service record retrieval .
12. The computer readable storage medium of claim 10 further comprising instructions for transmitting the electronic message over a TCP/IP socket connection.
13. The computer readable storage medium of claim 10 further comprising instructions for: parsing the electronic message to separate the segment identification codes and associated data; processing the associated data to identify a corresponding telecommunication service; and automatically generating an acknowledgment containing segment identification codes for the corresponding telecommunication service.
14. The computer readable storage medium of claim 13 further comprising instructions for: retrieving customer service information; formatting the customer service information using the segment identification codes; and forwarding the formatted customer service information to a telecommunication services reseller.
15. The computer readable storage medium of claim 13 wherein the instructions for processing the associated data include instructions for: identifying a request related to telephone number selection based on the data associated with a telephone number selection segment; - 134 - searching for available telephone numbers; and generating a response using a segment identification code having associated data including at least one available telephone number.
16. The computer readable storage medium of claim 13 wherein the instructions for processing the associated data include instructions for: identifying a request related to due date selection based on the data associated with a due date selection segment; searching for available due dates; and generating a response using a segment identification code having data including at least one available due date .
17. The computer readable storage medium of claim 13 wherein the instructions for processing the associated data include instructions for: generating a response indicating an error corresponding to unavailability of a requested service.
18. A system for electronically exchanging information related to telecommunication services, the system comprising: control logic for separating data representing the information to be exchanged into a plurality of predefined segments, associating a segment identification code with each of the plurality of predefined segments with at least one of the segments corresponding to one of the telecommunication services, grouping each of the plurality of predefined segment identification codes with corresponding data, concatenating the segment identification codes and - 135 - associated data according to a predefined sequence to form an electronic transaction, and transmitting the electronic message.
19. The system of claim 18 further comprising control logic for associating a associating a unique segment identification code for jeopardy notification, account loss notification, telephone number selection, due date selection, and customer service record retrieval .
20. The system of claim 18 further comprising control logic for transmitting the electronic message over a TCP/IP socket connection between a telecommunications reseller and a telecommunications wholesaler.
PCT/US1999/004215 1998-04-06 1999-02-26 Transaction sets for automated electronic ordering of telecommunications products and services WO1999052264A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU27926/99A AU2792699A (en) 1998-04-06 1999-02-26 Transaction sets for automated electronic ordering of telecommunications products and services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/055,846 1998-04-06
US09/055,846 US6104999A (en) 1998-04-06 1998-04-06 Transaction sets for automated electronic ordering of telecommunications products and services

Publications (1)

Publication Number Publication Date
WO1999052264A1 true WO1999052264A1 (en) 1999-10-14

Family

ID=22000533

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/004215 WO1999052264A1 (en) 1998-04-06 1999-02-26 Transaction sets for automated electronic ordering of telecommunications products and services

Country Status (3)

Country Link
US (6) US6104999A (en)
AU (1) AU2792699A (en)
WO (1) WO1999052264A1 (en)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6137873A (en) * 1998-04-06 2000-10-24 Ameritech Corporation Automatic electronic telecommunications order translation and processing
US6104999A (en) 1998-04-06 2000-08-15 Ameritech Corporation Transaction sets for automated electronic ordering of telecommunications products and services
US6249578B1 (en) * 1998-04-06 2001-06-19 Ameritech Corporation Interactive electronic ordering for telecommunications products and services
US20060167768A1 (en) * 1999-09-10 2006-07-27 Sculler Steven J Method and system for facilitating reseller transactions
US6901376B1 (en) 1999-09-10 2005-05-31 M&R Marking Systems, Inc. Method and system for facilitating reseller transactions
US7577243B1 (en) * 1999-09-27 2009-08-18 At&T Intellectual Property 1, L.P. Method, system, and article for determining an availability of a telecommunication device
US7003473B2 (en) * 2000-01-18 2006-02-21 Wisor Telecom Corporation Fully integrated service manager with automatic flow-through interconnection
WO2001061523A1 (en) * 2000-02-18 2001-08-23 Cedere Corporation Automated on-line business bandwidth planning methodology
US20010044743A1 (en) * 2000-03-28 2001-11-22 Mckinley James M. System and method for profile driven commerce
US20050033583A1 (en) * 2000-07-27 2005-02-10 Bergeron Heather Ellen Processing transactions using a structured natural language
JP2004511839A (en) * 2000-07-28 2004-04-15 アメリカン　カルカー　インコーポレイティド Technology for organizing and communicating information effectively
US7149717B1 (en) * 2000-10-26 2006-12-12 Kan Steven S Method and system to effectuate multiple transaction prices for a commodity
US8364798B2 (en) * 2001-01-23 2013-01-29 Verizon Business Global Llc Method and system for providing software integration for a telecommunications services on-line procurement system
US20020111839A1 (en) * 2001-02-13 2002-08-15 Nitin Nayak Method and system for forming dynamic vendor coalitions in collaborative e-commerce
US20030131120A1 (en) * 2002-01-09 2003-07-10 International Business Machines Corporation Automation and dynamic matching of business to business processes
US7213058B1 (en) * 2002-02-27 2007-05-01 Bellsouth Intellectual Property Corporation Systems and methods for processing and managing collocation application over a computer network
US20040024646A1 (en) * 2002-07-31 2004-02-05 James Iry System and method for automated authorization for service provider switching
US20040073569A1 (en) * 2002-09-27 2004-04-15 Sbc Properties, L.P. System and method for integrating a personal adaptive agent
US20050071254A1 (en) * 2003-09-25 2005-03-31 Aboujaoude Roger B. Integrated order management system for telecommunication services
US7577587B2 (en) * 2004-07-07 2009-08-18 Sap Ag Purchase order and purchase order response interactive forms
US20100290365A1 (en) * 2004-12-22 2010-11-18 Kwong Andrew W Multi-level hosted inbound administration for a telephony system
EA200600717A1 (en) * 2006-01-23 2007-04-27 Общество С Ограниченной Ответственностью «Интерактивная Мобильная Процессинговая Компания "Мегапэй"» METHOD OF PERFORMING THE PAYMENT FINANCIAL OPERATION (OPTIONS)
US20100125617A1 (en) * 2008-11-18 2010-05-20 Andrea Alexander System for Consolidating Business Documents
US10025622B2 (en) * 2009-11-12 2018-07-17 Oracle International Corporation Distributed order orchestration
US8509226B1 (en) * 2012-08-31 2013-08-13 Orisha Holdings, L.L.C. Multi-tenant service management in a VoIP network
US9210254B2 (en) 2013-10-09 2015-12-08 Shango Corp, LLC Unified services platform using a telephone number as a common subscriber identifier
US10771369B2 (en) * 2017-03-20 2020-09-08 International Business Machines Corporation Analyzing performance and capacity of a complex storage environment for predicting expected incident of resource exhaustion on a data path of interest by analyzing maximum values of resource usage over time

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4951196A (en) * 1988-05-04 1990-08-21 Supply Tech, Inc. Method and apparatus for electronic data interchange
US5491742A (en) * 1993-11-16 1996-02-13 Bell Atlantic Network Services, Inc. Method and apparatus for provisioning a public switched telephone network
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data
US5644619A (en) * 1993-11-16 1997-07-01 Bell Atlantic Network Services, Inc. Analysis and validation system for provisioning a public switched telephone network
US5794206A (en) * 1996-05-06 1998-08-11 Sterling Commerce, Inc. Method and system for displaying electronic data interchanges in a computer
US5794234A (en) * 1996-08-14 1998-08-11 The Ec Company Method and system for providing electronic commerce between incompatible data processing systems
US5870394A (en) * 1996-07-23 1999-02-09 Northern Telecom Limited Method and apparatus for reassembly of data packets into messages in an asynchronous transfer mode communications system

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4232199A (en) * 1978-10-18 1980-11-04 Summa Four, Inc. Special services add-on for dial pulse activated telephone switching office
US4782519A (en) * 1986-05-22 1988-11-01 Network Access Corporation Method and apparatus for enhancing the operating capabilities of a telephone switching system
US5086461A (en) * 1990-01-23 1992-02-04 Network Access Corporation Apparatus and method for providing existing 1ESS and 1AESS telephone switching equipment with the capability of using the SS7 protocol
US5012511A (en) * 1990-04-06 1991-04-30 Bell Atlantic Network Services, Inc. Method of and system for control of special services by remote access
US5283887A (en) * 1990-12-19 1994-02-01 Bull Hn Information Systems Inc. Automatic document format conversion in an electronic mail system based upon user preference
US5222125A (en) * 1991-09-03 1993-06-22 At&T Bell Laboratories System for providing personalized telephone calling features
US5528677A (en) * 1992-05-01 1996-06-18 Sprint Communications Company L.P. System for providing communications services in a telecommunications network
GB9221438D0 (en) 1992-10-13 1992-11-25 Philips Electronics Nv Time management for cordless telephone
US5416833A (en) * 1993-11-16 1995-05-16 Bell Atlantic Network Services, Inc. Method and apparatus for provisioning a public switched telephone network
US5881131A (en) 1993-11-16 1999-03-09 Bell Atlantic Network Services, Inc. Analysis and validation system for provisioning network related facilities
US5751802A (en) 1994-12-27 1998-05-12 At & T Corp Telecommunications service provisioning
WO1996041448A1 (en) * 1995-06-07 1996-12-19 E-Comm Incorporated Handheld remote computer control and methods for secured interactive real-time telecommunications
US5687224A (en) 1995-07-26 1997-11-11 Alley, Jr.; Willard Kent Telecommunications circuit provisioning and administration system
US6002758A (en) 1996-04-12 1999-12-14 Telcordia Technologies, Inc. System and method for developing message processing applications
JPH10105968A (en) 1996-09-24 1998-04-24 Sony Corp Optical recording method
US6061439A (en) 1997-03-27 2000-05-09 Nortel Networks Corporation Method and apparatus for providing subscriber services to a telephone
US6018570A (en) 1997-05-12 2000-01-25 Nynex Science And Technology Inc. Methods and apparatus for regulating the remote ordering, authorization, access and control of services and service features associated with a terminal
US6269399B1 (en) * 1997-12-19 2001-07-31 Qwest Communications International Inc. Gateway system and associated method
US6104798A (en) 1998-02-12 2000-08-15 Mci Communications Corporation Order processing and reporting system for telecommunications carrier services
US6104999A (en) 1998-04-06 2000-08-15 Ameritech Corporation Transaction sets for automated electronic ordering of telecommunications products and services
US6249578B1 (en) 1998-04-06 2001-06-19 Ameritech Corporation Interactive electronic ordering for telecommunications products and services
US6137873A (en) 1998-04-06 2000-10-24 Ameritech Corporation Automatic electronic telecommunications order translation and processing
US5951196A (en) * 1998-05-08 1999-09-14 Taiwan Semiconductor Manufacturing Co. Ltd. Frictional mount for engaging a monitor in a process chamber and method of using
AU2001266756A1 (en) * 2000-06-19 2002-01-02 Ashland Inc. Business method for facilitating the sale of goods and services
EP1361529A4 (en) 2001-02-15 2010-05-26 Ntt Docomo Inc Method and device for handling cost apportionment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4951196A (en) * 1988-05-04 1990-08-21 Supply Tech, Inc. Method and apparatus for electronic data interchange
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data
US5491742A (en) * 1993-11-16 1996-02-13 Bell Atlantic Network Services, Inc. Method and apparatus for provisioning a public switched telephone network
US5644619A (en) * 1993-11-16 1997-07-01 Bell Atlantic Network Services, Inc. Analysis and validation system for provisioning a public switched telephone network
US5794206A (en) * 1996-05-06 1998-08-11 Sterling Commerce, Inc. Method and system for displaying electronic data interchanges in a computer
US5870394A (en) * 1996-07-23 1999-02-09 Northern Telecom Limited Method and apparatus for reassembly of data packets into messages in an asynchronous transfer mode communications system
US5794234A (en) * 1996-08-14 1998-08-11 The Ec Company Method and system for providing electronic commerce between incompatible data processing systems

Also Published As

Publication number Publication date
US7107223B2 (en) 2006-09-12
US7072458B2 (en) 2006-07-04
US6411935B1 (en) 2002-06-25
US8140400B2 (en) 2012-03-20
AU2792699A (en) 1999-10-25
US7457759B2 (en) 2008-11-25
US6104999A (en) 2000-08-15
US20060133589A1 (en) 2006-06-22
US20050135576A1 (en) 2005-06-23
US20030007623A1 (en) 2003-01-09
US20090067601A1 (en) 2009-03-12

Similar Documents

Publication Publication Date Title
WO1999052264A1 (en) Transaction sets for automated electronic ordering of telecommunications products and services
US7406163B2 (en) Automated electronic telecommunications order translation and processing
US6681007B2 (en) Interactive electronic ordering for telecommunications products and services
EP1597689A2 (en) System and method for managing and processing of telecommunications invoices
CN110322190A (en) The method that steel industry intrabranch service order based on SAP automatically creates
JP5401717B2 (en) Service report system
Cuyvers et al. Electronic data interchange in international trade
Cuyvers et al. Assessing the impact of EDI: a cost accounting framework
Invoice QWEST Communications International Inc. Technical Publication
Yang et al. A Software Structure for JIT Supply Chain Production Synchronization System Using Internet and EDI
Luster et al. DoD Electronic Data Interchange (EDI) Convention: ASC X12 Transaction Set 860 Purchase Order Change (Version 003010)
XNfOTCTED Mms 251
Luster et al. DoD Electronic Data Interchange (EDI) Convention: ASC X12 Transaction Set 850 Purchase Order (Version 003010)
Egan et al. Using Electronic Data Interchange to Report Product Quality

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
NENP Non-entry into the national phase

Ref country code: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase