on ‎2022 Apr 12 7:14 PM
Request clarification before answering.
Hi,
the mentioned table is not an ALV, it is a table control. That's why the only way to extend it with a new field is to implement a modification to add the requested field to the table control. For this you need to generate an object key for the related dynpro to be able to change the dynpro definition.
Technically it should be not a problem to implement this, especially if you already have the data to be displayed already available, but... it's still a modification of SAP-standard.
I hope this helps you 🙂
Kind regards
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
nooooooo, I would never copy a whole transaction of SAP into the customer name space. The main disadvantage is that you copy tenthousands line of code and in case that SAP brings updates/bugfixes for the original transaction via S-Note or Support Package, you have to bring them into your copied version as well. This won't work from my point of view.
In this case, it's better to implement a good documented and capsuled modification.
Kind regards
Jens
Hello,
the answer of @Jeansy is correct.
I actually modified the table control and it turned out to be an "easy" one.
Create an append to structure MEREQ3214
Add the field to the table control:
As FRGDT is a field of table EBAN the field is already populated / no extra development necessary.
Best Regards
Hendrik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 39 | |
| 22 | |
| 21 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.