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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

Management Reporter: [G/L Transaction to Fact] has encountered an error. Processing will be aborted. Error text: Object reference not set to an instance of an object.

(1) ShareShare
ReportReport
Posted on by 2,165

We did a test upgrade of SL 2011 and MR 2012. Everything was fine in the test environment. We then completed the final upgrade for SL2011. We are rebuilding the data mart in MR and encounter an issue with the integration. We see the integration in progress, but it never completes. The Data Mart integration log does have one error in it that indicates the the C/L transaction to fact has encountered an error. Processing will be aborted. However, it looks like the integration is still in process. Any ideas on how to get this to complete would be appreciated. This is a very large database. Thank you.

*This post is locked for comments

I have the same question (0)
  • EDJJR Profile Picture
    Microsoft Employee on at

    Good Afternoon Deb,

    I would recommend for you to create a support case so that we can better troubleshoot the issue. There can be a variety of different issues that can cause the Fact table, in the DDM, not to populate.

    Thanks,

  • Verified answer
    Deb Lashua Profile Picture
    2,165 on at

    Thank you. I was able to determine the problem with the transactions and corrected them via sql. I have been able to rebuild the data mart without issue.

  • Community Member Profile Picture
    on at

    Deb,

    I am running into the same issue. Can you elaborate on what transactions were causing the problem?

  • Deb Lashua Profile Picture
    2,165 on at

    We actually had two issues - 1. Dimension Tran Error and 2.GL Tran Error. We were able to locate the affected transactions.

    1. The dimension tran error was caused by the vendorid in the fieldclassname field in the segdef table. Once we deleted this from the table, the error was resolved.

    2. The GL Tran error was caused by the curyid not be equal to USA or being blank in GLTran table. Once we corrected these transactions, the error was resolved.

    These errors can be caused by other things being incorrect in the tables. This is just an example of what you might run into.

    I hope this helps you. If not, I would suggest opening a ticket with Microsoft.

  • Camilo Virguez Profile Picture
    3 on at

    Hi ,  Yes...  agree with Deb Lashua's answer.  in my case we created a new environment and imported with .dat and .def file to a new environment  and we cleaned the transactions.  transactions on shared tables was not deleted for legal entities that were not present in the new environment.  had to go in ax and with a job finish the delete.  after that the MR  synch the information without any error.

  • Community Member Profile Picture
    on at

    Indeed, create an incident with Microsoft and ask them for the Diagnostic scripts that they have to look for any SL data that would cause problems w/ the MR integration. The scripts are extraordinarily useful in not only identifying the problem data but also on how to fix it.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans