Working with Teamspaces
-
- UpdatedJan 30, 2025
- 1 minute read
- Yokohama
- Strategic Portfolio Management
Strategic Planning can be integrated with Project Portfolio Management's Teamspaces to access and manage relevant projects and demands with the corresponding planning item records.
- Project Management TeamSpace 1 (com.snc.ppm_teamspace_1)
- Project Management TeamSpace 2 (com.snc.ppm_teamspace_2)
- Project Management TeamSpace 3 (com.snc.ppm_teamspace_3)
- Project Management TeamSpace 4 (com.snc.ppm_teamspace_4)
- Project Management TeamSpace 5 (com.snc.ppm_teamspace_5)
The teamspaces installed with these plugins contain the same components, but the components have different prefixes. For example, teamspace 1 includes a project table named Teamspace_1 Project [tsp1_project] and teamspace 5 includes a project table named Teamspace_5 Project [tsp5_project].
Also, the corresponding teamspace role must be added to the Strategic Planning admin (sn_align_core.apw_admin) role. For example, tsp1_portfolio_manager for teamspace1, tsp2_portfolio_manager for teamspace2 and so on.
- Create one alignment integration for all the teamspaces. On the alignment side, create extended tables to store individual teamspace table data (like TSP1 Portfolio [sn_align_core_tsp1_portfolio], TSP1 Demand [sn_align_core_tsp1_demand], TSP2 Project [sn_align_core_tsp2_project], and so on).
- In the alignment integration, map the extended tables you have created in Step 1, to the respective teamspace tables (like tsp1_portfolio, tsp1_demand, tsp2_project, and so on).

Related Content
- Create a table map
Create a table map to define the mapping between tables in Strategic Planning with the tables in Agile Development 2.0, SAFe, and PPM.