Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

eConnect bug with Receiving

(0) ShareShare
ReportReport
Posted on by 60

I'm getting the following error when I attempt to process a receipt having POPTYPE=3 (Shipment\Invoice):

"Cannot insert the value NULL into column 'ORTDISAM', table dbo.POP10300'; column does not allow nulls. INSERT fails"

If I run the process with POPTYPE=1 (Shipment), everything works fine.  I'm also able to manually enter the data in the Receiving Transaction Entry window as a Shipment\Invoice successfully.  Any suggestions?  This field 'ORTDISAM' is not even available in the eConnect POP nodes, so I'm not sure how to even go about a work-around.

Chris

*This post is locked for comments

  • Community Member Profile Picture
    on at
    RE: eConnect bug with Receiving

    I tried setting TRDISAMT=0. but I still see the issue.

    I am using GP 2013.

    Can some one please let me know how to overcome this issue.

    Thanks in advance..!!

  • Suggested answer
    Cole Solutions Profile Picture
    on at
    RE: eConnect bug with Receiving

    just ran into this issue.

    the easy work around is to set @I_vTRDISAMT = 0 in your taPopRcptHdrInsert.

    While ORTDISAM is not a parameter for this type of transaction. It is somehow related to I_vTRDISAMT .

    Good Luck....

  • sandipdjadhav Profile Picture
    18,302 on at
    Re: eConnect bug with Receiving

    Chris,

    I am using Ship\Invoice eConnect schema from GP9 and I have not face this issue. Currently it is working with GP2010.

    Can you post your XML? I will be happy to share my code whereas I created custom webservices using eConnect schema for Purchase Shipment\Invoice.

    Thanks

    Sandip

  • Chris Spencer Profile Picture
    60 on at
    Re: eConnect bug with Receiving

    Thanks for the response, Robert.  This client is actually on GP2010 SP2 - is it possible that the bug fix didn't address the Shipment\Invoice receipt type (POPTYPE=3)?

  • Community Member Profile Picture
    on at
    Re: eConnect bug with Receiving

    Hi Chris,

    Thanks for the question. There was a bug in eConnect which returned this same error when importing in POP transactions; the import failed on the original trade discount amount. Fixes for eConnect are actually shipped in GP service packs and a fix for this problem was shipped in GP10 SP4 (build 10.00.1368).

    Can you please check to see the build of GP that you are on. If it is lower than 10.00.1368 upgrading to the latest build of GP10 should correct this issue for you.

    Please let me know if you would like any additional information on this issue.

    Regards

    Rob

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Featured topics

Product updates

Dynamics 365 release plans