Transcript No Slide Title

Welcome to our EDI Overview
G.T.R. Data Inc.
EDI Demonstration
•
This demonstration will take you on a guided tour of our
software. After you have reviewed a slide click on the left
mouse button or hit enter to advance to the next slide. To
re-display a viewed slide use the backspace key.
•
Each slide will contain a screen image with a description of
the fields on the screen.
G.T.R. Data Inc.
Main Menu
This is the EDI Maintenance menu. All
housekeeping functions relating to partners and
their relationships are done here.
G.T.R. Data Inc.
File Locations - 1
G.T.R. Data Inc.
The file location will
define the directory
structure, file formats,
and communication script
for the file location. A
partner will be assigned a
file location to be used
when generating or
receiving data. We can
start a communication
script automatically upon
data generation by
entering a script name.
File Locations - 2
The communications script
variables will be defined on this
screen. They will be placed into
the script template when the script
is generated after leaving this
screen.
G.T.R. Data Inc.
Users
This is where you define the EDI
users. This will be the user that is
coded onto the ISA header as the
sender.
G.T.R. Data Inc.
Control File
This is the control file. It contains information that the system will use when
creating or integrating EDI data. It is keyed on the entity. The file location
tells the system where the location of the input, output and backup
directories and also defines the default communications script to use. The
delimiters are hex representations of the characters used between elements,
sub-elements and segments.
G.T.R. Data Inc.
Partner Profile
The Profile can be used to perform all
partner related maintenance. Upon
selecting a partner in the top browser you
may edit the partner or the file location
by clicking on the appropriate buttons.
Once a partner is chosen the bottom
browser will display the transaction sets
that the partner is trading. You may edit
the transaction set variables, the
partner/transaction variables, the partner,
and/or the transaction map.
G.T.R. Data Inc.
Partner – General Information
This screen allows the user to
enter Partners. Note the tab
folders at the top of the screen.
These are the options that the
user can select. We have selected
the General Option first.
G.T.R. Data Inc.
Partner – ISA Information
This screen defines the ISA
or outer envelope. The
Partners EDI ID is the send
address of the partner. The
qualifiers tell us what the ID
is. In our example ZZ means
mutually defined between the
partners.
The user ID is the sender on
the ISA envelope. The
security for send and receive
is also defined on this screen
with their qualifiers. The
test/prod switch allows for a
test environment between
you and your partner.
G.T.R. Data Inc.
Partner – GS Information
The information on this screen will
be encoded onto the GS or
functional group segment. The GS
is the inner envelope of an EDI
transmission. This envelope
surrounds the documents such as
the PO or INV.
G.T.R. Data Inc.
Partner – Send/Receive
•The send and receive quantity
method defines how the
translator deals with quantities
and UOM’s and up to 6 date
formats can be defined.
•The delimiters can be different
than the default.
•The reference year can be
defined as well as the
acknowledgment status.
•The program directories define
where the translator puts its
scripts.
•The file location defines the
communication script and data
locations.
G.T.R. Data Inc.
Partner - Parameters
Parameters are partner/document
specific switches and values that
are used to control the behavior
of the translator. For example the
third logical switch above will tell
the translator to check the gross
prices against the price on the
incoming order.
G.T.R. Data Inc.
Partner - Settings
The general option defines
the version number for the
partner, the entity code to
use on incoming
transactions, and whether
we will trade the document
with the partner (send or
receive). Also, the send and
receive switches are set.
The group and transaction
set numbers may be
controlled by partner. These
numbers are used for
controlling functional
acknowledgements.
G.T.R. Data Inc.
Customer Partner Xref
This program allows you to set up relationships between
Customers and Partners. Multiple customers can be
linked to a single partner where the customer has
multiple ship-to’s, but only one EDI partner relationship.
You may also set up relationships where the partner is
using multiple interchange addresses for different
documents.
G.T.R. Data Inc.
Vendor Partner Xref
This function has the same
purpose as the previous
except it allows for the
establishing of Vendor Partner
relationships.
G.T.R. Data Inc.
Keywords
Keywords allow us to pre-define a specific word that will
represent a file.fieldname in the database. This allows us to
use the field in a formula for outgoing and incoming
transactions. You will see how these are used in Segment
Maintenance where we tell the system the relationship
between an element and a database field.
G.T.R. Data Inc.
Functions
This function will return the discount date. The value can then be mapped to an element using the
segment maintenance.
The literals surrounded by the “|” are keywords. INVDATE is the keyword representing invoiceline.volume-disc and INVLNDPC represents invoice-line.dollar-pct. The if-then-else statement is
Progress like and illustrates the powerful capabilities of the formula.
G.T.R. Data Inc.
Translation Tables
A translation table allows you to change inbound or
outbound data from the table from to the table to.
For example when receiving data from our partner his
customer number 10 could be translated to our
customer 2023627370050 as illustrated above.
G.T.R. Data Inc.
Mapping
We have now completed the first part of the demonstration. We are
now ready to discuss how to set up EDI elements and segments, that
is, mapping.
Mapping is used to create the relationship between our database and
the EDI data. For example, if our partner sends us a purchase order
number mapping would tell the system where to store the purchase
order number in the database. At the same time we could tell the
map to manipulate the purchase order number by removing or
adding letters, for example. This manipulation of data can be done
using a formula or using a data translation table. A formula would be
used when the data you are manipulating is dynamic. A data
translation table would be used when the data is static. A purchase
order number would be considered dynamic because it is always
different, therefore if it must be manipulated then you would use a
formula. A customer number would be static because they are finite,
therefore if the number must be manipulated then you would use a
translation table. However, if there is a one to one relationship
between your partners representation of the customer number and
your internal number you may use a formula to manipulate the
number so that it matches yours. For example, if your partner sends
you 1000 and your internal customer number is A01000, then you
could use a formula to concatenate A0 to the front of the 1000.
G.T.R. Data Inc.
Mapping - 1
This is the mapping screen. Having chosen a partner and transaction set via the partner
profile the system displays the list of segments and elements within the segments. Our job
will be to map the database fields into the proper elements. The top level folders represent
segments and the lower level folders represent the elements. Field relationships are displayed
at the third level, underneath the element.
G.T.R. Data Inc.
Mapping - 2
This element represents the Purchase Order number. When this data is
received (incoming) it will be mapped to gtredi.tt-pedvenda.nr-pedcli.
The formula will limit the size of the po number to a length of 10.
G.T.R. Data Inc.
Transaction Processing
Invoices and purchase orders are posted using their respective programs
within your application (Frameworx, MXP, Syteline, Intrix, Darwin). If the
Vendor or Customer is designated as an EDI partner then a document
trigger is created when the document is finalized. The user then runs the
EDI generation program to create the EDI data. Once created the EDI data
can be transferred to the Value Added Network.
On the receive side, when data is received from the Value Added Network it
is integrated into the application using the receive EDI data function..
The next few screens illustrate these functions.
G.T.R. Data Inc.
Transaction Menu
This is the EDI Transaction Processing Menu. The
user can review the documents in the send
queue, EDI data can be generated and/or sent,
and data can be received. Functional
Acknowledgments can also be reviewed and
regenerated for those that your partner didn’t
receive.
G.T.R. Data Inc.
Document Review
Document Review allows the user to display outbound documents and to
change selected fields such as the status. The status indicates if the document
was sent and can be changed to resend the document. Documents are
reviewed by type; invoices, p/o’s etc.
G.T.R. Data Inc.
Acknowledgment Review
This function allows the user to review the
status of the functional acknowledgements
and optionally reset the send status to
resend. It will track all instances of a
document that was sent multiple times.
G.T.R. Data Inc.
Edit Data on Hold
When receiving EDI data, unprocessed transactions are stored in the database
as EDI data on hold. This function allows you to edit this data in its native
ascii format before re-processing.
G.T.R. Data Inc.
System Management
The System Management Menu
contains document purges, the
restore from backup function and
other miscellaneous housekeeping
functions.
G.T.R. Data Inc.
File Manager
The Data File Manager allows you to
restore input, output, or backup files
from the backup directories. This is used
if you must resend a file, for example.
G.T.R. Data Inc.
Thank you for viewing this overview.
Contact us for more information
about this module. Contact info is
available on the last slide.
Ask us about currently supported
documents and our plans for future
documents.
G.T.R. Data Inc.
How to reach us
Phone 514-738-6680
Fax 514-738-8538
Web
http://www.gtrdata.com
E-mail
[email protected]
G.T.R. Data Inc.