Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL forum
Unanswered

Violation of PRIMARY KEY constraint 'pjcomdet0'

Posted on by Microsoft Employee

I am having difficulty resolving this issue in SL 2011. My client has a PO that they are receipting but as soon as I release the batch i receive the below error from the event log. I have queried the PJCOMDET table and I can see the two entries that are duplicated but i do not know how to go about resolving this error.

You help is greatly appreciated.

Event Log Message:

Processing: Batch Number: 048099    , Receipt Number: 032696
System Message 5: [Microsoft][SQL Server Native Client 11.0][SQL
                  Server]Violation of PRIMARY KEY constraint 'pjcomdet0'. Cannot
                  insert duplicate key in object 'dbo.PJCOMDET'. The duplicate
                  key value is (201807, PO, 05



  Debugging info:
                  POAutoProjectCommitments '051123', '201807', '04400',
                  'AENSLIN'
  Cursor(csrProjectCommitment)
                  POAutoProjectCommitments '051123', '201807', '0440
  Optional
                  info: SqlState = 23000 NativeError = 2627 ErrorMsg =
                  [Microsoft][SQL Server Native Client 11.0][SQL
                  Server]Violation of PRIMARY KEY constraint 'pjcomdet0'. Cannot
                  insert duplicate key in object 'dbo.PJCOMDET'. The duplicate
                  key value is (201807, PO, 051123    ,
                  POAutoProjectCommitments
ODBCRowNumber = 1 Column = -1
                  SSrvrLine = 648 SSrvrMsgState = 1 SSrvrSeverity = 14 SSrvrPr

System Message 6127: Error occurred during an abortable transaction.  Processing
                     will continue.

  • CFROTON Profile Picture
    CFROTON 4,710 on at
    RE: Violation of PRIMARY KEY constraint 'pjcomdet0'

    Waren,

    Thank you for submitting your question to the forum. I suspect you are running into BUG 26049 reported in SL 2011. This bug was fixed in SL 2015 CU1 and there is a SL 2015 HF, but not one for SL 2011.

    I looked through some of the previous incidents and located reports where this message had occurred. To resolve the issue, they ran the Project Financial Transaction Transfer manually through the Project PA.TRN.00 screen. This transferred the commitment and allowed the Purchasing batch to release.

    Can you run the FTT process and then try releasing this batch within Purchasing?

    Please let us know if this helps.

    Thank you,

    Carolyn

    MSDSL Support Engineer

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

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,537 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,520 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans