OOTB Architecture for Strategic Portfolio Management

Brigid33770
Tera Contributor

I hope this is the right place to come. 

We have rolled out Strategic Portfolio Managment, and as you know, there are already requests for optimizations and changes. While I am not immersed in the architecture space, I do know that if you start making changes to data fields there will be downstream impacts, especially with updates and reporting. I want to avoid "undoing" work. 

 

So, if I change the Investment Class to Run, Grow, and Transform, are there any downsides to that? What other SPM module shares the same table, and what happens to those reports/widgets? I am unable to find a document that shares the OOTB config. or that shows the mapping between modules to make an informed decision on modifications. 

 

Is there anything documentation out there, that you can share? I really appreciate your assistance with this.

Best,

Brigid

1 ACCEPTED SOLUTION

M Iftikhar
Tera Sage

Hi Brigid, 

Great question, you're right to be cautious here. The Investment Class field isn’t just used in one place; it shows in projects, demands, portfolios, and even some OOTB reports and widgets. If you change the values to “Run / Grow / Transform,” nothing will break, but you will need to: 

  • Update any OOTB reports/dashboards that filter on the old values 
  • Test Scenario Planning, since it often uses Investment Class for comparisons 
  • Be mindful during upgrades, since new content packs might assume the original options 

Best practice is to test in sub-prod first, and document all changes. Some teams prefer to create a custom field instead of overwriting OOTB values, just to avoid upgrade surprises. 

For references: 

  • Check the Schema Map in your instance to see what’s connected 
  • The SPM docs have a good overview of tables, etc. 

Components installed with Project Portfolio Management (PPM) Standard 

Components installed with Strategic Planning Workspace 

  • Release notes for SPM content packs will tell you which widgets use what fields 

SPM relational database structure 

ifti122_0-1757502462918.png

 

 

So yes, you can change it but just make sure you know where it flows downstream. 🙂 
 
Thanks & Regards, 
Muhammad Iftikhar 

 
If my response helped, please mark it as the accepted solution so others can benefit as well. 

Thanks & Regards,
Muhammad Iftikhar

If my response helped, please mark it as the accepted solution so others can benefit as well.

View solution in original post

2 REPLIES 2

M Iftikhar
Tera Sage

Hi Brigid, 

Great question, you're right to be cautious here. The Investment Class field isn’t just used in one place; it shows in projects, demands, portfolios, and even some OOTB reports and widgets. If you change the values to “Run / Grow / Transform,” nothing will break, but you will need to: 

  • Update any OOTB reports/dashboards that filter on the old values 
  • Test Scenario Planning, since it often uses Investment Class for comparisons 
  • Be mindful during upgrades, since new content packs might assume the original options 

Best practice is to test in sub-prod first, and document all changes. Some teams prefer to create a custom field instead of overwriting OOTB values, just to avoid upgrade surprises. 

For references: 

  • Check the Schema Map in your instance to see what’s connected 
  • The SPM docs have a good overview of tables, etc. 

Components installed with Project Portfolio Management (PPM) Standard 

Components installed with Strategic Planning Workspace 

  • Release notes for SPM content packs will tell you which widgets use what fields 

SPM relational database structure 

ifti122_0-1757502462918.png

 

 

So yes, you can change it but just make sure you know where it flows downstream. 🙂 
 
Thanks & Regards, 
Muhammad Iftikhar 

 
If my response helped, please mark it as the accepted solution so others can benefit as well. 

Thanks & Regards,
Muhammad Iftikhar

If my response helped, please mark it as the accepted solution so others can benefit as well.

Thank you so very much, you have shared the information I've been looking for!!! 

Best,

Brigid