New Customer Mailbox Creation in EDI

New Customer Mailbox Creation in EDI

Introduction

If EDI mail comes in for a new trading partner, or an existing trading partner using a different ID#, this data will create a new, separate mailbox. When this happens, a screen will appear prompting the user to fill out the mailbox details.

It is important to note that if a mailbox is not created right away and there are other transactions to be received, this mail will not be received. As soon as the mailbox is not created, it stops retrieving the other files, which explains why there can be other PO's that are not found in the mailbox.

This wiki will show the user how to create a mailbox for a new customer in the EDI subsystem.


Setup

In EDI, go to:

  • Communications

  • Retrieve Mail


Click on "Yes" to proceed with retrieving mail.

A print option will immediately follow, asking if you want to print the EDI data retrieved. Printing the data is entirely up to the user.



In the From field, enter the Trading Partner's name.

In the Map Name field, select the proper mappings from the drop down menu.

Notes:

  • If you do not see the appropriate map name, it is most likely because this is a new trading partner where the programs have not been installed. Please contact jonar.

  • If you are unsure who this new mailbox is from, one trick is to note the INTERCHANGE. Sometimes this will be a name, easily identifying the trading partner, but if it is a number, type that number in google - odds are the results will tell you exactly who this is from!

Click on OK to continue


A set mail screen will prompt you to set the parameters for the new mailbox.

Company:

  • The JAS data company to be used for this trading partner / mailbox.

From:

  • This is the customer account code to be used with this mailbox.

  • Select the appropriate company.

  • The adjacent field will automatically populate itself according to the company selected.


Manufacturer Code:

  • Input the UPC digits by which the company is organized (it is usually the first six digits of the government issued UPC code for the company).

In the Ack Type field, you have the option to set it to either "Detail" or "Summary".

  • Select "Detail" (this should be the default).


When the fields have been fully entered, click on OK to proceed.

Afterwards, a Functional Acknowledgement (FA - 997) will automatically be generated.

This is done in order to document the creation of the new mailbox for validation purposes within the EDI subsystem.


You will then receive a notice saying that the mailbox has been created along with a unique numeric value identifying the mailbox in the EDI subsystem.

Click on Proceed to move on to the Mailbox Variables Setup.


In the Mailbox Settings tab, first make sure the AS2 Mailbox box has been checked off.

This is the default mailbox type (it is important to maintain consistency across different mailboxes in order to ensure that the EDI subsystem is able to effectively conduct operations).


Select the "Mailbox Variable Settings - 2" tab.

Make sure that the AS2 inbox and outbox have been defined (the outbox is especially important to set up).

The default file paths should have the same network locations, differentiated only by separate "in" and "out" folders in the last file category (notice the extensions "ext." next the the fields for the AS2 inbox and outbox).

Once you have finished, click on Update/Exit to proceed.


Important note: The specific paths above are just for demonstration purposes. The path entered should be specific path that your company uses.


A notice will appear asking if you want to send the previously generated Functional Acknowledgements Now or Later.

Your selection should be based on the arrangements in place with the customer.


Finally, one last notice will appear saying that the end of the process has been reached.

Now, the new mailbox is now ready to operate.


    • Related Articles

    • Associated Mailbox

        Introduction In EDI, ASN transactions might be sent through two different but identical mailboxes (they have the same sender and receiver ID's) from 1 trading partner. The result will be that the user will receive a message "the set count is ...
    • Procedure for moving JAS to a new server

      Introduction This document explains the general steps a user should take to move JAS and EDI onto a new server. Instructions Step 1. Copy over files onto the new server For JAS Locate the drive where your JAS is installed on, create the same letter ...
    • 2019 T4 XML Format - Preparation and Creation

      Introduction If you have over 50 employees, it is mandatory to submit your forms in XML format. Paper forms are no longer accepted by the government.  This wiki will explain the steps from the initial setup to submitting the file to the government. ...
    • 2019 Quebec XML Format - Preparation and Creation

      IntroductionIf you have over 50 employees, it is mandatory to submit your forms in XML format. Paper forms are no longer accepted by the government. This wiki will explain the steps from the initial setup to submitting the file to the government. ...
    • Moving JSI, EDI, & JAS Data from Aims

      Introduction The following document explains the steps that must be followed in JAS to move data from the aims directory to the main JAS directory. What to do for JAS Step 1: Locating the drives Locate the drive where your JAS is installed on, as ...