Considerations for implementing the Asset Management and SPO better together flow
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:
|
| Acknowledging asset receipt in Asset Management |
|
| 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. |
Parent Topic:Sourcing and Procurement Operations integration with Asset Management