SBX - Search With Button

SBX - Forum Post Title

SL 2018 CU1, SQL Message 93, GLPostDebug

Microsoft Dynamics SL Forum

StuartN asked a question on 28 Mar 2019 8:47 AM
My Badges

Question Status

Suggested Answer

My client is testing as part of the upgrade process (from SL 7.0). On releasing an AP batch, one of the users received SQL Message 93. A quick Google search turned up B2551470_FRx_SL2011.zip which alters a trigger for FRx. The batch did make it through to GL. However, when I try to post the batch, nothing happens. I get Process Complete, but the batch remains in the Post Transactions screen. Nothing in the event log either. 

I found and ran the GLPostDebug script, which told me I have "situation 3011," which would be great if I know what situation 3011 meant. Does anyone have a listing of the codes from this debug? Also, will the B2551470_FRx_SL2011.zip script work in SL 2018 CU1?

Thanks!

Reply
Mark E responded on 28 Mar 2019 4:23 PM
My Badges

Are you still using FRx with SL2018, or have you migrated over to MMR?  If using MMR, then all the FRx triggers can be dropped.  The 3011 Message can be found in the Messages table (or csv), and indicates the "batch is not in balance and not posted".  You can review the GL Batch in Initialize Mode from the Journal Transactions screen, selecting the AP module.  Hunch is that the Batch has no GLTran records.

Reply
StuartN responded on 29 Mar 2019 7:33 AM
My Badges

We will be migrating over to MR, just not sure if it’s immediate yet. I’ll drop those triggers and recreate the with the install.

 

An empty batch was the first thing I thought of. I have reviewed the batch and it does have records. Looked at them in SQL and didn’t see anything jump out at me.

 

Thanks!

Reply
Mark E responded on 29 Mar 2019 8:55 AM
My Badges
Suggested Answer

In SQL, review the GLPostDebug proc.  It calls the pp_01520 proc in debug mode.  Open that proc, and search on the 3011 text, you will see a few references to that situation code.  Review the scenarios where that code is referenced as an output.  One of them will match your situation, and should help you determine the cause of the out of balance error.  You might have a bad or missing CuryID issue or Cury Dr/Cr Amt vs Base Dr/Cr Amt.

Reply
Mark E responded on 29 Mar 2019 8:55 AM
My Badges
Suggested Answer

In SQL, review the GLPostDebug proc.  It calls the pp_01520 proc in debug mode.  Open that proc, and search on the 3011 text, you will see a few references to that situation code.  Review the scenarios where that code is referenced as an output.  One of them will match your situation, and should help you determine the cause of the out of balance error.  You might have a bad or missing CuryID issue or Cury Dr/Cr Amt vs Base Dr/Cr Amt.

Reply

SBX - Two Col Forum

SBX - Migrated JS