Managing Portfolio Planning with PPM

  • Release version: Yokohama
  • Updated January 30, 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 document provides essential guidelines for integrating Portfolio Planning with Project Portfolio Management (PPM) effectively, ensuring data consistency and synchronization across planning and execution tables within ServiceNow.

    Show full answer Show less

    Key Guidelines

    • Maintain Filter Conditions: Avoid changing the filter condition of a table map after records are interfaced to prevent data inconsistencies. If changes are necessary, manually update relevant attributes on interfaced records.
    • Configure Field and Choice Maps: Always configure relevant field maps and choice maps when creating a table map to ensure proper data mapping.
    • During Import Jobs: Do not modify the table map or its field maps while an import job is processing.
    • Tracking Record Origin: Use the Converted to field on the planning item form to identify the source record from which a planning item was converted.
    • Reference Fields in Field Maps: When alignment and execution tables reference different tables, ensure to set the Lookup field and Lookup column values in the field map for reference or glide list fields.

    Troubleshooting Data Synchronization

    • Check Integration error logs within the alignment integration record for synchronization failures.
    • Verify that the Alignment table filter (import) and Execution table filter (export) conditions are correctly set and active.
    • Ensure the Active flag is enabled on both the alignment integration record and the table map.
    • Confirm appropriate fields and choices are configured for every table map.

    Additional Configuration Notes

    • To view the Execution URL in planning items, configure the planning item record accordingly.
    • If the Execution URL field is blank in synced planning items, use the Fix execution URL(s) for planning items action under Portfolio Planning > Integrations to generate and update these URLs.
    • A new Primary goal field is added to projects, demands, and epics table maps to facilitate goal integration between alignment and execution tables.
    • When importing or exporting projects, ensure all related demands are synchronized to maintain data integrity.
    • You can create table maps for any execution table. However, if the table map is not based on delivered tables (dmndemand, pmproject) or their extensions, you must create a business rule to support interfacing these records.

    Next Steps for Customers

    Follow these guidelines to ensure seamless integration between Portfolio Planning and PPM. Proper configuration of table maps, filters, and field mappings helps maintain consistent data flow. Use the troubleshooting steps to resolve synchronization issues, and consider creating business rules when working with custom tables to enable smooth data interfacing.

    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.