EDI Manager User Guide - Squarespaceamiauto.squarespace.com/s/EDI-Manager-User-Guide.pdf · Symbols...

AMI AutoAGENT EDI Manager

E D I M A N A G E R i

Contents

Introduction .............................................................................................................................................................. 2 Understanding EDI .......................................................................................................................................... 3 Transaction Sets ................................................................................................................................................. 4 EDI Transmission .............................................................................................................................................. 5 Understanding the key Components of EDI Manager ................................................................................ 6 What's In This Manual ..................................................................................................................................... 8 Symbols and Conventions ............................................................................................................................... 9 EDI Manager Navigation Tips ...................................................................................................................... 10

Part 1: EDI Manager Setup ......................................................................................................................... 13

Chapter 1: Parameters ..................................................................................................................................... 15 Entering EDI Parameters .............................................................................................................................. 18 Entering EDI Communications .................................................................................................................... 20 Entering EDI Automated Communications Process ................................................................................. 20

Chapter 2: Application File ............................................................................................................................. 21 Entering Transaction Set Definition ............................................................................................................ 21

Part 2: Trading Partner .................................................................................................................................. 25

Chapter 3: General Trading Partner Profile ............................................................................................. 27 Entering Trading Partner Profile .................................................................................................................. 28

Chapter 4: Inbound Mapping ....................................................................................................................... 33 Entering Trading Partner Inbound Mapping Information ....................................................................... 33

Chapter 5: Outbound Mapping ................................................................................................................... 37 Entering Trading Partner Outbound Mapping Information ................................................................... 37

Chapter 6: Contact Information ................................................................................................................... 43 Entering Trading Partner Contact Information .......................................................................................... 43

Chapter 7: Special Fields ................................................................................................................................. 45 Entering Special Fields ................................................................................................................................... 45

Part 3: EDI Processing ..................................................................................................................................... 49

Chapter 8: Inbound Processing .................................................................................................................... 49 Processing Incoming Raw EDI Data ............................................................................................................ 49

i i E D I M A N A G E R

Chapter 9: Outbound Processing ................................................................................................................. 55 Processing Outbound EDI Data .................................................................................................................... 55

Part 4: Dictionary Maintenance .............................................................................................................. 60

Chapter 10: Transaction Sets ........................................................................................................................ 61 Entering Transaction Set Dictionary Maintenance .................................................................................... 61

Chapter 11: Segments ...................................................................................................................................... 64 Entering Transaction Segment Maintenance .............................................................................................. 64

Chapter 12: Elements ....................................................................................................................................... 65 Entering Element Maintenance ..................................................................................................................... 65

Chapter 13: Sub Elements .............................................................................................................................. 66 Entering Sub Elements ................................................................................................................................... 66

Chapter 14: Tools ............................................................................................................................................... 67 Entering Dictionary Tools .............................................................................................................................. 67

Copy Version ........................................................................................................................................... 68 Copy Transaction Set .............................................................................................................................. 69 Delete Version ......................................................................................................................................... 70 Delete Transaction Set ............................................................................................................................ 70

Part 5: (ASN) Advanced Shipping Notice Maintenance .......................................................... 73

Chapter 15: ASN Maintenance ..................................................................................................................... 73 Entering an ASN (Advanced Shipping Notice ........................................................................................... 73 Entering Ship To Maintenance ...................................................................................................................... 78 Entering Serial Maintenance ......................................................................................................................... 80

Part 6: Document Manager ....................................................................................................................... 83

Chapter 16: Purge ED ........................................................................................................................................ 84 Purging Document Manager ......................................................................................................................... 84

Chapter 17: Reports .......................................................................................................................................... 85 Daimler Chrysler 810 Invoice ........................................................................................................................ 86 Daimler Chrysler 820 Payment Order/Remittance Advice ..................................................................... 87 Daimler Chrysler 824 Application Advice .................................................................................................. 88 Daimler Chrysler 830 Material Release ........................................................................................................ 89 Daimler Chrysler 850 Purchase Order ......................................................................................................... 90 Daimler Chrysler 853 Routing and Carrier Instructions ........................................................................... 91

E D I M A N A G E R i i i

Daimler Chrysler 861 Receiving Advice ...................................................................................................... 92 Daimler Chrysler 862 Shipping Schedule .................................................................................................... 93 Daimler Chrysler 864 Text Message ............................................................................................................. 94 Daimler Chrysler 997 Functional acknowledgement ................................................................................ 95 Ford 824 Application Advice ........................................................................................................................ 96 Ford 830 Material Release .............................................................................................................................. 97 Ford 861 Receiving Advice ............................................................................................................................ 98 Ford 862 Shipping schedule .......................................................................................................................... 99

Glossary .................................................................................................................................................................. 100 Glossary of EDI and EDI–Related Terms .................................................................................................. 100

sdfsdf

INTRODUCTIO

N

2 E D I M A N A G E R

Introduction Welcome to EDI Manager an important component in AMI AutoAGENT. The EDI Manager can also be used as a stand-alone module for those organizations not needing a complete enterprise solution.

Electronic Data Interchange, or EDI, is the electronic exchange of information, in a specific electronic format. It is intended to replace paper and improve accuracy and timeliness of business document flow and has become the standard for most electronic commerce; however, integrating EDI into your business process can be a time consuming and difficult proposition requiring a clear understanding of EDI technologies.

AMI AutoAGENT’s EDI module comes preconfigured with many of the most popular automotive transaction sets. You also have the ability to map your own trading partner transaction sets using AMI AutoAGENT’s EDI Manager mapping tools.

I N T R O D U C T I O N

E D I M A N A G E R 3

Understanding EDI Electronic Data Interchange (EDI) is essentially an electronic version of forms and business documents directly exchanged between two computers. EDI’s paperless environment speeds the communication of important business information between customers and suppliers.

Where a conventional paper trail of data is relatively slow, EDI is fast and efficient. EDI eliminates the need for re-keying of faxed or mailed information, and eliminates input errors.

Primary to the function of EDI is the application of formatting standards. These standards provide a common means of interpreting information exchanged between computers, regardless of the industry, country or application environments. EDI standards focus mainly on defining and managing the information being exchanged and on document routing.

EDI standards are constantly changing as updates are released from the various standards committees. AMI AutoAGENT’s EDI supports many versions of ANSI X.12 and EDIFACT EDI standards. These standards come packaged with your AMI AutoAGENT’s EDI software product. Subsequent releases are free to customers on an AMI AutoAGENT Maintenance Plan.

The primary function of the EDI Manager is to allow you to customize the role of EDI within your organization and across your supply chain.

Once you’ve setup the EDI Manager you can:

• Retrieve raw EDI data from trading partners. • Translate raw EDI data into EDI Manager standard format. • Translate AMI AutoAGENT outbound data to trading partner format. • Transmit outbound data to a trading partner.



Transaction Sets A transaction set is a collection of EDI segments that create a document, which can perform a standard business transaction. Each transaction set includes a header, detail and a summary.

The following describes some of the more common business transactions that the AMI AutoAGENT EDI Manager supports:

• 830 Material Releases: Defines shipping requirements and/or production forecasts for products where a customer purchase order already exists. Updates release accounting material releases.

• 862 Shipping Schedules: Defines shipping requirements and

sometimes production forecasts for products where a customer purchase order already exists. Updates release accounting JIT shipping schedules.

• 850 Purchase Orders: Sends an order to be filled and creates a

customer order. • 861 Receiving Advices: Acknowledges the details of received

goods or informs about discrepancies with received goods. • 824 Application Advices: Acknowledges the receipt of an ASN

(Advanced Ship Notice) or an invoice. The status of applicable ASNs is updated and the advices are displayed.

• 820 Remittance Advices: Describes payments issued to you.

Information can be displayed, and printed. • 864 Text Document: Conveys electronic messages, contracts,

explanations and other one–time communications. • 856 Advanced Shipping Notices (ASNs): Lists the contents of a

shipment of goods as well as additional information relating to the shipment, product description, physical characteristics, type of packaging, marking, carrier information and configuration of goods within the transportation equipment. The 856 is automatically created and imported from the Automated Shipping Manager module or manually entered via the EDI Manager Maintenance routine.



EDI Transmission When you send EDI transaction data to a trading partner, the data first goes to your EDI software where it is translated into an EDI standard format. The data then goes to your EDI software electronic mailbox and from there it is transmitted (via an EDI network) to the electronic mailbox of the trading partner that you have indicated.

Each trading partner has a distinctive address (usually Duns number) to which transaction data can be posted. The data is translated by your trading partner’s EDI software into an internal format and is then processed by your trading partner’s computer system.

Similarly, EDI data sent to you by your trading partners goes (via an EDI network) to your EDI software electronic mailbox and from there it is translated into AMI AutoAGENT EDI Manager System. The data is then processed like any other data on your system.



Understanding the key components of the EDI Manager To help you to better understand how the AMI AutoAGENT EDI Manager works we must first define the components within the EDI Manager. There are four major components that within the EDI Manager that are integral to the setup and successful implementation of the EDI Manager:

1. Dictionary 2. Application Files 3. Trading Partner Mapping 4. Processing (Translation Occurs)

Each component plays a vital role in setting up the EDI Manger to be able to process all incoming (EDI-formatted data received from your trading partner) and outgoing (data extracted from the AMI AutoAGENT application system for transmission via EDI) transactions.

Dictionary

Within the EDI Manager dictionary there are two main EDI standards, X.12 and EDIFACT. Each of these EDI Standards can have multiple versions. Here is where you define, for each EDI standard and version, the transaction sets’ segment, element, and sub element requirements. The dictionary will be used during the translation process to properly map each trading partner’s segment/element to the application fields within AMI AutoAGENT.

Application Files

The Application Files are XML database tables (files) used to store current data. Each type of transaction, such as 830 or 862, has it own Application File. All versions of a transaction, regardless of trading partner, are stored in the same Application File. All 830s go into one Application File, for example, while all the 862s go into another Application File.

The other AMI AutoAGENT modules look to these Application Files for data. AMI AutoAGENT Release Manager will retrieve new 830 Releases from the 830 Application File.

Setting up the Application File requires two steps: (1) creating the file, which includes naming the file and defining the fields (name, type and length) within the file and (2) using the Trading Partner Mapping Tools to define the connection between the actual EDI file being received or sent to trading partners, and the Application File.

Trading Partner Mapping



EDI standards were developed to support a large number of industries, including manufacturing, banking, transportation, real estate and education. Within each industry there are many transaction types such as Releases, Mortgage Credit Reports, Motor Carrier Shipment Status Inquiries and Student Transcripts. In order to meet the diverse needs, the EDI standards must be flexible and allow each business to interpret and implement the standards in a way that works best for them. While there are certain mandatory requirements that all trading partners must use (i.e. All transactions must have a header that identifies the type of transaction. All transactions have fields and separators between fields.), each trading partner generally has a lot of options when it comes to defining which elements of the Standard will be used, how they will be used and what they mean. In order to take advantage of this flexibility, the AMI AutoAGENT EDI Manager module uses a tool called the Trading Partner Mapping Tool. The Mapping Tool is used to provide the link between the actual EDI document and the AMI AutoAGENT Application File. This process is typically called “mapping” since it identifies, for each piece of data received, where it will go to. Each map is specific to a particular trading partner’s interpretation/needs. Many transactions come pre-mapped by AMI; however, having this tool allows you the flexibility to make changes yourself if needed. It also provides a cost-effective way for AMI to manage the changes and differences between trading partners.

Processing

Processing is where the translation of the EDI data occurs. Processing uses the mapping created with the Trading Partner Mapping Tool to translate the actual EDI data and store it as the Application File for viewing or further processing through AMI AutoAGENT modules.

This introduction is divided into the following sections:

• What’s in this manual? • Symbols and conventions • EDI Manager navigation tips



What’s in this manual? This manual is designed to give you an in-depth understanding of how to use the features of The EDI Manager and how it integrates with AMI AutoAGENT. Step-by-step instructions guide the user through each function.

The manual is divided into the following parts:

• Part 1, EDI Manager Setup, introduces EDI Manager and explains the setup process.

• Part 2, Trading Partner, explains how to define Trading Partner

profiles and map all transaction sets to AMI AutoAGENT Application Files.

• Part 3, EDI Processing, explains how to process all inbound and

outbound transactions within your supply chain.

• Part 4, Dictionary Maintenance, explains how to build the dictionary for each transaction set version.

• Part 5, ASN Maintenance, explains how to enter and process

stand-‐‑alone ASN (advanced shipping notices).

• Part 6, Document Manager, describes how to access & view EDI documents (reports) and perform data purge routines.



Symbols and conventions This manual uses the following symbols to highlight specific types of information.

Light Bulb - The light bulb symbol indicates helpful tips, shortcuts, and suggestions.

Warning Symbol - The warning symbol indicates situations you should be especially aware of when completing tasks. Typically, this includes cautions about performing steps in their proper order, or important reminders about how other information may be affected.

Drop-‐‑down button -‐‑ This button allows you to select a single option from a list by clicking the arrow button to the right of the field. See AMI AutoAGENT System Setup User Guide for more navigation and windows tips.

Lookup button -‐‑ The lookup button indicates that a lookup window—a list of items already entered in the system—is available for a particular field or window. You’ll select an item from the list to enter in the window. See AMI AutoAGENT System Setup User Guide for more navigation and windows tips.

This manual uses the following conventions to refer to sections, navigation and other information.

Building a Template Italicized type indicates the name of a section or procedure.

File >>Print The (>>) symbol indicates a sequence of actions, such as choosing items from a menu or a toolbar or choosing buttons in a window. This example directs you to pick File and then pick Print.

TAB or ENTER Small capital letters indicate a key or a key sequence.

Underlined characters / fields on screen

An underlined field title on the screen indicates the ability to click on it to link to the screen where the record can be updated


1 0 E D I M A N A G E R

EDI Manager Navigation Tips To help you to better navigate through the AMI AutoAGENT EDI Manager menus and screens, here are some tips.

If you are using AMI AutoAGENT you will be able to access the EDI Manager under a short cut on the navigation menu, labeled EDI, located on the navigation panel on the left of the screen. If you are using the EDI Manager as a standalone web-based solution you can access the EDI Manager from a URL on web browser. Across the top of every EDI Manager menu are the following options:

1. Home – Select this option to return to the EDI Manager home screen at any time.

2. Back – Select this option to immediately go back to the previous EDI Manager screen you last visited.

3. Contact Us – Enter any question or comment you wish to send to an AMI representative by filling out the following contact screen. Upon completion, select Send to have the message to the AMI help desk.

2. Subject – Select the subject that most closely matches your issue. 3. Company Name – Enter your company name.

4. E-Mail Address – Enter your email address so that an AMI representative

will be able to immediately make contact with you to help you to answer your questions.

5. Contact Name – Enter your contact name.

6. Telephone – Enter your telephone number.

7. Type Additional Comments – Type in your question or comments in this

box.

8. Send – Choose Send to send this message to an AMI representative.


E D I M A N A G E R 1 1

9. Clear – Choose Clear to clear all the fields on the screen.

PART 1: SETU

P


Part 1: EDI Manager Setup If your EDI Manager module has been pre-configured with your needed trading partner transaction sets, you should skip Part 1 and Part 2 of this manual. Unless you are familiar with EDI requirements, you should not modify the pre-configured settings. For those familiar with EDI who have chosen to configure their own EDI, Part 1 and Part 2 of this manual guide the user through the setup process.

• Chapter 1, “Parameters”, builds a template of required information for the EDI Manager.

• Chapter 2, “Application File”, describes how to set up and link

transaction sets to the EDI Manager application files so that inbound and outbound raw data can be translated.


Chapter 1: Parameters If your AMI AutoAGENT package came pre-configured with EDI requirements, you should skip to Part 3 of this manual. Chances are that this screen is already configured by AMI with most of the required information. If your AMI AutoAGENT package was not pre-configured, you need to complete the one-time parameter setup process before EDI can be received, stored and processed.

Parameter maintenance allows you to build a template of required information for the EDI Manager. Each field in parameter maintenance must be completely filled out for you to be able to successfully use the EDI Manager. To set up EDI Manager: 1. Open the EDI Parameter Setup window.

(EDI >> EDI System Setup>> Parameters)

P A R T 1 S E T U P


2. Server – Enter the name of the server that will be used to store and process your inbound and outbound EDI transactions. Typically, this refers to the name of the computer from your location that will be designated as the EDI Manager Server for the AMI AutoAGENT EDI Manager. All inbound and outbound communications with your trading partners will go through this server.

3. Database – Enter the name of the database that will store all inbound and

outbound EDI transactions. This database must already exist on the server identified in step 2. Typically, this refers to the name of the SQL server database located on your EDI Manager server.

4. Login – Enter the login User ID to be used to access the SQL database.

This ID must already exist on the server identified in step 2 and must have read and write access to the SQL database.

5. Password – Enter the password associated with the User ID from step 4. It

is recommended that you use strong passwords in order to protect your company’s computer investment and data integrity. Contact AMI’s support department if you need assistance in developing strong passwords.

6. Confirm Password – Re-enter the password to confirm it has been entered

correctly.

7. Test Connection – Choose the test connection to verify that your connection to the EDI server is successful. If the connection is complete, the message “Connected Successfully!” will be displayed. Otherwise the message “Connection Failed!” will be displayed. If this occurs, you must verify that the Server, Database, Login and Password are correct. Note: These fields are case sensitive.

8. AMI AutoAGENT Integration – Choose this box if you plan on

integrating the EDI Manager module into AMI AutoAGENT.

9. ASN Entry Validation – Choose this box if you are using the EDI Manager as a stand-alone module and will be entering ASN manually.

10. Contact Us Email – Enter your AMI contact’s email address. This is the

person that is assigned to your account for questions and requests for additional trading partner EDI requirements you may need.

11. AMI AutoAGENT – Choose AMI AutoAGENT if you are using AMI

AutoAGENT communications protocol. If this option is checked you will see a Communications on the EDI dropdown menu located on the left of the menu screen. This option will allow you to further define the AMI AutoAGENT communications protocol you will be using with the EDI Manager module. Use communications to initially setup EDI communication defaults, to receive all inbound EDI, to transmit all

C H A P T E R 1 P A R A M E T E R S


outbound EDI and to automate the processing of EDI communications with your trading partners.

12. 3rd Party – Choose this box if you are using 3rd party communications

protocol such as CLEO Communications. If you select this option, the “Communications” menu option located on the left of the EDI menu will disappear and you will not be able to use the AMI AutoAGENT communications setup routine.

13. Connection Type – Select or enter the connection type, such as ANX or

dial-up. If connection type is DIAL UP, a prompt for phone number will appear.

14. Network Type – Select or enter the network used for this trading partner. 15. EDI Notification Email Address – The EDI module will automatically

send an email message when new EDI has been received. Enter the email address where notification should be sent.

Note: If you are using a 3rd party communications protocol this field will be dimmed out.

14. Email Server – Enter the server name where notification should be sent

when EDI files have been received and are ready to process.

Note: If you are using a 3rd party communications protocol, this field will not apply so it will be dimmed out.

P A R T 1 S E T U P


EDI Communications Setup Use setup communications to initially set up EDI communication defaults, to receive all inbound EDI and send outbound EDI.

To set up EDI Communications: 1. Open EDI Communications Setup window. (EDI >> Communications >> Setup)

If Manual Comm. Cmnd is selected, the Connection Type and Network Type are not accessible. Following are examples of ANX: manual and Dial–Up: manual & automated. The following description covers all the fields.

1. Communications setup screen ANX -MANUAL COMMUNICAITON COMMAND NOT CHECKED

2. Communications setup screen ANX -MANUAL COMMUNICAITON COMMAND CHECKED

3. Communications setup screen

C H A P T E R 1 P A R A M E T E R S


DIALUP - MANUAL COMMUNICATIONS COMMAND NOT CHECKED

4. Communications setup screen DIALUP MANUAL COMMUNICATIONS COMMAND NOT CHECKED

2. Trading Partner – Select a trading partner to begin the communications setup process.

3. User Name / Password / Account – Enter the user name, password and the

account that your trading partner has assigned to your organization for EDI communication.

4. Server Address – Enter the server IP address provided by your trading

partner.

5. Port # – Enter the port number you wish to assign to this communications protocol.

6. Phone Number – For dial-up communications only, enter the phone number in the following format: 248-555-1234. This option is only available when the “Manual Communication Command” is not checked.

7. Manual Comm. Cmnd – To manually enter the communications command

scripts check this box and you will be able to enter the receive and send commands.

8. Save – Choose Save to when you are finished.


P A R T 1 S E T U P


Automating EDI Communications Process

To automate the processing of EDI communications with your trading partners you can configure the EDI Manager to automatically receive your EDI data at a specific date and time.

To set up an Automated EDI Communications Process: 1. Open Automate EDI Jobs window. (EDI >> Communications >> Automate)

2. Trading Partner – Select a specific trading partner to schedule an automated EDI processing routine for that specific trading partner.

3. Run/At – Select the frequency and the time of day (HH:MM) and start date

when you want to run this automated EDI communications process:

4. Save – Choose Save to save the record. 5. Clear – Choose Clear to clear all the fields on the screen.

Frequency Description Only Once A one time event, not to

be repeated. Daily Will run everyday at a

specific time indicated

Weekly Will run weekly on specific days and time indicated


Chapter 2: Application File The “Application Files” are XML database tables (files) used to store the current data. Each type of transaction, such as 830 or 862, has its own Application File. All versions of a transaction, regardless of the trading partner, are stored in the same Application File. All 830s go into one Application File, for example, while all the 862s go into another Application File.

The EDI Manager comes pre–configured for many of the most popular automotive A.12 and EDIFACT transaction sets. Although you will have the capacity to create your own Application File for any transaction set, chances are you will not have to do so because it is already there for you.

P A R T 1 S E T U P


To define an Application File: 1. Open the EDI – Inbound Field Maintenance window. (EDI >> EDI System Setup>> Application File)

2. Transaction Set – Select the transaction set from the drop down box to display all the pre-defined fields for this transaction set.

3. Segments / Column Names / Data Types – Here is where you build a table of all the possible fields that are required for each segment for a transaction set. Maintaining only one application file for each transaction set makes future additions much easier to maintain.

Remember that this table stores all transaction set versions together under one transaction set name. There is only one Application File for any given transaction set regardless of the version. You can add, change or delete segments, column names and data type definitions from this screen. Any new elements that may need to be added to a transaction sets segment should be appended to the end of the segment list. To accomplish this, scroll to the bottom of the screen and a blank segment field will appear. Enter the new segment/column name (element) and data type for this element.

4. Save – Choose Save to save the record.

5. Delete – Choose Delete to delete this transaction set from the Application

File.

6. Clear – Choose Clear to refresh the screen and clear any changes you have made but no longer wish to save.

PART 2: TR

ADING PA

RTNER


Part 2: Trading Partner Each trading partner that you will be transmitting inbound and outbound documents with must be defined in the following trading partner tables that follow.

Here you will build a template for each trading partner that uniquely defines specific information necessary to allow you to successfully send and receive EDI documents with this trading partner that meet the trading partner transaction set standards.

Trading Partner allows you to define for each trading partner how you will be creating, storing and transmitting EDI transaction sets. The EDI Manager comes pre-configured with many tier one and tier two trading partners. Any trading partner’s profiles that may be required above and beyond these can be easily created by AMI for your convenience.

• Chapter 3, “General Trading Partner Profile”, defines trading partner profile header information.

• Chapter 4, “Inbound Map”, maps all inbound raw EDI data for a

trading partners transaction set to Application Files.

• Chapter 5, “Outbound Map”, maps all outbound transaction set data to the AMI AutoAGENT Application Files.

• Chapter 6, “Contact Information”, stores all contact information for

a trading partner.

• Chapter 7, "ʺSpecial Fields"ʺ, stores all additional trading partner requirements to properly communicate inbound and outbound transaction sets.


Chapter 3: General Trading Partner Profile To be able to send outbound EDI transactions for a trading partner you must build a general table for each trading partner.

This information is used during the mapping & translation processes for outbound transactions including X.12 (810 Electronic Invoice) / (856 Advanced Shipping Notice) and EDIFACT (INVOICE Electronic Invoice) / (DESADV Advanced Shipping Notice).

General trading partner profile maintenance allows you to define for each trading partner how you will be creating, storing and transmitting EDI transaction sets. The EDI Manager comes pre-configured with many tier one and tier two trading partners profile maps. You can easily create any trading partner’s profile that may be required above and beyond these or by AMI for your convenience.

The EDI Manager contains complete data dictionaries for many of the ANSI X.12 and EDIFACT standards for the automotive industry. These are included in the initial purchase of the software. Future versions of all of the supported standards are included in the maintenance contract and are available to you through AMI’s web site. This means that the EDI Manager module contains all of the transactions that you will ever need, eliminating hidden costs that are inherent in other systems.

You will only need to perform maintenance on trading partner profiles that you are creating internally that are not already available to your organization when you purchased the EDI Manager module.

To set up a General Trading Partner Profile: 1. Open the EDI – Trading Partner window.

P A R T 2 T R A D I N G P A R T N E R


(EDI >> Trading Partner >> General)

2. Trading Partner ID – Select or enter a Trading Partner ID to uniquely identify this trading partner.

3. Name – Enter the name of the trading partner.

4. Address – Enter the Address, City, State, and Zip code of the trading partner.

5. Header Type – Enter the Interchange Control Header:

X.12 Standard (Value) EDIFACT Standard (Value)

ISA UNB

6. VAN/Network – Enter the code that represents the 3rd party Value Add Network provider that will be used for this trading partner.

7. Auth Qual – Enter the Code to identify the type of information in the

authorization information field. Valid codes include:

X.12 Standard (Value) EDIFACT Standard (Value) “00” zeros = No Authorization Not applicable to EDIFACT “03” = Application Routing Instructions

8. Auth Info – Enter the Information used for additional identification or authorization of the sender or the data in the interchange. The type of information is set by the authorization information qualifier.

X.12 Standard (Value) EDIFACT Standard (Value) Use 10 Spaces Not applicable to EDIFACT

C H A P T E R 3 G E N E R A L T R A D I N G P A R T N E R P R O F I L E


9. Sec Qual – Enter the code to identify the type of information in the Security Information field. Valid codes include:

X.12 Standard (Value) EDIFACT Standard (Value) “00” = No authorization info present

Not applicable to EDIFACT

“01” = Password

10. Sec Info – Enter the code identifying the security information about the sender or the data in the interchange. The type of information is set by the security qualifier.

X.12 Standard (Value) EDIFACT Standard (Value) “00” (zeros)=No authorization info present


11. Intchg Std Id – Enter the interchange standard identification code for this

trading partner.

X.12 Standard (Value) EDIFACT Standard (Value) Use “U” for U.S.A. Not applicable to EDIFACT

12. Intchg Version – Enter the interchange version for this trading partner

requires for outbound transaction set documents.

X.12 Standard (Value) EDIFACT Standard (Value) “00” (zeros)=No authorization info present


13. Status Ind – Enter the Status Indicator for this trading partner.

X.12 Standard (Value) EDIFACT Standard (Value) Use “P” for production data, except when sending CAP invoices in test mode.

Use “0” for Production

Use “T” for test data. Use “1” for Test

14. Mfg. Source – Enter the OEM’s code to uniquely identify a division associated with this trading partner.

X.12 Standard (Value) EDIFACT Standard (Value) Based on trading partner Based on trading partner

15. Ack Req – Enter the code to indicate whether or not an acknowledgement is

required for this trading partner.

X.12 Standard (Value) EDIFACT Standard (Value) “0” no acknowledgement required.


“1” acknowledgement required



16. Resp Agency Code – Enter the responsibility agency code to represent if multiple files are received for this trading partner.

X.12 Standard (Value) EDIFACT Standard (Value) Use “X” Use “UN”

17. Cat In Files – Enter the code to indicate whether or not multiple files

received per session need to be concatenated.

X.12 Standard (Value) EDIFACT Standard (Value) Mark “YES” if multiple files per session

Mark “YES” if multiple files per session

Mark “NO” if single file per session

Mark “NO” if single file per session

18. Out File Name – Enter the file name for outbound data for this trading

partner.

X.12 Standard (Value) EDIFACT Standard (Value) Based on trading partner Based on trading partner

Data Separators

19. Seg Term – Enter the control syntax required by ANSI. The trading partner

will provide the proper hexadecimal code.

X.12 Standard (Value) EDIFACT Standard (Value) Trading partner specific Trading partner specific

20. Elem Sep – Control syntax required by ANSI. The trading partner will

provide the proper hexadecimal code.


21. Sub Elem Sep – Enter the control syntax required by ANSI. The trading

partner will provide the proper hexadecimal code.


22. Intchg Ctl No (Length/Value) – Enter the interchange control number length and value for this trading partner.


23. No Of Inc Grps Len – Enter the number of interchange groups length for

this trading partner.

C H A P T E R 3 G E N E R A L T R A D I N G P A R T N E R P R O F I L E



24. Func Grp Ctl No (Length/Value) – Enter the functional group control

number, length and value for this trading partner.

X.12 Standard (Value) EDIFACT Standard (Value) Uniquely assigned by the sender Uniquely assigned by the sender

25. Intchg Date Mask – Enter the interchange date mask for this trading partner

(YYYYMMDD).

X.12 Standard (Value) EDIFACT Standard (Value) Uniquely assigned by the sender.

Uniquely assigned by the sender

Example: YYYYMMDD Example: YYYYMMDD

26. Tset Ctl No (Length/Value) – Enter the transaction set control number length and value for this trading partner.


27. (Our) Intchg Id Qual – Enter your supplier interchange ID qualifier code

for this trading partner.


28. (Their) Intchg Id Qual – Enter this trading partner interchange ID qualifier

code.


29. (Our) Intchg Id – Enter your supplier interchange ID for this trading partner.


30. (Their) Intchg Id – Enter this trading partner interchange ID code.


31. (Our) Appl Id – Enter your supplier application ID for this trading partner.




32. (Their) Appl Id – Enter this trading partner application ID.


33. Save – Choose Save to save the trading Partner general information. 34. Clear – Choose Clear to clear all the fields on the screen.


Chapter 4: Inbound Mapping Inbound mapping allows you to properly organize raw inbound EDI data so that it follows both the EDI standards version and the trading partner's standards. Inbound maps contain the rules of the transaction; these rules will be used during the translation process. Mapping also includes integration with the AMI AutoAGENT application. The EDI Manager permits intelligent mapping and data conversion. Setting up maps is accomplished with an easy to operate interface. There is no scripting or programming language involved. You can set up as many maps between as many application file layouts and EDI transactions (or vise versa) as necessary. You can also assign any map to any number of trading partners.

Inbound mapping is an easy to use mapping screen to link a transaction set’s raw segments and elements to the AMI AutoAGENT application files for that transaction set. Once a transaction set is mapped to the AMI AutoAGENT application file, the formal translation process for all incoming data for this transaction set can take place. The application file stores the translated data. You can also print an XML report from this data. If your EDI Manager module is integrated to AMI AutoAGENT, this data will feed the AMI AutoAGENT Release Manager and Ship Scheduler.

To set up Trading Partner Inbound Mapping Information: 1. Open the EDI – In Map window. (EDI >> Trading Partner >> Inbound Map)

2. Trading Partner / Tran Set ID / Version No – Select the trading partner ID, transaction set ID & version number for the inbound mapping file you want to create or change.



If you are creating a new inbound map consider the following:

1. You may want to copy an inbound map from a trading partner transaction set that most closely resembles the one you want to create and then make changes for only the differences.

2. The trading partner must first be defined in “General” trading partner maintenance.

3. The Version No must exist in the Dictionary. 4. Trading Partner Transaction Set - The fields on the left of the

screen reference all the segments and elements of a transaction set that you can map to the AMI AutoAGENT application files. The fields on the right of the screen reference the AMI AutoAGENT application file for this transaction set. To map an element highlight the elements from the transaction set (on the left) and then highlight the field from the application file (on the right). A prompt will appear for you to designate the element and qualifier of this field.

You will only have to enter an element position for element type of

“ID” If the element type is an ID (Identifier) this element may or may not be based on another element. If it is based on another element enter the element here. Otherwise leave the Element Position blank. The qualifier refers to what this segment/element may only represent

For Example: MI is the qualifier for Material Release Issuer

Chrysler Material Release 830 VR-002040

SEGMENT/ELEMENT: N101 – Organization Identifier

Qualifier Value Returned SF Ship From ST Ship To MI Material Release Issuer MA Ultimate Destination SU Release Supplier Service Parts

Dealer Direct BT Bill-To

The mapped field will appear below the element with an X to indicate that the element and field are mapped. Additionally, the mapped field from the application file (on right), will display a checkmark next to the field to indicate that it is mapped. Once mapped all outbound raw EDI data can be translated to AMI AutoAGENT application files.

The EDI Manager ships out-of-the-box with many pre-defined

automotive tier one and tier two transaction sets already mapped to AMI AutoAGENT Application Files. You will not be required to maintain changes (additions & subtractions) for any out-of-the-box mapped transaction sets. AMI will make these available to you via our technical support business portal.

C H A P T E R 5 O U T B O U N D M A P P I N G


AMI can easily accommodate any transaction set that you may need mapped into the AMI AutoAGENT application.


4. Clear – Choose Clear to refresh the screen and not save any currently

changed data on the screen.

5. Delete – Choose Delete to delete the selected (received or processed) records on the screen.

6. Copy – Choose Copy Map to copy an existing inbound map to another

map, the following screen (EDI – Copy Inbound Map) will appear to allow you to copy one trading partner transaction set to another. This is useful when there is a new version release of a transaction set for a trading partner. You will be able to easily copy the older version to the newer version and then make the necessary changes to the new version.

1. Trading Partner – Select the trading partner ID you wish to copy from and to.

2. Version No – Select the version number you wish to copy from

and to.

3. Transaction Set ID – Select the transaction set you wish to copy from to.

The trading partner must be defined in “General” Trading Partner Maintenance and the version must be defined in the “Dictionary” before you will be allowed to complete the copy.


Chapter 5: Outbound Mapping Within the AMI AutoAGENT system there are two methods for creating and sending outbound transactions. AMI AutoAGENT customers that are using the Automated Shipping Manager can set up an outbound map for each outbound transaction set for a trading partner. If you are using the EDI Manager as a stand-alone module, you can manually enter information for an outbound X.12 (856) or EDIFACT (DESADV) advanced shipping notice using the ASN Maintenance routine.

Outbound mapping is an easy to use mapping screen to link AMI AutoAGENT Application Files for that transaction set to an outbound transaction sets raw segments and elements. Once an outbound transaction set is mapped to the AMI AutoAGENT application file, the formal translation process for all outgoing data for this transaction set can take place. The Application Files store the translated data. You can print an XML report from this data.

If your EDI Manager module is integrated to AMI AutoAGENT, this data will feed the AMI AutoAGENT Release Manager and Ship Scheduler.

To set up Trading Partner Outbound Mapping Information: 1. Open the EDI – Out Map window. (EDI >> Trading Partner >> Outbound Map)



2. Trading Partner / Version No / Trans Set ID – Select the trading partner

ID, version number & transaction set ID for the outbound mapping file you want to change.

3. Group Version Id – Enter the X.12 version and release number.


4. Functional Id Code – Enter the functional Id Code for this trading partner

transaction set. Refer to the table below for a list:

X.12 Standard EDIFACT Standard

820 RA 824 AG 830 PS 838 TD 841 SP 846 IB 847 MX 850 PO 853 RI 856 SH 859 FB 860 PC 861 RC 862 SS 864 TX 866 SQ 870 RS 996 FT 997 FA

Not Applicable

5. Trading Partner Transaction Set – The fields on the left of the screen

reference all the segments and elements of an outbound transaction set from the EDI dictionary (displayed in exact header, detail, and summary order) that you can map to the AMI AutoAGENT application files.

The fields on the right of the screen reference the AMI AutoAGENT application file for this outbound transaction set. The fields in the center of the screen refer to AMI AutoAGENT Application File fields that are mapped to this outbound transaction sets elements. To map an element highlight the elements from the transaction set EDI dictionary list (on the left) and then highlight the field from the application file (on the right). A prompt will appear for you to designate the element and qualifier of this field.

You will only have to enter an element position for element type of “ID”



If the element type is an ID (Identifier) this element may or may not be based on another element. If it is based on another element enter the element here. Otherwise leave the Element Position blank. The qualifier refers what this segment/element may only represent

For Example: MI is the qualifier for Material Release Issuer

Chrysler Material Release 830 VR-002040

SEGMENT/ELEMENT: N101 – Organization Identifier

Qualifier Value Returned

SF Ship From ST Ship To MI Material Release

Issuer MA Ultimate

Destination SU Release Supplier

Service Parts Dealer Direct

BT Bill-To

The mapped field will appear below the element with an X to indicate that the element and field are mapped. Additionally, the mapped field from the Application File will display a checkmark next to the field to indicate that it is mapped. To Create a New Outbound Map for the first time, choose the “Header” area (in center column). Now select the segment you want to map by clicking the “Segment” from under the “Header” area, (in left column). You will notice the segment appears in the “Header” area in the center of the screen. Choose the “Element” (in center column) that you want to map (it changes color to signify that this is the element you are about to map). Then Choose the field from the Application File list (right column). This filed will automatically be displayed in the element box.

Continue this process for the remaining header fields to be mapped for this transaction set. Repeat this process for the detail and summary sections.

Once mapped all outbound raw EDI data can be translated to AMI AutoAGENT Application Files.

To Edit an Existing Outbound Map – Choose the element (in center column) that you want to map (it changes color to signify that this is the element you are about to map). Then click the field from the application file list (right column). This filed will automatically be displayed in the element box.



Continue this process for the remaining header fields to be mapped for this transaction set. Repeat this process for the detail and summary sections. The EDI Manager ships out-of-the-box with many pre-defined automotive tier one and tier two transaction sets already mapped to AMI AutoAGENT application files. You will not be required to maintain changes (additions & subtractions) for any out-of-the-box mapped transaction sets. AMI will make these available to you via our technical support business portal.


7. Clear – Press Clear to refresh the screen and not save any currently changed data on the screen.

8. Delete – Press Delete to delete the selected (received or processed) records on the screen.

9. Copy Map – Choose Copy Map to copy an existing outbound map to

another map and the following screen (EDI – Copy Outbound Map) will appear to allow you to copy one trading partner transaction set to another. This is useful when there is a new version release of a transaction set for a trading partner. You will be able to easily copy the older version to the newer version and then make the necessary changes to the new version.

1. Trading Partner – Select the trading partner ID you wish to copy from

and to.

2. Version No – Select the version number you wish to copy from and to.

3. Transaction Set ID – Select the transaction set you wish to copy from to.



The trading partner and version must exist in the EDI Manager dictionary before you will be able to copy to it.


Chapter 6: Contact Information To help you provide better service to your customers requires you to have prompt service. You can store contact information for trading partners you may need to contact to help resolve EDI related problems or just to ask general questions.

To enter or update Trading Partner Contact Information: 1. Open the EDI – Contact Information window. (EDI >> Trading Partner >> Contact Info)

2. Trading Partner – Select the trading partner to display contact info for and the contact name, phone number, and email address will be displayed on the screen.

CONTACT

3. Name – Enter the name of the trading partner contact.

4. Phone – Enter the phone number for this trading partner contact.

5. Extension – Enter the name of the trading partner contact.

6. Fax – Enter the name of the trading partner contact.

7. Cellular – Enter the name of the trading partner contact.

8. Email – Enter the name of the trading partner contact.

ALTERNATE CONTACT

9. Name – Enter the name of the alternate trading partner contact.



10. Phone – Enter the phone number for this alternate trading partner contact.

11. Extension – Enter the name of the alternate trading partner contact.

12. Fax – Enter the name of the alternate trading partner contact.

13. Cellular – Enter the name of the alternate trading partner contact.

14. Email – Enter the name of the alternate trading partner contact.


16. Clear – Choose Clear to refresh the screen.


Chapter 7: Special Fields The Special Fields maintenance screen is reserved for additional information that may be needed per trading partner’s requirements, to allow you to properly communicate inbound and outbound transaction sets. Each trading partner has their own additional fields that may need to be defined and this is where you can edit these fields.

Each trading partner special fields table is already configured out-of-the-box with any fields that are required for that trading partner.

To enter or update Special fields: 1. Open the EDI – Contact Information window. (EDI >> Trading Partner >> Special Fields)

2. Trading Partner – Select or enter the trading partner to display contact information: contact name, phone number, and email address will be displayed on the screen.

3. Edit – After you press the Edit button the following special field

maintenance screen will appear as follows:

Displayed on the screen will be 10 special fields that will default to the currently defined special fields for this trading partner.

The EDI Manager comes out of the box with 15 pre-defined special fields that you can select for each trading partner as follows:

1. AETC Code 2. AETC Number 3. Air-bill tracking number



4. ASN Deliver 5. Broker Carrier 6. Broker SCAC Code 7. Carrier Pro Number 8. Dealer Code 9. Dealer Direct 10. Dealer Order Number 11. Delivery Arrival Date 12. Delivery Arrival Time 13. Equipment Code 14. Mixed Master Serial Number 15. Service Plant

Press the down arrow next to each special field you wish to define for this trading partner and select the appropriate field from the drop down list.

Note: If you need other special fields that are not currently defined please contact your AMI EDI support representative.

4. Trailer Num – Enter a trailer number for this trading partner.

5. Clear – Press Clear to refresh the screen and not save any currently

changed data on the screen.

6. Delete – Press Delete to delete the selected (received or processed) records on the screen.


PART 3: PR

OCESSIN

G TR

ADING PA

RNTER


Part 3: EDI Processing Processing is the heart of the EDI Manager, and is where all inbound raw EDI data and outbound raw EDI data is properly mapped to a trading partner, transaction set and version. Once properly mapped, all inbound EDI is stored in a SQL Server database and can be reported in the XML reporting module.

• Chapter 8, “Inbound Processing”, processes Map all incoming EDI into AMI AutoAGENT standard format.

• Chapter 9, “Outbound Processing”, processes Map all outbound

EDI documents for transmission to trading partners.


Chapter 8: Inbound Processing Inbound processing provides a powerful mapping engine that can transform incoming flat file EDI data into a standard AMI AutoAGENT format to prepare it to be seamlessly integrated into AMI AutoAGENT. Inbound mapping delivers out-of-the-box, many of the most popular automotive trading partner specific, X.12 and EDIFACT transaction sets already defined for use within the EDI Manager. This engine can perform transaction mapping and data conditioning to easily accommodate all trading partners in the automotive industry. There are three stages or states of EDI transactions: Received, Imported, and Processed:

• Received transactions have been received from your trading partner.

• Imported transactions have been received and pulled into the EDI

Manager to be processed.

• Processed transactions have been translated into the AMI AutoAGENT flat-‐‑file format.

To process incoming raw EDI data (communications set to 3rd party): 1. Open the EDI – Inbound Processing window. (EDI >> Processing >> Inbound)

If you are using a 3rd party package to receive inbound EDI you will have the option to import this data here. If there are any files to import, they will be displayed with a number of file(s) received as above.

C H A P T E R 8 I N B O U N D P R O C E S S I N G


Once these files are imported from the 3rd party package, they will be considered received files and are ready to be processed.

If you select Received Files will be displayed on the screen as follows:

Received is selected EDI COMMUNICATION PARAMETER SET TO 3RD PARTY

Place a checkmark on the select box for each trading partner received transmission file that you want to process. Press the process button to begin processing.

P A R T 3 P R O C E S S I N G


To process incoming raw EDI data (set to AMI AutoAGENT communications3rd party): 1. Open the EDI – Inbound Processing window.

(EDI >> Processing >> Inbound)

If you are using AMI AutoAGENT communications to receive inbound EDI, here is where you will receive any inbound transactions. To manually receive, press the receive button. A dialog box will appear as follows:

Symbol Description ANX

Dial up

Connection not defined



To receive transactions from a trading partner press the ANX or Dial up symbol next to the desired trading partner and the receive process will start. Upon completion, these files will be considered received and ready to process. Received is selected EDI COMMUNICATION PARAMETER SET TO AutoAGENT

2. Received Files – By selecting Received, all inbound transactions that have

either been imported from a 3rd party package or received through AMI AutoAGENT EDI will appear. Here you will be able to view the status of received transactions and identify any errors that may have occurred during the receive process.

3. Process –The next step is to process these files. Processing the inbound

EDI data reformats it into an XML files. These files can be immediately viewed via the Document Manager as an EDI Report.

If your EDI Manager is integrated with AutoAGENT, (AMI AutoAGENT Integration parameter is checked), the processed EDI data will automatically be updated into AMI AutoAGENT tables and will be the data source to generate ship schedules.

Select Processed to view already processed EDI data by trading partner. Perhaps there is a question or discrepancy on what data was actually sent and processed and you need to view the actual raw data to help resolve this problem. Here you will be able to select processed files to view this data.

You also have the capability to reprocess data by selecting a processed file and pressing the process button.



These reprocessed files will be updated as current EDI reporting data and if you are integrated to AMI AutoAGENT will be updated and ready to process as the data source to generate ship schedules.

4. Errors – Each received transmission will be flagged with the number of

errors that occurred. To view the error details click on the number and an error.


Chapter 9: Outbound Processing Outbound Processing converts outgoing EDI Manager information into a flat file format for transfer to most major communication vendor products if necessary. The EDI Manager places the processing logic, EDI document specifications, and trading partner specifications in database tables that can be modified at the user level with a set of maintenance programs. This table-driven conversion system allows a common software solution to seamlessly support a wide range of trading partners and document types.

Outbound processing will allow you to process any outbound transactions that are queued up and ready to process. The most common outbound transaction set is the advanced shipping notice or (ASN). The automotive ASN is either is formatted to X.12 standards, which is often referred to as an (856), or in the EDIFACT standard format, which is referred to as a DESASN.

The source of the ASN is either from The AMI AutoAGENT Automated Shipping Manager module or it was manually entered using the ASN maintenance routine within the EDI Manager module. In either case, these outbound ASN transactions would automatically be processed as new outbound transactions.

New outbound transactions are either imported from AMI AutoAGENT (if your EDI Manager module is setup to be integrated with AMI AutoAGENT) or they are manually entered using ASN maintenance entry option located on the EDI main menu.

C H A P T E R 9 O U T B O U N D P R O C E S S I N G


To Process all Outbound EDI Data: 1. Open the EDI – Outbound Processing window. (EDI >> Processing >> Outbound)

2. New – Choose New to process new outbound transactions. Any new transactions will be displayed as follows:

3. Process – Place a checkmark next to the outbound transactions to process. 4. Ready To Process – Transactions that are labeled ‘Yes’ are ready to

process. To complete a transaction that is labeled No, highlight ‘No’ and a



dialog box will appear as follows to allow you to complete the outbound transactions required data input.

• Manually Entered Data – Enter any required information such as trailer (truck number), mixed master serial number, delivery arrival date, delivery arrival time, part number and purchase order number. The fields that need to be completed here are the special fields as defined under “Trading Partner, Special Fields”. Enter the information that is necessary to complete this advanced shipping notice.

The only required field is the “Trailer Number”. If this field is blank this ASN, advanced shipping notice, will not be considered ready to process. The label will continue to say “No”.

• Save – Choose Save to save entered fields. . Upon successful entry

of required data, the outbound transaction should be labeled ‘Yes’ ready to process.

5. ASN File Name Displayed – Outbound transactions that have been

successfully processed will have a valid ASN file name displayed. Once an outbound transaction is successfully processed it can be exported to the trading partner outbound folder and flagged as ready to transmit.

6. Select to Export – To export outbound transactions place checkmarks in the checkbox labeled select and press the export button. These transactions will be moved to process history and be flagged as ready to transmit.

7. Transmit – Click on the transmit symbol to transmit outbound transactions for the desired trading partner and the transmission will be initiated. The following transmission status screen will appear:

C H A P T E R 9 O U T B O U N D P R O C E S S I N G


PART 4: D

ICTIO

NARY M

AINTEN

ANCE


Part 4: Dictionary Maintenance Dictionary maintenance allows you to define the transaction set’s dictionary of segments, elements and values as defined in the standards manual for both X.12 and EDIFACT respectively. Within the EDI Manager dictionary there are two main EDI standards, X.12 and EDIFACT. Each of these EDI Standards can have multiple versions. Here is where you define for each EDI standard and version, the transaction sets segments, elements, and sub element requirements. The dictionary will be used during the translation process to properly map each trading partner’s segment/element to the application fields within AMI AutoAGENT.

Dictionary maintenance is a component of the EDI Manager for building EDI dictionary files. Dictionary files are used for all EDI Manager translations of X.12 and EDIFACT transaction sets. The nature of EDI transactions is very inconsistent. Each EDI transaction is completely different from every other one. In effect, every single EDI transaction type is almost its own unique data format. The EDI Manager makes use of EDI dictionary files to allow for flexibility and ease of use in combating the inconsistent nature of different EDI transactions.

• Chapter 10, “Transaction Set”, describes how to create or maintain a transaction set.

• Chapter 11, “Segments”, describes how to create or maintain segments for a dictionary version.

• Chapter 12, “Elements”, describes how to create or maintain elements.

• Chapter 13, “Sub Elements”, describes how to create or maintain sub elements.

• Chapter 14, “Tools”, describes how to use EDI tools for copying and deleting transaction sets.


Chapter 10: Transaction Sets For every version number, the X.12 standards define commonly used business transactions in a formal, structured manner called transaction sets. A transaction set header control segment, one or more data segments, and a transaction set trailer control segment.

The Transaction set dictionary maintenance allows you to edit any changes that may need to be made such as adding a segment ID or deleting a segment ID from a transaction set.

To perform Transaction Set Dictionary Maintenance: 1. Open the EDI – Dictionary Maintenance window. (EDI >> Dictionary Maintenance >> Trans Sets)

2. Version No – Select or enter the version number for this transaction set.

3. Trans Set ID – Enter the transaction set ID that represents this transaction set.

4. Trans Set Area – Enter the transaction set section / area code as follows:

Code Code

Description H Header D Detail S Summary

Each transaction set has a unique section defined for the header, detail and summary data.

5. Position – Enter the position of this segment to sequentially order the segments in their respective order as defined in the dictionary manual.

C H A P T E R 1 0 T R A N S A C T I O N S E T S


6. Segment ID – Select the segment’s ID that identifies this segment. Press

view to open up this segment’s detail including elements.

The data segment is a collection of related data elements. For example, data elements are separated by the data element separator and the end of a data segment is marked by the use of the segment terminator identified in the ISA Control Segment.

All segments used in ANSI X12 Transactions Sets are listed in the X12 Segment Dictionary providing details on:

• Segment Identifier – a 2 or 3 character code uniquely identifying the segment within the ANSI ASC X12 context.

Purpose – a brief description of what the segment is used for.

The first segment of a transaction set is always the ST segment and the last segment is always the SE segment. You can think of these as the front and back flap of a manila folder. The information contained between the two segments, or in the folder, represents the document being sent.

7. Required – Choose the required checkbox if this segment ID is mandatory for this version.

8. Maximum Use – Enter the maximum number of times this segment can

appear in this transaction set as defined in the dictionary manual.

9. Loop ID – Enter the loop ID that identifies the loop type.

10. Loop Repeat – Enter the number of times this loop can repeat.

P A R T 4 D I C T I O N A R Y M A I N T E N A N C E



C H A P T E R 1 0 T R A N S A C T I O N S E T S



Chapter 11: Segments For every version number the X.12 standards dictionary contains a list of available segments that can be utilized in inbound and outbound transaction sets. Each segment is composed of: a unique segment ID; one or more logically related simple data elements or composite data structures, or both each preceded by a data element separator; and a segment terminator.

To perform Segment Maintenance for a Dictionary Version: 1. Open the EDI – Segment Maintenance window. (EDI >> Dictionary Maintenance >> Segments)

2. Version Number – Enter or select the dictionary version number, for example, 002001.

3. Segment ID – Enter the segment identification code that uniquely

represents this segment. Also enter the description for this segment.

4. Number – Enter the next sequential number to represent the element order for this element.

5. Element ID – Enter or select the element ID and check the required

checkbox if this element is required for this dictionary version.

6. Required – Choose Required if the Segment ID is mandatory for this version.


C H A P T E R 1 1 S E G M E N T S



Chapter 12: Elements An element is the basic unit of information in the EDI standards containing a set of values that represent a singular fact. It may be single-character codes, literal descriptions, or numeric values. For every piece of information in a paper document, there is a data element in the electronic document or transaction set. For each data element, the dictionary specifies the name, description, type, minimum length and maximum length.

To perform Element Maintenance: 1. Open the EDI – Element Maintenance window. (EDI >> Dictionary Maintenance >> Elements)

2. Element ID – Enter or select the element ID that uniquely identifies the element as defined in the dictionary manual.

3. Element Name – Enter the element name for this element.

4. Element Type – Select the element type and minimum and maximum

length for this element as defined in the dictionary manual.

5. Element Code / Description – Enter the element code and element code description for as defined in the in the X.12 and EDIFACT standards manuals. Each data element has a number of possible code identifiers, as defined in the X.12 and EDIFACT standards manuals respectively.



Chapter 13: Sub Elements Sub-Elements are used for EDIFACT only and are a further breakdown of elements into specific sub element categories.

To perform Sub Element Maintenance: 1. Open the EDI – Sub Element Maintenance window. (EDI >> Dictionary Maintenance >> Sub Elements)

2. Component ID – Enter or select the component ID that uniquely identifies the sub element as defined in the dictionary manual.

3. Sub Element No / Sub Element ID – Select or enter the sub element

number, sub element Id for this component Id.

4. Sub Element Required – Select O if this sub element is optional; Select R if this sub element is required for this component Id.



C H A P T E R 1 4 T O O L S


Chapter 14: Tools Tools give you the capability to copy and delete transaction sets & dictionary versions.

To access Dictionary Tools: 1. Open the EDI – Dictionary Tools window. (EDI >> Dictionary Maintenance >> Tools)

Select one of the following options from the menu below: Copy Version Copy Transaction Set Delete Version Delete Transaction Set



Copy Version This is useful when you want to duplicate an entire version library including all transaction sets within that dictionary. This function will copy all transaction sets within the version and copy them under the new version number.

1. Version No – Select the version number to copy from.

2. To Version No – Enter the version number to copy to.

3. Process – Select Process to execute the copying.

4. Clear – Select Clear to clear all the fields.



Copy Transaction Set This is useful when you want to duplicate a specific transaction set within a dictionary version under another version number and transaction set name.

1. Version No / Trans Set Id – Enter the version number and transaction set ID to copy from.

2. To Version No. / To Trans Set Id – Enter the version number and

transaction set ID to copy to. 3. Process – Select Process to execute the copying.




Delete Version This utility is useful to delete an entire dictionary version and all transaction sets defined within this version.

1. Version No – Enter the version number to delete.

2. Process – Select Process to complete the deletion.




Delete Transaction Set Use Delete Transaction Set when you want to delete an existing transaction set within a specific dictionary version.

1. Version No – Select the version number to access a transaction set from.

2. Trans Set Id – Enter the transaction set ID to delete.

3. Process – Select Process to complete the deletion.


PART 5: (A

SN) ADVANCED SH

IPPING NOTIC

E MAINTEN

ANCE


Part 5: ASN Maintenance ASN (Advanced Ship Notice) Maintenance allows you to create an ASN as a stand-alone entry within the EDI Manager. This function is primarily for stand-alone users that have no integration capabilities to AMI AutoAGENT modules.

Chapter 15, “ASN Maintenance”, describes how to enter advanced ship notices and the supporting file maintenance routines for advanced ship notices.


Chapter 15: ASN Maintenance Many EDI trading partners require an ASN (Advance Shipping Notice) from their suppliers for each shipment sent to them. An ASN is usually sent just minutes after a shipment is in transit.

In general, an ASN duplicates the information in the bill of lading that accompanies the shipment. This advance information allows the trading partner to prepare receiving records that need only be confirmed for items and quantities to be posted when the shipment arrives. ASNs are automatically generated by the AMI AutoAGENT Dock Monitor system when the shipments are posted.

The ASN maintenance routine allows you to enter manual ASN information or to change an ASN that has automatically been created from a shipment generated from AMI AutoAGENT. The ASN is used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, and type of packaging, marking, carrier information and configuration of goods within the transportation equipment.

To manually enter an ASN (Advanced Shipping Notice): 1. Open the ASN – Maintenance window. (EDI >> ASN Maintenance)

2. Shipper Num – Select or enter the Shipper ID number (SID) for this ASN. You can create an ASN for a current shipment or historical shipping document. Selection options include “Current” for current open shippers

C H A P T E R 1 5 A S N M A I N T E N A N C E


that have not been completely processed and “History” for past shippers that have already been completely processed.

3. BOL Number – Enter the bill of lading number for this ASN. Typically

the bill of lading number is the same as the shipper number.

4. Date – Enter the date for this transaction in any of the following formats: mmddyy or mm/dd/yy Mmddyyyy or mm/dd/yyyy

5. Trading Partner Mfg Flag – Select or enter the trading partner

manufacturing flag code that will link this ASN to a specific trading partner.

Refer to the following table:

Trading Partner MFG Code DAIMLER / CHRYSLER

C

FORD F GENERAL MOTORS G HONDA H TOYOTA T FREIGHTLINER 1 NISSAN 2

6. Manufacturers Ship To – Select or enter the manufacturers Ship To plant

code to represent the “ship to” location to which parts will be delivered.

7. Supplier – Enter the customer supplier number for this ASN.

8. Ship Mode – Select or enter the ship mode or carrier code for the parts shipped on this ASN.

9. SCAC Code – Select or enter the SCAC code, the Standard Carrier

Alpha Codes, as maintained by the National Motor Freight Association. They are a 4 letter code used to identify the many shipping carriers, frequently used in EDI and other documents.

10. Payment Method – Enter the payment method desired for this shipment.

For example, PRE-PAID.

11. Premium Transportation – Choose the Premium Transportation box if this shipment is subject to premium charges for expediting or air freight, etc. Checking premium transportation will require a customer supplied authorization code to be entered to approve the premium transportation costs.

P A R T 5 A D V A N C E D S H I P P I N G N O T I C E ( A S N ) M A I N T E N A N C E


12. AETC Number – Enter the AETC number to represent customer authorization of any extra or premium shipments. An Authorization for Excess Transport Cost number (AETC) is required for each extra shipment.

13. AETC Code – Enter the AETC code as follows: S = for the supplier to pay for premium transportation costs. A = For the Automotive (Customer) to pay for premium

transportation costs.

14. Airbill – Enter the airbill number ; typically this is the same as the bill of lading number.

15. Pool Point Code – Enter the 4digit pool point code for this shipment. If the

shipment is consolidated or sent to a pool point, this code will be required to be entered.

16. Gross Weight / Container Weight – Enter the total gross weight, &

container weight for this shipment.

17. Customer Part Number/PO Number – Enter or select the customer part number & valid purchase order number that represents the item being shipped.

18. Primary Container – Enter the one digit primary container type, secondary

containers, & secondary container type code to identify secondary container.

19. Quantity – Enter the quantity shipped, cum shipped for this

item/customer/purchase order.

20. Engineering Change Level – Enter the engineering change level for this item.

21. Unit Price / Unit of Measure – Enter the unit price & the unit of measure

for this item.

22. Save – Choose Save to save the record. Close the window to return to the ASN Maintenance entry screen.




Ship To Maintenance The Ship To maintenance routine is primarily used to manually enter ASNs by customers that are using the EDI Manager as a stand-alone module. Once you build a ship to record for a customer part number it will be saved as a static ship to for future shipments of specific part numbers to this customer ship to location. The information in the ship to file is required on the advanced ship notice.

If the EDI Manager Module is integrated to AMI AutoAGENT the ship to information will automatically be created and you will not have to manually enter the information. However you will be able to edit the information if necessary.

To enter a Ship To record: 1. Open the ASN Maintenance window. (EDI >> ASN Maintenance >> Ship To)

2. Ship To – Enter or select the ship to code to uniquely identify the ship to information for this customer ship to record.

3. Supplier Code – Enter the supplier code for this customer ship to record.

4. Int Consignee – Enter the interchange consignee for this customer ship to

record.

5. Part Number – Enter the part number.

6. Line No – Enter the line number for this part number.



7. PO No – Enter the purchase order number for this part number.

8. Eng Change – Enter the engineering change level for this part number.

9. Uom – Enter the unit of measure for this part number.

10. Dock Code – Enter the dock code for this part number.

11. Line Feed – Enter the Reserve Line for this part number.

12. Plant Code – Enter the plant code for this part number.

13. Delivery Order No – Enter the delivery order number for this part number.

14. Storage Loc – Enter the storage location for this part number.

15. Line Supply Loc – Enter the line supply location for this part number.

16. Retur Cntr – Enter the returnable container code for this part number.





Serial Maintenance The Serial Maintenance routine is primarily used for manually entered ASNs by customers that are using the EDI Manager as a stand-alone module. For each ASN that you create, you will need to key in a serial number for each part number quantity shipped. This information is located on the barcode label under the description Serial Number.

Note: The information in the serial file is required on the ASN.

If the EDI Manager Module is integrated to AMI AutoAGENT the serial file information will automatically be created and you will not have to manually enter the information. However you will be able to edit the information if necessary.

To enter a Serial Number: 1. Open the ASN Maintenance window. (EDI >> ASN Maintenance >> Serial)

2. Invoice Number – Select or enter the invoice number assigned to this shipment.

3. Part Number – Enter the part number assigned to this shipment.

4. Serial Number – Enter the serial number for this part number . This

information is located on the barcode label for this shipment.

5. Ship Quantity – Enter the ship quantity of this part number for this serial number.



6. Save – Choose Save to save the record. Close the window to return to the

ASN Maintenance entry screen.


8. Delete – Choose Delete to delete the record.

PART 6: D

OCUMENT M

ANAGER


Part 6: Document Manager Use the Document Manager to purge historical EDI information that is no longer required to be stored in the EDI database. You can analyze EDI transaction set information and display the information on the computer screen or on a printed report. You also can save it to a file.

• Chapter 16, “Purge Documents”, describes how to purge EDI documents from historical database.

• Chapter 17, “Reports”, view and print EDI XML reports.


Chapter 16: Purge EDI Use the Document Manager to purge historical EDI information that is no longer required to be stored in the EDI Manager database.

To purge Historical EDI Data: 1. Open the EDI – Purge History window: (EDI >> Document Manager >> Purge EDI)

2. Document Type – Select which type of EDI data you want to purge by highlighting the type of document you desire.

3. Trading Partner – Select a specific trading partner otherwise the purge

will purge all trading partners.

4. Date – Enter the date to purge up to but not including.

5. Process – Press the process tab to execute the purge.



Chapter 17: Reports You can analyze EDI transaction set information and display the information on the computer screen or on a printed report. You also can save it to a file.

To View or Print EDI Reports: 1. Open the Document Manager.

(EDI >> Document Manager >> Reports)

2. Trading Partner / Transaction Set – First select the trading partner and then transaction set to view or print.

3. Process – Choose the Process button to view the XML report on your

screen.

4. Print View – To print a hardcopy report of this transaction set, highlight the Print View link in the top right portion of the screen. The report will first display on the screen to preview. Select print to send the report to a designated file or printer device.

Here is a list of sample EDI Reports as they appear on your screen:

P A R T 6 D O C U M E N T M A N A G E R


DaimlerChrysler 810 Invoice This is used to report to provide for customary and established business and industry practice relative to the billing for goods and services provided.

C H A P T E R 1 7 R E P O R T S


DaimlerChrysler 820 Payment Order/Remittance Advice This can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice. This can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee’s accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.



DaimlerChrysler 824 Application Advice This is used to provide the ability to report the results of an application system’s data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgement sent in response to a purchase order).



DaimlerChrysler 830 Material Release This is used to report the material release forecasting information between organizations. The planning schedule (830), may be used in various ways or in a combination of ways, such as: (1) simple forecast; (2) a forecast with the buyers authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in “buckets,” such as weekly, monthly, or quarterly. The order release may contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.



DaimlerChrysler 850 Purchase Order This can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.



DaimlerChrysler 853 Routing and Carrier Instructions This provides the sender with the capability to transmit detailed routing and carrier information pertinent to a route. This transaction set only provides routing information and does not convey information about a shipping event or provide shipping authorization.



DaimlerChrysler 861 Receiving Advice This is used to report the notification of receipt or formal acceptance of goods and services.



DaimlerChrysler 862 Shipping Schedule This is used by a customer to report precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule (830). The use of the 862 will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the planning schedule (830), e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.



DaimlerChrysler 864 Text Message This can be used to provide for the capability to electronically move messages, contracts, explanations, and other one-time communications. The intent of this is to provide electronic communication (messages) for people, not for computer processing. The use of the Text Message transaction set demands of the sender certain detailed information about the recipient in some human-readable form. The recipient’s network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission.



DaimlerChrysler 997 Functional Acknowledgement This can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange.


1 0 0 E D I M A N A G E R

Ford 824 Application Advice This is used to provide the ability to report the results of an application system’s data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgement sent in response to a purchase order).

Ford 830 Material Release

This is used to report the material release forecasting information between organizations. The planning schedule (830), may be used in various ways or in a combination of ways, such as: (1) simple forecast; (2) a forecast with the buyers authorization for the seller to commit to resources,


E D I M A N A G E R 1 0 1

such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in “buckets,” such as weekly, monthly, or quarterly. The order release may contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

Ford 861 Receiving Advice

This is used to report the notification of receipt or formal acceptance of goods and services.



Ford 862 Shipping Schedule

This is used by a customer to report precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule (830).



The use of the 862 will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the planning schedule (830), e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.


Glossary A ANSI: American National Standards Institute. Coordinates and provides information on national and international standards. Application: This is a set of computer programs that manages a company’s data. Application file: A data file which is created by one of your in-house applications primarily for use by that application. ASC X12: Accredited Standards Committee X12. ASC X.12 is chartered by ANSI in 1979 to develop EDI standards. ASCII: American Standard Code for Information Interchange. A character set. Association: See industry subset. B C Communications Session: All communications that occur while the connection between your EDI software and a remote system is established, maintained, and released. Concatenation: Process of combining data from multiple user file fields into one element during translation for outbound documents, or combining multiple elements into one field for inbound documents. D Detail Area: Area in a Standards document that encompasses the actual body of a business transaction. Detail Record: User file record in a recurring format that contains line item details, such as quantity, description, and price. This corresponds to detail area of document. Document: Electronic business transaction that is made up of segments. Also known as a message or transaction set. Document Header Record: A user file record that marks the beginning of a document and contains the Trading Partner ID for that document. This record is implicitly associated with the document and cannot be associated with individual loops, segments, or element sets in the document. Download: Receive information from a host computer or network. E EDI: Electronic Data Interchange. This is the exchange of business information between two computers. EDI network: A third-party commercial service which transports and houses information between trading partners. This is also called a VAN (Value-added Network).

G L O S S A R Y


EDI software: Software that translates, envelopes, and addresses outbound EDI documents and identifies and translates inbound EDI documents. EDI Standard format: Predefined format that allows business partners with incompatible internal formats to exchange documents electronically. The major Standards include EDIFACT, ANSI X12. This is also referred to as a standard format. EDIFACT: Electronic Data Interchange for Administration, Commerce and Transport. The international EDI standards developed within the framework of the United Nations. The International Standards Organization (ISO) ratifies this EDI standard. The Data Interchange Standards Association (DISA) administers these standards in the United States. Element: Individual item of information within a Standard document. Groups of elements form data segments. Element Set: A group of elements that exists within the same segment that have a contiguous repeating structure. F FA: See functional acknowledgement. Functional Group: One or more messages of the same type headed by a functional group header segment and ending with a functional group trailer segment. G H Header Area: Area at the beginning of a Standard document that relates to the entire document. Header Record: User file record that usually contains information pertaining to the entire document, such as date, company name, address, totals, and so on. I Interchange Control Number: Unique number, assigned by the sender that identifies the interchange data. This can be used to maintain an audit trail. Interchange ID: ID that you and your trading partner and/or network agree to use for sending and receiving electronic data. This is used to determine who to route documents to, and who the documents came from. Interchange Qualifier: Code that indicates the type of interchange ID. J K. L M Mailbox: Network facility for gathering and holding electronic business documents to be retrieved by the subscriber.


Mapping: Process of identifying the relationship between data fields in your in-house applications and elements in the Standard document. Also refers to creating a translation format. Modem: Modulator/Demodulator. This is a device that converts the signal from a computer to a series of tones for transmission over a telephone line. It also converts this series of tones back into a signal a computer can interpret. N Network Configuration: This is a description of the resources that enable communications between the local and remote system. O P Q Qualifier: Data element that gives a generic segment loop or data element a specific meaning. R S SQL: Structured Query Language. Segment: Predefined set of functionally related data elements. Segment: Identifier: Code that occurs in the beginning of a segment which uniquely identifies the segment to the Standard. Segment Separator: A special character used at the end of a segment to separate each segment in a document. Segment Terminator: See segment separator. Source: Origin of a transaction or operation. Standard format: Predefined format that allows business partners with incompatible internal formats to exchange documents electronically. The major Standards include EDIFACT, ANSI X12, and ODETTE. This is also referred to as an EDI Standard format. Sub-element: See component data element. Sub-element Separator: See component data element separator. Syntax: Rules for the construction of Standards. T TCP/IP: Transmission Control Protocol/Internet Protocol. The suite of communications protocols used to connect hosts on the internet. Trading Partner(s): Referred to as companies sending and receiving documents via EDI. A company that sends an purchase order and the company that receives it are each other’s trading partners.

G L O S S A R Y


Trading Partner Relationship: Defines the unique business relationship between trading partners for each document type. Contains the information that tells the EDI software how to translate, envelope, and address outbound documents and how to identify and translate inbound documents. Transaction set: A collection of EDI segments which create a document, which can perform a standard business transaction. Each transaction set includes a header, detail and a summary. Translation: Process of converting data from a Standard EDI format to an internal format, or from an internal format to a Standard EDI format. Translation format: Describes the one-to-one relationship between data fields in an application and elements in a Standard document. It contains the map of the elements in a Standard document and the fields in a user file for a particular type of document. Translator: A set of programs that translates documents. U V VAN: Value-added Network. This is a third party network that transmits data between trading partners. This is also called an EDI network. Value-added Network: VAN A third party network that transmits data between trading partners. This is also called an EDI network. W X X12: See ANSI X12. Y Z

EDI Manager User Guide - Squarespaceamiauto.squarespace.com/s/EDI-Manager-User-Guide.pdf · Symbols...

Documents

Transcript of EDI Manager User Guide - Squarespaceamiauto.squarespace.com/s/EDI-Manager-User-Guide.pdf · Symbols...