Release notes

Symptom: The job code will not zero out when trying to edit values in the Productive and Non Productive categories.

Resolution: Corrected by updating formulas in the Jobcode calc method when using ADC to fully zero a value if needed.

Symptom: In the Add New Jobcode calc method, there appears to be an error in calculating the NYB FTE. The current calculation assumes a full year FTE of the hours assigned in the staffing grid. With this calc method, you can define the start and end months of the new position, so it is not necessarily a full year position.

Resolution: Corrected by updating the formula in column Q rows 11-16 and 19-23 of the Add New Jobcode calc method to accommodate a partial year FTE.

Symptom: During a provider set up, an issue was discovered in the AQ within the provider detail methodology. Within AQ8, some of the groupings were by DataType and others by DataType.BudgetType. This becomes an issue when a user maps their data types to the specific groupings.

Resolution: Corrected by updating the use of the provider primary stat and secondary stat to use DateType.BudgetType.

Symptom: Many single row calc methods (listed below) on the Provider tab have formulas that include an INDEX() function with range that is "locked" at a row in the 4500 to 4600 range. When adding providers below this row range, the formulas fail with a #REF error.

• Add New FinancialClass
• Add New Revenue
• Add New Revenue ProviderDetail FinClass
• Add New Revenue ProviderDetail Location
• Add New RVU
• Add New RVU ProviderDetail FinClass
• Add New RVU ProviderDetail Location
• Add New WRVU
• Add New WRVU ProviderDetail FinClass
• Add New WRVU ProviderDetail Location

Resolution: Corrected by reviewing all instances of Indirect, Index, and Match formulas to update the ranges.

Symptom: Column AU of the single line interfaced and inserted calc methods reference incorrect cells on the Variables tab due to moving a row Variables tab.

Resolution: Corrected by updating the calc method to the correct variable reference.

Symptom: When using the Initiative tab in the Budget workbook, the save logic for Bud20XX in column AN and Bud20XX-Detail in Column AO, the system:

• Does not allow for saving of zeroed out initiatives in either table for initiatives that were previously non-zero.
• Does not zero out a non-zero initiative from the Bud2020 table if it is Excluded.

Resolution: Corrected by updating the Save to Database logic setup.

Symptom: When using "Salary" as the primary ProviderComp model, it appears that the Projected Compensation for the current year is either over or understated pending on how much of an FTE is involved as the YTD portion of the calculation does not take this into account.

Resolution: Corrected by updating how the YTD value is calculated to match the same logic use in Remaining Projection.

Symptom: When adding Add Detail - Input Monthly or Add Detail - Input Total rows into a detail calc method block, a duplicate keys error message displays when saving the plan file.

Resolution: Corrected by updating the RECORDID column to increment by a factor of 1. This was essentially an issue if the detail records were zero and that records was saved back to the Detail database.

Symptom: In the Budget Master Template on the Summary worksheet, the hide row formula in the cells F64, F66-F79, F81-F83 should only look at the specified row to determine if it should be hidden from view.

Resolution: Corrected by updating the cell formulas accordingly.

Symptom: When using the Staffing tab and using a KHABGTMapped department, duplicate job codes resulted because of a bad sectional filter for AQ4.

Resolution: Corrected by updating the sectional filter in AQ4 to use Dept.KGABgtMap v.KHABgtCode.

Symptom: When in the Windows Client and drilling to JE and AP/MM/AR transaction detail from the Expense tab of the Budget Plan File filtering is turned on but not working. The filter area is not set properly.

Resolution: Corrected by updating cell formulas in KHA_Drill09JE and KHA_Drill03Transaction.

Symptom: When using the target setting rows, the GLAcct lookup in column CK contains an error in the formula causing the GL Acct not to populate.

Resolution: Corrected formulas in column CK of the JTargetAdj lines.

Symptom: The Variable_Stat calc method on the Expense sheet does not account for scenarios where the associated Stat_Rev row has 0 value, resulting in #DIV/0 errors.

Resolution: Corrected by adding additional formulas to test for zero values.

Symptom: When using the Employee tab and adding a new employee row calc method in the existing job code block, the formula in month 2 through 12 of the Hours fields are missing the check to see if the job code is flagged as 2080 hours (comes from Jobcode table).

Resolution: Corrected by copying to formula from column AG and copying to column AR.

