CloverLeaf reading Lawson Materials Mgmt file

Patrick,

It appears as though the file you were given has each segment delimited by a x0d x0a (CR-NL), rather than just the normal x0d (CR).  You’ll need to convert these x0d x0a’s to x0d’s.  If you used FTP from a windows-based machine to transfer this file, it’s very possible that the FTP tried to be “your friend” and convert the x0d’s to x0d x0a’s.  If you can simply re-transmit the file, try specifying a ‘binary’ transfer to preserve the x0d’s.  If not, you’ll need to create a pre-proc to convert these.

Hope this helps.

Jim Cobane

Henry Ford Health

Consider yourself lucky…their MSCM POU charge files export with double spaces between each segment.   I chose to handle it instead of dealing with their resources in the Phillipines.

Hi Patrick,

I am also dealing with the Lawson Materials Management file (IC527WK) and I also receive the file from a Windows server. To process this HL7 batch file, I have placed in the TPS Inbound Data a Tcl script that splits the file into individual messages and does the end-of-line (CRLF –> CR) translation.

I am not sure if your situation is the same, but Lawson is only sending me one MSH and one MFI segments for the whole batch, while the receiving system requires these segments for each message. Consequently, I had to save the MSH and MFI segments so that I can prepend them to each message when I split the batch.  Once this is accomplished, I am able to send each individual message to Translation, with no need to loop inside the Xlate.

I hope this helps. If desired, I can send you the sample code to give you a starting point.