Once EDI (Electronic Data Interchange) has been enabled for LMC (Lumbermens Merchandising Corporation), the next step is to configure the EDI settings for communication with the vendor. These settings are typically completed by support personnel; however, someone at your company may have to supply some of the information. Setup is done from the Branch Setup maintenance form which is accessed from the Maintenance area's Database menu. In addition to this setup, there is also mapping overrides, X12 IDs, and automation options available from the menu marker icon's ()context menu.

Settings for:

Select the wholesaler ID for the EDI option ("LMC" in this case). EDI options must be enabled by support, and only enabled EDI options are listed. This same code must be assigned to the vendor you use for LMC.

Account Number

The account number for your store (location) assigned by LMC.

Login

The "login" is used for electronic access to your mailbox and is usually different from the account. This information would be provided by LMC.

Password

This is the password provided for electronic access to your mailbox.

Warehouse Code

Not applicable.

Template Item

The template item is used for any new items added by EDI processing. For example, if you order an item from the vendor that you don't stock, the item may be added automatically upon receipt. The "template" provides the settings that the vendor would does not. Catalog information, when available, is also used when adding new items.Typically, new items need to be reviewed and modified to update their group/section, or other aspects as needed. You can use any SKU for the template item code, it does not have to match our example.

Base Pathname

This directory (folder) is a physical path on the local computer or a mapped drive and is important for many EDI functions. If a directory is specified that does not exist, the application will prompt the user when necessary to add it; however, this only applies to processing that is user initiated and not those that are automated.

For locally installed (not hosted) applications, the path name is a directory on the user's local computer or a mapped drive to a network share directory (on the server or another computer). This would usually only be done if EDI was being processed from different locations (computers) and you wanted to have all of the data files kept in the same location. Directory names can vary from our examples.

An additional directory, indicating the branch location, should be used any time the company has more than one location using the same EDI option; otherwise, there is a possibility that operations will conflict with each other causing another user's data to be overwritten.

C:\WSTieIn\{EDIName}\1000

For our cloud hosted systems, the path should be a UNC path name to a shared directory (folder) on the hosted servers. In some cases, it is instead a mapped drive that is automatically added when the user connects to the hosted environment. The UNC path will vary for each customer and point to their specific share directory (see below for an example).

\\server-name\SHARE\SharedFolders\ANYSupplyCo\EDI\{EDIName}\1000

 

When using a physical drive path, the letter of the drive may vary, but is usually either "R" or "S." It's best if letters for user's mapped drives do not conflict with any physical drive found on the server. For example, for servers where a physical drive of "R" exists, it's best to map the "local" drive to another letter. Both the drive letter, and path name, will be set for cloud hosted customers (this only applies to companies hosted by ECI Software Solutions, Inc.). An example is provided below:

R:\EDI\{EDIName}\1000

Some EDI operations run automatically and are initiated by services running on the server. In these cases, a physical path cannot be used (and the "mapped" drive won't exist). For this reason, there is a "services base path name" override found in the Automation dialog available from the context menu on the EDI tab of the Branch Setup form (Main Menu > Maintenance > Database > Branches). The services base path name resolves to the same location but is the UNC path name to that location.

Send Program

To enable sending (transmission) of data via the Internet (web) using FTP (File Transfer Protocol), you must set the SendProgram value to the file path to the LMCSendNEW.bat file as shown in the image example (near the beginning of this topic). If more than one "LMCSend" file exists in the EDIScripts directory, use the "New" one only. Their server address has changed and the old file will not work. The "EDIScripts" directory and .BAT file are located in the Library folder under the application's installation directory. The default installation directory for the application is listed below (this will be different for cloud hosted companies as well as companies who have more than one installation of the software on their server):

C:\SpruceWare.NET\Library\EDIScipts\LMCSendNew.bat

Recv Program

To enable retrieval (download) of data via the Internet (web) using FTP (File Transfer Protocol), you must set the RecvProgram value to the file path to the LMCRecvNEW.bat file as shown in the image example (near the beginning of this topic). If more than one "LMCRecv" file exists in the EDIScripts directory, use the "New" one only. Their server address has changed and the old file will not work. The "EDIScripts" directory and .BAT file are located in the Library folder under the application's installation directory.The default installation directory for the application is listed below (this will be different for cloud hosted companies as well as companies who have more than one installation of the software on their server):

C:\SpruceWare.NET\Library\EDIScipts\LMCRecvNew.bat

Upload Directory

Not required.

Download Directory

Not required.