Considerations for implementing the Asset Management and SPO better together flow

  • 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 Considerations for implementing the Asset Management and SPO better together flow

    This guidance outlines key considerations for implementing the integration between Asset Management and Sourcing and Procurement Operations (SPO) in ServiceNow. The integration enables streamlined purchase order and asset receipt processes while defining specific behaviors and restrictions to ensure seamless operation.

    Show full answer Show less

    Key Features

    • Purchase Order (PO) and Purchase Requisition (PR) Behavior:
      • The Cancel and Order options for POs in Asset Management are disabled to support integration consistency.
      • Edit and return flows for PRs and POs within SPO are not supported; thus, the Confirm Revision option is disabled for PRs in Pending Review state.
    • Asset Receipt Acknowledgment:
      • Purchasers acknowledge asset receipt through the PO in Asset Management after delivery.
      • Assets are created and viewable under the Asset Management PO’s Assets tab.
      • No assets or receipts are created directly from the SPO PO; SPO only generates a read-only receipt after Asset Management’s receipt slip is created.
    • Shopping Hub and Asset Management Purchase Flow:
      • All asset, consumable, and enterprise purchases must route through the Service Catalog.
      • Service purchases continue through Shopping Hub.
      • Shopping Hub controls prevent asset purchases directly from its catalog to maintain process integrity.
    • Supplier Product and Vendor Catalog Item Tables:
      • Purchases initiated via the integrated asset and SPO flow use the Supplier Product (snshopsupplierproduct) table from SPO instead of the Vendor Catalog Item (pcvendorcatitem) table.
    • Impact on Software Asset Management (SAM) and Coupa Integration:
      • The Asset Management and SPO integration does not support the existing SAM-Coupa integration.
      • Customers currently using SAM-Coupa should avoid installing the Asset Management Integration for SPO plugin.
      • If installing the better together application, specific steps must be followed to prevent conflicts, including disabling certain business rules and scheduled jobs, and ensuring proper mapping of PRs, POs, and receipts to Coupa entities.
    • Asset Creation for Services:
      • Creation of inventory assets for services in the almasset table is disabled for the integrated plugins.
      • Existing inventory assets for services remain unaffected.
      • Fixed assets continue to be created for services, and inventory asset creation for goods operates as usual.

    Key Outcomes

    Implementing this integration ensures a harmonized flow for asset-related purchases and receipt acknowledgments, leveraging SPO’s procurement capabilities and Asset Management’s asset tracking. It enforces process controls to prevent unsupported actions, maintains data consistency by using SPO supplier product records, and delineates clear boundaries for service versus asset purchases. Customers integrating with Coupa must carefully manage configurations to avoid conflicts. Overall, this integration enhances procurement and asset lifecycle management efficiency within ServiceNow.

    This section provides information on considerations for implementing the Asset Management and SPO better together solution.

    Functional detail Description
    PO and PR transaction behavior

    To enable seamless integration:

    • The Cancel and Order options are disabled for POs in Asset Management.
    • Edit and return flows for Purchase Requisitions (PR) and Purchase Orders (PO) in SPO are not supported in this integration. Therefore, the Confirm Revision option is disabled when the PR is in the Pending Review state.
    Acknowledging asset receipt in Asset Management
    • After asset delivery, the purchaser acknowledges receipt via the PO in Asset Management. Assets are then created and can be viewed under the Assets tab of the Asset Management PO.
    • In this workflow, no assets or receipts are created from the SPO PO.
    • A read-only receipt is generated on the SPO POL only after the Asset Management receipt slip is created.
    Shopping Hub and Asset Management

    As part of this flow, all asset, consumable, and enterprise purchases should go through the service catalog. Services purchases should continue to flow through Shopping Hub.

    Shopping Hub controls should prevent asset purchases directly from the Shopping Hub catalog.
    Supplier Product and Vendor Catalog Item table usage When a purchase is initiated using the Asset Management and SPO flow, the system doesn't use the Vendor Catalog Item (pc_vendor_cat_item) table. Instead, it uses SPO's Supplier Product (sn_shop_supplier_product) table to process the purchase.
    How Asset Management and SPO better together flow affects SAM-Coupa integration The Asset Management and SPO integration flow does not support the Software Asset Management (SAM) and Coupa integration. If you are currently using the SAM-Coupa integration and wish to continue doing so, do not install the Asset Management Integration for Sourcing and Procurement Operations (sn_spend_asset) plugin.

    If you choose to install the better together application, complete the following steps to successfully implement the SPO-Coupa integration:

    • Stop the "Create a Requisition" business rule from triggering on the Asset Management Purchase Order table (proc_po) when the status changes to Ordered.

    • Restrict the creation of new itam_procurement_integration_job scheduled jobs. Retire any existing daily jobs to avoid potential conflicts.

    • Delete all business rules associated with the app-itam-procurement-integration application to prevent integration conflicts.
    • Ensure that Purchase Requests (PRs), Purchase Orders (POs), and Receipts in SPO are properly mapped to corresponding entities in Coupa for seamless integration.
    Creation of assets for services

    The creation of inventory assets for services in the alm_asset table is disabled in the Sourcing and Purchasing Automation and Asset Management Integration for Sourcing and Procurement Operations plugins. The previously created inventory assets for services are not affected. For fixed assets, Asset Management continues to create corresponding records in the alm_asset table for services. Inventory asset creation for goods continues to function as before.