web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / The audit trail code c...
Microsoft Dynamics GP (Archived)

The audit trail code cannot be assigned. Information is incomplete or missing

(0) ShareShare
ReportReport
Posted on by Carlos Cabrera 200

 

Hola,

I am runing GP 10 with SQL 2005. Having trouble creating the new fiscal year, found the problem on the knowledge base in article 853548, followed the instructions for R10, and I was able to create the fiscal period. The problem is that nothing has posted through the general ledger since. Transactions are created on the general ledger, the edit list shows no errors, but the transaction goes to batch recovery when the post button is hit - we have no errors, but cannot post.

Update - I changed the posting setup to print the general posting journal - the report says that the audit trail code cannot be assigned. Information is incomplete or missing. I used the Professional Services Tools to recreate the SY00800 table as suggested but no luck. Can someone help please?

Carlos

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hello,
    I have received some information around your question. Please read the followin suggestions. Please read all the instructions before executing.

    It sounds like the user in question may have an issue with the Audit Trail Codes table - SY01000 in the Company database, the Source Documents table - SY00900 in the Company database, or the MESSAGES table in the DYNAMICS database. We can try the first two using Microsoft Dynamics GP | Maintenance | Clear Data and the third using a SQL statement via Query Analyzer/SQL Management Studio. Before doing any of these steps, a backup of both the Company and DYNAMICS database should be made in case an undesired data change occurs.

    First, here are the steps to rebuild the Source Document Master table:
    1. Go to Microsoft Dynamics GP | Maintenance | Clear Data.
    2. Change the Series to Company.
    3. Highlight the Source Document Master table and click Insert, then OK and finally Yes to begin the process.
    4. Check to see if the issue has been resolved by reviewing the report and attempting to post batches.

    If that does not resolve the issue, we can clear out the MESSAGES table:
    1. Access the appropriate SQL Server using Query Analyzer/SQL Server Management Studio.
    2. Select the DYNAMICS database and execute the following query:
    DELETE FROM MESSAGES
    3. Log back into GP to rebuild the MESSAGES table and then review the report/attempt to post batches.

    If that also does not work, we can try rebuilding the Audit Trail Codes:
    1. Go to Microsoft Dynamics GP | Setup | Posting | Audit Trail Codes
    2. Print the report on this screen for each Series - unfortunately you have to pick a Series, print the report, switch to the next Series, print a report, etc. This will ensure that the proper Next Number and Reprint values are preserved.
    3. Go to Microsoft Dynamics GP | Maintenance | Clear Data.
    4. Change the Series to Company.
    5. Highlight the Audit Trail Codes table and click Insert, then OK and finally Yes to begin the process.
    6. Go back to Microsoft Dynamics GP | Setup | Posting | Audit Trail Codes.
    7. Using the reports printed in Step 2, modify the Next Number and Reprint values for each code.
    8. Check to see if the issue has been resolved by reviewing the report and attempting to post batches.

    Please let me know if this helps. If it does not, it would probably be best for the Partner/Customer in question to create a support incident as I think this issue might be more complex than should be handled via the Communities site. Thank you!

     I hope this helps.

  • Steve Bowler Profile Picture
    Steve Bowler 5 on at

    This information was great. I had the exact error message in GP 9.0 and the second step helped resolve the issue. However, I find it very fustrating that this sort of information is not in the Knowledge Base. All I could find in the KB was article 852257 which applies to GP 6.0. I spent a whole day trying to resolve this issue before I did a google search on the error and found this forum as the first result in the search. Thank god for google.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans