Skip to main content

Editing views for the object-centric Open Purchase Requisition Processing app

The Open Purchase Requisition Processing app comes with a prebuilt set of views. Edit the app’s views in Studio if you need to:

  • Make any customizations and changes to suit your business process.

  • Change the look of the supplied views.

  • Include custom items that you added to the perspective that you’re using with the app.

The app doesn’t do anything automatically with custom items in a perspective. They won’t be surfaced in views unless they’re items we asked you to add during app setup. If you want to use your own custom items, you’ll need to edit the app’s views to include them. You don’t have to surface all (or any) of your custom items in the app’s views. If you don’t, it doesn’t cause a problem, the app just ignores them.

The Open Purchase Requisition Processing app requires the SAP ECC system-specific Catalog 3.0 extension in addition to the Procurement Core data model. The standard Core Procurement perspective does not contain all required objects and attributes for contract usage analysis, vendor master enrichment, and PR optimization logic.

The Open Purchase Requisition Processing app comes with these views:

  • Open Purchase Requisition Action View - Includes two tabs showing open and closed Purchase Requisitions:

    • Open Requisition Line tab: Provides a prioritized operational workspace for managing open requisition lines, highlighting risks, SLA breaches, and missing contract or supplier information as well as giving “Quick Opportunity" recommendations.The Quick Opportunities panel appears at the top of the Open PR Processing View and automatically categorizes each open requisition line into an actionable opportunity (f.e., free text, missing price, SLA exceeded etc).

    • Closed Requisition tab: Supports historical analysis of completed requisitions to identify trends and inefficiencies.

  • Profile / Supplier / Material Views - Enable contextual deep-dives into specific requisitions, suppliers, or materials to support informed sourcing and decision-making.

  • Notes and Tasks View - Allows users to track change history, collaborate through comments, and assign tasks to ensure transparent ownership and faster resolution.

  • Closed Requisition Lines View - Supports historical analysis of completed requisitions to identify trends, inefficiencies, and optimization opportunities.

  • Process Explorer - Provides a process flow visualization of the end-to-end procurement process, from purchase requisition through to invoice receipt. Allows buyers and analysts to understand how requisition lines are flowing through the process, identify bottlenecks, and investigate deviations from the expected process path.

You’ll need Analyst permissions for Studio and for the relevant views and components to modify them. If you need training, check out the training track “Build Knowledge Models and Views” on the Celonis Academy.

If you make any edits to view components that involve the calculated attributes from the Knowledge Model, we’ll automatically update the calculated attributes in the Knowledge Model to match your edits. You can also adjust them directly in the Knowledge Model before or after editing the views, as explained in Validating KPIs.

Here’s how to edit the Open Purchase Requisition Processing app’s views:

  1. In the Celonis navigation menu, select Studio.

  2. In the Studio overview, find the Open Purchase Requisition Processing app in the space where you installed it, and click its tile.

  3. Expand the package’s structure, then expand the folders to find and select the view you want to edit.

  4. In your selected view, click Edit View to enter edit mode.

  5. Select any component of the view to go to the component editor. Here you can add and remove data fields shown in a table or chart, change sorting and display attributes, add action buttons, and other edits, as relevant for the component type.

  6. When you’ve finished editing a component, click Save to save and exit.

  7. When you’ve finished editing all the components you want to, click the Save icon to save the view, then click the Exit Edit Mode icon (the blue square with the X) to lock it again.

    Tip

    It’s also possible to edit views in the YAML editor if there’s something you can’t achieve in the visual editor. To view the YAML, click the View settings icon and select Edit View YAML.

  8. When you’ve finished editing all the views you want to, publish a version of the app package. There's a Publish button at the top of all the screens in your Studio space.