75,730
Client wants the ability to change the checkbook ID on a checks batch after the batch has been created and the checks have been selected. I thought this tool was available in the PSTL tool but I have not been able to find it. This is for GP 2016 R2.
*This post is locked for comments
I would imagine if I create a check batch and then do a search for the batch name in the database it will show me all the GP/MEM and Mekorma tables involved. I have a sandbox in which to play so we will be fine. Once we get this developed we will start to market it to the entire GP community. Think of the millions we can make!
Funny, because nothing you mentioned above stated this one little detail ;)
I still don't understand the rationale behind this request. Why not build the checks with the right checkbook to begin with? The build process is not going to allocate any cash until the checks are printed and posted anyways.
Thanks Mariano, this client has over 200 checkbooks and has stated that this is a must have feature before they go live. This has to do with Binary Stream's MEM product and Mekorma's MICR and Multi-Batch. They need to select the checks using one entity(one checkbook) but cut the checks out of another checkbook.
The Professional Services Tools Library's Select Checks Combiner is used to consolidate checks for the same vendor within the batch, not to change the checkbook ID. All that said, I performed the following test:
1. I built a batch with couple transactions - Batch Number: TEST
2. After the batch was built, I checked the checkbook balance and noticed it hadn't change. That's important, because it means the checkbook balance is only updated after the batch is printed and checks are posted.
3. I ran the following query to change the checkbook ID at the payment transaction level:
UPDATE PM10300 SET CHEKBKID = 'UPTOWN TRUST' WHERE CHEKBKID = 'FIRST BANK' AND BACHNUMB = 'TEST';
4. Once payments were updated, I updated the Batch Headers table, as follows:
UPDATE SY00500 SET CHEKBKID = 'UPTOWN TRUST' WHERE BACHNUMB = 'TEST'
5. Finally, I was able to print the batch without any issues: all checks printed fine and the correct checkbook balance got updated.
Note that my test was conducted against Fabrikam. I sure don't need to tell you to backup all databases and make sure you conduct your test in a test environment prior to executing against production ;-)
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (