Alignment Planner extension to departments

[User291978]

I am currently trying to extend the APW functionality to show the department information coming from project and demand and making it available to the users for filtering/grouping. It works easily for the tables dmn_demand and pm_project, but if you want to use the Planning Hierarchy (which uses the the tables sn_align_core_* tables) i didn't find any possibility to make that happen. What I did:

I added the fields (reference to cmn_department) to the two tables sn_align_core_demand / sn_align_core_project. I added the field mapping for dmn_demand and pm_project by altering the table maps for sn_align_core_project and sn_align_core_demand. I added the fields to the Default and APW Default and APW Details views (for both demand and project) and extended the roadmap for sn_align_core_project and sn_align_core_demand. But in a roadmap that uses the planning hierarchy (and thus using the sn_align_core_* tables) the department is not shown for grouping nor coloring. Also it seems that the changes in the department field (when done in the APW workspace) are not saved.

Any ideas/suggestions? - BTW we are using SPM Standard - so we don't want to go into and add the department as a planning hierarchy due to license constraints.

[Rob Erickson · Accepted solution]

Hello,

in order for a field to be available as a grouping on any Planning Hierarchy Roadmap (and not an adhoc roadmap) it must be added as an available grouping in the Roadmap Preferences for the Planning Item table (sn_align_core_planning_item). As the department field is needed in multiple work item types, I would recommend adding that field to the Planning Item Table instead of individually to the sn_align_core_demand and sn_align_core_project tables. As those other tables are extended from Planning Item, that department field will be available to put on the specific forms for Demand and Project, and can be added to the field map for teh internal integration.

You will need to adjust the table map for your internal sync for the Demand and Project tables to have updates to the department synchronize from the execution tables (dmn_demand and pm_project) to the alignment tables (sn_align_core_demand and sn_align_core_project) and vice-versa.

Regards,

Rob Erickson, ServiceNow Sr. Manager SPM Outbound Product Management

[User291978]

Hi Rob,

thanks a lot for the clarification - I deleted the fieldsin the sn_align_core_* tables and added it to the planning item. Now I can use it for filtering and for all new demands/projects created in the execution tables it works perfectly fine.

Thanks for pointing to the correct location!

Regards,

Manuel

[michaelgoug]

Hi,

Thank you both for this post. I had a similar issue in Xanadu SPM (not APM) to map a custom field from the [pm_project] table to group records in hierarchy roadmap. I originally planned to add the field and mapping to the [sn_align_core_project] table until I saw this post. When I attempted to create a new mapping, I notices that there is no option to map to the [sn_align_core_planning] alignment table so I aligned to the field on the extended [sn_align_core_project] table even though I created the field on the [sn_align_core_planning_item] table.

This may sound obvious but I wanted to add the additional clarification.