2021 Jun 22 3:27 PM
Hi everybody,
I want to create a table with a range field type (i.e : /IWBEP/T_COD_SELECT_OPTIONS) for maintaining in SM30 tcode...
Is it possible?
Thanks for your Help,
Stéphane
Hi everybody,
I want to create a table with a range field type (i.e : /IWBEP/T_COD_SELECT_OPTIONS) for maintaining in SM30 tcode...
Is it possible?
Thanks for your Help,
Stéphane
2021 Jun 23 4:25 AM
Yes, it's possible. You can create such a table.
What specifically is it that's not working for you?
2021 Jun 23 7:32 AM
You could also include the structure of the TVARV / TVARVC table
2021 Jun 23 3:03 PM
Dear Stephane,
What is your requirement exactly? It seems like you want to store some values in the table with similar to select-option. There is a standard table already available "TVARVC". You can go to SM30 and give the table name TVARV. You can click on the "Selection Options".

You can go to change mode(by clicking on pencil button), then you can create button. Then lclick on the multiple-selection button and a selection-option pop-up will come. You can use that to store value. Also you can write a select-query to the table TVARVC to find out the values

Let me know if you are looking for the same or elaborate your exact requirement.
Cheers!
Gourab
2021 Jun 24 2:09 PM
Hi,
Thank you for your returns.
I need to qualify item with some criteria. For example, the program for the machine is different according to PRODUCT, COLOR, HEIGHT...
I would to create a table, accessible in SM30, to maintain the paramtere like in IMG_01.
I do it easely in an abap program :


I want to create the same table in SE11...
Frederic : In SE11, i can't put structure TVARV...
Gourab : I know i can do it in TVARVC, but i think it will be to difficult for user to maintain it...
2021 Jun 24 2:15 PM
2021 Jun 24 3:10 PM
Yes, BRF+ is a good candidate in this case.
I have done something similar in the past, which might work here too if there is only I/EQ rows in the ranges. I simply made a table like a matrix of valid options, like so:
PARAM | VALEUR | PRODUIT | MODELE | COULEUR | etc...
Programme | Pgm1 | PROD_A | AXISC | ROUGE |
Programme | Pgm1 | PROD_A | AXISD | BLEUE |
Programme | Pgm1 | PROD_B | AXISD | VERTE |
Programme | Pgm2 | PROD_C | AXISC | VERTE |It's kind of similar to a BRF+ approach, and it's working but it's a bit messy to enter in SM30, like there has to be a unique key for each line and there will need be a single line for each and every valid combination of all the fields... With BRF+ you get an awesome Excel export/import and good overview, (and it will handle the key, and provide simulations among other things)
2021 Jun 25 1:49 AM
Hello Stephane,
I also liked gdey.sapabap's suggestion to use TVARVC( since SAP does much of the heavy lifting to provide screens for select-option maintenance).
If you are open to using 3 tables instead of 1, you might want to explore using view clusters. The hierarchy of the views would then be:
Program IDs -> Criteria IDs(per program ID) --> Select-options( per criteria ID)
There is plenty of information on creating View Clusters and maintaining them....
Regards,
Nikhil Rao
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |