Looking at my IT Planning department hierarchy. At my lowest level, we have six digit department codes. However, some of those codes are 1:1 when rolling up to the next highest level. Those cannot have the same name, which is okay. So I currently have something like this:  

So my executive department is all the same cost center all the way up. It makes the IT Planning department drop down look weird in that a budget is created at Executive Department 400300 then submitted to Executive Group 400300 and on up. the tree is a bit wonky. My thought was to do this:

This would have my lowest level department numbers but not consistently in the same levels across the hierarchy. Will this work? Does anyone have other ideas? Does each department at level 1 HAVE TO have a parent? Does each department at level 4 HAVE to be made up of all lower levels?

@Kyle Sellner if I am understanding your structure correctly, this is how I would set up the reference data.

Which would give you a hierarchy drop down of this:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         Executive

o   Executive Team

§  Executive Group

·         400300 – Executive Department

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

If you do not want all of those levels for Executive, you could do this:

And that would give you a hierarchy of:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         400300 – Executive

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

Each department at Level 1 does not have to have a Parent Code.  If the Level 1 Department does not have a Parent Code it will be listed under All Departments and not in a Group. 

Original Message:
Sent: 03-28-2024 11:45
From: Kyle Sellner
Subject: Planning Department Hierarchy

Looking at my IT Planning department hierarchy. At my lowest level, we have six digit department codes. However, some of those codes are 1:1 when rolling up to the next highest level. Those cannot have the same name, which is okay. So I currently have something like this:  

So my executive department is all the same cost center all the way up. It makes the IT Planning department drop down look weird in that a budget is created at Executive Department 400300 then submitted to Executive Group 400300 and on up. the tree is a bit wonky. My thought was to do this:

This would have my lowest level department numbers but not consistently in the same levels across the hierarchy. Will this work? Does anyone have other ideas? Does each department at level 1 HAVE TO have a parent? Does each department at level 4 HAVE to be made up of all lower levels?

@Kyle Sellner if I am understanding your structure correctly, this is how I would set up the reference data.

Which would give you a hierarchy drop down of this:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         Executive

o   Executive Team

§  Executive Group

·         400300 – Executive Department

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

If you do not want all of those levels for Executive, you could do this:

And that would give you a hierarchy of:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         400300 – Executive

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

Each department at Level 1 does not have to have a Parent Code.  If the Level 1 Department does not have a Parent Code it will be listed under All Departments and not in a Group. 

Original Message:
Sent: 03-28-2024 11:45
From: Kyle Sellner
Subject: Planning Department Hierarchy

Looking at my IT Planning department hierarchy. At my lowest level, we have six digit department codes. However, some of those codes are 1:1 when rolling up to the next highest level. Those cannot have the same name, which is okay. So I currently have something like this:  

So my executive department is all the same cost center all the way up. It makes the IT Planning department drop down look weird in that a budget is created at Executive Department 400300 then submitted to Executive Group 400300 and on up. the tree is a bit wonky. My thought was to do this:

This would have my lowest level department numbers but not consistently in the same levels across the hierarchy. Will this work? Does anyone have other ideas? Does each department at level 1 HAVE TO have a parent? Does each department at level 4 HAVE to be made up of all lower levels?

related question. i'm trying to understand the difference between department and cost center. the help menu doesn't really answer my question. any ideas/guidance?

@Kyle Sellner if I am understanding your structure correctly, this is how I would set up the reference data.

Which would give you a hierarchy drop down of this:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         Executive

o   Executive Team

§  Executive Group

·         400300 – Executive Department

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

If you do not want all of those levels for Executive, you could do this:

And that would give you a hierarchy of:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         400300 – Executive

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

Each department at Level 1 does not have to have a Parent Code.  If the Level 1 Department does not have a Parent Code it will be listed under All Departments and not in a Group. 

Original Message:
Sent: 03-28-2024 11:45
From: Kyle Sellner
Subject: Planning Department Hierarchy

Looking at my IT Planning department hierarchy. At my lowest level, we have six digit department codes. However, some of those codes are 1:1 when rolling up to the next highest level. Those cannot have the same name, which is okay. So I currently have something like this:  

So my executive department is all the same cost center all the way up. It makes the IT Planning department drop down look weird in that a budget is created at Executive Department 400300 then submitted to Executive Group 400300 and on up. the tree is a bit wonky. My thought was to do this:

This would have my lowest level department numbers but not consistently in the same levels across the hierarchy. Will this work? Does anyone have other ideas? Does each department at level 1 HAVE TO have a parent? Does each department at level 4 HAVE to be made up of all lower levels?

Most of the time we set up the Department and Cost Center hierarchy to be the same.

Technically a Department could be a higher level and you could have multiple Cost Centers rolling into one Department.

related question. i'm trying to understand the difference between department and cost center. the help menu doesn't really answer my question. any ideas/guidance?

@Kyle Sellner if I am understanding your structure correctly, this is how I would set up the reference data.

Which would give you a hierarchy drop down of this:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         Executive

o   Executive Team

§  Executive Group

·         400300 – Executive Department

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

If you do not want all of those levels for Executive, you could do this:

And that would give you a hierarchy of:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         400300 – Executive

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

Each department at Level 1 does not have to have a Parent Code.  If the Level 1 Department does not have a Parent Code it will be listed under All Departments and not in a Group. 

Original Message:
Sent: 03-28-2024 11:45
From: Kyle Sellner
Subject: Planning Department Hierarchy

Looking at my IT Planning department hierarchy. At my lowest level, we have six digit department codes. However, some of those codes are 1:1 when rolling up to the next highest level. Those cannot have the same name, which is okay. So I currently have something like this:  

So my executive department is all the same cost center all the way up. It makes the IT Planning department drop down look weird in that a budget is created at Executive Department 400300 then submitted to Executive Group 400300 and on up. the tree is a bit wonky. My thought was to do this:

This would have my lowest level department numbers but not consistently in the same levels across the hierarchy. Will this work? Does anyone have other ideas? Does each department at level 1 HAVE TO have a parent? Does each department at level 4 HAVE to be made up of all lower levels?

@Kyle Sellner if I am understanding your structure correctly, this is how I would set up the reference data.

Which would give you a hierarchy drop down of this:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         Executive

o   Executive Team

§  Executive Group

·         400300 – Executive Department

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

If you do not want all of those levels for Executive, you could do this:

And that would give you a hierarchy of:

·         Apps Team Divisions

o   Business Apps Group

§  Salesforce Teams

·         500300 – App Support

o   Security Apps Group

§  General Ledger Teams

·         500310 – App Dev

·         400300 – Executive

·         Infrastructure Teams Division

o   Data Group

§  Storage Teams

·         610600 - Unix

o   Hardware Group

§  Servers Teams

·         605600 – Wintel

Each department at Level 1 does not have to have a Parent Code.  If the Level 1 Department does not have a Parent Code it will be listed under All Departments and not in a Group. 

Original Message:
Sent: 03-28-2024 11:45
From: Kyle Sellner
Subject: Planning Department Hierarchy

Looking at my IT Planning department hierarchy. At my lowest level, we have six digit department codes. However, some of those codes are 1:1 when rolling up to the next highest level. Those cannot have the same name, which is okay. So I currently have something like this:  

So my executive department is all the same cost center all the way up. It makes the IT Planning department drop down look weird in that a budget is created at Executive Department 400300 then submitted to Executive Group 400300 and on up. the tree is a bit wonky. My thought was to do this:

This would have my lowest level department numbers but not consistently in the same levels across the hierarchy. Will this work? Does anyone have other ideas? Does each department at level 1 HAVE TO have a parent? Does each department at level 4 HAVE to be made up of all lower levels?