ITOM Licensing Aggregator Store is generating zero count.DescriptionPrerequisite: 1. Instance Language is other than English. 2. The aggregation count is 0 in 'itom_lu_ci_counts' table. Steps to Reproduce Install Servicenow ITOM SU Licensing Store App2. Activate any other localization plugin (German/French) 3. If its not a prod instance, install dummy license. 4. Trigger the the ITOM Licensing Aggregator Store Job5. In itom_lu_ci_counts table the aggregation count is not correct for any application. Workaround ServiceNow ITOM SU Licensing Store App Version is prior to 2.4.0(How to Commit Update Set -> Steps)Navigate to System Update Sets > Update Sets to Commit.From the Related Links section at the bottom of the page, go to Import Update Set From XML.Choose File to Upload. Select the sys_remote_update_set_2ccc50e8432a5110c40de8a09ab8f2e5.xml file to upload.Click on Upload Dialog Box. You will be redirected to Retrieved Update Sets Table, Open the "Localization Issue" and click on Preview Update Sets.(this will check for any potential conflicts of the update set in your instance).After Successful Completion of the above step, click on Commit Update Set. Repeat Steps 2-6 with the second update set attached. This time you will have to open "Localization Issue Scripts" record and continue with above steps. (sys_remote_update_set_af813c3e43221110c40de8a09ab8f2b8.xml)You will start getting correct aggregation counts from next scheduled Job run. 9. If the customer has purchased Visibility License Subscription, disable the property "enable_license_count_without_subscription" as false. The correct count will be generated in daily count for Visibility rather than Discovery. ================================================================================================== ServiceNow Store App Version is 2.4.0 Navigate to System Update Sets > Update Sets to Commit. 2. From the Related Links section at the bottom of the page, go to Import Update Set From XML. 3. Choose File to Upload. 4. Select the sys_remote_update_set_a2e4b8c68769e11010f08519dabb35ec.xml file to upload. 5. Click on Upload Dialog Box. 6. You will be redirected to Retrieved Update Sets Table, Open the "Licensing Wrong Language Record Delete" and click on Preview Update Sets.(this will check for any potential conflicts of the update set in your instance). 7. After Successful Completion of the above step, click on Commit Update Set. 8. Repeat Steps 2-7 with the remaining two update set attached. This time you will have to open "Licensing Accounting Scripts" and "Localization Issue" record and continue with above steps. (sys_remote_update_set_6fd6814287e9e11010f08519dabb35de.xml & sys_remote_update_set_2ccc50e8432a5110c40de8a09ab8f2e5.xml respectively). 9. Run Once the On Demand Scheduled Job "Delete Aggregation Records Wrong Language" which gets imported as part of "Licensing Wrong Language Record Delete" Update Set. 10. Check 'itom_lu_ci_counts' table and filter with Aggregated=true. There shouldn't be any records. 11. Check versions of these three Scripts: a) ITOMLicensingAggregationHelperStore b)ITOMLicensingUtilsStore c)ITOMLicensingAccountingHelperStore The version should be -> Update Set: Licensing Accounting Scripts 12. From next run, will start getting correct aggregation counts with expected Application Name and accounting usage.13. If the customer has purchased Visibility License Subscription, disable the property "enable_license_count_without_subscription" as false. The correct count will be generated in daily count for Visibility rather than Discovery.Related Problem: PRB1605432