Symptom: In column CK of the JTargetAdj lines, the current formula does not properly look up mappings in the Jobcode.GLAcct column.

Resolution: Corrected by updating the Jobcode tab, column DD.

Symptom: Cell P48 on the Initiates tab should include the formula: =Expense!AI68. Instead, it contains =Expense!AI151. The issue was that the tenth month FTE factor resulted in zero.

Resolution: Corrected by adding the formula in cell P48.

Symptom: The formula to lookup the Hours GLCode in the Staffing tab is not consistent with other labor methods. If using the JOBCODE dimension for the Expense GLCode and PAYTYPE dimension for the Hours GLCode, the Hours GLCode resolves to zero (0). This is inconsistent with results for our other labor methodologies.

Resolution: Corrected by updating the JobCode and Add New JobCode calc methods for column CL.

Symptoms: There were items not interfacing into the Budget plan file even though there were records in the CPtoBP_2020 table.

Resolution: There was an issue with an AQ recognizing if Capital or Capital (Web) version was used. This had been corrected for either license type.

Symptom: When using either the Jobcode or New Jobcode blocks on the Staffing tab, the Weekly Hour total for the Evening shift does not change accordingly if a 12-hour shift is used.

Resolution: Corrected the formula on the Staffing tab.

Symptom: When working with the Initiative tab, if you approve an initiative, the dollars and hours flow into the Labor tab as expected, but this triggers the "Salaries Do Not Match" and "Hours Do Not Match" messages on the Expense tab since these amounts do not flow there (which is correct by design). The formula logic needs to be updated on the Expense tab so that these messages are not incorrectly triggered by the approved initiative amounts on the Labor tab.

Resolution: Corrected by updating formulas in cells in the JobCode tab

Symptom: When configuring the 04 Budget Driver and updating values in the IP, OP and Other columns, the updates are not reflected on the Stat_Rev tab of the plan file in the Global Drivers section.

Resolution: Correcting by removing the time stamp on the AQ and inserted blank rows in between the IP, OP, Other driver rows.​

Symptom: When interfacing plan files, the ProviderComp tab does not find GLAcct and HRAcct when using PayrollGLMapping. This problem presented to selected job codes while other job codes on this tab worked correctly (finding the GLAcct and HRAcct from the PayrollGLMapping table). This issue would occur when there was current year budget but no associated actuals.

Resolution: Corrected by bringing in the PayrollGLMapping table into the of Provider as part of setting up the provider tabs.

Symptom: On row 26 of the 30-line Jobcode Block calc method on the JobCode tab, the formula results in #DIV/0 in columns BH-BS (FICA).

Resolution: Corrected by updating the FICA logic to error trap for instances where the department primary statistic is zero.

Symptom: The following issues were discovered in regards to rebuildability of the sheet:

• Comments do not return after recreate/reprocess.
• Changes to the drop-downs and the input cells do not return on nested calc methods within the block.

Resolution: Corrected rebuildability issues.

Issue: In the Jobcode tab, column headers in cells EQ78:FB78 reference budget months in cells AG78:AR78 when in fact they should be formula driven by the rolling 12 actual history as defined in AQ7:Historical Hours Field Def row 17 (between columns EQ and FB).

Status: Corrected the category titles/labels to reflect the correct current actual year as well as the correct prior actual year. Also made formula changes to the JobCode tab in cell EQ147.

Symptom: The EmpID cell in the Provider Summary sheet displays ##### because the cell is not wide enough.

Resolution: Corrected by changing the cell formatting and right-justifying the EmpID label.

Symptom: Depending on the driver setting, the secondary or optional refresh variable could be Location or FinClass.

Resolution: Corrected by updating refresh variable to point to the correct FINCLASS or LOCATION element.

Symptom: In ProviderDetail, the sheet summary and provider summary are not dynamic. This means that when expanding provider, inputs are not reflected in the summary sections until the user saves the plan file.

Resolution: Corrected by updating the Department Summary section of Provider Detail and Provider Summary with dynamic formulas so changes to individual providers are reflected in real time.

Symptom: The CP_Integration calc method should not be available to non-administrator roles.

Resolution: Budget User role can no longer change the CP_Integration calc method. This is strictly an administrator-controlled calc method.

Symptom: In the Expense tab, a user can enter inputs in the twelfth month of the CP to BP integration calc method.

Resolution: Corrected by updating the twelfth month to a read-only cell that will balance to the total annual value.

Symptom: When adding a row to the Dept Other Pay section, the system does not display calc methods to select. Users should expect to see the same available calc methods when adding a department in the Other Pay section of the other labor tabs.

Resolution: Corrected by adding the following calc methods to labor sheets:

• JobCode tab - Added New PayType calc method
• Employee tab - Added New Dept PayType calc method
• Staffing tab - Added New PayType calc method

Symptom: The formatting of the blue box surrounding some columns displays intermittent white borders across rows.

Resolution: Corrected by removing white borders on the Expense tab and Expense calc method rows.

Symptom: On the Employee tab, the EPTO row is hidden.

Resolution: Corrected by fixing formula reference error.

Symptom: If a provider existed on the Provider Detail tab but not on ProviderComp tab, the FTE default of Relative Availability was not being used.

Resolution: Corrected so that Relative Availability is used if the system does not find a match in ProviderComp.

Issue: PFB-07001 - Budget Security Update error "Could not validate security filter on table." [TFS 30193]

Symptom: When opening and refreshing the Budget Security Update utility, a user changed the toggle to "Update" and performed Process File to update security. The system displayed the following error message: Could not validate security filters for <user> on table ACT_PAY1_2012. An expression of non-Boolean type specified in a context where a condition is expected near ")".

Resolution: Corrected by updating formulas in columns AA:AF in row 4 of the sheet calc method.

Issue: When using the capbud CYPMethod, those accounts where the YTD number exceeds the Current Year budget, the system appropriately projects zero for the rest of the year for all budget methodologies except for the Detail accounts. For those accounts, the system annualizes the rest of the year projection instead of projecting the rest of the year at zero.

Resolution: Corrected by adjusting the formula of the Add New Detail and Detail calc methods where zero will be the projection when YTD exceeds budget.

Issue: When using the GlobalProviderComp option for new providers on the ProviderComp tab, column P (total budget dollars) incorrectly includes a hard coded zero instead of the proper reference to BF for the current row.

Resolution: Corrected by adjusting the formula of the Add New Detail and Detail calc methods where zero will be the projection when YTD exceeds budget.

Issue: In a plan file with ProviderDetail, when a user expands the detail block and enters a number in the Amt Adjust column for Gross Charges and then saves and keeps the file open, the detail block stays expanded. The adjustment(s) then flows through to the Summary and Stat_Rev tabs as expected, but if the user hides the detail block and then re-expands it, the Amt Adjust value reverts to zero.

Resolution: Resolved in 2019.3 Patch 1.

Issue: When a user enters an input in the Manager Input, % Adjust, or Amt Adjust cells on the ProviderDetail tab, it is possible that the value will return on a different line.

The issue was mainly present if a key field dimension was mapped to more than one summary grouping. For example, if CPT A is mapped to CPT B and CPT B is mapped to CPT C, then when the expand/collapse action if selected, the AQ looked to the final mapping to bring back the inputs. In some cases this is when the inputs may move to a different row than they were originally added.

Resolution: Adjusted the logic for how the inputs are returned.

Workaround: If you experienced this prior to this patch, there is a workaround to change the affected dimension (usually CPT) to only use one level of mapping. For example, change the CPT dimension so that CPT B does not map to CPT C, and then re-input the values and save the plan file.

Issue: The system displays save errors on the ProviderDetail tab where long department numbers concantendated with a text string are saving to a column named “Save Custom”. This column included a column limit of 25 characters that caused a save error if exceeded.

Resolution: In the BUD related tables, correcting by reviewing and increasing the MaxStringLength parameter to 50 as needed.

Issue: In the GlobalSum calc method of the Stat_Revb tab, the formulas in columns CL:CN incorrectly reference row 73.

Resolution: Corrected by updating the formulas to reference row 75, which contains text that matches the column names in the GlobalSum driver.

Issue: When a user adds a new employee to an existing employee jobcode, the added employee does not reflect the merit increase amount from the Labor Rates driver and Empl_List sheet.

Resolution: Corrected by updating the formula in column CP to extend the match range so that the merit percentage is included for the newly added employee.

Issue: The following issues were discovered for initiatives:

• When inserting a project initiative, the profile of accounts do not populate even though the Preview Query displays the listing.

