Microsoft Dynamics SL 2018 & Web Apps Available Now!
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
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: 032696System 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 , POAutoProjectCommitmentsODBCRowNumber = 1 Column = -1 SSrvrLine = 648 SSrvrMsgState = 1 SSrvrSeverity = 14 SSrvrPrSystem Message 6127: Error occurred during an abortable transaction. Processing will continue.
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.
MSDSL Support Engineer
Business Applications communities