---
sourceDocument: Xanadu Finance and Supply Chain
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/source-to-pay-operations

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Creator


---

# Sourcing and Procurement Operations integration with Project Management

# Sourcing and Procurement Operations integration with Project Management {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Eliminate manual efforts of linking purchase orders to projects by integrating Sourcing and Procurement Operations with Strategic Portfolio Management's Project Management.
The Project Costing for Sourcing and Procurement Operations plugin (sn_spend_ppm) provides this integration. This plugin has dependency on the following applications that can be purchased separately:

* Sourcing and Purchasing Automation
* Source-to-Pay Common Architecture
* Finance Common Architecture
* Common Service Delivery
* Procurement Case Management
* Source-to-Pay Workspace
* Supplier Common Architecture
* Playbook Experience
* Document Templates
* Common Vendor Core
{#integration-psm-ppm__ul_hbq_xc4_mqb}  
The plugin also has dependency on the following system plugins that need to be installed separately:

* External User Self-Registration
* Finance Applications - Common Dependencies
* Fiscal Calendar
* GraphQL Plugin
* Insert Multiple Web Service
* PPM Standard
* Process Automation Designer Core
* Process Automation Designer for App Engine
* Scoped Application Restricted Caller Access
* Signature Pad
* User Criteria Scoped API
* Vendor Core
{#integration-psm-ppm__ul_y1l_31z_bbc}  
Important:  
Your administrator must manually assign the IT Project User, which is a licensed role, to your shopper for them to view project details during checkout. Also, as part of the Source-to-Pay pricing initiative, your administrator must manually assign the PPM user role to your procurement specialist.

With this integration, project managers or shoppers can associate a purchase with a project, which provides the reason for making the purchase, but also automatically creates cost plans and expense lines for that project. This
enables project managers, shoppers, and procurement specialists to easily track planned costs each time a purchase is made for a Project Management project, and realize actual costs each time an invoice is paid for a Project Management project purchase.

## Impact on checkout and purchase details {#integration-psm-ppm__section_ppd_l24_mqb}

When this application is installed, you must answer the additional question Is this a purchase for an existing project? during checkout. If your answer is in the affirmative, you must select your project
from the list to proceed with the checkout.  
Each project name is associated with a demand number, both of which are then auto-populated in the Purchase Reason field. You can add more information in the Purchase Reason field if you want to. On completing your checkout, these details are displayed on the purchase details page.  
Note:  
* If this purchase isn't made for an existing project, you must mention the reason for purchase in the Purchase Reason field to proceed with the checkout.
* During full checkout, you can select a project for the entire purchase or individually at the product level.
* You can't select a project for a credit purchase.
{#integration-psm-ppm__ul_vbg_d5l_cbc}

## Impact on purchase request line and purchase order line tables {#integration-psm-ppm__section_cbt_cj4_mqb}

When a purchase request is created, you can configure the Purchasing Details form layout on
the purchase request line table to display the Project field. This field
references the selected demand record. Similarly, when a purchase request line is converted to a
purchase order line, you can configure the Summary Details form layout on the purchase order
line table to display the same Project field.

As part of this integration, whenever a purchase is ordered as part of a demand or project, a
cost plan is automatically created in association with that purchase order line. You can
configure the Summary Details form layout on the purchase order line to display the new
Cost plan field. A Purchase Order Lines related list is also added to
the corresponding cost plan record. On the Cost Plan form, the Total planned cost field is auto-populated based on when the purchase order had been generated.
The Total actual cost field is populated based on invoice and expense
line creation.

For information on how to configure a form layout, see [Configuring the form layout](https://www.servicenow.com/docs/access?context=configure-form-layout&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US).

## Impact on invoice line and expense line tables {#integration-psm-ppm__section_m1p_5fs_mqb}

When an invoice is created, and both the invoice and the invoice line are in the Paid state,
an expense line is automatically created for the project. This expense line has an Invoice Lines
related list reference.

For more information on invoice creation, see [Invoices](https://servicenow-prod.fluidtopics.net/NmXngm8fg2FRLY1bZs3WRw "Invoices are generated for a payment against a purchase order. A purchase order can have multiple invoices depending on the payment schedule.").

## Impact of demand and project lifecycle on Sourcing and Procurement Operations flows {#integration-psm-ppm__section_ctx_hjs_mqb}

When a demand is converted to a project as part of demand and project lifecycle:

* The demand number isn't available for selection during checkout.
* When a purchase request line using that demand number is converted to a purchase order line, the latter references the project and not the demand number.
* The cost plan references the newly created project and not the one initially selected by the shopper.
* When an invoice is created, the associated expense line references the project and not the demand number.
{#integration-psm-ppm__ul_exq_zbj_4qb}  
When a demand or project is in a closed state:

* The demand or project number isn't available for selection during checkout.
* Cost plans and expense lines aren't created for closed demands and projects. However, if a cost plan is already created for a closed demand or project, expense lines continue to be auto-generated until all the invoices are paid out.
{#integration-psm-ppm__ul_lxp_2cj_4qb}

## Impact on sourcing request {#integration-psm-ppm__section_nqy_1vs_mqb}

When requesting pricing for a product that doesn't have pricing available, you must answer the
additional question Is this a purchase for an existing project?. If your
answer is in the affirmative, you must select your project from the list to proceed with
submitting the request. On successful submission, the project and demand details are displayed
on the sourcing request record.

As a shopper, you can compare the pricing for your purchase, select a supplier, and proceed to
checkout.

## Impact on off-catalog purchase request {#integration-psm-ppm__section_f12_k1t_mqb}

When requesting a quote for a product that is not available on the Shopping Hub catalog, you must answer the additional question Is this a purchase for an existing project?. If your answer is in the affirmative, you must select your project from the list
to proceed with submitting the request.

## Email notifications {#integration-psm-ppm__section_vbc_sys_mqb}

When a purchase order associated to a demand or project is created, updated, or canceled, the
assigned demand manager or project manager gets an email notification about its impacts on
the cost plans of the demand or project.
**Related concepts**   

* [Sourcing and Procurement Operations integration with Employee Center](https://servicenow-prod.fluidtopics.net/dtGRiCI_rtS7XRWU8Z69dQ "As an employee, shopper, or requester, you can view all procurement case types available to you, knowledge articles, open to-dos and purchasing tasks assigned to you, track your requests, and even access your purchases on the Employee Center (EC) portal by integrating Sourcing and Procurement Operations with Employee Center.")
* [Sourcing and Procurement Operations integration with third-party sourcing solutions](https://servicenow-prod.fluidtopics.net/MKM4DES14WCktTx3gVlt3w "ServiceNow can integrate with third-party sourcing solutions to automate the sourcing process within the Sourcing and Procurement Operations product. A generic, easily configurable sourcing integration framework is provided within Source-to-Pay Integration Framework to enable you to specify the business criteria for triggering an integration. This integration framework can also integrate with multiple third-party sourcing solutions based on different criteria.")
* [Sourcing and Procurement Operations integration with Third-party Risk Management](https://servicenow-prod.fluidtopics.net/SiQT9BfbAPafNE04_lSpBw "Leverage relevant supplier risk assessment capabilities by integrating Sourcing and Procurement Operations with Third-party Risk Management.")
* [Sourcing and Procurement Operations integration with Celonis](https://servicenow-prod.fluidtopics.net/YIyKGFdescG8Hlbms5jH0w "Identify inefficiencies in your customer business process, understand their business impact, and gain insights into the root causes, by integrating Sourcing and Procurement Operations with Celonis.")
* [Sourcing and Procurement Operations integration with Field Service Management](https://servicenow-prod.fluidtopics.net/2Y2CApC_2jib1tbKMuNUaw "The Procurement for Field Service Management plugin (snc.fsm_psm_mobile) provides an integration between the Field Service Management and Sourcing and Procurement Operations applications.")
* [Source-to-Pay Operations integration with Contract Management Pro](https://servicenow-prod.fluidtopics.net/OJQy4ExTW8QC6xiwMtfaUA "The Source-to-Pay Operations with Contract Management Pro plugin (com.snc.sn_spend_clm) provides an integration between the Contract Management Pro and Sourcing and Procurement Operations applications.")
* [Spendint API](https://servicenow-prod.fluidtopics.net/9zZHow_Pkslc0PyA0ch5hQ "The Spendint API provides endpoints that push the catalog, price, availability, order, shipment, and invoice information from a third party to the ServiceNow instance. This API is part of the Source-to-Pay Integration Framework application.")
* [Procurement File Transfer Framework](https://servicenow-prod.fluidtopics.net/eLCPddPT1EbMzckEXWY1Dg "Procurement File Transfer Framework (PFTF) helps you transfer information between the ServiceNow database and a third-party reseller through a File Transfer Protocol (FTP). You can set up an FTP server for access and transfer of reseller data without any spoke development by the third-party reseller.")  
**Related reference**   

* [ERP source validation on Sourcing and Procurement Operations objects](https://servicenow-prod.fluidtopics.net/6xHZWAYps1f3pV1OUzweGA "Sourcing and Procurement Operations supports multi-ERP integration that enables you to use different ERP systems for different regions or lines of business, as required.")