Considerations for implementing the ITAM-SPO better together flow

  • Release version: Yokohama
  • Updated July 31, 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 Considerations for implementing the ITAM-SPO better together flow

    This content outlines essential considerations for implementing the ITAM-SPO better together solution, facilitating effective integration between IT Asset Management (ITAM) and Sourcing and Procurement Operations (SPO). Key behaviors and workflows are detailed to ensure a smooth integration experience.

    Show full answer Show less

    Key Features

    • Purchase Order Behavior: In ITAM, Cancel and Order options are disabled for Purchase Orders (POs). Edit and return flows for Purchase Requisitions (PRs) and POs in SPO are not supported, with Confirm Revision disabled for PRs in Pending Review state.
    • Acknowledging Asset Receipt: Receipt acknowledgment occurs through the PO in ITAM after asset delivery, with assets viewable under the Assets tab. No assets or receipts are created from the SPO PO; a read-only receipt is generated only after the ITAM receipt slip is created.
    • Shopping Hub Integration: All IT asset and enterprise purchases should be routed through the service catalog, while service purchases continue via Shopping Hub. Controls in the Shopping Hub prevent direct IT asset purchases from the catalog.
    • Supplier Product Table Usage: The ITAM-SPO flow utilizes the Supplier Product table for processing purchases instead of the Vendor Catalog Item table.
    • SAM-Coupa Integration Considerations: The ITAM-SPO integration does not support SAM-Coupa integration. If you plan to use the SAM-Coupa integration, do not install the Asset Management Integration for Sourcing and Procurement Operations plugin. Specific steps are provided to avoid integration conflicts.
    • Inventory Asset Creation: Inventory asset creation for services in the almasset table is disabled in related plugins, while fixed assets continue to be created in the almasset table for services, and inventory asset creation for goods remains unaffected.

    Key Outcomes

    By understanding these considerations, ServiceNow customers can effectively implement the ITAM-SPO better together flow, ensuring seamless integration and proper management of asset transactions. Customers can expect more efficient workflows, clearer management of purchase processes, and reduced integration conflicts when following the outlined guidelines. Proper mapping of entities between SPO and Coupa is critical for achieving successful integration outcomes.

    This section provides information on considerations for implementing the ITAM-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 ITAM.
    • 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 ITAM
    • After asset delivery, the purchaser acknowledges receipt via the PO in ITAM. Assets are then created and can be viewed under the Assets tab of the ITAM 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 ITAM receipt slip is created.
    Shopping Hub and IT Asset Management

    As part of this flow, all IT 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 IT asset purchases directly from the Shopping Hub catalog.
    Supplier Product and Vendor Catalog Item table usage When a purchase is initiated using the ITAM-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 ITAM-SPO better together flow affects SAM-Coupa integration The ITAM-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 (com.snc.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 ITAM 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, ITAM continues to create corresponding records in the alm_asset table for services. Inventory asset creation for goods continues to function as before.