EDI / Cleo

Is anyone using Supply Chain in Lawson running EDI through Cleo to Vendors?
We are setup with cleo and get these erroneous errors in email everytime one of these ED501's run for specific vendors.
Anyone seen this kind of error notification can't figure out where it is coming from.
When a PO is created and the ED501 runs for 5 Vendors (Merrit - Patterson - Granger - Bard - Boston Scientific) that coordinate communication with Cleo - system produces an error with each transaction.
There are 12 Vendors on the Lawson Server that use direct FTP and the errors are not produced.
It appears that the ED501 job runs and a file is produced and placed in the $LAWDIR/prod/EDI/OUT - as in the example below.

This message contains errors only .
You can view the full log in the job scheduler or ED04

20140804153220, OUTBOUND : E:LSFPROD1LAWPRODEDIOUTPO850COOK150, PROBLEM ERROR BOSTONAS2 Communications FAILED

C:Program exited with value 1 :
E:/lsfprod1/law/prod/edi/comm/out/BOSTONAS2.20140804153220 saved for future transmission

Should it be looking in the edi/comm/out? Is this a Cleo configuration?

The file actually gets picked up by Cleo and sent so I consider this a false error message but maybe we have it pointing to the wrong place.

This started after we updated EDI to the 9.0.1_12 version

Any help will be appreciated.

Find more posts tagged with

Comments

jon-athey

Are you using Cleo Lexicom?

jon-athey

I believe the edi/comm/out/ directory is just a holding place for files to be resent when communications fail intially. You should be able to view the log files in /edi/logs/ to see if there's a comm error with Boston Sci.

dscheppa

I have no logs in that prodedilogs directory
This is what the ED04 shows

BEGINNING OUTBOUND EDI PROCESSING Mon Aug 4 15:32:18 2014
ATTEMPTING TRANSLATE AND SEND WITH:
[E:LSFPROD1LAWPRODEDIOUTPO850COOK150]
Moving E:LSFPROD1LAWPRODEDIOUTPO850COOK150 to work directory.
CONNECTING TO EDI TRANSLATION SERVER
Server : 10.75.126.184 port# 9901
Product line: prod
CONNECTION SUCCESSFUL
REQUEST ACCEPTED BY EDI SERVER: 10.75.126.184 port# 9901
Mon Aug 4 15:32:20 2014
CONNECTION ID = 20140804153220
OUTBOUND Translation Starting
OF: PO850COOK150
================================================
TRADING PARTNER = CTCA850COOK150
Outbound Interchange Control Number: 124
Translating using [E:/lsfprod1/law/prod/edi/bin/laws_out_91]
TRANSLATION SUCCESSFUL
================================================
BEGINNING OUTBOUND EDI PROCESSING Mon Aug 4 15:32:30 2014
ATTEMPTING SEND ONLY
NO TRANSLATION REQUESTED FOR FILE:
E:LSFPROD1LAWPRODEDIWORKPOINSIGHT140
CONNECTION ID: 20140804153230
File Does Not Exist: [E:LSFPROD1LAWPRODEDIWORKPOINSIGHT140]
TERMINATING EXECUTION

dscheppa

Sorry I'm not sure what Lexicom is?

Legacy Contributor

Cleo Lexicom is Cleo's secure file transfer product. We suggest this product if you need a communication package.

Cleo A+ is the old dial up package from Cleo that we no longer support.

jon-athey

Cleo doesn't support A+ any more either.

dscheppa

We use VLTrader which is built in Cleo

jon-athey

I'm sorry I wish I could help but your ED04 log looks very different from ours. Our logs don't give a drive letter and the filenames are not even close. Not familiar with VLTrader.

dscheppa

I've never configured Cleo but in the help notes it shows
VersaLex powers Cleo LexiCom®, a client solution for communication with major trading networks, Cleo VLTrader™, a server-level solution for the implementation and management of communications both up and down the supply chain, and Cleo Harmony™, an enterprise solution for both B2B and A2A communications.

So that tells me Cleo has 3 different solutions and we are using the server level solution called VLTrader

Copyright © 2025 Infor. All rights reserved.