246
I need to add the Shipping Method field to the default AP Check with Stub on Top and Bottom. It's not available in in any of the tables that already exist AP Check but is available in the PM20000 table. I'm having trouble adding that table to the existing AP Check format in Report Writer. Hope there's someone that can tell me how to add the table.
Thank you in advance for your help!
*This post is locked for comments
Wow Mick you're amazing and I'd love to try it. Sounds like you've hit on another possible scenario. I can test it in the test environment to be sure I get the same result.
THANK YOU SO MUCH!!!
Peggy,
I think we are good to use the PM10201 PONUMBER column.
The actual PM Invoice uses the PM10200 PORDNMBR which flows through the PM20000 and PM30200.
I checked a few different environments and didn't find the PM10201 PONUMBER populated, and it doesn't flow through the History tables in the PM30200 for the Payment.
If you would like to test the new PM10201 trigger let me know and will email through.
Sorry for delay but was testing different scenarios before responding.
Mick
Any other ideas???
Mick, thanks so much for responding!!! Yes we are using the separate remittance as well as the re-create remittance. AND, we ARE using the PO# field which is why we didn't try to use that field for the check. I hate that a field would be available on the check but NOT on the remittances.
Peggy,
Sounds like you are printing the Separate Remittance, the PM10300 isn't part of the Tables for that report.
I can create another trigger on the PM10201 to update the PONUMBER column in that table.
Just check your not using that field at the moment and it is blank in the table.
Mick
Hey Mick, The script you sent me works like a charm and I thank you SO MUCH. My problem now is that the Comment1 field is NOT available on the Remittance Form! I swear, as soon as I think I got it....another stumbling block. Have any ideas???
Peggy,
The code was actually developed on GP2010 a few years back, and I updated for you on GP2016, and there were no changes to be concerned.
Add a step in your upgrade documentation to check the code still exists after an upgrade, sometimes an upgrade can remove custom triggers, which is why we run queries on the database to see what custom code might be in place.
As you can see, the code is looking for the Batch Source to match "XPM_Cchecks".
Mick
Ok Mick, I think you're a lifesaver! It didn't work for the first few times I tested it but I think I needed to relaunch GP for it to work. I'll do some more testing a bit later but can't imagine anything would pop up.
Don't want to over step but I have a couple more questions if you don't mind. What will happen when I upgrade to 2015 and beyond? Will I need to do anything additional? Thinking is should be fine unless the tables change?
THANK YOU SO MUCH for your help!!!
Hey Mick! Thanks for chiming in here. Are you saying you successfully linked the PM Transaction Open with the PM Payment Work in the AP Check with stub on top and bottom-graphical? The field I need to access is the Shipping Method in the PM Transaction Open. If so, I'd LOVE if you can shed some light on how you did it successfully!
Thanks Again!!!!
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
