Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / GP Workflow - restrict...
Finance | Project Operations, Human Resources, ...
Answered

GP Workflow - restricting Financial Batches

(0) ShareShare
ReportReport
Posted on by Ron Alexander 185

Hello

I'm working with a customer on their Financial Batch workflow.  They would like to require approval only on general journal entry batches and exclude batches created from subledger modules (like Sales and Purchasing).  We've put in Conditions to exclude if Batch ID contains PMTRX, RMSLS, etc. however it seems a user could name a financial batch PMTRX and get around the approval process.

Is there a condition or option to require approval for batches created in Financial Series?  I saw the Origin field listed in the conditions however I wasn't sure how to link it in the Conditions.

Best Regards - Ron A

Categories:
Microsoft Dynamics GP
  • Ron Alexander Profile Picture
    Ron Alexander 185 on at
    RE: GP Workflow - restricting Financial Batches

    Thanks for the helpful information.  We'll try the customization piece to see if it helps.

    Best Regards - Ron

  • Verified answer
    Isaac Olson Profile Picture
    Isaac Olson on at
    RE: GP Workflow - restricting Financial Batches

    Hi Ron,

    The quick answer would be to change the posting setup to post 'Through' from sub modules so that batches from those other modules don't stop at the GL to require approval.  If that's not possible or their business process doesn't allow that, then you would have to add an extra join to your workflow to the GL10000 table so that you can use the SOURCDOC field to determine whether the Journal Entry lines in the batch originated from a different module or not.  

    select SOURCDOC,* from GL10000 --GJ would be General Journals

    By default the GL10000 is not a table that you can create conditions on, but we have a tool that allows for enhanced workflow condition editing where you could join the SY00500 to the GL10000 to make workflow condition based on the SOURCDOC field.

    Physical Name Display Name Technical Name
    GL10000 Transaction Work GL_TRX_HDR_WORK

    Below is an article with more information and the DEX.ini switch that enables this.  I would recommend trying it in a test company with a copy of live first, then repeat the process once fully tested.  The custom joins for workflow are made per company database. 

    community.dynamics.com/.../joining-in-additional-tables-for-workflow-conditions

    QueryDesignerAllFunctionality=TRUE

    I hope this helps!

    Isaac Olson

    Microsoft Support

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

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans