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 document outlines essential guidelines for integrating Portfolio Planning with Project Portfolio Management (PPM) to ensure data consistency and effective management of project records.

    Show full answer Show less

    Key Features

    • Table Map Guidelines: Avoid changing filter conditions after records are interfaced to prevent data inconsistencies. If changes are necessary, manually update the relevant attributes.
    • Field Mapping: Configure relevant field and choice maps when creating a table map for effective data handling.
    • Execution URL Management: Ensure that the Execution URL field is visible and correctly updated, especially when syncing planning items.
    • Primary Goal Integration: A new Primary goal field has been introduced for better alignment between goals in integration tables.
    • Business Rule Creation: For custom table maps not extending from standard tables, a business rule must be created to facilitate interfacing.

    Key Outcomes

    By following these guidelines, ServiceNow customers can maintain data integrity during project planning and execution, streamline integration processes, and effectively manage project demands and goals. This ensures that all relevant data syncs correctly, enhancing overall project management efficiency.

    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 to apply a custom table map configuration.