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) / get/change operation o...
Microsoft Dynamics GP (Archived)

get/change operation on table 'pm1099PeriodDtl' failed accessing SQL data. Number of results columns doesnt match table definition.

(1) ShareShare
ReportReport
Posted on by Staal@Barr 40

We just upgraded from GP 2010 to GP 2013 and few days ago and also installed the latest service pack, which happened to be the 2015 Year End Update for GP 2013.

Now we get the error "A get/change operation on table 'pm1099PeriodDtl' failed accessing SQL data. Number of results columns doesnt match table definition." whenever attempting to work with any Vendor in Purchasing and access the 1099 Detail table.  For example, just going to Cards => Purchasing => 1099 Detail and bringing up a vendor will generate this error.  We first noticed it when trying to post a batch to payables that had a check.

So it would seem our 1099 Period Detail table has more or less fields than it should.  It's hard to imagine how that happened since there were no errors during the upgrade process.  We also don't have any third party products installed and just a couple of very simple VBA customizations that don't relate to this area.

Here is our 1099 Period Detail table (PM00204) definition from SQL:

[VENDORID] [char](15) NOT NULL,

[TEN99TYPE] [smallint] NOT NULL,

[YEAR1] [smallint] NOT NULL,

[PERIODID] [smallint] NOT NULL,

[TEN99BOXNUMBER] [smallint] NOT NULL,

[TEN99AMNT] [numeric](19, 5) NOT NULL,

[TEN99FRNORUSDTL] [char](41) NOT NULL,

[TEN99STATECD] [char](3) NOT NULL,

[TEN99STATIDNUM] [char](21) NOT NULL,

[TEN99TAXEXMTCUSIPNUM] [char](13) NOT NULL,

[TEN99DIRSALECB] [tinyint] NOT NULL,

[TEN99STATNMBR] [char](21) NOT NULL,

[TEN99FATCAFILEREQ] [tinyint] NOT NULL,

[DEX_ROW_ID] [int] IDENTITY(1,1) NOT NULL,

Does anyone know what could be causing this problem?  Any help would be appreciated.

Thanks,

- Dave

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hello Dave,

    I am facing the exact same scenario. I will do some research tonight, but sounds like this is due to versions mismatch. Perhaps a client was installed with an extra module than what was installed on server? First thing I will do is run DynUtils on server.

    In any case, if you find a solution, please do post it for all to try.

    Thanks!

    FB

  • Staal@Barr Profile Picture
    Staal@Barr 40 on at

    Hi, Fitz.

    Thanks for letting me know that I'm not the only one seeing this problem.  I'll definitely let you know if we find a solution.

    We only have a few clients and I'm pretty sure I installed them all exactly the same way, but that's a good thought about checking the modules.

    Thanks,

    - Dave

  • Dale Stratton Profile Picture
    Dale Stratton 90 on at

    Dave,

    I am having the exact same issue.  I upgraded from GP 2010 to GP 2013 with the 2015 PYEU as well (12.00.2038).  I also receive errors when trying to post a payables batch as well as when trying to look at any of the 1099 details windows through Inquiry or Cards.  The column list for PM00204 is the same on this install as it is on other 12.00.2038 installs that function correctly.  Please post if you find any resolution.

    Thanks,

    Dale

  • Staal@Barr Profile Picture
    Staal@Barr 40 on at

    I just found some more useful information from the Dynamics GP Support and Services Blog: https://community.dynamics.com/gp/b/dynamicsgp/archive/2015/11/05/microsoft-dynamics-gp-year-end-release-2015-table-and-column-changes-in-us-year-end-update .  They added a new column to the table that is causing the error:

             PM00204 – New Column: TEN99FATCAFILEREQ

    So it would seem clear to me that something in the year end update patch is causing this problem, where the code and the table do not match up correctly.

  • Verified answer
    Dale Stratton Profile Picture
    Dale Stratton 90 on at

    I submitted a ticket to Microsoft.  We had to recreate the PM00204 table using PSTL.  The PSTL Toolkit has an option to recreate a table and the data in it.  It did resolve the issue we were having.

  • Staal@Barr Profile Picture
    Staal@Barr 40 on at

    Hi, Dale.

    Thanks, that's very helpful!  I got the PSTL (which I had to get from my reseller/partner) and am playing around with it on my test database.  I'll post again here after I've given it a shot.

    - Dave

  • Verified answer
    Staal@Barr Profile Picture
    Staal@Barr 40 on at

    Thanks again to Dale for providing the solution to fixing this problem.  Here is some more detailed information on how to do it.  I guess I should add a disclaimer that I'm not an expert and you should make sure you have database backups in case something goes wrong.

    First, you need the Professional Services Tools Library (PSTL), which you can no longer download from Customer Source.  I had to contact my reseller/partner to get the PSTL, and then I installed it using the instructions from here:  http://www.azurecurve.co.uk/2012/04/how-to-install-professional-services-tools-library/ .

    Next, launch Professional Services Tools Library and do the following:

    Select "Toolkit", then Next.

    Select "Recreate SQL Objects", then Next.

    You will now see this screen:

    Select Series: Purchasing

    Select Table: PM00204

    Select "Recreate Selected Table"

    Check the check box for "Recreate data for selected table(s)"

    Finally, click the "Perform Selected Maintenance" button and it will recreate the table and data, but not before asking you repeatedly if your sure.

  • Community Member Profile Picture
    Community Member on at

    We are currently suffering an Unhandled script exception when opening the vendor details window. The error is: Illegal address for field '1099 FATCA Requirement' in script 'Set1099DetailFields'. We used the PSTL to recreate PM00204 with data recreating for selected table, without success. Anyone else have this issue after installing the Year End Update from MS?

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi Manuel,

    I experienced this same issue, and for me it was due to MEM's window not accommodating the update.  I changed the window back to the Microsoft Dynamics GP window, and now we are all set.  Our partner has opened a case with Binary Stream to alert them to the issue.

    John

  • Community Member Profile Picture
    Community Member on at

    We just did the same upgrade , GP2010 => GP2013 with the service packs available on CustomerSource and got the same error. I will be contacting my dealer/vendor with the same questions on how to resolve this issue.

    As far as anyone knows, is this error confined to the AP module ? I'd hate to try and run a Gl ,AR or PR posting and find out the same type of error is present.

    Thanks

    Andrew

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