Unhandled Database Exception Error When Posting Project Accounting Employee Expense Transactions

Issue

Using Table Import and the updated Software Development Kit documentation on Employee Expenses, I have created source files and import definitions for the following Project Accounting tables: PA Employee Expense Header, PA Employee Expense Detail and PA Employee Expense Distribution. I run checklinks on the PA Employee Expense Transactions and receive messages that the batch has been created with its total amount and transaction count updated and the PA Key Master records are created.


When the batch of Employee Expense Transactions is posted, this error is returned:


'Unhandled database exception: A get/change operation on table 'PM_Key_MSTR' could not find a record.'


The transactions do update my Project Accounting tables; however, I only receive one posting journal, the Employee Expense Posting Journal. On the Payables side, I'm not confident that the tables have been updated correctly.


I tried modifying my import routine and including checklinks on the PM Transaction Logical Files after running checklinks on the PM Employee Expense Transactions, but still received the error when posting.


Resolution

Import into the PM Key Master table, PM00400.


Note - Information on required fields for the PM00400 is located in the PMTrx.rtf Software Development Kit document.


1. Import into the Project Accounting Employee Expense tables and the PM Key Master table.


2. Run Checklinks on the PA Employee Expense Transactions only (do not run checklinks on the PM Transaction Logical Files).


3. Print an edit list of the batch.


4. Post the transactions.


No errors should be returned during the posting process and all Project Accounting and Payables tables should be updated appropriately.



This article was TechKnowledge Document ID:23336

TechKnowledge Content

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×