Show ZMRQ/SMRQ in fiori "create incident" application (solman 7.2)


In the application "create incident" we have the following documents/transactions to pick from:

We have now been asked to extend the application so that we can pick ZMRQ/SMRQ from the selection list. Does anyone know the correct way (or any way) of doing this?

Thanks in advance!



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Mar 31, 2017 at 08:14 AM

    Hi Keith,

    You took me in the right direction!

    These parameters in "DNO_cust04" changes which documents you can see in "create incident":

    So after the change:


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 09, 2017 at 06:16 PM

    Dear Mike.

    if you need to set one transaction type for default please implement the SAP Note: 2340690 - ST-UI: Corrections for Fiori App Create Incident 1.1 Patch

    Best Regards.

    Jorge Rodriguez.

    Add comment
    10|10000 characters needed characters exceeded

    • Thank you very much, this note solved my 2 issues (Navigation to "My Incidents" App is not possible after creation of an incident and Process Type selection is shown, if only one process type is valid)


  • Mar 28, 2017 at 05:49 PM

    Hi, Mike.

    You can find the extensibility information for the Create Incident app at the following locations:

    Create Incident - Fiori Apps Library
    App Extensibility: Create Incident -


    Keith Nunn
    SAP Product Support

    Add comment
    10|10000 characters needed characters exceeded

    • Hi, MIke.

      So it seems the app is just using the standard types associated to the logged-on user as defined in transaction DNO_CUST04. If you can verify that's what you're seeing then it may just be adjusting the types defined there to have the app display the ones you want. This is likely to affect backend processes as well, however. If you want to have different types for the Fiori app than what you have available to the user in the backend then it would fall outside of the standard extensibility scope, most likely. Consulting or other SCN users could potentially provide further details for you, in that case.



Skip to Content