Skip to Content
avatar image
Former Member

Unable to generate xml for UI components using t-code /n/tmwflow/mopz_stack

Dear Experts,

I have installed successfully Netweaver gateway component of Fiori app.

To install UI component, I have to generate xml file because we are at

SAP NetWeaver 7.00 Enhancement Package 02

I tried following 2 ways to generate xml but nothing working for me:

1. Manual generation of xml file using t-code /n/tmwflow/mopz_stack

-          Started new MOPZ transaction

-          Manually added files and confirmed them.

-          Completed the transaction

-          Used the transaction no. in t-code /n/tmwflow/mopz_stack to generate xml file but got following error:


2. Automatic calculation of files and xml generation

-          Started new MOPZ transaction.

-          Chose automatic calculation of files and selected UI component to add in the basket.

-          While confirming the files, along with UI files MOPZ recommended other files also and downloaded them in the basket (no option to download only UI files). Hence xml file is generated with lot of components which I don’t want to install.

Please help me to generate xml file only for UI components.

My system details:




1.png (2.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 08, 2013 at 09:22 AM

    Hi Hardeep,

    Stack xml file generation is addressed in the below thread.

    Thanks & Regards,

    Akila Sangili.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Masayuki Sekihara

      Thanks Masa for your response.

      I tried 2nd option as well "Select Files Manually". Once I completed my transaction, I have to goto t-code /n/tmwflow/mopz_stack to generate xml based on transaction ID, but I am getting following error:

      Using "Calculate Files Automatically - Recommended", I am forced to download few extra files along with UI files.

      Both ways of generating xml files are not working out for me. Please suggest me workaround.



      1 (2).png (2.3 kB)