910
Other than the PM Vendor Master File table (PM00200), what are the other tables that are updated when new vendors are added? We acquired 7 new facilities recently and are importing their existing vendors. I want to be sure we update all the correct tables on the SQL side since it will be easiest to perform a SQL table import for this large amount of vendors.
*This post is locked for comments
Thank you very much Rubal, Bron, and Leslie. This is all extremely helpful information. I had started working on using I.M. before I had submitted this question, but I was getting some cryptic errors that were leading me to a dead-end, and am more comfortable working with SQL so I thought I would try that route. I've used the Resource Descriptions window before but usually find it unspecific for what I'm looking for. Thanks again for everyone's suggestions, this should get me what I'm looking for.
Below are the files identified in the SDK
Files to import
PM Vendor Master PM_Vendor_MSTR PM00200
PM Address Master PM_Address_MSTR PM00300
PM Class Master PM_Class_MSTR PM00100
PM Vendor Master Summary PM_Vendor_MSTR_SUM PM00201
PM Vendor Master Period Summary PM_Vendor_MSTR_Period_SUM PM00202
Purchasing 1099 Period Detail pm1099PeriodDtl PM00204
Vendor Accounts PMVendorAccounts PM00203
Vendor Class Accounts PMClassAccounts PM00101
The import of vendors requires importing into the PM Vendor Master & the PM Address Master. After the import, perform a checklinks on the PM Vendor master logical file to create the summary records. To use the rolldown feature with the Vendor classes, the best method is to:
1. Create the Vendor Class with only the required fields filled in.
2. Import the vendors normally.
3. Go back to the Vendor Class Setup window and enter the fields to rolldown.
4. Save the class and press yes to rolldown changes.
Kind regards,
Leslie
The SDK which is installed from the Tools\SDK folder in the install media has a section on importing the Vendor master files. This part of the SDK was very valuable back in the old days before Integration Manager (imagine!) and eConnect. Table Import utility was all we had.
Be aware that this is core only. If you have any other dictionaries that include payables functionality, be sure to check with those tables. You can run a DEXSQL log to discover table activity. Also you could run a SQL trace.
Like Rubal said, have a backup and TEST, TEST, TEST. I have done it several times very successfully. Be sure to run CheckLinks after any import.
Kind regards,
Leslie
The best practice is to use Integration Manager to import Vendors. Each environment is a little different and table imports can be tricky.
I would be certain you have not purchased Integration Manager before attempting table import.
Having said that.........
Tools > Resource Descriptions - choose Microsoft GP - choose Purchasing (series). Will list all tables......
Master record tables typically start with '00' such as PM00200, PM00201, etc.......
After Importing (if you table import) definitely run checklinks........immediately after........make SQL backup before (just in case).......
For vendor address, you will also need to save data in table PM00300.
For importing data directly in SQL tables, you will require to apply all validations and constraints yourself. Make sure you test the scripts before using them in production environment.
Rubal,
#1
André Arnaud de Cal...
291,711
Super User 2024 Season 2
#2
Martin Dráb
230,458
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