• After the accounts populate, the Acct and Acct.Desc do not populate.

Resolution: Corrected by updating the Control Sheet and adjusting the formula in the appropriate AQ and adding the applicable database fields to the Initiatives tab.

Issue: When using the Employee Labor method and adding new employee(s) to a new block, the rate now propagates down to the FTE allocation section of the block and will not produce dollars. However, it will produce hours.

Resolution: Corrected by updating the formulas in column H of the Jobcode calc method.

Issue: When adding a new job code on the Jobcode tab, the dollars and hours flow to the Expense tab, but the totals for FTEs, Hours, etc. at the top of the Jobcode tab (Summary section) do not update, causing a mismatch between the Expense and Jobcode tab.

Resolution: Corrected by expanding ranges to the Dept Total line.

Issue: On the Stat_Rev tab, the budget method to find the applicable key-stat for the non-key statistics is incorrect due to the formula in column AZ, which does not resolve correctly for other non-key stats.

Resolution: Corrected by updating the formula in column AZ for the StatOth and OthStat calc methods.

Issue: The Percent variable that displays on the Jobcode tab should not be visible if the job code is set to Fixed.

Resolution: Corrected by updating the conditional formatting to hide when the job code is set to Fixed.

Issue: When using the GlobalProviderComp option for new providers on the ProviderComp tab, column P (total budget dollars) incorrectly includes a hardcoded zero instead of the proper reference to BF for the current row.

Resolution: Corrected by updating the formula in column P to reference the correct cell.

Issue: When using ProviderDetail, the Amt Adjust column is missing the formula to acquire unit changes from the GlobalVolChg driver, if configured.

Resolution: Corrected by updating the formula in column FN to reference the GlobalVolChg driver.

Issue: When using ProviderDetail, a duplicate set of provider blocks interfaced after expanding.

Resolution: Corrected by updating the AQs that control the expand/collapse option to eliminate the second occurrence of the provider blocks.

Issue: In the Expense tab, the NoBudget calc method does not recognize CYPMethod.

Status: Under consideration for future patch or version release.

Issue: When inputting a percentage in the Admin Expense Adjustment driver, the note states "10=10%", but when looking at the plan file after making the adjustment, it appears that 10=1000%.

Status: Under consideration for future patch or version release.

Issue: In the Labor Rates driver, the Job Class Exceptions is not compliant with the Jobcode.JobClass character width of 50. In the 2019 Labor Rates Assumptions table, column O is set for a 25-character width, thus not saving if the Job Class selected within the drop-down is more than 25 characters. As a result, the system displays an error message, and the driver will not save.

Status: Under consideration for future patch or version release.

Issue: On the initial process of the [BUD20] 38 Provider Vol driver, WRVUs were stored in BUDGET2020_Provider Vol for this provider. The Provider_Comp tab used the Global configuration to process WRVUs. When the user changed PROVIDER.VolSum for this provider, [BUD20] 38 Provider Vol driver correctly did not include this provider in the refreshed results. However, there is no zero-on-save logic in [BUD20] 38 Provider Vol, so the WRVU record for this provider remained orphaned in the BUDGET2020_Provider Vol table.

Status: Under consideration for future patch or version release.

Issue: AQ1 should include the account level in the sum by. When using a multiple account filter for the driver, the accounts are overstated. This is because AQ1 currently only runs at the department level. It returns an account and account description but only through a COALESE function on these fields, returning the first account value of the summed records, which includes multiple accounts. For departments that would return multiple accounts, the accounts are summed together, but the system returns a record with the first account of the summed list and saves back to the table, overstating the account.

Status: Under consideration for future patch or version release.

Issue: When printing the CDMRevenue tab, only key stat rows are included in the output. Non-key stat rows do not display.

Status: Under consideration for future patch or version release.

Issue: In V2019.3 file group (Budget 2021), when manually inserting a JobCode block on the Jobcode tab, the system does not display the 2080 hours from JOBCODE.StdHours.

Status: Under consideration for future patch or version release.

Issue: When using the Employee Labor type, if the Jobcode block does not have any CYA Hours or Dollars, it calculates the Current Rate as $0.00 and then forwards that rate to the NYB, basically creating a zero-dollar budget for the job code.

Status: Under consideration for future patch or version release.