Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not show principal cost centers in the columns of step-down cost allocation report #5979

Closed
jniles opened this issue Oct 5, 2021 · 1 comment · Fixed by #5982
Closed

Comments

@jniles
Copy link
Collaborator

jniles commented Oct 5, 2021

Here is the current step-down cost allocation report, we currently have every cost center listed in the columns. This doesn't make sense. We should only have the cost centers that are being allocated in the columns.

Here is the current report with fake data from the Vanga dataset:

image

Notice how many columns we have! But we only have 3 auxiliary cost centers that are allocating their costs. We should only have three columns.

Here is an example for Essentials of Healthcare Ch. 13:

image

See how there are four cost centers, but only two columns, since only two of the four cost centers are auxiliary cost centers. This is what we should be doing.

@jniles
Copy link
Collaborator Author

jniles commented Oct 6, 2021

I'll tackle this one.

bors bot added a commit that referenced this issue Oct 6, 2021
5982: fix(cost center): uniquely show auxiliary cost centers in columns r=mbayopanda a=jniles

This commit fixes the presentation of the cost center report to only show the allocation ratios for the auxiliary cost centers in the columns.

Closes #5979.

![image](https://user-images.githubusercontent.com/896472/136187131-68d3ed8a-09ed-4938-96d0-25eba5e54fde.png)


Co-authored-by: Jonathan Niles <jonathanwniles@gmail.com>
@bors bors bot closed this as completed in 1be0759 Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant