Problems with Reference Numbers in EDI Business Cycle

Subject:	Exchanging Cross Reference Tables and Reports
Date:	Tue, 11 Aug 1992 11:24:51 - 0400
Sender:	EDI-L@edu.uccp.uccvma
Reply to:	Electronic Data Interchange Issues
To:	Multiple recipients of list EDI-L@edu.uccp.uccvma>
Via: (to 11 Aug 92 20:58:52 BST
Msg ID:  
Received: from by with Internet SMTP
		id ;
		Tue 11 Aug 1992 20:57:38   +0100
Received: from UCCVMA.UCOP.EDU by (IBM VM SMTP V2R2)with BSMTP
		id 7358:  Tue 11 Aug 92 12:57:27 PDT
Received: from UCCVMA.BITMAP by UCCVMA.UCOP.EDU (Mailer 82.08) with BSMTP
		id 9544:  Tue 11 Aug 92 12:57:26 PDT
Original-Sender: Electronic Data Interchange issues 

I have questions in two general areas that I hope readers of the list can help me with.  Since
 implementing X12 nearly three years ago (we are currently exchanging nine different transaction
 sets with a variety of trading partners), we have regularly encountered a need to exchange 
reference numbers in machine readable form with trading partners.  

This is the result of a variety of factors, including the fact that our industry is only now 
developing X12 mapping conventions and there are few situations where both trading partners' 
systems fully accommodate each other's data.  

Thus, standard use of codes and identifying numbers is starting to occur, but, since the 
industry has used manual methods, industry tape conventions, and proprietary formats to 
exchange reference number tables for many years,  a need for a standard approach to exchange 
these reference numbers persists and will persist for a while.  

As reengineering occurs throughout the manufacturing industry, it will become possible for both
parties to capture and store necessary data in the course of exchanging a set of business 
transactions, but that is still in the future.

We are interested in identifying a transaction set that efficiently accommodates an exchange 
of reference numbers - for example a list of service or product numbers and a key for the
loading system.  We have considered various approaches to meet this need, and as members of 
ASC X12 we monitor standards activities, but we really have not found a suitable transaction
set for this purpose.  

Has anyone out there also encountered this need?  

Is anyone currently exchanging cross reference tables in an X12 transaction set?  

Is anyone aware of any standards development work (either X12 or EDIFACT) in this area?

Another question I have is whether anyone has implemented (or can suggest) a transaction set
to use to exchange information in structured analytical reports.  

We have looked at both the X12 863 (Report of Test Results) and X12 864 (Text Message) but do
not find them suitable.  

Is there any work in X12 or EDIFACT that anyone knows of that might help here?

Thanks for any information you can provide.

Joe Santosuosso		Tel:  617-329-3350. Ext. 464
Senior EDI Analyst		Fax:  617-329-9875
The Faxon Company	    Email:
15 Southwest Park

Subject:	I still can't post to edi-l - help!
From:	Richard Hintz 
Date:	Wed, 12 Aug 1992 09:22:09 POT
SOriginal-Sender: Electronic Data Interchange issues EDI-L@edu.ucop.uccvma
Comments:  Originally-From: Paula Swatman

Note:  the following posting is originally from Paul Swatman
-----------------------------------Original Message----------------------------------
Dear Joe,

I have some information which you may find helpful on the topic of communicating with 
industry-specific trading partners.  

The EDI Council of Australia has created a number of "Industry Working Parties" to (and I quote
from EDICA's Members' Sourcebook):

"ensure that, to the extent possible, the implementation of the standard be consistent so as
to enable easy document exchange between trading partners within a given industry as well as 
those trading on a cross-industry basis.  

To this goal, the Council has established industry working parties at the request of users 
within defined industry segments, to:-

- represent the industry in all matters relating to the information transmission needs of 
  the industry.
- identify how these information needs may be represented in the data standard.
- communicate this information to the industry at large.
- define and assist in the publication of industry implementation guidelines for use by the
- prepare and forward document standard change requests to EDICA so that they be passed to the 
  relevant standards body.
- encourage and prepare for industry progression to a single, world-wide document standard.
- liaise with other industry groups as required.
- Assess other industry group guidelines as they become available with a view to considering 
  their impact on cross industry trading."

These industry groups (currently comprising agribusiness, banking, chemical, communications, 
construction, government, hardware, heavy engineering, life insurance, local government, medical,
pharmaceutical, retail, steel, travel, tourism and leisure, transport and wholesale/distribution)
are working to develop industry implementation guidelines - at least some of which are already 
well on the way to completion.  

At present the ASC X12 guidelines are complete, while the EDIFACT guidelines are still under 

For further information, contact the EDI Council of Australia, P.O. Box 521, Hawthorn, Victoria,
Australia, 3122.  Fax +619 818 3129.  Tel +619 819 6860.

Subject:	I still can't post to edi-l - help!
From:	Richard Hintz 
Date:	Wed, 12 Aug 1992 09:22:09 POT
Sender:	EDI-L@edu.uccp.uccvma
Reply to:	Electronic Data Interchange Issues
To:	Multiple recipients of list EDI-L 
Comments:	Resent-from: Richard Hintz 



We have been speaking with a management consultancy from Australia, HALISA INTERNATIONAL, 
who researched a reference coding methodology (RUBAC - Rational Universal Business Co-Ordination 
Code) for Electronic Information Interchange (EII).

They are working on a number of projects in the UK involving cross industry communication 
including Health, Education and Local Government.

They have received considerable support from the Australian Trade Commission (AUSTRADE) for 
a major EII project with the European Aerospace Association (AECMA).

The RUBAC Information communication methodology provides a number of facilities for EII 
not found with EDI including:

a. The reference code is automatically generated by passing through menus.

b. The reference code automatically updates different indices when an electronic document is 

c. Incoming messages are automatically matched with outgoing messages.

d. Individual item tracking with EDI purchase and support cycles.

RUBAC was researched to file all communications types - data, text, graphics, voice, image,
X-ray, radio-waves etc.  

In 1987 the Yankee Group noted in their report "EDI in Australia" dated September 1987 that 
RUBAC was "Way beyond EDI".

The code encompasses all standards including ANSI-X12, EDIFACT, X-500, the CCC Harmonised System
(for article numbering) and MPEG by holding the standard tables and translation tables in memory.

It enables you to retain your existing product codes and internal referencing systems by holding
translation tables developed after surveys by their experts.

The concept is very different to current EDI operations but it will provide a solution to the
problems you have identified.

If you want further information I suggest you fax 44-753-68-6025, 61-75-317-081, 61-49-988-247 
or 61-2-499-6398.

As Stephen Gould, the Projects Co-ordinator, is in England for the next 3 months implementing
SO 9001/2 in a small business the 44-753-68-6025 is likely to produce the best response.

We are considering becoming members of the Halisa-UK Consultant Co-operative Bulletin Board
network to collaborate on a number of projects so may be able to provide further information 
in due course.

Hope it helps.

Dave Morgan
University of Salford

Revised: S: 12:29 Sat 16/06/2001 Syd 2089
F: 12:34 Sat 16/06/2001 Syd 2089
Who: sgg
Authorised: sgg
Created: S: 12:29 Sat 16/06/2001 Syd 2089
By: sgg
Revision: CPKCHIN1.03
Original Page: cpkCHIN1
Change date: