Eclipse EDI Support Documentation Table of Contents...EDI_101_Packet.DOC Updated 2/9/2017 Page 9 of...

EDI_101_Packet.DOC

Updated 2/9/2017 of 42

Eclipse EDI Support Documentation Table of Contents

Administration and Tasks EDI Admin Daily Tasks Daily tasks that should be performed by the site’s EDI Administrator EDI Testing: How to setup and test new trading partners Alternate Trading Partner ID Often used with new trading partners who have a testing ID Control Number Mismatches How to manage this commonly seen error EDI Definitions Explanation of common EDI terminology and a list of the common inbound and outbound documents EDI Cheat Sheet Cheat sheet to help you setup new trading partner profiles EDI Info Template Template to create an info sheet to send to your trading partners Vendor 850 Quote Numbers How to send your vendors Quote numbers, Contract numbers, or special pricing reference numbers within the Outbound 850 Purchase Order

EDI Trading with Customers 850 Inbound Setup How to setup your system to receive 850 Purchase Orders from Customers 850 Inbound Processing Instructions for your order takers to manage and process inbound EDI purchase orders

Eclipse EDI Error Glossary List of possible errors that can be received into the EDI error queue with instruction on how to handle the errors

EDI_101_Packet.DOC


Eclipse EDI Administrator Daily Tasks

Overview There are several tasks that should be completed on a regular basis by the designated administrator for Eclipse EDI. Typically, it is recommended that these tasks are completed on a daily basis. Depending on your EDI traffic, you may want to adjust the schedule of these tasks, completing them anywhere from several times a week to several times a day. For our Platinum EDI clients, these tasks are handled by the Eclipse EDI Support Group. We recommend that all sites, either through Platinum Support or on their own, maintain the EDI queues and check the EDI Activity Log regularly. This will aid in finding problems and resolving them in a timely manner.

***Note: EDI has not fully been intergraded into Solar at this time. When you reach a screen that is not solarized an Eterm session will be launched and you will be asked to log in to your Eterm account.

Daily Tasks These three areas should be checked daily as outlined below: 1) EDI Activity Log: calls completing 2) EDI Outgoing Status Queue: up to date 3) EDI Error Queue: no errors System > System Programming > EDI > EDI Maintenance to view Maintenance options

EDI_101_Packet.DOC


EDI_101_Packet.DOC


EDI Activity Log The EDI Activity Log (In Eterm, F2 > S > E > M > V) has the most recent activity at the top, and should be checked for the following: 1) EDI transmissions are starting and completing properly.

a. For normal transmissions with your VAN you should see the following: Connect To (VAN name) Completed ** Connected to (URL or IP address). ** TRANSFER COMPLETED - SEND ** Connected to (URL or IP address). ** TRANSFER COMPLETED - RECEIVE Connect To (VAN name) Started

b. If there are no documents to send, or no documents at the VAN to receive you would see the following: Connect To (VAN name) Completed ** Nothing to Transmit to Epicor TDX ** Connected to (10.16.25.19). ** NO MATCHING FILES - RECEIVE Connect To (VAN name) Started

Watch for any errors or failures

2) Check that documents are being enveloped and created. How many you see and what time of day you see them depend on your volume of EDI trading.

a. Enveloped: 02/09/17 12:08pm Enveloped : 997 -

02/09/17 12:08pm Enveloped : 850 - P001097256.0001 b. Created: 02/09/17 12:08pm Created 850 - S001833229 -

Hint: You can search for entries in the log by selecting (ALT-S). The Select Pattern will allow you to search for any text in an entry. You can pull up all entries regarding your VAN to see calls completing. For inbound orders that are created, you can view or edit the order by placing your cursor on the line and doing an Alt-V for View or Alt-E for Edit.

Example:

EDI_101_Packet.DOC


EDI Outgoing Status Queue The purpose of this queue (System- System Programming- EDI- EDI Maintenance- EDI Outgoing Status Queue) is to review recent documents that are pending or have been sent, and are waiting to be acknowledged by the trading partner. When a user creates an EDI outbound document, an entry for that document is added to the EDI Outgoing Status Queue. At first, the document is in a SEND status meaning that it will be sent on the next EDI VAN transmission. When a document is in the ENVELOPED status it means that a call is in the process of being transmitted to your VAN/Trading Partner. Once the transmission is complete, the status will change to SENT. When the trading partner receives the document, they will send a 997 Acknowledgement back in return. When the 997 is received, the applicable entry is cleared off the queue automatically.

Verify Older Documents. Documents should not sit in the Outgoing Status Queue for more than one or two business days. If you see a document older than that, contact your trading partner and ask if they have received the document. Resend as requested or manually post the 997.

Resend Standard (850,810,855 and 856) Documents As Needed If the trading partner has not received your document you can recreate it by going into the order and selecting EDI in the print option drop down from the order status screen.

Post Manual 997 As Needed/ Create Manual 997(Solar) If the trading partner has received your document, Right-Click > Create Manual 997 to post a manual 997. The manual 997 posting will list the acknowledgement in the change log of the order.

Research ACK ERROR status A document in the queue with a status of ACK ERROR means that your trading partner received your document, but there was an error on the document you sent. Contact your trading partner and ask what the problem is. Once the error is resolved resend the EDI document if need be.

Note: Problems to watch for: A document stuck in ENVELOPED status for more than a few minutes may indicate a hung transmission. Check the EDI Activity log to see how long the transmission has been active. If active for more than 10 minutes, contact EDI Support for assistance.

Other helpful hot keys:

Right-Click > View Document will show you the raw EDI data of the outbound document.

Right-Click > Delete will allow you to delete a single entry.

Right-Click > Delete By Date will allow you to delete all items on the selection list older than the chosen date.

Right-Click > Change Status will switch the status of a document between HOLD and SEND.

EDI_101_Packet.DOC


EDI_101_Packet.DOC


EDI Error Queue This queue (F2 > S > E > M > Q) shows errors on pending EDI documents. These errors need to be dealt with as quick as possible as they are often for important incoming documents. The documents in this queue are pending and have not yet been processed into your system. Ideally, this queue should be empty except for any new errors. The follow instructions are a quick guide on the common hot keys used in the EDI error queue. We have listed some of the more common error you may see in this queue just below. For a complete list of errors please refer to the ‘EDI Error Glossary’ located on page 35 of this guide. To view any error in the EDI Error Queue put your cursor on the line in question and hit enter. This will allow you to view the EDI document. For documents that need to be requeued (see error glossary for full list) perform the needed update and then do an Alt-R on the document in question. Documents that need to be deleted (see error glossary for full list) do an ALT-D. To get access to your Trading Partner Profile quickly do an Alt-P To process the Partner Sub-ID errors do an Alt-S and enter your ship-to account number when prompted.

EDI_101_Packet.DOC


Common Errors (for full list, see document EDI Error Glossary) 5 - Partner Sub-ID Not Found -ECIERR : XXXX-XXX The bill-to or ship-to (N1-BT/N1-ST) data specified in the error message was not found in the EDI Group Profile Receive Code Table accessed from the EDI Group Profile Maintenance screen. You need to enter the bill-to or ship-to (N1-BT/N1-ST) data specified in the error message into the Receive Code Info Table screen for this trading partner. Then requeue this document. 5 - NO MAPPING FOUND -ECIERR: XXX A mapping subroutine is not defined on the EDI Group Profile Maintenance screen for this trading partner and document type. You must set up and define a mapper for this document on the EDI Group Profile Maintenance screen for this trading partner. Then requeue this document. 4 - Duplicate Recv Doc -EUNERR: XXX Duplicate control numbers have been received from a particular trading partner for a specific document type. Contact your trading partner and tell them which control numbers have been received in duplicate. Then ask them to verify whether or not it is a duplicate. If the document that was sent was not a duplicate, they must resend it with control numbers that have not yet been used. When resolved, delete the error. 1 - NO TRADING PARTNER PROFILE FOUND -ECUERR: XXXX No trading partner profile could be found for the given interchange ID. Set up a trading partner profile for the given interchange ID. 7 Purchase Order # Already Exists. -OCLERR The purchase order number that the EDI document tried to create already exists on Eclipse. This could be caused by your trading partner trying to reuse a previously used purchase order number or resending a previously sent order. Contact your trading partner to have problem corrected. 3 - SEG COUNT MISMATCH IN SE -EUNERR: XXXX/XXXX The number of segments indicated in the “SE” segment does not match the number of segments actually counted. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. After fixing the problem, you can requeue the document from the Inbound Document Archive. 3 - TS CONTROL# MISMATCH ST/SE -EUNERR: XXXX/XXXX The control number in the transaction header does not match the control number that is in the transaction footer. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance.

EDI_101_Packet.DOC


Eclipse EDI Document Testing

Overview: This document will provide you with useful information and assist you in setting up and testing EDI inbound and outbound documents using the Eclipse EDI package.

* It is strongly recommended that you have completed EDI 101 training prior to testing.

Steps to Setting up and Testing a new Trading Partner: You must communicate with your new potential trading partner. Certain information should be exchanged so the setup goes well. Prior to beginning the exchange of production EDI data, all documents that are to be used should be thoroughly tested. This serves two purposes; it ensures that the intended party receives the transmitted data and that the data meets the needs of both you and your trading partner. The below topics will be covered in this section.

Sharing Information with Trading Partner Authorize Interconnect at VAN Create Trading Partner Profile Create tests Send tests to Trading Partner (and/or) Receive tests from Trading Partner You and your Trading Partner agree to Move to Production

Sharing Information: Contact your new EDI trading partner and acquire the following information from them:

VAN Qualifier ISA ID Group ID Any test ID’s List of EDI documents they utilize The version of EDI they are using (version 4010 is recommended)

* Eclipse maintains generic maps for most documents for version 4010.

Your Trading Partner will also need this information from you. It is recommended that you create an “EDI Information” document that you can easily send to any trading partner when requested. An example of this can be found on page 26 of this guide.

EDI_101_Packet.DOC


The Trading Partner may also ask for your EDI specs. These are available for download from

the Customer Support website. http://support.epicor.com/ After logging in, go to the’

Eclipse’ link and chose the Support tab to allow you to access to the link for ‘Download Center’. Here you will find the EDI specs under the title ‘EDI Mapping Specifications’. You can chose from Vendor mapping specs or Customer mapping specs.

Authorize Interconnect with your VAN: Once you have the Trading Partner’s EDI information listed above, contact your VAN and ask them to set up an interconnect between you and your trading partner. The VAN will need your Trading Partner’s EDI information to setup the interconnect. If you do not notify your VAN that you want to start trading with the new trading partner, you may not be able to send or receive documents with the trading partner in question.

Create Trading Partner Profile: Trading Partner setup is detailed in EDI101 training class.

The below will show you the basic EDI trading partner setup (please refer to the EDI Administration recording for more details on Trading partner setup.): Start by setting up the ISA portion of the EDI trading partner profile.

http://support.epicor.com/

EDI_101_Packet.DOC


Once you have the ISA portion set you can set up the Group piece of the EDI profile. To get into the Group put your cursor on the Group ID and do an Alt-G.

The following points are helpful when testing. ISA15 – Test Mode Indicator Your trading partner may require you to indicate in the test document that they are to receive from you have a test indicator in the ISA15 of a ‘T’. To set this option set the ‘Test’ option to yes ‘Y’. The default status is no “N”. When testing is complete ensure that this field is set back to “N”.

EDI_101_Packet.DOC


Trading Partner Testing ID If your trading partner utilizes a test ID the test ID will need to be entered in the Alternate Interchange ID field in for the specific document being tested. For more detail on the Alternate ID refer to document Alternate Trading Partner ID beginning on page 17 of this document. Default Status A helpful tip when testing is to change the default status of outbound test documents to “Hold”. This is done in the Add’l Doc Info screen for the document being tested. Changing the default status to “HOLD” will allow you to control when an outbound test document is sent.

Add’l Doc info settings It is recommended that you take the time to review the different options available to you in the Add’l Doc Info for each EDI document. The F9 and F11 will give you details of each option and help you determine if that will be needed for your current trading partner setup.

Create Tests:

Vendor Testing – Outbound 850 Normally the first document tested will be the outbound 850 Purchase Order. You will need to create a purchase order to generate the test 850 document. Your purchasing staff may create one for you containing items you would normally order from that vendor. Note: Eclipse provides functionality to allow you send special price quote and contract numbers to your vendors. Please see additional documentation 850 Quote Numbers found on page 28 of this guide if you need to add a quote/contract number to your test 850. On the status tab of the PO, select EDI as your print option.

From the File drop down at the top select ‘Exit’ to generate the EDI Document. When prompted select ‘Next Scheduled’ to send your EDI document to the Outgoing status queue (System > System Programming > EDI > EDI Maintenance > Outgoing Status Queue). You will want to notify the trading partner prior to sending the test document. The document must be in ‘SEND’ status in order for it to be sent to your Trading partner. If your document is on HOLD you can change it to SEND by selecting the file drop down from the top of the page and selecting ‘Change Status’. Once the document is in the SEND status it will go out on your next scheduled VAN transmission.

EDI_101_Packet.DOC


Vendor Testing – Inbound 855, 856 and 810 To test inbound documents ensure that the correct map is in place in the Group Profile Maintenance screen and that the 997 flag is set correctly.

Recommended Settings for the 997 Inbound Documents: Y Outbound Documents: N

Note: If desired, you can wait until the inbound 855, 856 or 810 document comes in before adding the document to the profile. With the document type missing from the profile, the document will be routed to the EDI Error Queue with the message “No Mapping Found” and the EDI.ADM message group will be notified of the new error. You can add the document to the profile at that point and Requeue the document from the EDI Error Queue. When the 855, 856 or 810 document comes in, the system adds it to the appropriate EDI Review Queue. Go to Purchasing > Queues for the 855 PO Acknowledgment and 856 Advance Shipping Notification (ASN) review queues, and go to the A/P menu for the 810 Invoice review queue. Management of these queues is covered in the Eclipse training class EDI Review Queues. To sign up, log into the customer website and go to the Education section. http://erpcustomer.epicor.com/cws/public/signIn.do

Customer Testing – Inbound 850 To test customer documents ensure that the correct mappers are in place in the Group Profile Maintenance screen and that the 997 flags are set correctly.

Recommended Settings for the 997 Inbound Documents: Y Outbound Documents: N

http://erpcustomer.epicor.com/cws/public/signIn.do

EDI_101_Packet.DOC


Normally, the first document tested is the 850. Your trading partner must generate a test PO on their system and send a test 850 to you. A received 850 Purchase Order can be view or edited from the Remote Order Entry Review Queue (Orders > Queues > Remote Order Entry Review.) Enter in the appropriate branch information or “ALL” and for the Src (order source) enter “EDI”.

To edit or view the order, select the ‘Order’ dropdown from the top of the page. Either option will take you to the Sales Order Entry screen.

EDI_101_Packet.DOC


From the Order Status screen, you can return the outbound 810 Invoice, 855 PO Acknowledgment, and 856- Advanced Ship Notice, depending on the order status.

The trading partner must contain the map for the document that you are attempting to create.

Customer Testing – Outbound 855, 856 and 810 855 = Open order status To create the 855 the order must be in one of the open statuses (Call When Complete, Ship When Specified, etc.) The 855 will not print if the order is in a Bid, Cancel, or Pick Up Now status.. 856 and 810 = Invoiced or Pick up now Status To create the 856 or 810 the order must be in one of the closed statuses (Pick up Now or Invoiced) The 856 and 810 will not print if the order is in a Bid, Cancel, or Pick Up Now status. Create the Outbound EDI Document To create the EDI document and place it on the outgoing status queue, the “Print” field must be populated with an “EDI”. After entering the “EDI” and exiting from the sales order, you will receive messages on the screen asking if you want to send the document, in the case of the 810 and 856 you will have the option of sending either one or both. If the system will not accept an “EDI” in the PRINT field, you need to make sure that the customer account number is attached to an EDI profile and that the proper outbound mapper is set up in Group Maintenance. The outbound document(s) will automatically be placed in the Outgoing Status Queue. (System > System Programming > EDI Maintenance > Out Going Status Queue). It is recommended that you notify the trading partner prior to sending the test document. The document must be in ‘SEND” status. If your document is on HOLD, use the ‘Change Status’ option from the files drop down. The status will be changed to SEND and the document will go out on your next network call. EDI and Batch Invoice Printing Once the Trading Partner relationship is put into production, if you want the 810 Invoice to be sent automatically during the Batch Invoice Printing process, you will need to add that

EDI_101_Packet.DOC


functionality to the customer account file by placing “EDI” in the Invoice Fax Copies field. To do this, go to your Maintenance drop down at the top of the page and select ‘Customer’. Enter in your Customer account number or the sales order number. Once you have selected the proper account click on ‘Pricing’ then ‘Customer Pricing and Printing’ now select the ‘Printing tab.

Moving to Production: After a successful round of testing, you and your trading partner can decide when to move the trading to production status. Things to note before send or receive your first EDI production document.

If you have been using the Test Mode flag, be sure to set it back to N

If you have been using an Alternate Testing ID, be sure to remove that ID from the Alternate interchange ID field in your Trading partners Group profile.

If you set any default status to HOLD for outbound documents set it to SEND.

For Inbound 850’s (orders) it is recommended that you set option ‘ Check for Duplicate PO #s’ which can be found in the Global Settings (Alt-G) of the Group Profile.

EDI_101_Packet.DOC


Eclipse Alternate Trading Partner ID

Overview Some Trading Partners will have a test EDI ID as well as a production ID.

ZZ~ABCTEST~ABCTEST ZZ~ABCPROD~ABCPROD

This document demonstrates how to set up a Trading Partner Profile using both EDI ID numbers. The Alternate Trading Partner ID can also be used when a trading partner is changing their ID number. This process is described at the end of the document.

Using a Testing EDI ID Number When setting up the partner for EDI, set up the Trading Partner Profile with the Production ID. Set up the profile as you normally would using the production ID, in this example: 01~000111222

1. Add your documents as needed.

2. For each document, go into the Add’l Info Screen, ALT-A

EDI_101_Packet.DOC


3. Add the full testing (or alternate) EDI ID to the Alternate Interchange ID field. The full ID

includes the Qualifier, ISA ID and Group ID, in this example: 01~000111222T~000111222T

After adding the alternate, you will see duplicate pairs show up when you search for the partner in the trading partner profile screen.

