Show TOC

Manage Change RequestsLocate this document in the navigation structure

With the transactional app Manage Change Requests, you can follow up on changes you have requested from your vendor as well as place requests for changes you have collected. You create change requests when using the apps for managing materials or uncovered requirements. You can request that the vendor change the quantity or delivery date in a purchase order or stock transport order so that material availability can be ensured and customer requirements can be fulfilled. At the end of the process, you either apply the changes, which automatically updates the order, or you discard the request.

Key Features

By launching the Manage Change Requests app from one of the four delivered tiles, you can manage your change requests according to their status. You can view all your change requests, find your new requests so that you can place them, track your requested changes to enter the vendor’s response and new proposals, and apply or discard the requests that have been answered.

With the Manage Change Requests app, you can do the following:

  • View a list of vendors and contacts from whom you have requested or want to request changes

  • View details of the change requests in a table

  • View additional information about the MRP elements in a quickview

  • Add notes to the change request

  • Send an email to the vendor to request changes

  • Enter the response from your vendor

  • View the stock/requirements situation of the item as a table or as a chart

  • Apply the changes to the purchase order or stock transport order

  • Discard the change request if it is outdated or no longer needed


To improve the performance of the Manage Change Requests app, authorized users can delete closed change requests (with status applied or discarded) from the database by running the report PPMRP_CHANGE_REQUEST_DELETE in the back-end system. For more information, see the report documentation.

Technical Features

In addition, this app supports the following technical features and options. Some of these features require additional components or settings in your system landscape:

  • If the long material number has been activated in your back-end system, it is automatically displayed in the <Material> field in this app. For more information, see Long Material Number in SAP Fiori Apps.

Navigation Targets

This app enables users to access other apps directly (for example to display detailed information).


Linked apps have to be already available in your system landscape or you have to implement them along with this app.

Fact Sheets Linked

From the corresponding quickviews, you can navigate to the following fact sheets:

Transactions in the ABAP Back End

From the corresponding quickviews, you can access the following transactions in your ABAP back-end system:

  • Display Purchase Order (ME23N)

  • Display Purchase Requisition (ME53N)

  • Display Sales Order (VA03)

  • Display Production Order (CO03)

  • Display Process Order (COR3)

  • Display Planned Order (MD13)


You cannot access SAP GUI transactions or Web Dynpro transactions if you are working with SAP Fiori apps on a mobile device or tablet.

System Landscape Requirements

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. One of the requirements for your system landscape is that your back-end product meets the required product version stack:

Required Back-End Product (Product Version Stack)

  • SAP enhancement package 8 for SAP ERP 6.0 (01 (01/2016))
  • SAP enhancement package 7 for SAP ERP 6.0 (11 (01/2016))

The front-end components of this app (such as the user interface) are delivered together with the components of other apps as part of this SAP Fiori product:

Front-End Components Delivered with (Product Version Stack)

SAP Fiori 1.0 for SAP ERP ( 09 (01/2016) )

For more information, see the app implementation document of this app.

Component for Customer Incidents