![]() ![]() ![]() Doing this can trigger GP to automatically recover the batch for you, negating the need for any intervention at SQL level.įor example the user “sa” wasn’t active with the batches “SL JAN INVS” or “RMSLS0000009” so after logging the “sa” user back into GP we were prompted with the message below: If they aren’t then the first course of action is to ask them to log out of GP and log back in. Once in this window it gives you an overview of what users have which batches open and a status of what is happening in those batches.Īrmed with this information we can check directly with those users to see if they are indeed working in those batches. You can access the window via the option “Enquiry > System > Batch” The “Batch Enquiry” window is a little known window that gives you a peak into the “Batch Activity” table (the SY00800 table in the DYNAMICS database – a row is inserted into this table when a user is active in a batch). When this occurs users and admins can be tempted to delve straight into SQL however you can also use the “Batch Enquiry” window to see which users are active with those batches. (as this is receiving transactions from the Sales Invoice batch I’m posting)Īs I mentioned above this is all normal behaviour, however instances can arise where no one is in the batch yet the batch status remains as “Busy” or “Receiving”. In the scenario below I’m posting some Sales Invoices, so the General Ledger Batch RMSLS000009 is showing a status of “Receiving”. For example I’m working in the “GAV JAN INVS” batch so the series post window shows this batch as “Busy” When you are working in a batch in Dynamics GP the batch status changes to record you are active in that batch. You can then take some remedial action to hopefully prevent any long winded SQL fixes. When this happens users and admins will often dive straight into SQL to investigate further, however this post shows how you can use the little known “Batch Enquiry” window to get a greater insight into what is happening with batches in Dynamics GP, without the need for SQL. This is generally nothing to worry about, it just means a user is active with that batch, however if the batch continues to say “receiving” or “busy” when no one is posting, further investigation may be needed. Situations can arise where batches show a status of “Receiving” or “Busy” in the various series post windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |