Sourcing and Procurement Operations integration with Project Management
Eliminate manual efforts of linking purchase orders to projects by integrating Sourcing and Procurement Operations with Strategic Portfolio Management's Project Management.
- 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
- 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
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
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.
- 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.
Impact on purchase request line and purchase order line tables
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.
Impact on invoice line and expense line tables
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.
Impact of demand and project lifecycle on Sourcing and Procurement Operations flows
- 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.
- 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.
Impact on sourcing request
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
When requesting a quote for a product that is not available on the ShoppingHub 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
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.