Using an EDI-856 or EDI-861 to submit Critical Tracking Events

Submit traceability events using your existing EDI-856 Advance Shipping Notice (ASN) or EDI-861 Receiving Advice EDI documents. 

Overview

Electronic Data Interchange (EDI) is a standard for B2B communication between trading partners used for transmitting information relevant to procurement, sales, and logistics. Within the context of a traceability program, oftentimes an existing EDI-856 Advance Ship Notice (ASN) or EDI-861 Receiving Advice document can be repurposed to convey the Critical Tracking Events (CTEs) and Key Data Elements (KDEs) that are integral to traceability.

Setting Up an AS2 Connection + EDI Document Map

Once logged-in to your FoodLogiQ account, click on the Settings button in the top right of the menu bar, and choose Integrations.

NOTE: You have the option of setting up multiple AS2 Configurations and EDI maps as needed, which may be useful if you have multiple systems submitting EDI transaction data that you want to send to FoodLogiQ.

Step 1: You can setup multiple configurations per business if needed. This may be useful if multiple systems are submitting data that you need to share with FoodLogiQ. Additionally, you may have different EDI Maps per Community/Customer you need to submit data in FoodLogiQ for. 

Click the "+" button to setup a new AS2 configuration.

From the AS2 (EDI) > AS2 Configurations tab, click the plus button to configure a new AS2 connection and EDI map.

Part 1: Your Configuration  

1. Name your new AS2 configuration something meaningful. 

• Example: TF-EDI-856 Config
• Enter an AS2 Identifier. This identifies your company or organization in the header of your AS2 transmissions. 

• Example: Tyler Farms SHA1
• Upload your Public Certificate either by dragging and dropping the file, or by clicking browse to locate and select your file. Once uploaded, the filename of your certificate will be displayed.

• Example: TYLER FARMS-AS2 CONNECTOR.cer

Enter an email address (required) that should be notified in the event of a data transmission error. The field will preload the email address of the user creating the new AS2 configuration, though it can be changed. This email address will only be contacted if a submitted EDI document fails our error validations.

Part 2: FoodLogiQ Information

1. Make note of the Receiving URL and FoodLogiQ’s AS2 Identifier.

• • Receiving URL: http://as2-server.foodlogiq.com/as2connector/pub/ReceiveFile.rsb)
  • FoodLogiQ AS2 Identifier: FOODLOGIQ

Download FoodLogiQ’s Public Certificate which you will use with your EDI provider to transmit encrypted EDI-856 and 861 transactions to FoodLogiQ.

Part 3: Configure and Preview your EDI Map

1. Find a sample EDI-856 or EDI-861 document from your records and upload it to begin configuring your EDI map.

2. Once a sample EDI file is uploaded, we will automatically attempt to parse and map the EDI fields and selectors contained in your document, to the key data elements for critical tracking events.

Note: If your customer asks for additional data fields not present in the default set, use the ‘Add Field’ button to name the custom field and specify the appropriate EDI Field and Selector from your sample file.

3. To verify your EDI file was mapped correctly click the  button to see that the data contained in your sample EDI document is translated correctly, and confirm that there are zero errors in the event output on the right.

4. Make any necessary changes to your mapping, and repeat the preview step until you are satisfied with your EDI map. 

5. Click the ‘Save’ button at the top right of the page to complete the AS2 Configuration for this particular EDI document type. 

6. You should receive an email notification indicating your configuration is complete within a few business days, and once you have received confirmation, you are ready to start sending EDI files to FoodLogiQ.