We are using the legacy Accounting Subledger product in NPSP. The settings include a daily scheduled job (2am) and Accounting Review. The generated ledger entries are passed daily through an integration to our Lawson financial database following the NPSP job completion.
Our users need to merge contacts in NPSP but are challenged by unwanted ledger entry creation, usually as a result of the donorID field changing. The extra ledger entry records are confusing for the finance team which has already seen the initial records come through. We have struggled to find a way to prevent these from being created or to automatically mark them in some way that is specific. The ledger entry records appear to be locked down from editing unless one manually inactivates the abacus.LEDG_PreventModification_TDTM trigger.
Does anyone have advice for managing the record merge scenario in your org where the legacy subledger tool is in play?
-Margaret
Thanks for that insight, @Samuel De Rycke. I added my vote. I'm very curious how other teams have found ways to "safely" merge records without affecting the ledger entry creation.
