2014 Jan 28 8:17 AM
Hello all,
being a strict OO-focused developer, I always face the same problem when I need to develop a dialogue program in ERP: I am forced to mix up classical module-driven dynpro coding with objects and classes. To avoid this, I am thinking of a possibility, to place an editable ALV on the screen where the user can make his inputs. What I need is a two-column grid with the labels for my input fields on the left and editable fields to receive user input at the right.
A good example for this could be the WD view editor (programm id SAPLWDY_WB_VC_EDITOR), where an ALV similar to what I think of is appearing on the bottom right, where one can edit the element settings.
Instead of creating for each case a dedicated ALV table and coding for displaying the labels, performing search help calls and so on, I would prefer to create a generic class containing all the basic logic in order to reuse it for each specific case. The basic functionality should include the following:
- create the input table out of a ddic structure, generating one line for each field
- populate the label column for each field with the field description from ddic
- provide search help out of the ddic settings
- create listbox-like fields on demand
- pass the input to a structured data element based on the ddic structure
Now, before I start coding this generic class, I'd like to know if anyone of you already did something similar, and maybe if there are any SAP standard classes I could use for this.
Thank you in advance for any suggestions
Best regards
Joerg
Hello all,
being a strict OO-focused developer, I always face the same problem when I need to develop a dialogue program in ERP: I am forced to mix up classical module-driven dynpro coding with objects and classes. To avoid this, I am thinking of a possibility, to place an editable ALV on the screen where the user can make his inputs. What I need is a two-column grid with the labels for my input fields on the left and editable fields to receive user input at the right.
A good example for this could be the WD view editor (programm id SAPLWDY_WB_VC_EDITOR), where an ALV similar to what I think of is appearing on the bottom right, where one can edit the element settings.
Instead of creating for each case a dedicated ALV table and coding for displaying the labels, performing search help calls and so on, I would prefer to create a generic class containing all the basic logic in order to reuse it for each specific case. The basic functionality should include the following:
- create the input table out of a ddic structure, generating one line for each field
- populate the label column for each field with the field description from ddic
- provide search help out of the ddic settings
- create listbox-like fields on demand
- pass the input to a structured data element based on the ddic structure
Now, before I start coding this generic class, I'd like to know if anyone of you already did something similar, and maybe if there are any SAP standard classes I could use for this.
Thank you in advance for any suggestions
Best regards
Joerg
2014 Jan 29 3:43 PM
Hi,
Why not
Just some usefull class for DDIC stuff: CL_RECA_DDIC* (to fetch labels, get fields list...)
And of course RTTS classes for dynamic structure/table/field creation: CL_ABAP_*DESCR.
But I'm wondering about the "look&feel" such an approach would have comparing to classical dynpro coding...
Have fun,
Manu.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |