User specific default variant setting

Hi gurus,
My requirement is Report should get executed with default user specific Variant.
For example while running MB51 system should pick the corresponding variant based on the user who is executing the report.
Based on threads i created variants with U_userid like U_RAM & U_LAX.
I checked with user ids of RAM and LAX, But system is not picking automatically.
can u help me

hi,
see this.
https://forums.sdn.sap.com/click.jspa?searchID=14929390&messageID=5872211

Similar Messages

User specific default variant in a selectio screen

Is it possible to provide an option to create user specific default variant in a selection screen?
I have developed a custom report program. Now I want to allow users to choose one of their variants as default variant ? Please help.

Hi very Simple and easy solution:
In SE93 when u are creating the transaction for the program use the option 'Start with variant' and give your own vaiant name for the program start. This will help you in starting your proam always with your default variant.
Hope That Helps
Anirban M.

User specific default variant for FBL1n FbL5n

Friends,
I am trying to create a variant for FBL1n report layout for specific user. Now the issue is the user has to go and select his specific variant every time he executes FBL1n. Is there any way by which we can default the specific variant for specific user.
Any help is much appreciated.

Hello,
Go and change the variant selection settings in FB00. You select the relevant variant.
Regards,
Ravi

User-Specific Report Variants

Hi,
is there an easy way to assign a user-specific report variant without modifying the report or create own transactions. For example by assigning the report variant somehow to the user-parameter?
Thanks for your help,
Andreas

Hi,
Maybe you could play with the GET PARAMETER ID ...
Or maybe you could create a program that start the real program after selecting the default variant of the user. After you call the program with this variant.
SUBMIT REPORT01
       VIA SELECTION-SCREEN
       USING SELECTION-SET 'VARIANT1'
       USING SELECTION-SETS OF PROGRAM 'REPORT00'
       AND RETURN.
Rgd
Frédéric

User Specific Transaction Variant

Hi,
Can i please have guidelines for Transaction variant creation, specially user specific transaction variant creation along with example?
Regards,
Samir Wadajkar

Dear
Please see this wiki for useful :http://wiki.sdn.sap.com/wiki/display/Snippets/Transaction%20Variant%20-%20A%20Step%20by%20Step%20Guide%20for%20Creation
OR
Go to SHD0
Enter the transaction code - Enter the transaction variant YXXX under transaction variants tab
Create - the transaction variant. When you back after creating .... Save all the screens and do a syntax check - this will take you to different screen - Just execute and come back
You should now be in SHD0 with your transaction code as well as transaction variant.
Now, go to 'GOTO' on application tool bar - Create transaction variant. Do not check 'Inherit GUI attributes' under classification and check all under GUI SUPPORT
Execute your newly create Ytransaction
Go back to SHD0 again and repeat the same process but enter different name than previous one. do the exact same process.
Create new transaction which means enter different transactio name like if the previous one is yxxx1 ... create this as yxxx2.
You can take the standard transaction from every user or who you dont want to give by removing the authorization from user master (talk to security people)
Hope this will be usefull
Regards
JH

Error MEQ006 - no user specific selection variant found in VL31N

Dear gurus,
in VL31N I get an error message MEQ006 - no variant found. Where from system takes user specific selection variant in tx VL31N?
P.

Hi Pavel,
Check this Note 305541 - VL31N: load selection variant automatically
Regards,
Pavan

User specific screen variants

Hi All,
Can anyone tell me, how can i create user specific Screen Variants for the Customer Mater (XD02) ??

As I have tried the same but its not working for the specific user. Can you suggenst me any other process how can i create the same ???
Edited by: siddharth patel on Apr 14, 2010 7:46 AM
Edited by: siddharth patel on Apr 14, 2010 7:47 AM

Disabling User specific/Default Setting

In the output of CV04n selection while 'Save Layout' how is it possible to enable/disable
'User Specific' or 'Default setting'

Hi,
Did you mean Set or enable / disable? Anyways if you want to set, you can do it as follows:
1. Global: I.e. Available for all
Selection Variant: Global do not toggle the User specific box
Description: XYZ
2. User Specific: Available only for the user
Selection Variant: aaa Toggle the user specific box.
Description: uvw
If this doesn't answer your query, please explain further.
regards
C

User specific default setting

Hi Guru's,
I have one ALV z-report.
I have created two layout which is user specific.
At the time of selection of layout system is allowing me only default setting and the field of user specific is showing gray.
What will be the problem?
Can anybody help me for this?
I want to assign that layout to my specific user.
But in the std report e.g. MB51 system is allowing me to assign layout at user specific.
Thanks & Regards,
Nilesh Ithape
9967166393

Hi Nilesh,
As you are telling it is Z-Report,definitely problem may be with coding. Consult your technical people over there or post this in ABAP related forum.
Regards.

User Specific Display Variants

Hi
Were on ECC 6.0 and when I choose to create and save a display variant from and ALV screen the user-specific box is ticked and I can not un-tick it because its grayed out - no matter what we do we can not un-tick this checkbox. We need to create global display variants so that all user can use these display variants.
Is there a configuration setting that we can adjust ?? any suggestions to overcome this problem are welcome.
Thanks

Hi Eric,
I'm a bit busy now and I cannot give you a complete solution, but sure can give you some c(l)ue. Just see if you have some success. If you do not, then i wuill get back to you later.
Refer to the follwoing SAP Tables and see if you have some luck.
==========================================================
LTDX --> Generic storage of display variants
LTDXD --> Default display variants
LTDXS --> SAP Default Display Variants
LTDXT --> Display variant texts
==========================================================
The idea is to try and manipulate the table entries for various users.
Regards,
Anand Mandalika.

User specific default layout in BCS

Dear all,
We set a default layout in BCS for all users.
Know I wonder if it is possible to set a different default layout (in Total Records) for a certain group of user?
Any one an idea?
Regards,
Oliver

Hi,
What do you mean by 'layout'? Layout for budget in FMBB? In this case, each user is free to select to him(her)self the layout to work with.
Regards,
Eli

Copying user specific reporting variants to other users

Hi,
Does anyone have experience in copying user saved variants to other users?
We'd like to create a few complex variants for reporting and then distribute them to all of our users.
Thanks!
-Miikka
Edited by: Miikka Åkerman on Nov 18, 2009 2:40 PM

Hi,
In reports input Screen you have this option,
In selection screen you can find, Save as a New varient, give some name and save , don't select Save as User Varient and save it.
Note: Check with the select Save as User Varient & Use as default Varient options.
Thanks
Reddy

How to restrict users to not default layout while creating a user specific?

Hi all,
I have a problem with frequent changes in report layout setting. When users trying to create a user specific layout in the window "Default" is set, out of "User specific" & "default" checkbox defaultly, so users saving the layouts. so it's overwritting on existing layout. we are ossing the old data. how to restrict end users to create new one with out changing the existing one.How to change that default check in "Default" check box to user specific defaultly. where i have to do settings for this. Thanks in advance.
Pradeesh

Hi ,
My problem is still not resolved. I tried applying the people picker property and set a specific field(an email id field) to be available to only admins. Now the field is not visible to the normal users but only admins which is good but that email field
should be able to take normal users as wel as admin's email ID. currently due to the people picker property it only takes admin's ID and not normal user's ID - which is not as per expectation.
What this email ID field does is - when a normal user is logged in he/she wont see this field in that view. But when an admin logs in he/she can switch to admin view and see this field . The admin can put any user's ID in this field and pull out the required
resource's Time Report for modification.
Please let me know how do i overcome my problem. Detailed step description will be very helpfull .
As per Cameron's suggestion (add a rule on the "additional admin section") , i am not sure how exactly that is done. Would help a lot if i got to know how this works.
Regards,
Guru

User Specific VA01 Screen variant (item overview tab first then sales tab)

Hi,
One of my user wants to see more number of line items on the sales order creation screen. Is it possible to create user specific screen variant? Like bringing item over view tab first and then sales tab at VA01 screen for one particular user.
Thanks in anticipation.
Regards
Suman Jha

hi,
you have two solutions for your issue.
1. please check the resolution of your desk top which you are working.
2. SAP has fixed the screens like that onlly so please write to SAP if there is any solution on this they will provide because no enhancements or developments or no programs i think we can do that.
regards,
balajia

User-specific break-point

Hi
while debugging whether it is possible to have a <b>user-specific breakpoint???</b> if so gimme idea how to make it???
Thanks in advance

ABAP Debugger
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a line of code that tells the ABAP runtime processor to interrupt the program at that line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Running a Program in Debugging Mode
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also useful if you do not know the program very well and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator Select a report or transaction and program and choose Program Test Debugging.
From the ABAP Editor Choose Program  Execute  Debugging (or the Debugging pushbutton).
From any screen Choose System  Utilities  Debug ABAP.
From any screen Enter " /h " in the command field.
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose
System  Utilities  Debug system from any screen. To stop the system Debugger, choose Debugger  Debugging off.
Displaying Program Attributes
You can display the attributes Fixed point arithmetic, System program and Unicode checks active of the program that has just been executed by choosing Goto  Further Information  Program Attributes.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto  Display data object.
Single field Displays the contents and technical attributes of a field.
Structured
field Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table Displays the type, line numbers and contents of an internal table.
Object Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Breakpoints
Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoint
at statement The Debugger stops the program directly before the specified statement is executed.
Breakpoint
at subroutine The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module The Debugger stops the program directly before the specified function module is called.
Breakpoint at method The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Use
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted a BREAK-POINT statement in an ABAP program, the system always interrupts the program at that point. You should only use static breakpoints during the development phase of an application. You should set static breakpoints whenever more than one programmer is working on the same program and you always want to stop the program in the same place.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. You should, therefore, use them when you only want the program to be interrupted when you run it yourself. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter (for example, only activate the breakpoint after it has been reached five times).
Special Dynamic Breakpoints
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the program code. Event here is used to refer to the occurrence of a particular statement, for
example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger.
Transferring Breakpoints to HTTP and Update Sessions
If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.
If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC <> 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities  Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
1. Position the cursor on the line of the source code at which you want to set the breakpoint.
example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger.
Transferring Breakpoints to HTTP and Update Sessions
If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.
If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC <> 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities  Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
1. Position the cursor on the line of the source code at which you want to set the breakpoint.
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
1. Choose Breakpoint  Breakpoint at  Function module...
2. Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
3. Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint  Breakpoint at  System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint  Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint  Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto  Control debugging  Breakpoints.
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint  Set/delete. To delete all breakpoints, choose Breakpoint  Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint  Activate/deactivate.
http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
For debugging tutorial:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://www.sapdevelopment.co.uk/tips/debug/debughome.htm
http://www.sap-basis-abap.com/sapab002.htm
Chaeck the following documents,
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Hope you can get all the required information from the above documents.
Reward points if helpful.

User specific default variant setting

Similar Messages

Maybe you are looking for