Error in Stored Procedure SOPTrxDuplicateTaxes

  • Error in Stored Procedure SOPTrxDuplicateTaxes

    Posted by DSC Communities on November 6, 2019 at 4:46 pm
    • Charles Allen

      Member

      November 6, 2019 at 4:46 PM

      A client is receiving a message, “the stored procedure SOPTrxDuplicateTaxes returned the following results: DBMS: 512, Microsoft Dynamics GP: 0.

      Has anybody encountered this message?

      Thank you

      ——————————
      Charles Allen
      Senior Managing Consultant
      BKD Technologies
      Houston, TX
      ——————————

    • Matthew Arp

      Member

      November 6, 2019 at 5:14 PM

      So the 512 error code in SQL looks like it is related to a subquery returning more than one result. Is this for any SOP document, or just a particular document? If it is just a single document I’d recommend looking at the SOP10105 & SOP10200 for the source document and seeing if anything looks wonky.

      ——————————
      Matthew Arp
      Business Systems Developer
      Hunton Group
      Houston TX
      ——————————
      ——————————————-

    • Charles Allen

      Member

      November 6, 2019 at 5:22 PM

      Thank you for the response. It’s every quote or order that is entered that has sales taxes. I’ve looked but will look again.

       

       

      Charles Allen

      Senior Consulting Manager | BKD

      2700 Post Oak Blvd. Suite 1500

      Houston, TX 77056

      713.499.4629 Direct

      713.494.2104 Mobile

       

       

       

      ****** BKD, LLP Internet Email Confidentiality Footer ******

      Privileged/Confidential Information may be contained
      in this message. If you are not the addressee indicated in
      this message (or responsible for delivery of the message
      to such person), you may not copy or deliver this message to
      anyone. In such case, you should destroy this message, and
      notify us immediately. If you or your employer do not consent
      to Internet email messages of this kind, please advise us
      immediately. Opinions, conclusions and other information
      expressed in this message are not given or endorsed by my
      firm or employer unless otherwise indicated by an authorized
      representative independent of this message.

      Any tax advice contained in the body of this email was not
      intended or written to be used, and cannot be used, by the
      recipient for the purpose of avoiding penalties that may be
      imposed under the Internal Revenue Code or applicable state
      or local tax law provisions.

      These discussions and conclusions are based on the facts
      as stated and existing authorities as of the date of this
      email. Our advice could change as a result of changes in the
      applicable laws and regulations. We are under no obligation
      to update this information if such changes occur. Our advice
      is based on your unique facts and circumstances as you
      communicated them to us and should not be used or relied
      on by anyone else.

      ——Original Message——

      So the 512 error code in SQL looks like it is related to a subquery returning more than one result. Is this for any SOP document, or just a particular document? If it is just a single document I’d recommend looking at the SOP10105 & SOP10200 for the source document and seeing if anything looks wonky.

      ——————————
      Matthew Arp
      Business Systems Developer
      Hunton Group
      Houston TX
      ——————————

    • Matthew Arp

      Member

      November 6, 2019 at 5:29 PM

      Do you get the same error if you invoke the stored proc manually thru SSMS?

      ——————————
      Matthew Arp
      Business Systems Developer
      Hunton Group
      Houston TX
      ——————————
      ——————————————-

    • Chris Donnelly

      Member

      November 7, 2019 at 8:07 AM

      Charles,

      You probably have some sort of data corruption.Ā  I would start with running reconcile and checklinks.Ā  Then move on to interrogating the data in the tables manually.Ā  Based on the name of the stored procedure, I would focus on the tax tables, looking for issues in referential integrity (the one-to-one, one-to-many relationships).

      Good luck,

      Chris

      ——————————
      Chris Donnelly
      Sr Mgr of Info Systems and Financial Reporting
      Healthmark Industries
      ——————————
      ——————————————-

    • David Morinello

      Member

      November 7, 2019 at 8:36 AM

      Do they have any 3rd party products installed that might be part of the problem?
      Is the data entered through GP or fed in from an outside source?

      ——————————
      David Morinello
      Senior Dynamics GP Systems Architect
      Ascend Learning, LLC
      Leawood KS
      ——————————
      ——————————————-

    • Charles Allen

      Member

      November 7, 2019 at 9:29 AM

      In fact, the issue is tied up in some customizations. There are several add-ons to the Sales Transaction Entry window with their own triggers. A combination of triggers and functionality was causing the issue. I haven’t figured out what the reason is but I did find the offending trigger.

       

      Thank you for your response.

       

       

      Charles Allen

      Senior Consulting Manager | BKD

      2700 Post Oak Blvd. Suite 1500

      Houston, TX 77056

      713.499.4629 Direct

      713.494.2104 Mobile

       

      Solver badge-7829

       

      ****** BKD, LLP Internet Email Confidentiality Footer ******

      Privileged/Confidential Information may be contained
      in this message. If you are not the addressee indicated in
      this message (or responsible for delivery of the message
      to such person), you may not copy or deliver this message to
      anyone. In such case, you should destroy this message, and
      notify us immediately. If you or your employer do not consent
      to Internet email messages of this kind, please advise us
      immediately. Opinions, conclusions and other information
      expressed in this message are not given or endorsed by my
      firm or employer unless otherwise indicated by an authorized
      representative independent of this message.

      Any tax advice contained in the body of this email was not
      intended or written to be used, and cannot be used, by the
      recipient for the purpose of avoiding penalties that may be
      imposed under the Internal Revenue Code or applicable state
      or local tax law provisions.

      These discussions and conclusions are based on the facts
      as stated and existing authorities as of the date of this
      email. Our advice could change as a result of changes in the
      applicable laws and regulations. We are under no obligation
      to update this information if such changes occur. Our advice
      is based on your unique facts and circumstances as you
      communicated them to us and should not be used or relied
      on by anyone else.

      ——Original Message——

      Charles,

      You probably have some sort of data corruption.Ā  I would start with running reconcile and checklinks.Ā  Then move on to interrogating the data in the tables manually.Ā  Based on the name of the stored procedure, I would focus on the tax tables, looking for issues in referential integrity (the one-to-one, one-to-many relationships).

      Good luck,

      Chris

      ——————————
      Chris Donnelly
      Sr Mgr of Info Systems and Financial Reporting
      Healthmark Industries
      ——————————

    DSC Communities replied 5 years, 10 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Error in Stored Procedure SOPTrxDuplicateTaxes’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!