Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

View Variant

Former Member
0 Likes
4,907

hi,

What are view variant (present in transaction SE54) and how it can be implemented. Is it same as normal variant for a view or is it different. i already googled but didnt got any relevant answer. What other functionalities can we have with view variant.

in SE54, under edit view variant button, there are two radio buttons ABAP Dictionary and Dialog Control. ABAP Dictionary will create, change and display view variant, what does dialog control radio button do.

thanks,

tanmaya

Edited by: Tanmaya Gupta on May 24, 2010 6:02 PM

6 REPLIES 6
Read only

Former Member
0 Likes
1,750

Hi,

SE54 is used to create a maintenance dialog for tables. That is, a screen mask where you can look, create and edit data in your table. The view is called from SM30, and it appears like a customizing.

Is a pretty way to users change some basic data (unlike SE16...) and you can configure authorizations to the access to the view.

A maintenance view variant is like a view that you can read, change, insert and delete data.

Best regards,

Leandro Mengue

Edited by: Leandro Mengue on May 24, 2010 1:10 PM

Read only

0 Likes
1,750

hi,

i want to know about view variant push bitton tab in SE54...not about edit table tab.

thanks

tanmaya

Read only

0 Likes
1,750

Maintenance view variants

Definition

Maintenance view variants are partial views of generated maintenance dialogs, i.e. a maintenance view variant restricts the maintenance dialog on which it is based, e.g. to a smaller number of maintainable fields, or uses a more restrictive database selection than the initial dialog. The maintenance view variant has no maintenance dialog of its own, it uses the maintenance dialog on which it is based, including the maintenance screens and all its checks.

Use

Existing customizing views are often too detailed for a process-oriented customizing perspective. To make these views useful for the process perspective, they must be split into smaller views. This would mean that new maintenance dialogs must be generated and that any individual adjustments required per new maintenance dialog must be repeated. Maintenance view variants restrict existing dialogs to the contents required for the a process-oriented perspective, without additional generated dialogs.

Best regards,

Leandro Mengue

Read only

0 Likes
1,750

hi leandro,

can you explain this with an example...in simpler language.......

thanks

tanmaya

Read only

0 Likes
1,750

Hi,

A View variant is like the as maintenance dialog (screen & list to look and edit tables).

The diference is that a View variant uses a maintenance dialog and you can select less fields (columns) that you wish to show. Also, you can restrict the selection of records.

Example:

- You create a maintenance dialog for a table with employees.

- You create a view variant 1 that uses the maintenance dialog but restrict the selecion to only man employees.

- You create a view variant 2 that uses the maintenance dialog but restrict the selecion to only woman employees.

Best regards,

Leandro Mengue

Read only

0 Likes
1,750

hi,

i have created the view variant from se54 but i am not able to display the contents....from there (se54, display or change mode).

Also what is the logic.....

when you test data then first data comes to actual view (from which the view variant has been created) and then goes to view variant.....

or data comes directly to view variant irrespective of the view from which it is created.

according to me when we fetch the data then view variant will check the selection criteria and fields from view then it checks the selection criteria of variant and then display the records.

if this is the logic then definitely it will take more time as compared to normal maintenance view.......but view variant documentation says that "Existing customizing views are often too detailed for a process-oriented customizing perspective" means that smaller view variants are less time consuming....

can any one explain...as both the things contradicts according to my understanding...

Thanks

Tanmaya

Edited by: Tanmaya Gupta on May 31, 2010 11:22 AM