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

(0) Share

Report

Posted on by Igor_CF

173

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

I have the same question (0)

All responses (14)

Answers (1)

Suggested answer

Community Member on at

Like (1)

Report

The primary key on the apadjust table consists of the adjusted reference number, the adjusted doc type, the adjusting reference number, the adjusting doc type, the vendor id, the adjusting account number and the adjusting sub-account number. So, it appears that this combination already exists in the apadjust table. That either means it existed before you released this check batch or the release of this batch had gotten far enough to make this entry and now a second attempt to release the batch is running into this entry. However, it has been my experience that SL handles the later case without error. The third possibility is that there is an issue with your check batch you are trying to release such that it has this same combination twice thereby causing the error. So, I suspect that your issue is not one of trying to re-release the batch. One way to determine that would be to run a query against the apadjust table filtering for the primary key combination and look at the adjbatnbr field for the record that is found. If that field contains the current check batch number then you will know the issue is not caused by a prior batch with the same combination of items. You can also look at the artran records for the current check batch. They provide the information that goes into apadjust. Once you determine whether the collision is from a prior batch or from the current batch we can then determine what needs to be done to correct it.

One final thought. Has this database been active for a fairly long time and have you possible changed bank accounts such that you have started to recycle check numbers? If so then the possibility that the issue is resulting from a prior and older batch.

Was this reply helpful? Yes No
Igor_CF 173 on at

Like (0)

Report

Thank you for replying. the database is fairly new and we know for certain that check numbers weren't reused.

Doesn't look to me there is a collision with another batch, but looks like second possibility you describe. I'm not sure what is the policy for the forum, but i could post whole output of sqldebug script.

In the output i noticed this:

######################## LOOK FOR TOP ERRORS #################

Stuck records in WRKRelease or WRKReleaseBad

WRKRelease

BatNbr Module UserAddress tstamp

(0 row(s) affected)

WRKReleaseBad

BatNbr Module MsgID UserAddress tstamp

001748 AP 0 CFAPPSERVER3RDP-Tcp#0 0x00000000004A7302

I'm not too sophisticated with SQL, but i found there is an entry in apajust for batch number 001747 that printed the first check.

What else i can check?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

If this is the case of a partially released batch trying to be released again then the batch should have a status of S. You did not indicate that in your post but I suspect that is what you have. To further diagnose the issue and come up with a solution we need to know some more information. Let's start with how many checks are in this batch. This helps determine what cautions need to be taken during the resolution. I would like to see the apadjust records that have the adjbatnbr equal to this batch and the aptran records from this batch. This tells us how many records have been added to the apadjust table for this batch and what is left to be done. Care needs to be taken because not only are apadjust records being added but the paid vouchers are being updated as well as the vendor history during the release process. Normally working this issue is best done where the "expert" has a remote connection to the database and performs the necessary steps to correct the situation as opposed to a forum post on what to do since the actions taken vary depending on what is in the database and the actual cause of the problem. Are you the end user or an SL partner trying to resolve this issue?

Was this reply helpful? Yes No
Igor_CF 173 on at

Like (0)

Report

Here is better explanation from one of our accountants:

Check batch #001747 was for 1 check $5,000.00 (which printed fine as check #000357) This was a partial payment against voucher 001563. The aged AP shows the current balance for this voucher to be $3,922 (orig. $8,922 less $5,000 check). This batch is not posted to the general ledger and the check is not included on the check register.

Check batch #001748 was for 1 check $3,922 (which printed fine as check #000357-same number as above) This was the final payment against voucher 001563. This check batch cannot be released and doesn’t show in the AP vendor maintenance screen or the check register.

So looks like it's check number collision.

We're end user and this forum was always a big help for us.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Igor_CF 173 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Igor_CF 173 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Igor_CF 173 on at

Like (0)

Report

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

Was this reply helpful? Yes No

Community site session details

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

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Featured topics

Product updates

Community site session details

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

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Featured topics

Product updates