EDI or DIE Stuart Richler President G.T.R. Data Inc

Your Success is Our SuccessYour Success is Our Success

EDI or DIEEDI or DIEStuart RichlerStuart Richler

PresidentPresidentG.T.R. Data Inc.G.T.R. Data Inc.


G.T.R. Data Inc.G.T.R. Data Inc.

• Foresight affiliate & solution partner since 1984

• Developed

• Canadian Payroll 1984

• US Payroll 1992

• Human Resources 1993

• EDI Module 1993


AgendaAgenda

• Discussion about existing features

• Introduce new enhancements

• Discussion about 856, UCC-128 etc.

• EDIFACT

• Supported Documents


EDI Features - GeneralEDI Features - General

• Supports all ANSI X.12, VICS, AIAG standards.

• Does not require the use of a third-party translator.

• Multi-company and Multi-division support.


EDI Features - PartnersEDI Features - Partners

• Unlimited number of partners.

• Trading partners can be used by all companies and divisions.

• Multiple partners can use the same interchange envelope partner.

• Generating and receiving options of EDI data is maintained by trading partner, as well as information specific to a particular transaction set.


EDI Features - MappingEDI Features - Mapping

• Support for all versions of the ANSI X.12 standard is provided. Default transaction set mappings for all versions supported are also provided..

• Segment mapping can be done for all trading partners, or for a specific trading partner.

• You can define which database fields are to be used when generating EDI transaction sets, and can specify the field to use when assigning elements from incoming transaction sets.


EDI Features - MappingEDI Features - Mapping• An open-ended translation facility exists to convert data

from incoming or outgoing transaction sets. This allows you to specify the “correct” EDI abbreviation for things such as unit of measure and currency coded. When processing incoming data, the translation feature allows you to determine the correct item number and/or customer number from the transaction set information provided.


EDI Features - MappingEDI Features - Mapping

• Formulas are used to specify the values to be placed in generated transaction sets. The formula can be up to 240 characters, can refer to database files, fields, constants, other formulas, and PROGRESS functions such as IF THEN ELSE, MINIMUM and MAXIMUM.

• Utilities are provided to copy system transaction set mappings to trading partners, and to copy a trading partners transaction set mappings to other trading partners..


EDI Features - SendEDI Features - Send

• Allows you to specify whether or not a particular document type (i.e. purchase orders, invoices, etc.), is to be sent via EDI by customer and/or vendor.

• Documents to be sent via EDI are not printed on standard form when a document is printed. They can be printed on stock-tab if a paper copy is required.

• You can specify which version of the ANSI X.12 standard to use for a particular trading partner and document type.


EDI Features - SendEDI Features - Send

• Details of when the EDI documents was generated, along with the user and terminal that generated the data is kept on file.

• A batch number is assigned to EDI documents when they are generated. This allows you to easily re-send a large number of documents in the event of a system crash or communications failure.

• Generated transaction sets are automatically backed up on disk, once they are processed..


EDI Features - ReceiveEDI Features - Receive

• An incoming purchase order can be converted into either a quotation or sales order.

• You can define which database field a particular data element goes into.

• Incoming data elements can be “translated” before being assigned to a database field.


EDI Features - ReceiveEDI Features - Receive

• A “simulation” mode is provided when processing incoming EDI documents. This allows you to verify incoming transaction sets before actually creating documents in the system.

• Incoming transaction sets are automatically backed up on disk, as a safety precaution, once they are processed.

• Formulas may be applied to incoming elements.


EDI Features - Acknowledgments


• Outgoing acknowledgments are generated immediately when incoming transaction sets are processed.

• Allows you to specify whether or not acknowledgments are to be sent for a particular trading partner.

• Outgoing Acknowledgments can be reviewed at any time

• The ability to regenerate outgoing acknowledgments is provided. Details of when the acknowledgments was generated, along with the user and terminal that generated the acknowledgment are kept on file.




• A batch number is assigned to outgoing EDI acknowledgments when they are generated. This allows you to easily re-send a large number of acknowledgments in the event of a system crash or communications failure.

• Incoming acknowledgments will update the EDI document record automatically to indicate that the trading partner has acknowledged your outgoing documents.


New EnhancementsNew Enhancements

• The ability to define separate input/output directories by partner.

• Definition of a communication script to be executed after the generation process.

• Create “reversing” translation tables automatically.


New EnhancementsNew Enhancements

• EDI message review has been enhanced.

• UNIX script for wrapping unwrapped data.

• Progress 8 compatibility.

• Specify document types on generation of EDI data.

• Acknowledge multiple documents within one FA as well as acknowledge by functional group.


ASN’sThe Document from Hell

ASN’sThe Document from Hell

• There are many different shipping documents required by partners:

• Pick/Pack-different items/carton• by pallet (tare)/carton (pack) /item

• Standard Pack-same item/carton • by item/pallet (tare)/carton (pack)


FA ExampleFA Example

ST

AK1

AK2

AK5

AK9

SE

ST

.........

ST

AK1

AK2

AK5

AK2

AK5

AK9

SE

ST

AK1

AK9

SE

Separate sets Multiple docs Single Groupper document per Set


ASN’sASN’s

• We have designed a shipping module that allows for box/carton/pallet assignments plus UCC-128 label printing.





EDIFACTEDIFACT

• EDIFACT is the standard in the rest of the World.

• We will provide a direct translation to EDIFACT.

• Release 2nd qtr 1998.


Future EnhancementsFuture Enhancements

• Better rip ‘n read with print templates for loaded data.

• Acknowledge when inputting to holder file.

• Better handling of holder file.

• Improvement to segment override and segment list.


Currently SupportingSEND

Currently SupportingSEND

• 810 - Invoices

• 820 - Remittances (beta)

• 850 - Purchase Order

• 855 - Purchase Order Acknowledgment

• 856 - Advance Shipping Notice

• 860 - Purchase Order Change

• 997 - Functional Acknowledgment


Currently SupportingReceive

Currently SupportingReceive

• 810 Invoices

• Received as A/P Vouchers

• 850 Purchase Orders

• Receive as Orders or Quotations

• 820 Remittances (beta)

• 830 Sales Forecasts

• 864 Text

• 997 Acknowledgments


G.T.R. Data Inc.How to reach us

G.T.R. Data Inc.How to reach us

• Phone 514-738-6680

• Fax 514-738-8538

• [email protected]

• http://www.gtrdata.com


Thank You for Attending.

Thank You for Attending.

Your feedback is important to us! Your feedback is important to us! Please complete and hand in your Please complete and hand in your

evaluation form at the end of this session.evaluation form at the end of this session.