web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Dynamics GP 2016 - Err...
Microsoft Dynamics GP (Archived)

Dynamics GP 2016 - Error when opening "Transaction by Document" Inquiry screen

(0) ShareShare
ReportReport
Posted on by Community Member

version: Dynamics GP 2016 R2

When our users go to Purchasing -> Inquiry -> Transaction by Document

they all recieve a nuisance unhandled script exception

SCRIPTS - data area

EXCEPTION_CLASS_SCRIPT_OUT_OF_RANGE

SCRIPT_CMD_INDEX

After clicking ok, they still get to the inquiry screen and are able to continue without a problem.

Ive seen a few posts related to stuff like this but no solutions.

Can anyone point me in the right direction?

*This post is locked for comments

I have the same question (0)
  • twelvestrikes Profile Picture
    twelvestrikes 3,657 on at

    Hi Pietro

    I recently had a client with a very similar problem.

    The issue I found was that an invoice did not entirely clear from the PM open tables and move to the PM history tables.

    Do your users get an error if they go to Inquiry > Purchasing > Transaction by Vendor?

    Check the PM20000 (PM TRx Open) vs the PM30200 (PM trx history) to see if there are any duplicate records.

    This resolved the issue for my client.

    If the above doesn't work you will need to expand and check the PM10000, and PM20000 to see if a duplicate exists there.

    Failing that you may need to further expand your search to the PM distribution tables.

  • Community Member Profile Picture
    Community Member on at

    Thanks for the response. Interestingly it doesnt come up when going to "Transaction by Vendor", only the "Transaction by Document". I verified there were no duplicates in those tables.

    I did notice when the transaction inquiry screen does load after the error, there is a historical entry at the top that shows a blank doc number, type and vendorid and the amount is zero and the date is 0/0/0000. This leads me to believe there is some kind of bad/malformed record. When i attempt to click this top entry, the same error appears once again. Upon searching the table for any rows missing this information, nothing looks out of the ordinary though.

  • twelvestrikes Profile Picture
    twelvestrikes 3,657 on at

    Hi Pietro

    That sounds like the puppy causing you the problems.

    I would first make a backup of the database before doing anything else.

    You could try running check links on the Payables Historical and Payables open transactions to see if that fixes the problem

    If check links doesn't fix the problem, you will have to go into the tables and find the bad record in the history table and remove it.  Then run check links so it removes the record in the keys file.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans