Considerations for implementing the ITAM-SPO better together flow

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.