2019 Oct 29 6:01 PM
Hi Experts,
I received a requirement to add additional fields to the output of transactions QM10,QM11 and QM12. I was able to add the fields in the output of QM10 and QM11 by appending in the structure of RQMQMEL1, but had a dump when I tried to add the fields in the alv layout so I came up with the solution to append these fields in structure QMEL as well and this solved the abap dump. Now I can display the fields and to fill values to these fields, I created an implicit enhancement inside program RQMELL10.
Now, I did the same steps for QM12. I added append structure in RQMQMSM, then I encountered a similar dump when I tried to add the fields in the ALV layout, I thought adding fields in QMSM structure should remove the dump but I cannot add the same field due to the error that it has been already added in RQMQMSM...I cannot activate the table QMSM and I'm currently stuck here.
I attached the short dump when trying to add fields in the layout output of alv.
I hope someone has already done a solution to this issue and able to share, help me resolve this.

Hoping to get help as soon as possible...
Geoff
2019 Oct 30 2:42 AM
Resolved by adding the fields in qmsm instead of rqmqmsm. I noticed it's in the same structure which is different from qm10 and qm11. I added in qmsm and found the fields in the layout selection table. Just add a condition to avoid your changes if the user is using qm13 since qm12 and qm13 shares the same program.
Hope this information helps someone in the future.
Geoff
Hi Experts,
I received a requirement to add additional fields to the output of transactions QM10,QM11 and QM12. I was able to add the fields in the output of QM10 and QM11 by appending in the structure of RQMQMEL1, but had a dump when I tried to add the fields in the alv layout so I came up with the solution to append these fields in structure QMEL as well and this solved the abap dump. Now I can display the fields and to fill values to these fields, I created an implicit enhancement inside program RQMELL10.
Now, I did the same steps for QM12. I added append structure in RQMQMSM, then I encountered a similar dump when I tried to add the fields in the ALV layout, I thought adding fields in QMSM structure should remove the dump but I cannot add the same field due to the error that it has been already added in RQMQMSM...I cannot activate the table QMSM and I'm currently stuck here.
I attached the short dump when trying to add fields in the layout output of alv.
I hope someone has already done a solution to this issue and able to share, help me resolve this.

Hoping to get help as soon as possible...
Geoff
2019 Oct 30 2:42 AM
Resolved by adding the fields in qmsm instead of rqmqmsm. I noticed it's in the same structure which is different from qm10 and qm11. I added in qmsm and found the fields in the layout selection table. Just add a condition to avoid your changes if the user is using qm13 since qm12 and qm13 shares the same program.
Hope this information helps someone in the future.
Geoff
2019 Oct 30 10:08 PM
Thanks for an update. Please mark the question as answered (see this blog).
2019 Nov 02 12:21 AM
Hi Jelena, I tried to refresh cache but it didn't give an option to mark the question as answered. only thing I noticed is when I close it, there's an option to close - question answered. But I think there's a better way to mark it as answered as doing this will still not categorize my question as answered. I don't see any option beside the subject question to mark it as answered even if I refresh the cache as shown in the blog...
2019 Nov 04 7:23 PM
As the question's author, you should have an option "Accept" right underneath the answer:

If you click on it, it will mark the answer as accepted and this will let others know this has been answered. This is like telling others "thanks, I don't need any more help with this". In addition to that, you can also close the question using Actions -> Close button underneath the question:

This will mark the question as closed and no one will be able to post additional answers. It would be like telling others "this is done, I moved on and don't want to hear anything about this anymore". 🙂
2019 Nov 04 7:24 PM
Sorry, I meant to post this as a comment but due to some bug Submit button didn't work. 😞
2019 Nov 12 6:12 PM
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |