Managing Portfolio Planning with PPM

  • Release version: Australia
  • Updated March 12, 2026
  • 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 guide provides essential best practices and configuration steps to ensure effective integration between Portfolio Planning and Project Portfolio Management (PPM) in ServiceNow. Proper setup and maintenance of table maps, field maps, and synchronization processes are critical to maintaining data consistency and operational efficiency in portfolio management.

    Show full answer Show less

    Key Practices for Integration

    • Table Map Configuration: Do not alter filter conditions on a table map after records have been interfaced, as this can cause data inconsistencies. If changes are necessary, manually update the relevant attributes on interfaced records.
    • Field and Choice Maps: Always configure associated field maps and choice maps when creating a table map to ensure completeness of data mapping.
    • Import Job Restrictions: Avoid modifying table maps or their field maps while an import job is processing to prevent synchronization errors.
    • Reference Fields Mapping: When execution and alignment tables reference different tables, include Lookup field and Lookup column values in the field map for reference or glide list field types.

    Troubleshooting and Maintenance

    • Investigate data synchronization failures by reviewing integration error logs within the relevant alignment integration record.
    • Verify that alignment and execution table filters and active flags are correctly set to enable proper data flow.
    • Confirm that all necessary fields and choice values are configured accurately for each table map.
    • To fix blank Execution URL fields in synced planning items, use the “Fix execution URL(s) for planning items” action under Portfolio Planning > Integrations.

    Additional Configuration Notes

    • A new Primary goal field supports integration of goals between alignment and execution tables and is included in projects, demands, and epics table maps.
    • When importing or exporting projects, ensure that associated demands are also synchronized to maintain data integrity.
    • Custom execution tables require a business rule to support interfacing if the table map is not derived from delivered tables such as dmndemand or pmproject. Guidance on creating these business rules is available.

    Following these guidelines helps ServiceNow customers maintain reliable and consistent data synchronization between Portfolio Planning and PPM, ensuring accurate portfolio visibility and management.

    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.