Best way to pre-populate material variable with values for users

[Former Member]

Hi, I have a requirement to prepopulate a material variable with about 5 materials and that is the materials that will default when the query is called. The users would also need the ability to change those values.

My thought is to create a User-exit variable that derives the values from a user maintained table (infoobject).

Does anyone else have any suggestions or ideas on the best way to handle this?

[klaus_werner · Accepted solution]

Hi Kenneth,

what you describe sound exactly like what the personalization is meant for? Then you don't have to do anything but the users type in their materials once (into the variable selection at runtime) and press the "personalization" button.

Regards, Klaus

[klaus_werner · Accepted solution]

Sorry, I was mistaken, this only works in transaction RSRT but not in the frontend because the variable line vanishes after personlization. I agree that your suggestion is probably the best one.

REgards, Klaus

[Former Member]

Hi Kenneth !

I think you idea is best way (and I think you already know how you can do it!)...but just an explaination...what does it mean 'from a user maintained table (infoobject)' ?

Ok, right from a custom table for which your users can use SM30 to update/modify your entries, but the '(infoobject)' specification ? I hope you don't want to refer to your master data table...

Bye,

Roberto

[Former Member]

Roberto, I was thinking of having someone maintain the values in an infoobject. Much easier than having to set up a Z table. THoughts?

Thanks!

[Former Member]

I don't know if there is a best solution...

• Infoobject

With this option you have to create a new infoobject (ZMATERIAL) without attribute (you need only a list material codes) and then to set the authorization profile for the user in order to manage the content.

The creation of an infoobject corresponds to a table creation, but you don't need any other specific options that belong to the infooject (as technical object)...

• Table

With this option you have to create a Z table with only one field and then to allow the maintenance of the table by SM30....

In the ending, if you want to be a purist use the table, otherwise use an infoobject (but there are no significant differences !

Bye,

Roberto