Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / System Message 6909: A...
Microsoft Dynamics SL (Archived)

System Message 6909: Another process has already added the cursor=DefaultCreated

(0) ShareShare
ReportReport
Posted on by Igor_CF 165

Hello!

We're running SL 2011 and experienced a problem with releasing an AP batch. One check was printed. It's grayed out, partially released, no way to release or delete. When we try to release we get "System Message 6909: Another process has already added the cursor=DefaultCreated..." message.

I ran debug script and got the following error:

Violation of PRIMARY KEY constraint 'APAdjust0'. Cannot insert duplicate key in object 'dbo.APAdjust'. The duplicate key value is (001563    , VO, 000357.......

So looks like the process started and there is an entry in APAdjust, but something happened and it couldn't finish the process,

Does anyone has any idea how to fix it? I saw similar question from 2012, but no answer or even reply. 

Thanks in advance.

Igor

*This post is locked for comments

  • Igor_CF Profile Picture
    Igor_CF 165 on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    There was only one person entering the batches and she didn't notice anything unusual until she tried to release.

    Not sure, maybe network problem, connection to database prevented the process to finish correctly.

    In any case thank you very much, will contact MS partner for help.

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    OK, the pieces are starting to fall into place.  Batch 001748 is giving the error because it thinks its check number is 000357 but that check number already exists in apadjust for the same vendor and voucher.  Batch 001748 got check number 000357 because the document for batch 001748 is missing so it thought that check number 000357 was still available but the other parts of batch 001747 exist (the aptran, the gltran, the apadjust and the reduction of the voucher's balance by the $5000 payment from batch 001747.  We still do not know why the document for batch 001747 is missing.  However, the solution is to manually add in the missing document for batch 001747 and to change the reference number in batch 001748 to the next check number (assuming that 00358 has not been used elsewhere).  Like I said before, you need an experience SL support person to add back in that missing document as you have to get all the fields set correctly.

    Out of curiosity, did you experience anything unusual during the entry of batch 001747 or during the keep check process?  Is it possible that 2 different users were entering these batches at the exact same time such that the second batch was started before the first one was released?  I still have no idea how you ended up with that missing document.

  • Igor_CF Profile Picture
    Igor_CF 165 on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    APAdjust has only 001747:

    adjbatnbr vendid adjamt adjdrefnbr adjgrefnbr curyadjdamt curyadjgamt AdjAmt AdjBatNbr

    001747     SML001  5000 001563     000357     5000 5000 5000 001747

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    This is very odd.  Batch 001747 should have 1 apdoc record and 2 aptran records once the batch is released.  When a batch is not released then there is just the one aptran record but there still should be an apdoc record.  You also said that you have what appears to be a valid batch on the GL side which suggests that the batch was released.  The fact that the apdoc record is missing explains why the next batch got assigned the same check number.  The fact that you got the error on releasing the second batch indicates that the first batch also has records in the apadjust table.  So, something very odd happened during the release of the first batch.  This is not something I have ever seen in my 20+ years of supporting Solomon/Dynamics SL.  It appears that what needs to be done is to add back in the missing apdoc record for the first batch and change the reference number in the second batch to the next check number and release the second batch.  This is not something that I suggest the end user attempts to do.  You need an experienced SL partner or Microsoft support to help you with this one.

    One last thing, can you provide what you find in apadjust for both batches 001747 and 001748 just so I can confirm that apadjust looks like I think it does?

  • Igor_CF Profile Picture
    Igor_CF 165 on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    ApDoc doesn't have any entries for 001747, APTran is below:

    Batnbr vendid Trantype Refnbr DRCR Tranamt CuryTranamt Rlsed

    001747     SML001         CK 000357     D        5000 5000 1

    Thank you

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    That is what is there for batch 001748 (the second batch) which shows the check 000357 as voided which makes some sense given the issue you had releasing that batch.  Does apdoc have any records for batch 001747 (the first batch where you used that same check number)?  How about records in aptran for batch 001747?  this is why I believe you need someone doing a remote session with you that can look at the various data tables involved.

  • Igor_CF Profile Picture
    Igor_CF 165 on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    Hello!

    Here is what we have in APDoc:

    Batnbr vendid Doctype Refnbr Rlsed Docbal origdocamt curydocbal curyorigdocamt selected

    001748 SML001 VC        000357 0       0        3922 0        3922        0

    Thanks again for taking time

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    Even with the added information, my question still stands as to whether you tried to use the same payment reference number (check number) in both batches.  I understand that the system, on the check screen, displays the next available check number and that you did not change what it presented.  However, the system determines the next available check number by looking for the largest check document in the system and then adds 1 to that number.  The check documents are not created until you do the keep checks action on the check update screen that is presented after the checks are printed.  So, if the first check printing presented the check update screen and you did not process the check update but, rather, just closed the screen and then ran the second check process, I believe the next available check number would be the same as it was on the first run because the checks from the first run had not yet been kept and this problem might happened under that scenario.  All of this is assuming the payment were selected using either the payment selection screen or the edit/select documents screen and then the checks processed using the check screen (that assumption is based on the last piece of information supplied).  However, you have stated that these are wire transfers and not actual checks which makes me wonder if something was done differently on these payments away from your normal check processing steps.

    So, we are back to trying to determine why both check batches are trying to use the same check number.  Further, it still sounds like the first payment is not showing in all the places it should (e.g., the check register).  We need to look at the APDoc table to see if there is a check document for that batch using that check number.  To take this further, it sounds like you need someone to do a remote session with you that knows all the pieces to look for.  You stated you are the end-user.  Do you have a Dynamics SL partner that you are active with?  If so, they are you first choice.  If not, you could open an incident with Microsoft.  As a last resort, I may be able to assist you depending on your location.

  • Igor_CF Profile Picture
    Igor_CF 165 on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    This again the reply from the person who entered the info:

    Check batch 1747 for $5,000 can be viewed under GL post transactions as unposted.  I never select the check number for these wire payments.  I only enter 1 and the system automatically assigns the next available number. I was processing two separate payments for two different dates for the same voucher 001563.  Both AP batches were through edit/select document for payment process.  The AP aging shows the $5000 payment.  Periods are correct.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: System Message 6909: Another process has already added the cursor=DefaultCreated

    Based on the unique key structure for apadjust, you cannot have the same check number (adjrefnbr) entered for two different check runs.  From you last post, it sounds like you created 2 different check batches using the same check number (000357) paying the same vendor and voucher.  That has me confused as it sounds like you were attempting to make 2 payments against the same voucher using the same check number.  That sounds illogical.  You also said that check batch 001747 contains the 5000.00 check and has been released but the check does not show in the check register.  It should if that batch successfully released so there is something wrong or incorrectly stated on this.  Did the first check batch get posted to a different period than you ran the check register for?  I would like to resolve this portion of the issue before moving on to what appears to be something illogical (using the same check number in two batches.  not even sure how you were allowed to do that since the check screen would not let you enter an existing check number).  Where these check batches from the manual check process or the payment selection process?

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans