Update to Ledger Code in Asset Types Configuration Is Not Triggering the Correct Post Processing Required - Support Advisory
Issue
For clients who update or change a Ledger Code in the Asset Types tile within the Configuration Settings workspace for a specific Product Category, the system is not triggering the correct post-processing required to ensure those new changes will reflect in reporting.
When could the issue manifest?
When updates or changes have been made to the Ledger Code for a Product Category and the Asset Types Ledger Code is mapped to at least one GL String in at least one ledger on the Ledger Configuration tile within the Configuration Settings workspace.
How does the issue manifest?
All reports that show the GL Segment will continue to show the old value that was there before the update/change was made.
To identify impacted schedules, generate a BU Asset report for your current Open Period AsAt, without specifying a ledger, and filter on the Asset Type column within the report for the specific Asset Type that had the Ledger Code change.
Recommended Solution
Follow the steps below to import a Bulk Event template to recalculate the listed schedules that would be impacted by the Asset Types Ledger Code changes.
Step |
Action |
|---|---|
1 |
From Ask Alex’s menu, download the Bulk Event Import Template. |
2 |
Populate the template with the list of impacted Schedule numbers. |
3 |
From the Event Type drop-down, select Recalculate. |
4 |
Input the earlier of the Lease Start Date or AFUD in the Event Date. |
5 |
Enter any relevant Comments. |
6 |
Select Deal Summary from the Document Type drop-down. |
7 |
Save your template and navigate to the Bulk Import workspace within the UI. |
8 |
Select the Event tile in the Lease section. |
9 |
Click Choose File and select your saved Bulk Event Import Template. |
10 |
Click Validate. |
11 |
Verify there are no validation errors. |
12 |
Click Import. |