Finance | Project Operations, Human Resources, ...

WorkFlow - GL Approval batch gets stuck in 'busy' state ?

(0) Share

Report

Posted on by Beat Bucher GP Gee...

28,061 Moderator

I've a customer who has recently implemented the WF GL Batch approval process in GP 18.3 and ever since they started submitting batches for approval, the main approver complains about not being able to approve the batches, because their status in GP looks like 'busy'.

I checked the batches and the workflow setup (which looks fairly simple and straightforward), and in both cases the WF was escalated due to timeout of 4hrs in the approval deadline.. Is it possible that this "escalation" is causing the batch to become 'busy' ?

Thanks for any insights on this topic.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Margi Jandro Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

Has the customer considered changing the escalation if the deadline is being missed at 4 hours?

The values for Workflow_Status will follow the same rules on the header of the transaction in workflow such as the SY00500 for batches.

When a batch get stuck in a ‘busy’ state, we recommend using this KB article to resolve the issue. KB - A batch is held in the Posting, Receiving, Busy, Marked, Locked, or Edited status in Microsoft Dynamics GP

The transaction header Workflow_Status should match the WFI10002 workflow_status in the workflow tables.

The Workflow_Status values:

1- Not Submitted

2- Submitted (Deprecated)

3- No Action Needed

4- Pending User Action

5- Recalled

6- Completed

7- Rejected

8- Workflow Ended (Deprecated)

9- Not Activated

10- Deactivated (Deprecated)

I hope this helps!

Margi Jandro

Microsoft Support

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,061 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you Margi,

I'm fully aware of the procedures to unlock stuck batches from the SY00500 table... the question is : why would a workflow that is overdue and triggers an escalation cause a GL batch to get 'busy' ? This shouldn't happen, as the final approver would be unable to approve the batch, even if it was overdue...

I had already found the KB article from Microsoft about the new WF 2.0 capabilities and table description, which helped me to confirm the status of the GL Approval batch WF, but not to understand why it happens.

support.microsoft.com/.../workflow-2-0-tables-used-with-microsoft-dynamics-gp-32a70d68-6cb9-0180-199b-bc23b575a5ba

Was this reply helpful? Yes No
Nicole Hellerud 1,712 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Beat-

Thanks for the post and update.

In my testing I was unable to re-create. I allowed the workflow on my General Ledger Batch to escalate do to failure to approve in the time window. My status remained at 0 in the SY00500 table. Do you know whether these are re-occurring batches and if they allow the workflow to escalate on a test batch does the same busy status appear?

We look forward to your update when available.

Wishing you and yours healthy and happy days ahead!

Nicole Fiskum

Microsoft Dynamics Support

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,061 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks Nicole,

I wasn't able to reproduce it myself either, and I'm waiting back from the customer to confirm another occurrence of the issue..

I'll check periodically with them if they had a chance to submit and approve more batches.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,061 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Nicole

After several months of more WF submissions and more GL Batches that kept stuck in "Busy" state it looks like we narrowed down the problem to be related to the AA module (Analytical Accounting) in GP.. The customer has over a dozen companies, from which some don't have AA installed / enabled, and others do use it.

All companies are setup with WF approval for GP batches, and they never run into any issues in the companies that don't have AA.

This looks like to be a bug related to the AA module in conjunction with the WF approval process for GL Batches.. .

Update (2021-10-26): it looks like this bug was fixed by Microsoft along a few others in the Fall 2021 release (18.4). Going to plan an upgrade with customer ASAP to fix that.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,061 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

The issue was definitely fixed with the Fall release 2021 update.

Case closed.

Thanks for all the input.

Was this reply helpful? Yes No