---
sourceDocument: Yokohama Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-business-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Managing Portfolio Planning with PPM

# Managing Portfolio Planning with PPM {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Managing Portfolio Planning with PPM

This guide outlines essential best practices for integrating Portfolio Planning with Project Portfolio Management (PPM) in ServiceNow.
Proper configuration and maintenance of table maps, field mappings, and synchronization processes are critical to ensuring data consistency and smooth portfolio planning operations.
Show full answer Show less  

## Key Guidelines

* **Table Map Configuration:** Do not modify filter conditions on table maps after records have been interfaced to avoid data inconsistency. If a filter change is necessary, relevant attributes on existing records must be updated manually.
* **Field and Choice Maps:** Always configure associated field maps and choice maps when creating a table map to ensure correct data mapping.
* **Import Job Restrictions:** Avoid modifying table maps or their field maps while an import job is in progress to prevent synchronization issues.
* **Reference Fields:** When execution and alignment tables reference different tables, include Lookup field and Lookup column values in field maps for reference or glide list types.
* **Data Synchronization Checks:** In case of synchronization failures, verify integration error logs, filters on alignment and execution tables, activation status of alignment integration and table map, and proper configuration of fields and choices.
* **Execution URL Management:** To view or fix missing Execution URL fields on planning items, configure the planning item record accordingly and use the "Fix execution URL(s) for planning items" option in Portfolio Planning \> Integrations.
* **Primary Goal Field:** A Primary goal field is introduced in projects, demands, and epics table maps to support goal integration between alignment and execution tables.
* **Demand Synchronization:** Ensure that demands associated with a project are synced when importing or exporting the project.
* **Custom Table Maps:** For custom execution tables that do not extend from default tables (dmndemand, pmproject), a business rule must be created to support record interfacing.

## Practical Benefits

Following these guidelines helps ServiceNow customers maintain data integrity across portfolio and project records, ensures reliable synchronization between alignment and execution tables, and supports advanced configurations including custom tables and goal tracking. It enables efficient portfolio planning operations without data inconsistencies or synchronization failures.  
Ensure that Portfolio Planning is integrated properly with Project
Portfolio Management (PPM) following these guidelines.
* Do not change the filter condition of a table map after the records are interfaced. The already interfaced records might not match with the new filter condition and any change in the filter condition can result in data inconsistency. If you need to change the filter condition, ensure that the relevant attributes on the interfaced records are updated manually to avoid data inconsistency issues.
* Whenever a table map is created, ensure that the relevant field maps and choice maps are also configured.
* When an import job for a table map is running (processing), do not modify the table map or its field maps.
* Using the Converted to field on the planning item form, you can identify the original record from which it was converted.
* Ensure that the Lookup field and Lookup column values are added whenever the execution and alignment tables are referencing two different tables, while creating a field map for field type of reference or glide list.
* If there is a data synchronization failure, check if:
  * The Integration error logs related list within that Alignment integration record.
  * The Alignment table filter (for import) and Execution table filter (for export) conditions are met.
  * The Active flag in both the alignment integration and the table map is checked.
  * The appropriate fields and choices are configured for each table map.
  {#managing-integration__ul_n1j_ywj_jvb}
* If you want to view the Execution URL field, configure the planning item record to view it.
* If the Execution URL field in your synced planning item(s) is blank, navigate to Portfolio PlanningIntegrations and click Fix execution URL(s) for planning items. This action creates and updates the execution URL field.
* A Primary goal field is introduced to the projects, demands, and epics table maps to support the integration of the Goal field between alignment and execution tables.
* When you are trying to import or export a project, ensure that the demands (that are a part of that project) are synced.
* You can create a table map for any execution table. If a table map is not created from one of the delivered tables (dmn_demand, pm_project) or does not extend from them, you are required to create a business rule to support the interfacing of the table map records. For more information on creating a business rule, see [Create a business rule for custom table map configuration](https://www.servicenow.com/docs/j_ByIdV5rn2tCS7XHcADfw "Create a business rule to enable import for your new custom table map configuration from Agile Development 2.0, SAFe, and PPM applications.").
{#managing-integration__ul_th1_chv_nqb}

*[\>]: and then