EDI Configuration
The setup and management of EDI (Electronic Data Interchange) trading partners takes place in the EDI section of the Configuration Manager (File → Configuration Management → EDI).
To create a new EDI Partner
- File → Configuration Management → EDI → Trading Partners.
- Click New.
Continue populate the applicable fields based on the information below.
System Defaults
Each EDI trading partner is setup in the Trading Partners section. To make the configuration of multiple trading partners easier, defaults can be set. System Defaults can only be defined for one type of trading partner, either Customer or Warehouse. Unless you enter different configuration information for a trading partner, the trading partner will use the System Defaults settings.
System Options
Partner Option
The Partner Options tab allows you to define defaults that can be used by other EDI partners.
Field |
Field Type/ Length |
Definition |
Trading Partner Type |
List |
You can set system defaults for either customer or warehouse trading partners. These defaults can be used by other trading partners of the same partner type. |
Partner ID |
Text / 15 Characters |
The Partner ID for <system> cannot be changed. |
Partner Name |
Text / 50 Characters |
The Partner Name for <system> cannot be changed. |
Partner Vendor ID |
Text / 15 Characters |
The Partner Vendor ID will match the database name and cannot be edited. |
Advanced System Options
Clicking the Show Advanced button will reveal advanced configuration options.
Partner Options
Field |
Field Type/ Length |
Definition |
Partner Qualifier |
Text / 2 Characters |
|
Logging Level |
List |
This option can only be set for the partner, but applies to all partners. Logging entries can be found in the Acctivate Logs.- Information
- Warnings: Warnings and greater events (e.g. Errors) encountered in the Process EDI window are logged in the Acctivate Exception Log.
- Errors: Errors and greater events encountered in the Process EDI window are logged.
- Exceptions: Only exception errors are logged.
|
Our Qualifier |
Text / 2 Characters |
Our Qualifier cannot be changed; it will always be "ZZ". |
Our ID |
Text / 15 Characters |
The Partner Vendor ID will match the database name and cannot be edited. |
Usage |
List |
|
Consolidate Shipments |
Checkbox |
When checked, orders being shipped to the same location will be consolidated into single shipments during the Create Shipments step. |
Incoming Files
Field |
Field Type/ Length |
Definition |
Mailbox Path |
Text / 256 Characters |
The file path where files from your VAN (Value Added Network) will be deposited for Acctivate to import. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. These behave as a variable that Acctivate will use to match the correct file: - %PARTNERID%: If this File Mask is entered, Acctivate will only import in files that have the Partner ID in the filename. For example, if the Partner ID is "ABC", then only files formatted as "ABC.{FileExtension}" will be imported.
- %TRANSACTIONID%: If this file mask is used, Acctivate will only import in files with the name
850 (the 850 EDI Transaction is the only transaction type Acctivate imports). - %BRANCHID%: Not Used.
You can use an asterisk as a wildcard. For example, if the Partner ID is "ABC" and the mailbox path is set to %PARTNERID&* , any filename that starts with "ABC" will be imported in. For example "ABC20200101.txt" |
File Extension |
Text / 50 Characters |
You can define a specific file extension to be matched during the import, such as txt , or you can enter an asterisk (* ) to act as a wildcard and match on all file extensions. |
Outgoing Files
Field |
Field Type/ Length |
Definition |
Mailbox Path |
Text / 256 Characters |
The file path where files exported from Acctivate will be deposited. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to create a file name: - %PARTNERID%: This File Mask adds the EDI Partner ID to the file name.
- %TRANSACTIONID%: This variable adds the Transaction ID (856, 810, 940) to the file name.
- %FILESTAMP%: This variable adds a sequentially incrementing 8 digit number to add uniqueness t the file name..
- %TIMESTAMP%: This variable is used to add a timestamp to the file name, formatted as yyyyMMddHHMMSS.
- %BRANCHID%: This variable is only used with 940 Transaction File. If this variable is used, Orders will be exported into different files for each Sales Order Branch.
|
File Extension |
Text / 50 Characters |
You can define a specific file extension to be used for the exported file. The default extension is txt . |
FTP Options
Acctivate supports downloading files from and exporting to FTP (File Transfer Protocol) Folders. Your VAN (Value Added Network) or trading partner will need to setup and host the folders as well as provide you with connection credentials. The connection credentials can be entered on the FTP Options tab. You can use the Test Download and Test Upload to confirm a successful connection. In both instances a test file with arbitrary text will uploaded/downloaded.
The transmission of EDI Files to and from an FTP folder still requires setting up incoming and outgoing mailbox paths on your local network. When opening the Process EDI window in Acctivate, files are first downloaded a copy of the file from the FTP Server In directory to the local incoming mailbox path configured. During the export process, Acctivate will export the EDI transaction file to the local outgoing mailbox path configured, then it will upload a copy of the file to the FTP Server Out directory. A copy of all incoming and outgoing files will remain on your local network.
Field |
Field Type/ Length |
Definition |
FTP Service Provider |
Text / 32 Characters |
A description of the FTP Service Provider, typically the VAN or host of the FTP folder. Used for descriptive purposes only |
FTP Enabled |
Checkbox |
If checked, Acctivate will download files from the FTP Server In folder into the Incoming Mailbox, then import the files into Acctivate. Likewise, Acctivate will export files to the Outgoing Mailbox location, then upload the files to the FTP Server Out folder. If unchecked, files are only imported/exported to the incoming/outgoing mailbox on your network. |
FTP Server In |
Text / 256 Characters |
The FTP path that EDI Transaction files will be downloaded from. Format example: ftp://ftp.<servername><.com|.net>/<directoryname> |
FTP Server Out |
Text / 256 Characters |
The FTP path that EDI Transaction files will be uploaded to. Format example: ftp://ftp.<servername><.com|.net>/<directoryname> |
Tip
The default port for FTP connections is port 21. To use a port other than the default, include the port number you wish to use after the server name.
For example, to use port 2121, change the FTP server path to ftp://ftp.servername.com:2121/out
Note
The Add/Remove Item and Add/Remove Transaction aren't available to be set for the trading partner. Click Show Advance to see additional options.
New Partner Setup
You can create a new Trading Partner, however once created it cannot be deleted and will count against the number of trading partners you're licensed for. To create a new trading partner, follow these initial steps:
- Go to File→ Configuration Management→ EDI→ Trading Partners.
- Click New.
- Select Customer or Warehouse for the Trading Partner Type.
- Enter the Partner ID and Partner Name.
- Click Save
Partner Options
The Partner Options tab allows you to define basic information for this trading partner.
Field |
Field Type/ Length |
Definition |
Trading Partner Type |
List |
The following options are available: - Customer: Select this option if the trading partner is a customer you sell products to.
- Warehouse: Select this option if the trading partner is a third party logistics firm (3PL) that ships your sales orders.
|
Partner ID |
Text / 15 Characters |
The Partner ID for the trading partner. If using a Value Added Network (VAN), they will typically supply this ID. |
Partner Name |
Text / 50 Characters |
The user friendly name for the Trading Partner. |
Partner Vendor ID |
Text / 15 Characters |
The Partner Vendor ID will match the database name and cannot be edited. |
Advanced Partner Options
Clicking the Show Advanced button will reveal advanced configuration options.
Field |
Field Type/ Length |
Definition |
Partner Qualifier |
Text / 2 Characters |
|
Our Qualifier |
Text / 2 Characters |
Our Qualifier cannot be changed; it will always be "ZZ". |
Our ID |
Text / 15 Characters |
The Partner Vendor ID will match the database name and cannot be edited. |
Usage |
List |
|
Consolidate Shipments |
Checkbox |
When checked, orders being shipped to the same location will be consolidated into single shipments during the Create Shipments step. Applies to Customer trading partners only. |
Incoming Files
Any fields that are populated will apply to this trading partner. If a field is left blank, Acctivate will use the trading partner, if the field is filled in there.
Field |
Field Type/ Length |
Definition |
Mailbox Path |
Text / 256 Characters |
The file path where files from your VAN (Value Added Network) will be deposited for Acctivate to import. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. These behave as a variable that Acctivate will use to match the correct file: - %PARTNERID%: If this File Mask is entered, Acctivate will only import in files that have the Partner ID in the filename. For example, if the Partner ID is "ABC", then only files formatted as "ABC.{FileExtension}" will be imported.
- %TRANSACTIONID%: If this file mask is used, Acctivate will only import in files with the name
850 (the 850 EDI Transaction is the only transaction type Acctivate imports). - %BRANCHID%: Not Used.
You can use an asterisk as a wildcard. For example, if the Partner ID is "ABC" and the mailbox path is set to %PARTNERID&* , any filename that starts with "ABC" will be imported in. For example "ABC20200101.txt" |
File Extension |
Text / 50 Characters |
You can define a specific file extension to be matched during the import, such as txt , or you can enter an asterisk (* ) to act as a wildcard and match on all file extensions. |
Outgoing Files
Any fields that are populated will apply to this trading partner. If a field is left blank, Acctivate will use the trading partner, if the field is filled in there.
Field |
Field Type/ Length |
Definition |
Mailbox Path |
Text / 256 Characters |
The file path where files exported from Acctivate will be deposited. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to create a file name: - %PARTNERID%: This File Mask adds the EDI Partner ID to the file name.
- %TRANSACTIONID%: This variable adds the Transaction ID (856, 810, 940) to the file name.
- %FILESTAMP%: This variable adds a sequentially incrementing 8 digit number to add uniqueness t the file name..
- %TIMESTAMP%: This variable is used to add a timestamp to the file name, formatted as yyyyMMddHHMMSS.
- %BRANCHID%: This variable is only used with 940 Transaction File. If this variable is used, Orders will be exported into different files for each Sales Order Branch.
|
File Extension |
Text / 50 Characters |
You can define a specific file extension to be used for the exported file. The default extension is txt . |
FTP Options
Acctivate supports downloading files from and exporting to FTP (File Transfer Protocol) Folders. Your VAN (Value Added Network) or Trading Partner will need to setup and host the folders as well as provide you with connection credentials. The connection credentials can be entered on the FTP Options tab. You can use the Test Download and Test Upload to confirm a successful connection. In both instances a test file with arbitrary text will uploaded/downloaded.
The transmission of EDI Files to and from an FTP folder still requires setting up incoming and outgoing mailbox paths on your local network. When opening the Process EDI window in Acctivate, files are first downloaded a copy of the file from the FTP Server In directory to the local incoming mailbox path configured. During the export process, Acctivate will export the EDI transaction file to the local outgoing mailbox path configured, then it will upload a copy of the file to the FTP Server Out directory. A copy of all incoming and outgoing files will remain on your local network.
Tip
If you want this trading partner to use the FTP settings configured for the trading partner, you only need to check the FTP Enabled checkbox.
Field |
Field Type/ Length |
Definition |
FTP Service Provider |
Text / 32 Characters |
A description of the FTP Service Provider, typically the VAN or host of the FTP folder. Used for descriptive purposes only |
FTP Enabled |
Checkbox |
If checked, Acctivate will download files from the FTP Server In folder into the Incoming Mailbox, then import the files into Acctivate. Likewise, Acctivate will export files to the Outgoing Mailbox location, then upload the files to the FTP Server Out folder. If unchecked, files are only imported/exported to the incoming/outgoing mailbox on your network. |
FTP Server In |
Text / 256 Characters |
The FTP path that EDI Transaction files will be downloaded from. Format example: ftp://ftp.<servername><.com|.net>/<directoryname> |
FTP Server Out |
Text / 256 Characters |
The FTP path that EDI Transaction files will be uploaded to. Format example: ftp://ftp.<servername><.com|.net>/<directoryname> |
Additional EDI Partner Options can be found in the grid when viewing Advanced options. Applies to Customer trading partners only.
Option Name |
Setting |
PackagingOption |
There are three packaging options that apply to the Create Shipment process: - Automatic: When shipments are created, the products will be packaged into individual cartons automatically based on their packaging unit.
- Single Carton: When shipments are created, all products are packaged into a single carton.
- No Auto Packaging: When shipments are created, the products are not packaged automatically. The user must package the products into cartons.
|
StoreAsAlternateCustID |
Acctivate CYMA Edition Option. If this option is enabled, the location ID in the 850 will be compared against the Alternate Customer ID for customers associated with the trading partner. The customer that has the matching Alternate Customer ID that matches the Location ID will be selected. |
Assigned To
You can assign this trading partner to one or more customers in Acctivate (you must hide click Hide Advanced to hide the advanced options and see this option):
- Go to File→ Configuration Management→ EDI→ Trading Partners.
- Click Edit.
- Click +Add Item and select the Customer or Warehouse (depending on the Trading Partner Type).
- When prompted if you want to continue, select OK.
- If necessary, repeat again.
- Click Save.
Note
If the same Trading Partner ID is assigned to multiple customers in Acctivate, the Acctivate customer with the Location ID that matches the 850 Ship To Location ID will be used.
Customer Transactions
For trading partners that are customers, we support importing in Customer Purchase Orders (850 EDI Transaction) and exporting Customer Advance Ship Notices (856) and Customer Invoices (810). You can add a transaction for the Customer trading partner by clicking +Add Transaction (you must hide click Hide Advanced to hide the advanced options and see this option):
- Customer Purchase Orders (850):
The Customer Purchase Order (850 EDI Transaction) is a purchase order submitted to you from your customer. Customer Purchase Orders are imported in as your sales order.
- Customer Advance Ship Notice (856):
The Customer Advance Ship Notice (856 EDI Transaction) is a transaction exported from Acctivate containing shipment data.
- Customer Invoice (810):
The Customer Invoice (810 EDI Transaction) is a transaction exported from Acctivate containing sales invoice data.
Customer Purchase Order
Once the Customer Purchase Order transaction has been added a new Customer Purchase Order tab will appear. Configuration options specific to the Customer Purchase Order (850 EDI Transaction) are defined here:
Field |
Field Type/ Length |
Definition |
Enabled |
Checkbox |
If checked, Acctivate will attempt to import in available 850 transaction files for this trading partner. |
Mailbox Path |
Text / 256 Characters |
The file path where files will be imported in from If left blank, the Mailbox Path in the Partner Options section will be used. If that is blank, the Mailbox Path for the trading partner will be used. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to identify files to import in: - %PARTNERID%: When this File Mask is used, only files that have the Partner ID in the name will be imported in.
- %TRANSACTIONID%: When this File Mask is used, only files that have the transaction type "850" in the name will be imported in.
- %BRANCHID%: This variable is not used.
If left blank, the Mailbox File Mask in the Partner Options section will be used. If that is blank, the Mailbox File Mask for the trading partner will be used. |
File Extension |
Text / 50 Characters |
You can define a specific file extension to be matched during the import, such as txt , or you can enter an asterisk (* ) to act as a wildcard and match on all file extensions. If left blank, the File Extension in the Partner Options section will be used. If that is blank, the File Extension for the trading partner will be used. |
Additional EDI Customer Purchase Order Options can be found in the grid on this tab.
Option Name |
Setting |
IgnoreUOM |
- Checked: If checked, the sales order unit in the 850 file will be ignored and the default sales unit in Acctivate will be used instead.
- Unchecked: If unchecked, the sales order unit of measure in the 80 will be used.
|
ProductSearchOrder |
An 850 transaction file can contain up to three different product identifiers: Customer Product ID, Buyer Product ID and Vendor Product ID. Acctivate can compare these against various Acctivate product identifiers to make a match. The 850 data can be compared to the Customer Product ID, Product ID, UPC and Alternate Product ID. The sequence in which these are searched can be changed by reordering the values, though the default is recommendedCustomerProductID=@EDI_BP : Acctivate will attempt to match the Buyer Product ID (Header Row, Position 4 of the 850) to a Customer Specific Product ID.ProductID=@EDI_VP : Acctivate will attempt to match the Vendor Product ID (Header Row, Position 3 of the 850) to a Product ID.UPC=@EDI_UP : Acctivate will attempt to match the UPC (Header Row, Position 5 of the 850) to a Product UPC.AlternateProductID=@EDI_VP : Acctivate will attempt to match the Vendor Product ID (Header Row, Position 3 of the 850) to an Alternate Product ID.
|
ShipToDistributionCenter |
When enabled, a customer's Ship To EDI configuration will be evaluated when an 850 transaction does not have a Ship To location, but includes a Mark for Store location. If disabled, the Mark for Store location will be used as the Ship To location when no Ship To location is included in the 850 transaction file. |
SetPriceUnit |
- Checked: It is recommended this option is enabled as well as the 810 option "ExportInSalesUnit". If checked, the sales order unit in the 850 file will be also used for the sales price unit.
- Unchecked: If unchecked, the sales price on the 850 will use the list price unit assigned to the product in Acctivate.
|
Customer ASN
Once the Customer Advance Ship Notice (ASN) transaction has been added a new Customer Advance Ship Notice tab will appear. Configuration Options specific to the ASN (856) are defined here:
Field |
Field Type/ Length |
Definition |
Enabled |
Checkbox |
If checked, Acctivate will attempt to export available 856 transaction data for this trading partner. |
Mailbox Path |
Text / 256 Characters |
The file path where files exported from Acctivate will be deposited. If left blank, the Mailbox Path in the Partner Options section will be used. If that is blank, the Mailbox Path for the trading partner will be used. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to create a file name: - %PARTNERID%: This File Mask adds the EDI Partner ID to the file name.
- %TRANSACTIONID%: This variable adds the Transaction ID (856, 810, 940) to the file name.
- %FILESTAMP%: This variable adds a sequentially incrementing 8 digit number to add uniqueness t the file name..
- %TIMESTAMP%: This variable is used to add a timestamp to the file name, formatted as yyyyMMddHHMMSS.
- %BRANCHID%: If this variable is used, Invoice will be exported into different files for each Sales Order Branch.
If left blank, the Mailbox File Mask in the Partner Options section will be used. If that is blank, the Mailbox File Mask for the trading partner will be used. |
File Extension |
Text / 50 Characters |
You can define a specific file extension to be used for the exported file. The default extension is txt . If left blank, the File Extension in the Partner Options section will be used. If that is blank, the File Extension for the trading partner will be used. |
Additional EDI Customer Advance Ship Notice Options can be found in the grid on this tab.
Option Name |
Setting |
IncludeSSCCAI |
- Checked: If checked, the 18 digit SSCC-18 Package ID will include the two digit "00" Application Identifier..
- Unchecked: If unchecked, the 18 digit SSCC-18 Package ID will be exported without the two digit application identifier.
|
ShipmentStructure |
Different trading partners may require the ASN Transaction be formatted differently. Acctivate can generate the 856 Transaction File in three different formats:- Pick & Pack (SOPI): With this structure, the Shipment information is listed, then the Order information, then the Package information, then the Item information. This is also commonly referred to as "Pick and Pack" as a package may contain multiple different products.
- Standard Pack (SOIP): SOIP lists the Shipment information, Order information, item information and then Pack information.
- No Pack (SOI): The SOI structure lists the Shipment information, Order information and then item information. There is no package information included.
|
Customer Invoice
Once the Customer Invoice transaction has been added a new Customer Invoice tab will appear. Configuration Options specific to the Invoice (810) are defined here:
Field |
Field Type/ Length |
Definition |
Enabled |
Checkbox |
If checked, Acctivate will attempt to export available 810 transaction data for this trading partner. |
Mailbox Path |
Text / 256 Characters |
The file path where files exported from Acctivate will be deposited. If left blank, the Mailbox Path in the Partner Options section will be used. If that is blank, the Mailbox Path for the trading partner will be used. |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to create a file name: - %PARTNERID%: This File Mask adds the EDI Partner ID to the file name.
- %TRANSACTIONID%: This variable adds the Transaction ID (856, 810, 940) to the file name.
- %FILESTAMP%: This variable adds a sequentially incrementing 8 digit number to add uniqueness t the file name..
- %TIMESTAMP%: This variable is used to add a timestamp to the file name, formatted as yyyyMMddHHMMSS.
- %BRANCHID%: If this variable is used, Orders will be exported into different files for each Sales Order Branch.
If left blank, the Mailbox File Mask in the Partner Options section will be used. If that is blank, the Mailbox File Mask for the trading partner will be used. |
File Extension |
Text / 50 Characters |
You can define a specific file extension to be used for the exported file. The default extension is txt . If left blank, the File Extension in the Partner Options section will be used. If that is blank, the File Extension for the trading partner will be used. |
Additional EDI Customer Invoice Options can be found in the grid on this tab.
Option Name |
Setting |
ExportInSalesUnit |
- Checked: It is recommended this option is enabled as well as the 850 option "SetPriceUnit". If checked, the invoice detail quantity (810 I row, position 7), unit of measure (810 I row, position 8), and unit price (810 I row, position 9) will be exported in the sales quantity's unit.
- Unchecked: When unchecked, the quantity and unit of measure will be exported in the product's stocking unit. The unit price will be calculated as the unit price of the invoice divided by the stocking units shipped.
|
InvoiceSelection |
- EDI Only: If this option is selected, only invoices created for orders that originated through the EDI import will be transmitted to the trading partner.
- Include All: All invoices for the customer will be transmitted, regardless of origin.
|
Warehouse Transactions
For Trading Partners that are Warehouses (3PL), we support exporting the Warehouse Shipping Order (940 EDI Transaction) and importing in the Warehouse Shipping Advice (945 EDI Transaction). You can add a transaction for the Warehouse trading partner by clicking +Add Transaction (you must hide click Hide Advanced to hide the advanced options and see this option):
- Warehouse Order (940):
The Warehouse Shipping Order (940 EDI Transaction) is a transaction that is sent to your third party logistics (3PL) firm containing order information that needs to be shipped to your customers.
- Warehouse Shipment (945):
The Warehouse Shipping Advice (945 EDI Transaction) is a transaction that is returned from your third party logistics (3PL) firm containing shipping information corresponding to your sales orders.
Warehouse Order
Once the Warehouse Order transaction has been added a new Warehouse Order tab will appear. Configuration Options specific to the Warehouse Shipping Order (940 EDI Transaction) are defined here:
Field |
Field Type/ Length |
Definition |
Enabled |
Checkbox |
If checked, Acctivate will attempt to export available 940 data for this trading partner. |
Mailbox Path |
Text / 256 Characters |
The file path where files will be imported in from If left blank, the Mailbox Path in the Partner Options section will be used. If that is blank, the Mailbox Path for the trading partner will be used (if the trading partner uses the Warehouse Trading Partner Type). |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to create a file name: - %PARTNERID%: This File Mask adds the EDI Partner ID to the file name.
- %TRANSACTIONID%: This variable adds the Transaction ID (940) to the file name.
- %FILESTAMP%: This variable adds a sequentially incrementing 8 digit number to add uniqueness t the file name..
- %TIMESTAMP%: This variable is used to add a timestamp to the file name, formatted as yyyyMMddHHMMSS.
- %BRANCHID%: When used, orders will be exported into different files for each Sales Order Branch.
If left blank, the Mailbox File Mask in the Partner Options section will be used. If that is blank, the Mailbox File Mask for the trading partner will be used (if the trading partner uses the Warehouse Trading Partner Type). |
File Extension |
Text / 50 Characters |
You can define a specific file extension to be used for the exported file. The default extension is txt . If left blank, the File Extension in the Partner Options section will be used. If that is blank, the File Extension for the trading partner will be used (if the trading partner uses the Warehouse Trading Partner Type). |
Additional EDI Customer Purchase Order Options can be found in the grid on this tab.
Option Name |
Setting |
FilterOrdersByWorkFlow |
Only sales orders with the workflow status you select here will be included in the exported 940 Transaction File. Typically, this would be Ready to Pick. |
OrderWorkflowStatus |
Sales Orders that have been exported in a 940 Transaction File will be updated to the status selected here. Typically, this would be Pick in Progress. |
SendKitComponents |
If this option is checked, Acctivate will send the kit components in the 940 transaction file instead of the kit product. The price and extended amount of the kit will be associated with the first component in the 940 transaction file. Other components will have a $0 price. Note: The components and quantities sent will be based on the Kit item's scheduled quantity. Regardless of the "SendKitComponents" EDI option being enabled, if the 945 contains kit components, rather than the kit itself, the scheduled quantity of the kit will be set to the number of complete kits shipped, based on the shipped quantity of the components. |
Warehouse Shipment
Once the Warehouse Shipment transaction has been added a new Warehouse Shipment tab will appear. Configuration Options specific to the Warehouse Shipping Advice (945 EDI Transaction) are defined here:
Field |
Field Type/ Length |
Definition |
Enabled |
Checkbox |
If checked, Acctivate will attempt to import available 945 data for this trading partner. |
Mailbox Path |
Text / 256 Characters |
The file path where files will be imported in from If left blank, the Mailbox Path in the Partner Options section will be used. If that is blank, the Mailbox Path for the trading partner will be used (if the trading partner uses the Warehouse Trading Partner Type). |
Mailbox File Mask |
List |
Double click in this field to view and select from a list of options. The Mailbox File Masks behave as a variable that Acctivate will use to identify files to import in: - %PARTNERID%: When this File Mask is used, only files that have the Partner ID in the name will be imported in.
- %TRANSACTIONID%: When this File Mask is used, only files that have the transaction type "945" in the name will be imported in.
- %BRANCHID%: This variable is not used.
If left blank, the Mailbox File Mask in the Partner Options section will be used. If that is blank, the Mailbox File Mask for the trading partner will be used (if the trading partner uses the Warehouse Trading Partner Type). |
File Extension |
Text / 50 Characters |
If a specific file extension is entered here, only 945 files with that extension will be imported in for this trading partner. The default extension is txt , or you can enter an asterisk (* ) to act as a wildcard and match on all file extensions. If left blank, the File Extension in the Partner Options section will be used. If that is blank, the File Extension for the trading partner will be used (if the trading partner uses the Warehouse Trading Partner Type). |
When a 945 Transaction File is imported in, the shipment data is added to the Packages tab of the Edit Sales Order window and the sales order's Workflow Status is updated to Shipped.