Import Sales Orders

Field Name

Type / Max Length

Action / Description

Name of file to import

Required
45 alphanumeric

Enter the name of the file (up to 8-characters) if it resides on a native disc or enter the full path name including the file extension (e.g., C:\My documents\CMX.XML or U:\IMPORT\VMX.XML where U: is a mapped network drive) if the file is on your PC or network.

If the PC file is not found or if the file resides on a native disc, the program prompts to check for a sequential file. Click Yes if you entered the file name correctly or click No to re-enter the name of the file to import.

By default, the last file imported is displayed. To exit to the menu, clear the field and press Enter or Tab.

Name of batch file

Required
5 alphanumeric

Enter a batch name for this file. This name is associated with this file until import is complete.

D=Delimited or F=Fixed length

Required
1 alphanumeric

Select D if the file uses a delimiter or select F if fields are a fixed length.

If you import data from an ASCII file generated from Microsoft Excel, fields are a fixed length.

Field delimiter

Conditional
1 alphanumeric

If you selected D for D=Delimited, enter the field delimiter used in this file; for example T for tab, a ; (semicolon), or a , (comma).

Qantel Technologies recommends the semicolon delimiter because address and comment fields can include commas.

If the EDI Order Log reports the Invalid record type message for every order header and line, you entered the wrong delimiter.

Sales branch

Required

Select the branch to use if the ASCII file does not have a sales branch in the order header.

The program allows you to import orders regardless of branch or whether the branch is in your inventory group. However, you should import orders for each branch in a separate batch.

Use existing line numbers

Optional

Select to use the line numbers assigned in the ASCII file or leave blank to assign line numbers.

Select this option if your imported orders have line numbers that are not sequential. If imported line numbers have leading zeros, Order Import strips them.

If you select and the ASCII file does not include line numbers, the program assigns them and generates an error in the EDI Order Log.

If you leave blank, the program assigns line numbers, starting with 1.

Skip price validations

Optional

Select if you do NOT want to validate item pricing during order import or leave blank to validate prices in the file against prices set up in the system.
If you select, you must also select Always use EDI pricing, Always user system pricing, or Use system price if EDI price is zero.

If you leave blank, performance may be slower. Not only does validation take more time, but the program writes a message to the log file for each price variance. This includes when the price in the import file is blank or zero. The system places orders that have a price variance on hold.

Always use EDI pricing

Conditional

Select to use the price from the customer's ASCII file to populate the offline sales order line selling price.

Always use system pricing

Conditional

Select to ignore the price in the ASCII file and use the price that you set up for the customer, item, and quantity in the Price-Contract Maintenance (PCM) program to populate the offline sales order line selling price.

Use system price if EDI price is zero

Conditional

Select to use the price  from the customer's ASCII file unless the price is zero. In that case of zero prices in the ASCII file, use the price that you set up for the customer, item, and quantity in the Price-Contract Maintenance (PCM) program to populate the offline sales order line selling price.

If you select this option, pricing errors are included in the EDI Order Log, but orders that have pricing errors are not placed on hold.

Erase import file when done?

Optional

Select to erase the file after import or leave blank to retain it.

Use hdr date if line date blank?

Optional

Select to default line dates (Date wanted, Date promised, and Expected ship) to the Date wanted on the order header if the file has no line dates or leave blank to use your User transaction date for the current session.

The Date wanted offset in days (also Date promised and Date expected) are calculated after these fields are set. Date entered is always your User transaction date.

Adjustment window in days

Required
3 numeric

Enter the number of days in the adjustment window. This number together with the login date determines the range of dates for which the Date wanted, Date promised, and Expected ship offsets are applied.

For example, if today is February 1 and the adjustment window is 5 days, the offset applies to dates in the 02/01 to 02/05 range. The offset is not applied to any dates outside this range. The dates in the adjustment window do not have to be on the shop calendar.

Date wanted offset in days

Required
3 numeric

Enter the number of days that you want the Date wanted to be offset for dates within the adjustment window.

For example, if you enter -5, the Date wanted moves backward five days. If the window is from 02/01 to 02/05 and the Date wanted on an order is 02/05, it is changed to 02/01.

Date promised offset in days

Required
3 numeric

Enter the number of days that you want the Date promised to be offset within the adjustment window.

For example, if you enter -10, the Date promised moves backward 10 days. If the window is from 02/01 to 02/14 and the Date promised on an order is 02/14, it is changed to 02/04.

Date expected offset in days

Required
3 numeric

Enter the number of days that you want the Expected ship date to be offset within the adjustment window.

For example, if you enter -10, the Expected ship moves backward 10 days. If the window is from 02/01 to 02/14 and the Expected ship on an order is 02/10, it is changed to 02/01.

Reason for order close?

Optional

Select the default reason for order cancellation. The default is used if there is no reason code in the import file. See Reason Codes Maintenance (TRCM).