Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cheques printing cheque amount on first line

Status
Not open for further replies.

Luvsql

Technical User
Apr 3, 2003
1,179
CA
Our cheques have suddenly started to print the payment number, the cheque amount, zero date on the first line of all our stubs when we use the edit cheques procedure. I have verified that before posting, this extra line of info appears in the PM10201 table. We have been using GP for 3 years now and it just started to happen (have not applied any sps lately or upgrades). We are on version 7.5.

In the PM10201 table we have:

NetCkAmt 0
PdTot Chequeamt
NegTot -Chequeamt
Keyfield 00000
Amtpaid chequemt
Crdtamnt -chequeamt


It is getting very confusing for our vendors. Check links doesn't do anything because once we post, the data is removed from the work tables.
 
I have found the issue and Great Plains is seriously corrupting data. After entering a payment, applying to an invoice, the PM10201 table looks like this:

NetCkAmt PdTot NegTot
.00000 585.00000 -585.00000
585.00000 1170.00000 1170.00000

The amount of the payment is 585.00 and the amount of the invoice it is paying is 585.00. There is nothing wrong with the invoice. It does this for every cheque we issue.
 
It turns out to be a Great Plains security issue? My user ID does not have the problem GP creating this weird data. Yet another user gets the issue with the exact same vendor, invoice etc. I created a brand new class and assigned that user to the class and now the data is getting even worse (creating 4 extra lines for each vendor that a cheque is created).


How can security mess with how data is updated in tables? It is definitely security doing this as it's a user by user issue (we are on version 7.5).

 
Microsoft has just confirmed with me that this has also been caused by Adv Security. I'm going to remove it completely so I don't mistakenly use it again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top