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

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

"Violation of Primary Key constraint..." when select POP Doc Enquiry on the PO

(0) ShareShare
ReportReport
Posted on by

Hi,

I have a situation where user created PO and posted both Shipment and Invoice Matching. The PO is in Closed Status. But the Shipment appears in both POP10300 and POP30300. When I go to Receiving Entry, it says the RCT is posted. If I remove the RCT from POP30300, run check links, the Shipment will be shown in Receiving Entry and cannot be posted. Edit list message PO is closed.

If I remove RCT from POP10300, the RCT is not shown in POP Doc Inquiry.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Tom Cruse Profile Picture
    1,477 on at
    RE: "Violation of Primary Key constraint..." when select POP Doc Enquiry on the PO

    From what you said you removed the RCT from POP30300 which is the history table and then removed it from POP10300 which is the open table and then you said it doesn't appear in the POP inquiry.

    Have you run checklinks against this PO?

    You'll have POPReceipts living in POP10500 and the invoice match in POP10600.

    If the RCT is only found in POP10500 and POP10600 and not in the POP10300 and POP30300 tables you can delete them and then re-recreate them.

  • Community Member Profile Picture
    on at
    RE: "Violation of Primary Key constraint..." when select POP Doc Enquiry on the PO

    Hi Tom,

    I have already run check links against this PO but nothing is corrected.

    Both Shipment and Invoice appears in POP10500. The Invoice also appears in POP10600. There is also record shown in POP10300. Both POP30300 and POP30900 is also updated. The only details not updated is POP30310.

    So what I really want to achieve is update POP30310. (No matter how I reconcile this record cannot be updated. I tried the below method:-

    1. I amended the POP10100 and POP10110 status to 2, Released

    2. And then I was able to post the shipment successfully although there was an error indicated "Error: posting to POP30390".

    3. This will create another journal in GL. (Based on GL checking, the RCT shipment has already updated GL). I plan to ask user to reverse, else there will be two entries posted for the same Shipment in GL.

    4. Final step, update POP10100 and POP10110 back to 5, Closed. I assume I can ignore the POP30390 error message as the table is not affected.

    Do you think it is okay that I go with this solution? POP Doc Inquiry all seemed okay now.

  • Suggested answer
    Tom Cruse Profile Picture
    1,477 on at
    RE: "Violation of Primary Key constraint..." when select POP Doc Enquiry on the PO

    So are you saying that the only thing missing is POP30390? This is the Distribution History table.

    Is the error still a primary key violation?? I'm traveling remote for holidays so I don't have the tables pulled up in SQL so I'm sure the PK for that table is a combination of both the POPRCTNM and the SEQNUMBR. Has that RCT Number already been used in that table? I would be curious if the RCT and SEQ is already in use for another transaction.

    If not you can always manually create the distributions, I'm not sure how comfortable you with creating these so I would highly advise taking a backup before creating these transactions if this is your first time.

  • Community Member Profile Picture
    on at
    RE: "Violation of Primary Key constraint..." when select POP Doc Enquiry on the PO

    No the only table missing is POP30310. POP30390 is already updated.

    I have a Shipment still showing as unposted but at the same time is has also updated the History table partially. Basically updated everything but POP30310.

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…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans