Reply from LCC352 on Mar 31 at 10:02 AM An elegant solution! My concern would be that the users would get the "bug" for this type of information and come back to you for more in the future - they may even want to associate something with these flags in the form of a field or two (or thirty!) that would ride along with the flag.
Along the lines of Horacio's last comment, I toss this to the group: would it be advantageous to set up a small table keyed to MATNR and the flag "number"? This would allow for expansion of fields associated with the flag as time went on, and if coded properly, would allow for an additional flag without too much coding. The flags could be part of a screen developed to ride along with the rest of the data (as you probably are doing anyway) but would be more dynamic.
Opinions? Am i hallucinating yet again?
Lou
| | | ---------------Original Message---------------
From: neobat
Sent: Friday, March 28, 2014 9:30 PM
Subject: Defining Multiple Fields in One in MARA... Is That Possible?
Hi all,
I added a couple of fields in the past in MARA and now the requirement is to
add 35 more (yes, 35 more!!, what is this company thinking!!)
But all of these fields are pretty much the same type and description
except for the value, meaning is the same field repeated.
The field name is called Extra so I will need extra1, extra2,.... extra35
So I was thinking that instead of defining 35 fields I could just define
only one as zzextra, but on the screen I could represent them with 35
checkboxes and what is going to be store in the table for that field will
be a long text for the checkboxes selected as 1;2;5;33 (if checkbox 1,2,5,
and 33 were selected)
What do you think of this? Is this possible?
or any other input on how I can accomplish this?
Thanks,
neo |
| Reply to this email to post your response. __.____._ |   _.____.__ |
