Managing Portfolio Planning with PPM

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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 guidance helps ServiceNow customers properly integrate Portfolio Planning with Project Portfolio Management (PPM) to maintain data consistency and synchronization between planning and execution tables.

    Show full answer Show less

    Key Practices

    • Table Map Integrity: Avoid changing the filter conditions of a table map after records have been interfaced, as this can cause data inconsistencies. If changes are necessary, manually update the relevant attributes on existing records.
    • Configuration Completeness: Whenever creating a table map, ensure corresponding field maps and choice maps are also configured to enable proper data mapping.
    • Import Job Stability: Do not modify table maps or their field maps while an import job is in progress to prevent errors.
    • Record Traceability: Use the "Converted to" field on planning items to trace back to the original record source.
    • Reference Field Mapping: When alignment and execution tables reference different tables, include Lookup field and Lookup column values in field maps for reference or glide list types to maintain correct links.

    Data Synchronization and Troubleshooting

    • Check integration error logs within alignment integration records if synchronization fails.
    • Verify that filter conditions for both alignment (import) and execution (export) tables are correctly configured and active.
    • Ensure the Active flag is enabled on both alignment integrations and table maps.
    • Confirm that all necessary fields and choice mappings are properly set for each table map.

    Additional Features and Recommendations

    • Configure the planning item record to display the Execution URL field, which provides direct links to execution records.
    • If the Execution URL field is blank, use the Portfolio Planning > Integrations > Fix execution URL(s) for planning items action to generate or update these links.
    • A new Primary goal field is added to projects, demands, and epics table maps to enable integration of the Goal field between alignment and execution tables.
    • When importing or exporting projects, ensure associated demands are also synchronized to maintain data integrity.
    • For custom execution tables not derived from delivered tables (dmndemand, pmproject), create a supporting business rule to enable interfacing of records in the table map.

    Practical Impact

    Following these guidelines ensures reliable and consistent integration between Portfolio Planning and PPM modules. Customers can expect accurate data synchronization, easier troubleshooting of integration errors, and enhanced traceability of planning items to execution records. Proper configuration supports seamless project and demand management, helping organizations maintain alignment between strategic planning and execution.

    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.
    • 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 Planning > Integrations 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.