Who's On?

	Membership:
	Latest: Chris Radcliffe
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5187

	People Online:
	Visitors: 409
	Members: 0
	Total: 409

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3288
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1351
Roger French	1311
mark.cook	1244

Duplicate Journal Entries

Sort:

You are not authorized to post a reply.

Author

Messages

jgibson

Basic Member

Posts: 7

5/9/2007 4:39 PM

I have noticed with our 7.2.2.4 version of Lawson that when users submit CB175, AR190 and even AP175 jobs, the system is creating duplicate journal entries however only releasing one journal entry report when these programs are run. It is only caught by reviewing the GL190 and by reviewing GL45 to see if we missed any duplicates at month end.

This problem seems to be happening more often, has anyone else come across this. We have version 7.2.2.6 but have never installed it. I'm going through the documentation to see if there was a fix for this issue but I doubt it.

This is very scary for any general ledger package to have an error like this.

Jason

John Henley

Senior Member

Posts: 3348

5/9/2007 5:45 PM

Jason,
Are they the same JE #? Look closely at the GLTRANS (DBGLT) table at the STATUS and JE_SEQUENCE fields. It could be that the original entries are creating memo/error suspense entries.

jgibson

Basic Member

Posts: 7

5/9/2007 6:04 PM

John, they don't have the same JE #'s. They are completely unique records in the GLTRANS table and others.

It's almost like the program didn't realize it created a journal entry for a released transaction, even though it had.

The exact issue that happened today was that a user ran a CB175 to create a journal entry. After the user ran the CB175 she printed a second trial balance. From the time she printed the first trial balance to the second two accounts changed values. Nobody else was running any jobs and she didn't run a GL190. Besides that the accounts that changed weren't the accounts affected by the journal entry created from the CB175 report. I looked at the GL45 and saw the CB journal entry that she created and it looked normal, it had a status of unreleased as I would expect. But, right above that journal was another released by CB175 by the same user, however she didn't actually release it. It was a duplicate of a previous entry and had the status of quickpost. She didn't go into the GL45 and quickpost it. As a result we have had to create entries in the reverse and post them to correct the errors.

thanks for checking,

Jason

John Henley

Senior Member

Posts: 3348

5/9/2007 6:18 PM

What platform are you on? Regardless, this is a pretty old version...I doubt Lawson will even let you open a support call...

jgibson

Basic Member

Posts: 7

5/9/2007 7:12 PM

ISeries.

They will open a single call for a minimum charge of $2,500 but they're about to drop that option too. We're going through the release notes of 7.2.2.6 too see if there's any reference, we've had that release since '02 I guess and never installed it.

Lawson is actually a slight overkill for our organization but the implementation of any other package or even an upgrade to 9 is just too costly. but, if we keep having issues like this we may be forced.

Thanks for responding.

John Henley

Senior Member

Posts: 3348

5/9/2007 9:07 PM

Have you talked to CIBER or Analysts International about on-going/on-call support? I know they have done it for clients in the past.

You are not authorized to post a reply.