Art,

While the NTE segment is technically included in the industry guidelines for
the 811, there is also a strong recommendation against its use.  Typically,
there are specific uses for human-readable text associated with a bill -
OC&C descriptions, regulatory messages, etc.  The 864 guidelines include an
industry-standard set of codes to describe the text being attached to the
bill.  So, you are nominally correct but there are good reasons to use the
864 for all but the simplest (and nonstandard) of text messages.  This
scenario is very much a known entity in telecom billing and is documented on
an industry and carrier basis.

Mickey Dossey
EDI Manager
Neustar

 
-------Original Message-------
 
From: [EMAIL PROTECTED]
Date: 01/19/05 13:34:46
To: [email protected]; [EMAIL PROTECTED]
Subject: RE: [EDI-L] Help needed: 811-864 Transaction set
 
If all you need is more than 80 bytes for your text, the approach can be as
simple as using up to 100 NTE segments back to back.  That way you can avoid
the 864 altogether.

Art Douglas
Manager, eCommerce Systems
PaperPak
San Dimas, CA
909-971-5025


-----Original Message-----
From: Mickey Dossey [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 19, 2005 4:39 AM
To: EDI-L Mailing List
Subject: Re: [EDI-L] Help needed: 811-864 Transaction set


I assume this is a telecom implementation, since the industry does have a
convention of using the 811 and 864 together to render a complete electronic
bill.  The guidelines are, as William stated, maintained by the ETB
Committee.  The link is old, since TCIF no longer exists as a forum - it was
incorporated into OBF (Ordering and Billing Forum) over a year ago.  The
link to the ETB Committee home page is:

http://www.atis.org/obf/etb_home.asp

The 811/864 is used more often by larger carriers who service larger
business clients, so if you are working on a project for a carrier of this
type, you should have access to these specifications.

Mickey Dossey
EDI Manager
Neustar


-------Original Message-------

From: William J. Kammerer
Date: 01/19/05 07:11:58
To: EDI-L Mailing List
Subject: Re: [EDI-L] Help needed: 811-864 Transaction set

Usually REF segments would be used to "tie" the two transaction sets
together;  or else their association could be inferred from being placed
in the same interchange (ISA-IEA).  Your industry may have guidelines on
the proper usage of the 811 and possibly 864. The 811 is popular in
telecommunications, as well attested by David Frenkel, a popular
personality here on EDI-L.  Where's Dave when you need him?  He would
point you to the EDI Telecommunications Billing (ETB) guidelines at
http://www.atis.org/atis/tcif/etb/aboutetb.htm.

William J. Kammerer
Novannet, LLC.
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320

----- Original Message ----- 
From: "Sasi Mr" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, 18 January, 2005 05:54 PM
Subject: [EDI-L] Help needed: 811-864 Transaction set



Hi,

I am currently working in creating EDI 811 Transaction set. We have a
constrain of providing text message not more than 80 bytes. But we
noticed that we can do it by 864 Transaction sets. Is there any way to
incorporate 811 Transaction set data with the 864 data?

Any help will be appreciated.

Thanks,
Sasikumar.





..  
Please use the following Message Identifiers as your subject prefix: <SALES>
 <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at:  http://groups.yahoo.com/group/EDI-L





Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
  
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
  
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


 

[Non-text portions of this message have been removed]



.  
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at:  http://groups.yahoo.com/group/EDI-L
 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to