Known Issues · SFDO Accounting Subledger
SFDO Accounting Subledger (ASL) customers with Large Data Volumes (LDV) may run into performance issues while running the LEDG_CreateLedgerEntry_BATCH batch job. Increasing the batch size will cause cpu time increased therefore potential throttles could occur.
In Review ·Reported By 3 ·Updated 2022-10-06
In an Org that has Accounting Subledger installed with a single-object Accounting Set Active, changing the Fund Name does not generate the correct data. If you change the Fund Name of the Allocation Ledger Entries are reversed and redone, but not the Payment and Transaction.
No Fix ·Reported By 0 ·Updated 2022-08-09
When the Payment is not created at the same time as the opportunity, the Payment allocation converts all the allocations to Percentage allocations when creating the Allocations on the Payment. And these Payment Allocations Percentages that are determined are truncated. When the nightly Subledger Accounting...
Fixed in version NPSP 3.210 ·Reported By 6 ·Updated 2022-08-08
When loading Opportunities into an Org with Accounting Subledger enabled, a "Too many SOQL queries" governor limit error is presented. *Note: Currently this issue is only present in Sandboxes following the upgrade to Accounting Subledger 1.33, and is not scheduled to be pushed to Production instances...
Fixed in version Accounting Subledger 1.34 ·Reported By 3 ·Updated 2022-08-08
If a user reduces the Payment Amount on a paid Payment after initial Ledger Entries were generated, adjustment Ledger Entries will be created representing the correction. The Fulfills An Accrual field is incorrectly checked on the adjustment Payment Ledger Entry record.
No Fix ·Reported By 1 ·Updated 2022-07-21
When support for Multiple Accounting Sets is enabled, Accounting Data Record Type filters are not respected in active Accounting Sets. Accounting Subledger creates Ledger Entries for all active Accounting Sets, regardless of record type.
No Fix ·Reported By 1 ·Updated 2022-07-21
Customers with large numbers of Ledger Entries (>200k) may see time outs in the Accounting Scheduled Job. Because that job queries for null values in the Accounting Set Name and Primary Object Id fields, and because null values are not included in indexes by default, the nonselective query times out....
Fixed in version Subledger 1.7.0.1 (Summer '22) ·Reported By 3 ·Updated 2022-06-14
Users can now customize Accounting Sets to map data in source records to fields in Ledger Entries, including the Transaction Date. If one record in an Accounting Scheduled Job has a Transaction Date that does not fall within an open Accounting Period, it causes all records in the batch to fail, even...
Fixed in version Subledger 1.7.0.1 (Summer '22) ·Reported By 0 ·Updated 2022-06-14
SFDO Accounting Subledger - $0 Opportunity with $0 Allocations causes Divide by Zero Error
If a User creates a $0 Opportunity, with a $0 Allocation, when the Accounting Subledger Batch Job runs appearing successful but instead no Ledger Entries are generated.
In Review ·Reported By 2 ·Updated 2022-05-16
When using Accounting Subledger for NPSP, if customer writes off a pledged Opportunity payment, a Ledger Entry record is created that credits the original GAU Allocation instead of the receivables account identified by the Default Accrued Account Code. The resulting Ledger Entry records do not properly...
Fixed in version SFDO 234.4 ·Reported By 1 ·Updated 2022-02-16
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
