Use Function and Document Security in Procurement Command Center

Use function and document security in Procurement Command Center so dashboard access, actions, and visible records follow the user security model. This enhancement is important for controlled rollout because procurement dashboards often expose operational actions and sensitive purchasing data.

The following security and document management improvements are included in this release:

  • Only users designated as buyers in Oracle Purchasing can perform actions for requisitions, orders, and agreements in Oracle Procurement Command Center.
  • Requesters and their supervisors can access requisitions as document-level security feature is implemented for the Requisitions dashboard.
  • Any incomplete purchase orders and agreements that have been deleted in Purchasing will also be removed from the dashboards when you run the PO PCC ECC Data Load program with the incremental load option. Previously this required the full load option to be used.

Steps to enable and configure

  • Apply the Procurement Command Center update that delivers function and document security in Procurement Command Center and confirm the required Oracle Enterprise Command Center Framework level is installed and enabled.
  • Grant the Procurement Command Center pages, actions, function security, and data access to the procurement users who will use the feature.
  • Run the applicable Procurement Command Center data load as an initial full load, then schedule incremental refreshes that match the operational review cycle.
  • Validate the dashboard metrics, refinements, result tables, and action links with representative requisitions, orders, agreements, suppliers, items, and negotiations.
  • Review responsibilities, functions, grants, and document security rules for each user group.
  • Test with users who should have full access, read-only access, limited document access, and no access to restricted actions.

Tips and considerations

  • Confirm responsibility, operating unit, buyer, supplier, and document security before broad rollout so users see the right records and actions.
  • Use selected refinements and result-table drilldowns during testing so users can move from a summary metric to the transaction or setup page where action is taken.
  • Treat security validation as a required implementation step; test both dashboard visibility and action availability, not only menu access.

Key resources

Oracle Purchasing User's Guide