Documente Academic
Documente Profesional
Documente Cultură
1. INTRODUCTION
2.WHAT IS EDI?
3.WHY USE EDI?
4.ADVANTAGES OF EDI OVER
DOCUMENT TRANSFER SYSTEM
5. HOW EDI WORKS?
6.EDI COMPONENTS
7.FILE TYPES.
8.EDI SERVICES.
9.CONCLUSION.
PAPER-BASED
INTRODUCTION
Everybody uses business connections of one sort or another to
get orders, send bills, make collections, determine and pay what it
owes, move goods, and control its money. The business connections
used historically to perform these operations have been the postal
service and the telephone. A relatively new link is electronic data
communications facilities.
Your links to business connections are limited to the mail and
the telephone. Both are slow. Both terminate with that wall of people
who feed the computer and who may make errors.
What your company needs is a better link to business
connections and that is what electronic data interchange is all about.
To appreciate what electronic data interchange (EDI) means, think
about all those orders, invoices, freight bills, shipment instructions,
tracing requests, payment instructions, government reports, and the
like that your company sends out or receives every day. Think about
each as a single transaction.
WHAT IS EDI?
Traditionally, the transfer of data from one company to another
has been by paper documents. This is known as a paper-based system.
These documents have to be manually forwarded and entered to the
destination computer.
EDI is the electronic exchange of structured business
information, in standard formats, between computers, EDI eliminates
the need for a paper-based system by providing an electronic link
between companies. This reduces data entry tasks and improves
business cycle times.
In an EDI System:
The application program generates a file, which
contains the processed document.
The document is converted to an agreed standard
format.
The file containing the document is sent electronically
over the network. This network links the originating
company and its trading partner.
EDI COMPONENTS
A typical EDI system implements a specific set of EDI by
enabling the exchange of business documents. It accepts documents
from business software applications, converts the document to a
standard format and sends it to another software application or trading
partner.
EDI system converts generic EDI messages (in EDIFACT or
any other EDI standard) format to RDBMS format and from RDBMS
format to EDI format. There are EDI application programs for
software developers to configure EDI to work with the various user
application software programs. There is normally no end-user
interaction with EDI--it is entirely within the background of the EDI
system.
RDBMS database contains the data to be translated into EDI
format and where EDI data is to be converted (and written) to . EDI
treats the application database generically--it reads and writes to the
tables and fields specified according to the message mapping created
by the |EDI Administrator during EDI message configuration. These
are done by EDI Configuration programs under the purview of EDI .
Documents
Business
Application
Internal format
Transmission
Tranmission
files
files
files
Application
Tranmission
Communication
Service
Service
Services
TRADING
PARTNER
FILE TYPES
EDI creates the following files as a document passes through the system:
Internal Format File (IFF)
External Format File (EFF)
Transmission File
Each of these files is described in the following sections.
Internal Format File:
An internal format file (IFF) contains a single document for a
single trading partner. Internal format file is principally for EDI's own
use.
Transmission File:
A transmission file contains one or more documents for the
same trading partner. Documents of the same type are packaged
together in functional groups. The functional groups going to one
trading partner are packaged into an interchange set. An interchange
set contains one or more functional groups of documents with the
same sender and receiver.
TRADING PARTNER A
Document Type 1
1
Interchange
Set
Functional
Group
1
Document Type 2
2
2
Functonal
Group
TRANSMISSION FILE
EDI SERVICES
The three EDI services all perform different tasks. The
following sections give an overview of what happens in each of three
services.
Application Service:
The Application Service provides the link between a business
application and EDI. It allows you to send document to, and receive
documents from, an EDI system.
A set of callable routines is used to transfer documents from the
business application into EDI. Documents destinations can be either
intra-company or to external companies, i.e., trading partners.
The EDI Application Service holds each incoming and outgoing
document as a single internal format file. EDI converts the document
to a standard format and sends it to the trading partner using the
relevant communication protocol. A number of different standards and
communication protocols are available.
The following list describe what happens in the Application Service:
For outgoing documents:
The business application uses the callable routines to send a
document from the business application to the Application
Service. The document is now in the EDI system and is
called internal format file.
File server
Internal
Formal File
Callable
Routines
Internal
Format File
Translation Service:
Converts outgoing documents from an internal format file to
an agreed external format.
Translates incoming documents from an external format to
the EDI internal format file.
The external document standards that an EDI system supports
are EDIFACT, X12, TDCC, and ODETTE
FILE SERVER
INTERNAL FORMAT
FILE
DOCUMENTS
BUSINESS
APPLICATIONS
DOCUMENTS
CALLABLE
ROUTINES
MANAGEMENT INTERFACE
INTERNAL
FORMAT FILE
APPLICATION SERVICE
Translation Service:
Converts outgoing documents from an internal format
file to an agreed external format.
Translates incoming documents from an external
format to the EDI internal format file.
MANAGEMENT INTERFACE
INTERNAL
FORMAT FILE
INTERNAL
FORMAT FILE
TRANSMISSION
FILE SERVER
C
TFB
TFS
FILE
TRANSMISSION
FILE
C
= CONVERTER.
T =TRANSLATOR.
TFB =TRANSMISSION FILE BUILDER.
TFS =TRANSMISSION FILE SPLITTER.
CONCLUSION: