PM40103 table is empty in Dynamics GP 2015 R2

(0) Share

Report

Posted on by Community Member

I was wondering if anyone else has seen this before. While writing a SmartList Builder report to return AP distribution information, I added in table PM40103 and quickly found that for a client this table was empty. We are not sure how or why this table is empty, and in searching for possible articles on this topic I wasn't able to find anything. For now, I have updated the SmartList for the Distribution type (DISTTYPE) under Set Field Options with the values and long description but wanted to check with any other Dynamics GP experts to see if continuing to keep this table empty will or would be affecting GP functionally in any way?

Thank you for any feedback you may have.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Community Member on at

Like (0)

Report

RE: PM40103 table is empty in Dynamics GP 2015 R2

Jen, thank you for your feedback and looking as well. My guess also was that if this client has been running along without issues that it must be ok and as you mentioned it is all embedded in code. Appreciate your time.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: PM40103 table is empty in Dynamics GP 2015 R2

Mariano, thank you for the feedback. I did check SQL and it was empty, sorry if I didn't state that in my original post. Also, thank you for the script to repopulate the table. Much appreciated!

Was this reply helpful? Yes No
Jen Kuntz 3,220 on at

Like (0)

Report

RE: PM40103 table is empty in Dynamics GP 2015 R2

For what it's worth: that table is also empty on my installation. My guess is the actual list is embedded in code and thus the table itself isn't necessary for GP to function.

Was this reply helpful? Yes No
Suggested answer

Mariano Gomez 26,225 on at

Like (0)

Report
RE: PM40103 table is empty in Dynamics GP 2015 R2

I would suggest you check the table directly in SQL Server Management Studio. However, if this was an accidental deletion, you could run the following to repopulate the table:

TRUNCATE TABLE PM40103; INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (1, 'CASH','CASH'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (2, 'PAY','Accounts Payable'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (3, 'AVAIL','Discounts Available'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (4, 'TAKEN','Discounts Taken'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (5, 'FNCHG','Finance Charge'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (6, 'PURCH','Purchases'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (7, 'TRADE','Trade Discounts'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (8, 'MISC','Miscellaneous'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (9, 'FREIGHT','FREIGHT'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (10, 'TAXES','TAXES'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (11, 'WRITE','Write Offs'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (12, 'OTHER','OTHER'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (13, 'GST','GST'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (14, 'PPS','PPS'); INSERT PM40103(DISTTYPE, DSNMSHRT, DSNMLONG) VALUES (15, 'UNIT','UNIT');

Be sure to test this out first, then backup your production environment and run against it.

Was this reply helpful? Yes No