When the testing period is over and your trading partner informs you to start using the production ID, go back into the respective Add’l Doc Info screens and delete the Alternate ID. The test ID will no longer be used for those documents. Changing Interchange ID Numbers

When a trading partner changes their EDI ID, create a new profile with the new EDI ID, then go into the Group Maintenance screen and use the Alt-C Copy/Move Profile hot key. An information / prompt screen appears with your cursor at the bottom right corner. F10 and select ‘Move’.

A prompt screen then appears where you would enter the qualifier and ISA ID of the “old” ID on the first line, and the Group (GS) ID of the “old” ID on the second line. Then press Enter.

EDI_101_Packet.DOC


A message then appears. Press the Esc key and you will see that all of the information from the “old” profile has been moved into this “new” profile. The “old” profile still exists with the same documents and Add’l Doc Info settings, but all of the entities including Send and Receive codes have been moved from the old profile to the new one.

EDI_101_Packet.DOC


Eclipse Control Number Mismatches

Overview The Eclipse system monitors all incoming interchange and group control #s, respectively. When either is received out of sequence, Eclipse sends a system message to the EDI Administrator that a control # (ISA or GS) is out of sequence and resets the control # in the EDI profile to the last control # that was received. This function was set up to inform the EDI Administrator that documents may be missing and allows the EDI Administrator to follow up with the trading partner to confirm. However, in many cases the trading partner does not follow a sequential order when sending control numbers. Here is how you can suppress the warning message.

Setting Ignore Ctrl # flags The EDI Trading Partner Maintenance has a flag called 'Ignore Ctrl#'s' in the ISA potion of the EDI profile, as does the EDI Group Profile Maintenance called 'Ignore GS Ctrl # Mismatch Warnings' under the Global Settings. These flags are set at the trading partner level and are independent of other trading partners. Setting these will cause Eclipse to "ignore" the control # sequence mismatches. Eclipse will not generate the message to the EDI Admin if the options are set to on. The ISA control number is set by doing an ALT-I. This is a toggle so to turn it off just do another ALT-I. In the Group section under the Global Settings set the ‘Ignore GS Ctrl # Mismatch Warnings’ to ‘Y’. ISA

Group

EDI_101_Packet.DOC


EDI Definitions ANSI: American National Standards Institute is a private, non-profit federation of standards organization. ANSI does not develop standards, nor does it make judgments about the content of a standard. It certifies that these voluntary standards bodies have arrived at standards through on of three accredited procedures. As the member body of ISO and the manager of U.S. IEC activities, ANSI also coordinates the U.S. standards position in the international arena. ASCII: American Standard Code for Information Interchange. Control Number: The number incremented by the sender, used to identify an EDI envelope. The Control Number consists of three sets of numbers, an ISA a GS and ST number. EDI (Electronic Data Interchange): This is a set of computer interchange standards for business documents such as invoices, bills, and purchase orders. EDI Envelope/Envelope: Electronic structure that contains EDI data. FTP (File Transfer Protocol): A common method of moving files between two Internet sites. FTP is a way to login to another Internet site for the purposes of retrieving and/or sending files. GS Control Number: Reference number that refers to a specific group of transactions within an EDI Envelope. GS ID or Group ID example: 12~5122785570~5122785570. This number can indicate a branch, group, or division within a company. Interconnect: Term used to describe the link/path between two VANs to enable the exchanging EDI data. ISA Control Number: Reference number that refers to a specific Interchange Control Header within an EDI Envelope. ISA ID or EDI ID: example: 12~5122785570 Consists of the qualifier and ISA ID. Map: Program that will accumulate and format EDI data. On Network: When your Trading Partner and you use the same VAN. Qualifier: The first two digits of the ISA/EDI ID 12~5122785570. The qualifier indicates what type of number the ISA ID is, 12 = phone number, 01 = Dun and Bradstreet, etc. ST Control number: Reference number that refers to a specific document within an EDI Envelope. Trading Partner: A company, either customer or vendor that is exchanging data via EDI with your company. VAN (Value Added Network): A communications facility using common carrier networks for transmission and providing extra data features with separate equipment. Store and forward message switching, terminal interfacing and host interfacing features are common extras. VMI (Vendor Managed Inventory): When sellers maintain inventory they own on the buyers' premises. This helps to minimize the buyer's investment in inventory.

EDI_101_Packet.DOC


VPN (Virtual Private Network): A theoretically safe area on the ‘Net’ in which secure transactions can take place. X12: Name of the standards for inter-industry electronic interchange of data for business transactions. XML (eXtensible Markup Language): XML is a computer language that was created to facilitate e-commerce because it allows disparate systems to more easily transmit data and communicate. More specifically, XML creates a universal way for companies to describe products, components and services on the Internet, in order to avoid miscommunication. Commonly used EDI documents: 810: Invoice 820: Remittance Advice 840: Request for Quote 843: Response to Request for Quote 845: Contract Pricing Update 844: Sales Rebate Report 849: Reply to Rebate Request (844) 850: Purchase Order 852: Product Activity Report 855: Purchase Order Acknowledgment 856: Advance Ship Notice 860: Purchase Order Change Request 867: Point of Sale Report 997: Functional Acknowledgement

EDI_101_Packet.DOC


Available Transaction Sets

The Eclipse system is capable of receiving and printing any valid ANSI X12 formatted transaction. Any

inbound document not listed in the following tables can be translated using the EDI.PRINT.DOC print

routine, which produces a report that is placed in the Hold file.

The following tables list the transactions integrated into the system. All documents listed have a generic

mapper that can be used with many trading partners. Some trading partners will require customization to

the generic mappers. Customization is subject to a custom programming charge for those clients who do

not subscribe to the EDI Platinum service. For those clients who subscribe to the EDI Platinum service,

most customized mappers are provided at no charge.

Customer Transaction Sets

The following table lists the customer transaction sets integrated into the system.

Transaction

Set Description Inbound Outbound

810 Generic Invoice: Customization likely X

830 Forecast Schedule: Produces sales order bid, customization

likely X

840 Request for Quote (RFQ): Produces sales order bid X

843 Response to RFQ X

850 Purchase Order/Sales Order X

855 P/O Acknowledgment: Acknowledges customer order X

856 Advance Ship Notice X

857 Advance Ship Notice & Billing X

860 Purchase Order Change Requests: creates Hold file report

only X

865 P/O Acknowledgment With Change: Acknowledges customer

order with changes X

997 Functional Acknowledgments X X

EDI_101_Packet.DOC


Vendor Transaction Sets

The following table lists the vendor transaction sets integrated into the system.

Transaction

Set

Description Inbound Outbound

810 Invoice X

820 Generate Remittance Advice X

844 Product Transfer Account Adjustment/Rebate Reporting with Book

Letters of Credit option

X

845 Price Authorization Acknowledgment: Creates price contract. X

849 Response to Product Transfer Account Adjustment when used with

Book Letters of Credit option.

X

850 Purchase Order/Sales Order X

852 Product Activity Data: Customization likely. X

855 P/O Acknowledgment: Type 1 – Creates VMI purchase order

generated by vendor.

X

855 P/O Acknowledgment: Type 2 – Updates expected ship dates and

compares pricing.

X

856 Advance Ship Notice X

867 Point of Sale Reporting X

997 Functional Acknowledgments X X

EDI_101_Packet.DOC


EDI Trading Partner Setup Cheat Sheet Share Information with Trading Partner

Authorize Interconnect at VAN Contact VAN with info above and authorize the interconnect

My VAN: _________________________________

VAN Contact: ______________________________

VAN Phone: _______________________________

VAN Email: ________________________________

Create Trading Partner Profile See screen shots on next page for reminders

Create tests, send to or receive from Trading Partner Trading with Vendors: you create 850 PO, they send 855, 856 and 810 to you Trading with Customers: they create 850 and send to you, you create 855, 856 and 810

You and your Trading Partner agree to Move to Production

My Info Trading Partner

Company Name

VAN

Qualifier

ISA ID

Group ID

Test ID

Documents

Version

EDI_101_Packet.DOC


Example Vendor Trading Partner Setup

Example of documents for Customer Trading Partner

EDI_101_Packet.DOC


COMPANY EDI Information Product or Purchasing Contact: Name

Company

Address

City, ST Zip

Phone: Fax: Email: EDI Technical Contact: Name

Company

Address

City, ST Zip

Phone: Fax: Email: VAN: van Standard: X12 ISA Version: 4010 Qualifier: 00 ISA/GS ID: 012345678 Documents: 810, 850, 855, 856, 997

EDI_101_Packet.DOC


Vendor 850 Quote Numbers Entering Price Quote, Quote or Contract Numbers for EDI

Overview: Eclipse provides a generic 850 mapper that allows users to send Price Quote (a.k.a. Promo), Quote or Contract numbers in the Purchase Order Request Transaction (850). This can be accomplished in one of two ways, at Line Item level or header level. Quote numbers are used instead of free-form text to accurately communicate special offers or programs.

Quote and Contract Qualifiers: You will have to contact your Trading Partner to see what qualifier(s) they want you to use (*PR/*Q1/*CT). As your Trading Partner announces special programs or quotes, remember to ask for the quote numbers you should use to take advantage of the program.

*PRquote for a price quote number

*Q1quote for a quote number

*CTcontract for a contract number

Note: The generic outbound 850 mapper look for *PR, *CT and *Q1 in ALL CAPS to create an individual REF segment for each applicable PO1 segment on the PO. When entering the code do not add a space between the *PR/*Q1/*CT and the number as this will prevent the number from being picked up by the mapper.

Below are a few examples of the incorrect ways to enter the codes followed by the correct way on the right. Incorrect Problem Correct

*pr9999 lowercase letters *PR9999

CT9999 there is no * *CT9999

*Q9876 the qualifier is *Q1, not just *Q *Q19876

*PR 4444 space between *PR and quote number *PR4444

EDI_101_Packet.DOC


Adding at Line Item Level:

1) Price Quote, Quote, or Contract numbers can be entered for specific Line Item(s) by entering a Comment in the Body of PO (Click on the line item, click the ‘Line Item’ tab at the top of the screen, and then select the ‘Comment’ option). Use the following syntax: Example: Quote # 9889 should be entered as *Q19889 and will display on the EDI 850 as REF*Q1*9889

2) Price Quote, Quote, or Contract numbers can be entered as *CT123456, *PR123456 or *Q1123456 in the Matrix Tag Along Comments of the Buy/Sell Matrices off the Price Maintenance Menu (Select the ‘Maintenance’ menu, select ‘Price Maintenance’, select ‘Buy Matrix’, enter the selection criteria, and then select the ‘Comment’ tab at the bottom of the screen). This default creates an individual REF segment at the line item level, without having to enter a Comment in the Body of PO. This method should only be used if the line item will always have the same Price Quote, Quote, or Contract number.

EDI_101_Packet.DOC


Adding at Header Level: Price Quote, Quote, or Contract numbers can also be sent at the HEADER level by entering the same *CT123456, *PR123456, or *Q1123456 in the Vendor Instructions field within the Header of the purchase order. This creates a REF Segment at Header level and applies to ALL products on the order.

You can also enter any header level shipping instructions as well. The above example will produce the following lines in the 850 order: REF*CT*33355 MSG*PLEASE CALL TO SCHEDULE DELIVERIES. ASK FOR WAREHOUSE MANAGER Do not use free-form descriptions of special buying programs or quotes in the Vendor Instructions. Aside from the *PR/*CT/*Q1 quote numbers, the Vendor Instructions are to be used for delivery/shipping instructions only.

EDI_101_Packet.DOC


Default Vendor Instructions If you often, or always, need to include the same quote number for ALL orders, you can add a default vendor instructions message. Go to Vendor Maintenance (Select the ‘Maintenance’ menu, and then select ‘Vendor’), select the ‘Orders’ tab, then select ‘Vendor Order Entry Instructions’. At the prompt for ‘Instruction Type’, select ‘Vendor Instructions’ and enter the *PRquote# there. The quote number will appear on every purchase order, and can be edited or deleted if an order does not qualify for the quote.

Expected qualifiers for vendors: Through working and testing with the vendors, Eclipse has learned what qualifiers work with some of the vendors: 3M - *CT or *PR for price quotes Advance Transformer - *CT or *Q1 Burndy - *PR Bussmann - *PR or *CT Cooper Power - *PR* Eagle/Cooper Wiring - *Q1 EGS - *PR Elkay - *Q1 Federal Signal - *Q1 Ideal - *CT or *PD for promo order Joslyn - *Q1 Juno Lighting - Can not accept quoted pricing via EDI. The PO must be submitted manually. Kichler - *Q1 or *PR Kohler Canada - *PR Leviton - *PR Littelfuse - *PR MacLean - *PR or *Q1 Masco - *PR at the line item level Mersen/Ferraz - *PR Moen Canada - *Q1 ***Eclipse recommends that each user confirm the correct qualifier with the vendor before sending quote numbers in an 850. If the vendor doesn’t receive the correct qualifier, the special pricing may not be applied.

EDI_101_Packet.DOC


Inbound 850 Setup Customer PO to Eclipse Sales Order Eclipse can trade EDI transactions with customers. The Inbound 850 PO will create a Sales Order on the system. Users will typically return the 855 PO Acknowledgements, 856 Advanced Ship Notice and 810 Invoices. Triggers can be setup to automatically create the 855 and/or the 856. The 810 can be generated from the Batch Invoice process referred to on page 15 of this guide.

Customer Maintenance Setting Home Branch For inbound EDI orders the Home Branch should be defined. To do this, go to the Customer Maintenance screen (Maintenance-Customer). Pull up the customer in question and go to the Orders dropdown and select ‘Accessible Branches’. In the field call ‘Home Branch’ list your Branch. Then when an 850 sales order is created from an inbound 850 the order will be generated under that branch.

EDI_101_Packet.DOC


EDI Setup Maintenance System-System Programming- EDI- EDI Maintenance-EDI Setup Maintenance

When an order comes in, the system creates a sales order and tries to add products based on the product ID’s listed in the inbound 850. In some cases there may not be enough information to do a part number match. For those occurrences we have a default EDI product called ‘***EDI Product Not Found***’. This generic EDI product will allow the sales order to still be created. This Item is setup for you at your EDI install. When you receive an inbound order with an EDI Product Not Found DO NOT delete and rekey the item. The way to update the sales order is to type over the product description with the correct item. This will create an entry into your customer cross reference table. It will also leave the EDI Ledger info properly linked for your return EDI documents. Without that info from the inbound 850 the return EDI documents may fail on your customer side.

EDI_101_Packet.DOC


Inbound 850 Processing Customer PO to Eclipse Sales Order When an 850 PO comes in from a customer, a sales order is created. Users may or may not be notified based on the Trading Partner settings. All orders are added to the Remote Order Entry Queue. This queue is also used for web, B2B, and other remote ordering methods.

Remote Order Entry Review Queue Orders-Queues-Remote Order Entry Review Queue You can narrow your selection by Branch, User ID, and source. Set branch to ‘ALL’ and the source to ‘EDI’ will list the orders that have come in from EDI for all branches.

This queue should be reviewed daily. This queue will show all orders that come in via a remote method. Users should work on these orders to get them from a Bid status to an open status so the product is sent out.

To work the queue: 1. Review Orders in Bid Status 2. Make any needed changes 3. Set the order to an open status 4. Clear the Order from the Queue

Review Orders in Bid Status (and make any needed changes)

EDI_101_Packet.DOC


All orders that show in a ‘B’ status are orders that need to be reviewed. Users need to fix products or pricing if needed and set to an open status so the order can be shipped. You can view the errors by clicking on the Edit drop down and selecting the ‘Error Detail’. When ready to work on the order, select the Order drop down and select the edit option. Users may need to review pricing. Trading partners can be setup to respect the customer pricing or use system pricing. Orders will use system pricing by default. If there is a mismatch between the system pricing and the PO pricing, the order will show that as an error. The item will be priced per system pricing, but the customer pricing will be shown in the item comments. If the flag is set to respect customer pricing, the system will not show an error even if the customer pricing does not match the system pricing. After all products and pricing have been fixed, the order is ready to be set to an open status. In the status screen, set the order from Bid to the appropriate open order status. Escape from the order which will take you back to the Remote Order Entry Review Queue

Clear the Order from the Queue If you have completed all work on the order and set it to an open status, it can be cleared from this queue. From the Edit drop down select either the Clear Current Order or Clear orders w/o error.

The Remote Order Entry Queue should be reviewed daily. Orders should be fixed and set to an open status so the order can be shipped. Once work is completed on the order, the entry should be cleared from the queue. This will keep the queue clean and let users know what orders still need to be fixed and shipped.

EDI_101_Packet.DOC


Eclipse EDI Error Glossary

EDI Error Glossary The following EDI Error Glossary provides information regarding EDI system errors that display on the following screens:

EDI Error Queue

EDI Activity Log

Order Entry in SOE or POE

EDI Trading Partner Maintenance Please reference the screen name when communicating errors to Eclipse EDI Support. For each program that produces error messages, the glossary shows:

The message as it appears on the terminal screen.

A definition of the message.

The recommended course of action.

EDI Error Queue Maintenance Screen Errors The following errors display on the EDI Error Queue Maintenance screen: CANNOT OPEN EDI.OUT.STATUS -E9PERR The EDI.OUT.STATUS file does not exist, or permissions are incorrect. Contact Eclipse EDI Support for assistance. 5 - MAP SUBR -ECIERR: XXX.XXX.XXX.X NOT CATALOGED : XXX Mapping subroutine defined on EDI Group Profile Maintenance screen for this trading partner and document does not exist or has not been compiled. Verify that the mapping subroutine that has been defined is correct. If it isn't, correct it and requeue this document. If the routine is correct, contact Eclipse EDI Support so the mapper can be made available to you. 5 - NO MAPPING FOUND -ECIERR: XXX A mapping subroutine is not defined on the EDI Group Profile Maintenance screen for this trading partner and document type. You must set up and define a mapper for this document on the EDI Group Profile Maintenance screen for this trading partner. Then requeue this document. 5 - Partner Sub-ID Not Found -ECIERR : XXXX-XXX The bill-to or ship-to (N1-BT/N1-ST) data specified in the error message was not found in the EDI Group Profile Receive Code Info Table accessed from the EDI Group Profile Maintenance screen. You need to enter the bill-to or ship-to (N1-BT/N1-ST) data specified in the error message into the Receive Code Info Table screen for this trading partner. Then requeue this document. Doc Type Undefined -ECIERR: XXX Received document is an invalid or undefined type. Verify that the document type being sent to you is correct and that it is defined for this trading partner. After verification, if the problem still exists, contact Eclipse EDI Support for assistance. EDI Customer/Vendor : XXXX not on file -ECIERR

EDI_101_Packet.DOC


No customer or vendor account was found for the specified trading partner. The customer or vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. EDI Bill-To -ECLERR: XXXX not found The account specified on the EDI Trading Partner Profile Maintenance screen cannot be found. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. EDI Customer : XXXX not on file -ECLERR The account specified on the EDI Trading Partner Profile Maintenance screen cannot be found. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. EDI Customer Xref not found -ECLERR No customer Xref account was found for the specified trading partner. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. EDI Pay-To : XXXX not found -ECLERR The account specified on the EDI Trading Partner Profile Maintenance screen cannot be found. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. EDI Vendor : XXXX not on file -ECLERR No vendor account was found for the specified trading partner. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. Invalid Ship-From Br - ECLERR The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a ship-from account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. No EDI items found -ECLERR No valid line items were found on the received EDI order. The most likely cause for this error is that the individual line items on the incoming EDI document have a zero quantity or no part number. Determine if the problem is related to the quantity or part number and then contact your trading partner to have the problem corrected on their end. After fixing the problem, you can requeue the document from the Inbound Document Archive. Non Bill-To specified -ECLERR: XXXX The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a bill-to account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. Non Pay-To specified -ECLERR The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a pay-to account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document. Non Ship-To specified -ECLERR: XXXX The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a ship-to account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.

EDI_101_Packet.DOC


*** Bad Qty : XX - Set to 1 -ECLERR *** The received quantity specified in the quantity field of the line item is not a number. Contact your trading partner and have them correct the data that they are sending. 1 Entity ID not found. -OCLERR The entity specified on the EDI Trading Partner Profile Maintenance screen was not found. Contact Eclipse EDI Support for assistance. 2 No Items found. -OCLERR (Zero Qty) No items were found for which to create a ledger record. This is a possible mapper problem. Contact Eclipse EDI Support for assistance. 3 Ledger Record not found. -OCLERR The ledger record specified by the EDI document does not exist. Contact Eclipse EDI Support for assistance. 4 Ledger GEN not found. -OCLERR The generation specified by the EDI document does not exist. Contact Eclipse EDI Support for assistance. 5 Ledger Record locked. -OCLERR The requested ledger record is locked by another process and is not available. Contact Eclipse EDI Support for assistance. 6 Purchase Order # Wrong Format. -OCLERR The purchase order number specified by the EDI document is not in the correct format to be received by Eclipse. The purchase order number that your trading partner is sending you, which should be in Eclipse format, is not in the correct format. Contact your trading partner and have them correct the data they are sending. 7 Purchase Order # Already Exists. -OCLERR The purchase order number that the EDI document tried to create already exists on Eclipse. This could be caused by your trading partner trying to reuse a previously used purchase order number or resending a previously sent order. Contact your trading partner to have problem corrected. 1 - DOCUMENT TYPE XXX NOT FOUND -ECUERR The document type specified by this document was not found on the EDI Trading Partner Profile Maintenance screen for this trading partner. Before you can process this type of document for this trading partner, you must define it on the EDI Group Profile Maintenance screen for this trading partner. 1 - FUNCTIONAL GROUP XX NOT FOUND -ECUERR The functional group type received in the GS segment was not found in the EDI tables. Verify that your trading partner is sending a valid functional group type. 1 - NO TRADING PARTNER PROFILE FOUND -ECUERR: XXXX No trading partner profile could be found for the given interchange ID. Set up a trading partner profile for the given interchange ID. 1 - NON-NUMERIC CONTROL NO -ECUERR: XXXX The given control number cannot be updated because it is not in numeric format. Contact your trading partner and tell them that you can only accept numeric control numbers.

EDI_101_Packet.DOC


0 - BAD ISA -EUNERR There was something other than ISA found where the interchange control header was expected to start. This typically indicates data corruption in the file. Contact your trading partner to resend the transactions. 2 - BAD GE SEGMENT -EUNERR There was something other than GE found where the group footer was expected to start. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 2 - BAD GS SEGMENT -EUNERR There was something other than “GS” found where the group header was expected to start. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 2 - BAD TS COUNT IN GE SEGMENT -EUNERR XXXX/XXXX The number of transactions indicated in the “GE” segment does not match the number of transactions actually counted. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 2 - GROUP CONTROL# MISMATCH GS/GE -EUNERR: XXXX/XXXX The control number in the group header does not match the control number that was last received from your trading partner. This may indicate that you have missed a transmission from your trading partner. It often indicates that your trading partner does not send control numbers sequentially. Verify with your trading partner whether or not they send sequentially numbered control numbers, and proceed from there. 3 - NO SE FOUND -EUNERR There was no transaction footer found. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 3 - NO ST FOUND -EUNERR There was no transaction header found. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 3 - SEG COUNT MISMATCH IN SE -EUNERR: XXXX/XXXX The number of segments indicated in the “SE” segment does not match the number of segments actually counted. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 3 - TS CONTROL# MISMATCH ST/SE -EUNERR: XXXX/XXXX The control number in the transaction header does not match the control number that is in the transaction footer. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. 4 - Duplicate Recv Doc -EUNERR: XXX Duplicate control numbers have been received from a particular trading partner for a specific document type. Contact your trading partner and tell them which control numbers have been received in duplicate. Then ask them to verify whether or not it is a duplicate. If the document that was sent was not a duplicate, they must resend it with control numbers that have not yet been used. IEA FG COUNT # GROUP COUNT -EUNERR: XXXX-XXXX

EDI_101_Packet.DOC


The number of functional groups indicated in the “IEA” segment does not match the number of functional groups actually counted. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. Interchange Control# ISA/ISE mismatch -EUNERR: XXXX/XXX The control number in the interchange control header does not match the control number that is in the interchange control footer. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. No IEA Segment found !!! -EUNERR There was no interchange control footer found. This typically indicates the receipt of corrupted data from the network. Contact Eclipse EDI Support for assistance. After fixing the problem, you can requeue the document from the Inbound Document Archive.

EDI Activity Log Viewing Screen Errors The following errors display on the EDI Activity Log Viewing screen. Mapping Subroutine not Cataloged -ECDERR The mapping subroutine specified on the EDI Group Profile Maintenance screen does not exist or has not been compiled. Recheck the mapping subroutine you are using on the EDI Group Profile Maintenance screen. Make sure each zero and letter O is in the right place. No Mapping Defined -ECDERR No mapping subroutine entered for the specified EDI document on the EDI Group Profile Maintenance screen. Enter the appropriate mapping subroutine on the EDI Group Profile Maintenance screen for the trading partner. No Trading Partner Profile Defined -ECDERR A trading partner profile has not been set up on the EDI Trading Partner Profile Maintenance screen. Set up a trading partner profile for this trading partner. Trade Partner : XXXX not on file -ECDERR The trading partner does not exist on Eclipse. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Error in 852 Transmission -EP8ERR: XXX An error occurred while creating the 852 document. Contact Eclipse EDI Support for assistance.

Order Entry Screen (SOE or POE) Errors The following errors display on the Status screen of Sales Order Entry or Purchase Order Entry after changing the status to E and pressing Esc. Ledger Record not found -ECOERR: XXXXXXX The ledger record specified by EDI does not exist on Eclipse. Contact Eclipse EDI Support for assistance. Mapping Subroutine not Cataloged -ECOERR The mapping subroutine specified on the EDI Group Profile Maintenance screen for this trading partner does not exist or has not been compiled. Recheck the mapping subroutine you have entered on the EDI Group Profile Maintenance screen. Make sure each zero and letter O is in the right place. No Mapping Defined -ECOERR

EDI_101_Packet.DOC


No mapping subroutine has been defined on the EDI Group Profile Maintenance screen for the specified trading partner. Enter the appropriate mapping subroutine on the EDI Group Profile Maintenance screen for the trading partner. No Trading Partner Profile Defined -ECOERR No trading partner profile has been found in Trading Partner Profile Maintenance for the account specified on this order. Set up a trading partner profile for this trading partner. Transmission Aborted!!! -ECOERR The system returns this message if No is the response to the following prompt: This document has already been Transmitted - Continue (Y/N). No action is necessary. No Document specified -EDSERR No document type has been specified for the attempted transaction. Enter the appropriate document type on the EDI Group Profile Maintenance screen for the trading partner. No Mapping Defined -EDSERR No mapping subroutine has been defined on the EDI Group Profile Maintenance screen for the specified trading partner. Enter the appropriate mapping subroutine on the EDI Group Profile Maintenance screen for the trading partner. No Trading Partner Profile Defined -EDSERR No trading partner profile has been found in Trading Partner Profile Maintenance for the account specified on this order. Set up a trading partner profile for this trading partner. CANNOT OPEN EDI.STND.DE -EPDERR The EDI.STND.DE file does not exist, or permissions are incorrect. This file contains ANSI data element information. Contact Eclipse EDI Support for assistance. CANNOT OPEN EDI.STND.SEG -EPDERR The EDI.STND.SEG file does not exist, or permissions are incorrect. This file contains ANSI segment information. Contact Eclipse EDI Support for assistance. CANNOT OPEN EDI.STND.TS -EPDERR The EDI.STND.TS file does not exist, or permissions are incorrect. This file contains ANSI transaction set information. Contact Eclipse EDI Support for assistance. Branch EDI Group ID is not Defined -ESDERR The “GS” interchange ID is not defined in the EDI OUTGOING ID record in Control File Maintenance for the specified branch. Set up the interchange ID for the specified branch in Control File Maintenance under EDI OUTGOING ID. Branch EDI ISA ID is not Defined -ESDERR ISA interchange ID is not defined in Control File Maintenance under EDI OUTGOING ID for the specified branch. Set up the interchange ID for the specified branch in Control File Maintenance under EDI OUTGOING ID. Trading Partner not found -ESDERR: XXXX No trading partner profile was found in Trading Partner Profile Maintenance for the account specified on this order. Set up a trading partner profile for this trading partner.

EDI Trading Partner Maintenance Screen Errors The following errors display on the EDI Trading Partner Profile Maintenance screen. Ascii decimal value must be 255 or less

EDI_101_Packet.DOC


The three digit decimal value entered in the Separator/Sub-Separator field cannot be greater than 255. Re-enter the separator or sub-separator in the correct format. Entity already assigned to EDI group An entity can only be assigned to one EDI group. Enter a different entity or find the current trading partner profile that is linked to that entity and delete it. Single character or 3 digit decimal value for ascii character The value placed in the Separator/Sub-Separator field must be either the character used as the separator or its three-digit decimal-value ascii equivalent. Re-enter the separator or sub-separator in the correct format. There Are Still Active Groups. Delete Them First You cannot delete a trading partner profile until all groups belonging to that profile have been deleted. Go to the EDI Group Profile Maintenance screen and delete all groups. Then go back to the EDI Trading Partner Profile Maintenance screen and delete the profile. Wrong Format. Use Qualifier Tilde ID. ex 01-12345 The trading partner ID number must be entered in this format. Enter the trading partner ID number in the correct format. You Must Delete Through Group Maintenance. Press <Enter> A group cannot be deleted from the EDI Trading Partner Profile Maintenance screen. Go to the EDI Group Profile Maintenance screen to delete the group. Group is not in file. When using the Copy Profile command, the group profile you are attempting to copy must exist. Verify that the group ID you are entering exists in a trading partner profile. ISA ID is not in file. When using the Copy Profile command, the ISA ID you are attempting to copy must exist. Verify that the ISA ID you are entering exists in a trading partner profile. You cannot copy a group from itself When using the Copy Profile command, you must enter the group whose profile you are copying, not the group receiving the profile. Verify the source group and target group. Duplicate <Press Enter> The entity being entered has already been entered. Enter a different entity. Entity already assigned to EDI group An entity can only be assigned to one EDI group. Enter a different entity. PT Acct# Must Match First PT Acct# The pay-to account being entered does not match the first pay-to account entered. Re-enter the correct pay-to account.

Eclipse EDI Support Documentation Table of Contents...EDI_101_Packet.DOC Updated 2/9/2017 Page 9 of...

Documents

Transcript of Eclipse EDI Support Documentation Table of Contents...EDI_101_Packet.DOC Updated 2/9/2017 Page 9 of...