Setting up Communication Engine for Vision Stock Received

Configure Communication Engine mappings for Vision stock received messages.

Prerequisites

Bevica Warehouse Integration extension installed.

Communication Engine extension installed.

Account with a Vision managed warehouse: LCB, Vinotheque, Lanchester, EHD, Coterie Vaults.

Communication Engine

The communication engine is a solution framework to enable the communication of data between Bevica and various endpoints such as a Vision warehouse.

Initial Setup

If you are not already using the communication engine to send or receive other files from the warehouse, e.g. sales orders, you will need to complete some initial setup. If you are already using the communication engine you can skip this part and move to setting up the communication engine route.

1. Warehouse Integration Setup

You will need to populate the following Vision account information in the Warehouse Integration Setup record. The information will be supplied by Vision or your warehouse.

• Path to API e.g.

  • http://kingmoor.lcb.co.uk (LCB)
  • http://edi.ehdlondon.co.uk (EHD)
  • http://kingmoor.lanchestergroup.com (Lanchester)
• Customer Code
• Site Code
• API Username (Client ID)
• API Password (Client Secret)

2. Communication Engine Setup

Prior to setting up any communication engine routes you need to initialise the communication engine. To do this:

1. Search for Communication Engine Setup and select to Initialise Setup. Note that if you receive an error about the TVTCOM package this can be ignored.
2. Search for Warehouse Integration Setup, open the Warehouse Supplier Setup card and select Actions, Create Communication Engine Auth.

Users will need the COMMUNICATION ENGINE permission set to access this functionality if they are not a super user.

Setting up a Communication Engine Route

You will need to set up a new communication engine route for Warehouse Goods Received Integration. To do this, search for Communication Engine Routes and create a new record. Populate the fields as follows:

Field	Note
Code	Enter a code for the record e.g. LCB_RECEIPT
Type	Http
Direction	Inbound
Communication Code	• Enter a Code, e.g. LCB_RECEIPT • End Point = /service/GdsRcvd/CustomerCode//SiteCode/ • is the URL base e.g.http://kingmoor.lcb.co.uk • is the Customer Code e.g. ABCDE • is the Site Code e.g. CR • Content Type = application/xml • Method = Get • Authentication Code, drill down and select the record that has been created e.g. LCB01
Description	Enter a description
Route Action	Vision Goods In
Synchronise Routes	Tick this
Process Message	Tick this
Task Scheduler	Tick this if you are going to set up the job queue
Task Sched. Parameter	Populate this, e.g. RECEIPT. This will be the value to populate the Parameter String on the job queue for codeunit 68807. See below.
Whse. Integration Setup	Select the relevant Warehouse Integration Setup record.

Retention policy setup

If you don't have this setup already, you can define a retention policy to delete outdated communication engine message records. To do this:

1

Step 1

Choose the icon, enter Communication Engine Setup, and then choose the related link.

2

Step 2

Select Setup Comm. Messages Retention Policy.

3

Step 3

Amend the defaults if required and select to Enable.

For more information, see Retention Policies.

Importing receipt files manually

Whilst you are testing the functionality you can run the process manually. For more information see Processing Receipt Confirmations.

1. Import stock file from Vision

   • From the Communication Engine Routes page, select Run Communication Engine in the ribbon.
   • This will import the file from Vision and create an Inbound Request record. You should see the No. of Messages Completed has increased. Drill down to see the message created.
2. Process the Inbound Request

   • Search for Inbound Requests. You should see a new record in here which was created in step 1.
   • Select Process Requests in the ribbon. Select the Warehouse Code and optionally enter the Entry No. you would like to process.
   • This will create the stock transaction entries for review.

Setting up the job queues

Once you are happy with the functionality you can set up the job queues to run these two functions:

1. Import the stock file from Vision

   • This will retrieve the data from Vision and create an Inbound Request record in Bevica.
   • Create a job queue entry for Codeunit 68807 TVTCOM Run from Job Queue.
   • Set the Parameter String to be the same value as the Task Sched. Parameter value on the Communication Engine Route record for the stock reconciliation record. Note that if you are unable to see the Task Sched. Parameter field on the Communication Engine Route page you will need to personalise the page.
   • Set the job queue entry to run on relevant days e.g. Monday to Friday.
   • Set the Starting Time and Ending Time according to when you want to bring the file into Bevica.
   • Set the job queue to Ready.

Note

You are only able to retrieve the file 6 times in a 1 hour period. If you exceed this Vision will return an error.

1. Process the inbound request record created

   • This will process the inbound request record and create the Warehouse Item Reconciliation batch.
   • Create a job queue entry for Report 71302 Whse. Integration Process Inbound Requests.
   • Under the Job Queue ribbon, open the Report Request Page enter the relevant Warehouse Code and optionally enter the Supplier Request Code (RECEIPT).
   • Set the job queue entry to run on relevant days e.g. Monday to Friday.
   • Set the Starting Time and Ending Time to run after codeunit 68807.
   • Set the job queue to Ready.

Troubleshooting

See Communication Engine Messages for details of how communication engine messages are generated and what to do if the message errors.