Setting up the SCM Procurement Workspace
Installing the Workspace
Starting with the Fall 2020 release, SCM Workspaces is no longer part of the Certinia SCM core product. Contact Certinia Onboarding to have the SCM Workspaces package installed into your org.
For more information about editing and assigning permission sets, adding tabs to apps and profiles, and configuring apps, see the Salesforce Help.
Complete the following setup for your users to access the SCM Procurement workspace:
- Assign the SCM - Workspaces - Procurement Workspace permission set to the users that require access to the workspace. The SCM - Workspaces - Procurement Workspace permission set provides access to the SCM Procurement Workspace.
- The workspace links to various parts of the product and is populated by the relevant records. To view the dashboard correctly with populated data, you must assign the SCM Super User permission set to ensure that your users have access to the following objects:
- Purchase Order
- Purchase Order Line Item
- Requisition
- Requisition Line Item
- RTV
- Sourcing Request
- Supplier Catalogue
- Supplier Site
- Purchase Contract
- Purchase Contract Line
- Manually add the SCM Procurement Workspace tab to any apps. By adding this tab to the relevant apps you gain maximum benefit from the SCM Procurement workspace, supporting your workflows, and reducing the time needed to access the information required in your role.
- Manually add the Procurement Workspace tab permission on the profiles that require access to the workspace.
List Views
The SCM Procurement workspace includes the following list views:
List View | Object |
---|---|
Active Catalogues - Procurement | Supplier Catalogue |
Active Suppliers - Procurement | Supplier Site |
All - Procurement | Purchase Contract |
Approve Requisitions | Requisition |
Open Purchase Orders - Procurement | Purchase Order |
Open Sourcing Requests | Sourcing Request |
Purchase Orders Awaiting Approval | Purchase Order |
Some list views have “Procurement” appended to their name. This is to differentiate them from the list views with the same name included in the SCM package.