---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Custom publisher part numbers (PPN)

# Custom publisher part numbers (PPN) {#ariaid-title1}

Release version: Australia  
Updated July 31, 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 Custom Publisher Part Numbers (PPN)

Custom publisher part numbers (PPNs) in ServiceNow can be replaced by standardized PPNs and discovery maps (DMAPs) from the Software Asset Management Content Service to ensure accurate and consistent software asset data.
This replacement helps propagate updates to entitlements and software models across your instance, improving data integrity and reducing manual maintenance.
Show full answer Show less  

## How Replacement Works

* Replacement occurs only if a custom PPN matches a genuine publisher SKU in the normalized product catalog.
* The normalization engine swaps the custom PPN with the standardized product record from the Content Service.
* If the custom PPN does not map to a valid SKU, it remains a manually maintained entry that you must manage.

## Process and Interaction

* After Content Service updates are downloaded, the scheduled job **SAM - Find Product Definition Suggestions** runs to identify matching PPN and DMAP records.
* Matching suggestions are created in the **Part number suggestions \[sampswpartnumbersuggestion\]** table for review.
* Custom PPNs marked as "Exclude from content service" will not generate suggestions.
* You can accept or reject suggestions; accepting replaces the custom PPN and DMAP with Content Service versions.

## Impact of Accepting Content Service PPN Replacement

* All affected entitlements are updated with the new PPN.
* Downgrade rights from the Content Service DMAP overwrite existing entitlement entries.
* License type and license metric values are updated according to the new PPN where necessary.
* Entitlements remain in the "In use" state throughout the update.

## Impact of Accepting Content Service DMAP Replacement

* Associated software models are updated with the new DMAP.
* The following software model fields are updated: short description, asset tracking strategy/unit, and next version.
* Suite components and parent relationships are overwritten with Content Service DMAP values.
* Any custom components previously added will be deleted, with a warning provided before the change.
* Software model life cycles are overwritten, also with a warning.

## Practical Benefits for ServiceNow Customers

This process streamlines software asset management by aligning your custom part numbers with authoritative publisher data, automating updates to entitlements and software models, and ensuring accurate license tracking. It reduces manual effort, minimizes errors, and helps maintain compliance by leveraging up-to-date, standardized publisher content.  
Propagate changes to entitlements and software models by replacing your custom PPNs and
custom discovery maps (DMAPs) with the Software Asset Management Content Service PPNs and
DMAPs.  
Note:  
A custom PPN can only be replaced if its part number maps to a genuine publisher SKU in the normalized product catalog. Replacement works by matching the part number against the publisher's authoritative content library. The
engine then swaps the custom entry for the standardized product record. If the part number isn't a valid SKU, nothing in the catalog matches it. The normalization engine can't validate or replace it, so it remains a
manually-maintained custom entry that you must manage yourself. For information on custom part numbers, see [Custom publisher part numbers (PPN)](https://www.servicenow.com/docs/rRBipf7ecYyuLB_EUZUmcw "Propagate changes to entitlements and software models by replacing your custom PPNs and custom discovery maps (DMAPs) with the Software Asset Management Content Service PPNs and DMAPs.") and [Add a custom part number](https://www.servicenow.com/docs/ykLijMEZBQw8rWKoognVZg "You can add a custom part number to resolve an entitlement import error that occurs when a part number does not exist in the Software Library.").

Once the Content Service updates are downloaded to your instance, the scheduled job,
SAM - Find Product Definition Suggestions, runs. The scheduled job
checks all custom PPN and DMAP records to find corresponding PPN and DMAP matches on the
Content Service. If a match for the custom PPN and DMAP is found, then a suggestion record is
created in the Part number suggestions \[samp_sw_part_number_suggestion\] table. You can view
the suggestions record by navigating to the Part number suggestions
option.  
Note:  
If you have excluded custom PPNs from the Content Service by selecting the Exclude from content service option in the Custom Part Number form, then suggestions aren't shown for those custom PPNs.  
Note:  
For details on viewing the suggestion records, see [View publisher part number (PPN) suggestions in workspace](https://www.servicenow.com/docs/ekMjrkp1GM~hsSssiCmxkw "View Content Service suggestions for your custom PPNs and DMAPS in the Software Asset Workspace.") or [View publisher part number (PPN) suggestions in Software Asset Management classic](https://www.servicenow.com/docs/Y6o0sisBg6S_OfTq9bYocA "View content service suggestions for your custom PPNs and DMAPS in the Software Asset Management classic application.").

You can accept or reject the suggestions. If you accept the suggestion, the custom PPN and DMAP
are replaced with the Content Service PPN and DMAP. All changes to entitlements and software
models are propagated automatically.  
The propagation of the content service PPN results in the following changes:

* All impacted entitlements are updated with the new PPN.
* Downgrade rights associated with the content service DMAP gets copied to the entitlement.
* Downgrade rights that are copied overwrite any existing entries made by you.
* Values for license type and license metric get modified based on the PPN (where needed).
* Entitlement remains in the In usestate.
{#customppn-swap__ul_byl_1nx_5qb}  
The propagation of the Content Service DMAP results in the following changes:

* Associated software model is updated with the new DMAP.
* Fields get impacted on the software model:
  * Short description, Asset tracking strategy/unit, next version.
  * Suite components/parents get overwritten with the Content Service DMAP values.
  * Any custom components that were added are deleted, as stated in a warning.
  * Life cycles get overwritten (with a warning message).
  {#customppn-swap__ul_jdn_bpx_5qb}
{#customppn-swap__ul_idn_bpx_5qb}