No user-specific shop papers are defined

Hello Experts,
While trying to print the notification the above mentioned error is given ( No user-specific shop papers are defined).
In customisation, the setting for shop paper has been done as * (star) for user, i.e it means its applicable for all users, still the error prevails.
Please help to fix this ....
Regards
Rahul Chitte

To Start with
1.Quality Management -->Quality Notifications --> Notification Processing -->Print Control.
Enter " N" for notification
2.Define Shop Papers---->
Output program RQQMUD01( or your own )
Form Routine    PRINT_PAPER
Form            Make sure that you have entered correct form
3.Assign shop paper to Notification type---->make sure that you have selected both correctly
4.Define printer -
>In User Its better if you create a user Gr or Profile instead of " * "
(ex check profile Q_QMEL       A       Process all quality notifications completely) or simply keep it blank
.Enter the shop paper you have created

Similar Messages

Anyone know where user-specific print parameters are stored?

and is it possible to change parameters (such as Time of Print = Immediate) for other users?
I'm using R/3 4.7 Enterprise.

Interesting, thanks.
But how about other parameters, such as Storage Mode, New spool Request, Do Not Append Print Jobs, etc. Any idea where those are stored?

OIDH - User specific print control

Hi Experts,
In OIDH, we used to maintain user specific print control for the combination of Planning Plant & Planner Group.
There following same entry was maintained in 2 different ECC instances(Testing & Quality)
User - No entry(blank)
Planning Plant - *
Planner group - *
Shop paper - No entry(blank)
Output device - LOCL
New Spool Request - enabled
Print Immediately - enabled
Delete after output - enabled
In Testing environment, For a released work order, when i select Order-> Print -> Order, a pop up appears showing the entries of Shop papers.
In Quality environment, For a released work order, when i select Order-> Print -> Order, a pop up appears mentioning "No user-specific shop papers are defined".
Could you Pls let me know what could be the reason for the same User specific setting, Testing & Quality instances are behaving in a different way.
I hope the Quality system displays the right output message for the above Config setting.
Regards,
Karthik Bhaskaran

Please make changes in the following fields
User - No entry(blank) Instead of blank " * "
Shop paper - No entry(blank) Instead of blank " * "
Create the transport and move it to Quality and test it.
Hope this helps.
Thanks
S.N

Setting OMCQ User specific.

Hi All,
Transaction OMCQ is used to set the error messages in SAP standerd applications but I want to make it user specific, though in OSS Note 935755 SAP has suggested to work with this transaction by making it user specific , but steps are not given, Can any body suggest me how to make it user specific.
Regards,
Sifath...

Hi
You have to create a version for the actual message by copying the same.
Example:
Copy the following message
Verson Application area Mesaage
00 06 042
as
01 06 042 
and against this message assign user specific message like error or warning.
Assign this version number to user parameter MSV in user settings.By defining different versions and assigning this number to users , we can configure user specific messages.
I think this will solve your problem.
Regards
Ramakrishna

Queries related to shop papers

Please explain the following terms and its significance in shop papers:-
1.Archive-object id
2.Significance of underlying print program
3.Significance of user specific printer
4.Significance of activate print diversion
5.Significance of activate print online.
6.Significance of spool request
7.Are there any shop papers linked to plans/task lists/list editing?

Check these links
I think Archive object ID is used for store the achieved shop papers,which you can display in future
Refer following links.
[Displaying and Archiving Shop Papers|http://help.sap.com/saphelp_47x200/helpdata/en/5b/ae365f4b8611d182ba0000e829fbfe/content.htm]
[Settings for Printing Shop Papers|http://help.sap.com/saphelp_470/helpdata/en/32/da2e88713c11d58cd90000e8284931/content.htm]

Printing Shop Papers for Completed Notifications

Hello,
This issue has been brought up on this forum before, but I have not managed to find an actual solution that was implemented by an organization.
We are basically trying to print Shop Papers for completed (NOCO) Notifications that have Orders assigned but that have been completed and TECOu2019d. The thread Need to REPRINT the Service Notification explains that it is not possible to print such shop papers. Is there some way to create a work around using user exits or a custom program to enable such shop papers to be printed? I've already checked with SAP and was told that no SAP note fulfills this requirement on ECC 6.0. I would much appreciate any insight on a solution you may have implemented.
Thanks in advance,
Tarun

PeteA is right you will need to have some custom code to by-pass the status checks that SAP has implemented.
Prometheus Group has a program called the Work Order Print Manager that can do this for work orders. I am a developer for this solution.
The program gathers all document related to the work order (services for objects, DMS, sapscripts/smartforms, equipment doc, functional location docs, material docs, etc) and puts them into a nice GUI for printing.
Specifically for work order you cannot print them from standard SAP if the order is in created status because the menu is greyed out). However we can put a button in a user exit to call the program. The sapscripts appear along with the other documents and can be printed.
Additionally we can add watermarks and/or to the document to let the users know they are trying to print a work order in the incorrect status. We/ I can demonstrate the work order solution to you and prototype a IW52 solution after a short discussion to help us understand your issue in particular.
http://prometheusgroup.us/wopm.php
if you are interested in a demo email them to set up a demonstration with me.
Edited by: Tim Huang on Mar 17, 2010 1:14 PM
Edited by: Tim Huang on Mar 17, 2010 1:20 PMv

User-Specific Variable in Web Interface

I have created a manual planning layout with User-Specific variables one for Sale Group and one for Sales District.
The variable successfully restricts user access to data when executed in SAP GUI.
A Web Interface was successfully generated from the Planning Folder containing the manual planning layout described above.
When I execute planning via the web, all possible values are displayed, even though the User-Specific variable limits this user to a single value for each variable.
Is there a way to restore the restriction defined in the User-Specific variable ?
I saw an earlier thread indicating that the Planning Level property of the Selector Variable Value for each variable used in the Web Interface Builder had to be set - but that field is protected from input.
Any insights would be appreciated !
Thanks,
Lyle

Narasimha,
Each variable was created as :
- Replacement Type = User-Defined Values.
- Restriction of Values required by User = OFF.
- Input Allowed by User = OFF.
Several users are defined within each variable.
Most users represent Sales Representatives, with a single value assigned to each a single Sales Rep is assigned a single Group and District ( i.e one-to-one relationship ).
The other type user represents a Sales Manager, and includes all the values assigned to the Sales Reps reporting to him.
When Restriction functionality is turned on, the following error message is received :
Restrict variable UDSALDST (Sales District - User-Defined) (area ZBILLIC (IC Billings Estimate)) to single value
Diagnosis
Variable UDSALDST (Sales District - User-Defined) (planning area ZBILLIC (IC Billings Estimate)) is defined so that the user must restrict the values of the variable (indicator 'Restriction of values required by user' is set). However, you have not defined a restriction.
Procedure
Restrict the variable or change the definition of the variable so that restriction is no longer required.
 To restrict the variable, choose Goto -> Set variables and search for variable UDSALDST (Sales District - User-Defined) in the list. Make the restriction and subsequently continue the planning session.
 To change the variable definition, choose the tab page Variables in the context of planning area ZBILLIC (IC Billings Estimate) and reset the indicator 'Restriction of values required by user'.
While the first option ( Goto > Set Variables ) seems to defeat the purpose of a User-Specific variable, I tried it. When I use F4 to determine available values, it displays those previously assigned when creating the User-Specific variable !? this doe not seem to add any more than I already have.
The second option effectively puts me back to where I was when I posted the question.
Of interest though, I noticed when the Restriction functionality was turned on, the All value previously displayed as available for selection was no longer available but the specific values for each of the other Sales Reps continue to be reflected, and this user can select values related to another Sales Rep..
As mentioned in my original posting,
I saw an earlier thread indicating that the Planning Level property of the Selector Variable Value for each variable used in the Web Interface Builder has to be set but that the field is protected from input.
Should this object property be open to permit input ? If so, is there a step or setting that needs to be performed. Could authorization be an issue ?
Thanks,
Lyle

Layout is it User-specific or Standard ?

I have an ALV report that contains user specific layout and standard layout. My question is if user enters the layout name in the selection screen . i wanted to know whether the layout is user-specific or standard layout.
How we can differentiate this ?
a®

Layouts can be saved for specific users or for all users.
User-specific layouts are only visible to the users who have created them.
Layouts for all users can be selected by all users. These layouts always start with a forward slash in the name (for example, /Standard).
The layouts are report-dependent and you can only create, change or delete them within the display of the respective ALV list. User-specific layouts can only be changed or deleted by the user who created them.
To save layouts for all users, you need the authorization S_ALV_LAYO with activity 23 as of Release 4.6C. You can only go to the layout administration if you have this authorization.
You must maintain the authorization object S_ALV_LAYO using the user administration.
If you would like to use or save the Excel view in your layout, you also require the additional authorization S_BDS_DS with activity 01,02,03,06,30; CLASSNAME ALVLAYOUTTEMPLATES and CLASSTYPE OT.
Furthermore, there are applications that have their own authorization checks installed.
In some ALV lists, you can only save user-specific layouts. In these cases, the indicator "user-specific" is active , on a grey background and unable to be changed. This is related to the parameter I_SAVE. This controls which options you have to save the layout.
To be able to define default layouts, the parameter I_DEFAULT must have the value 'X'.
Notes 409190 and 601803 also provide further information on authorizations.
For further details ..
check saptechies.com
Regards
Manthan.

User Specific catalog UI configuration - Custom catalog user role

Hi all,
We need different user specific layout settings for each user. i have duplicated catalog user role for each user and maintained specific named search for that particular user in constraint. but when we want to configure specific layout for individual user. its not showing that catalog user in the catalog config UI for the layout configuration. please advice. if it shows that specific user then we would configure each specific user layout with individual look and feel ( like shopping lists, search fields, images, etc., ). thanks for your inputs.
Your help would be highly appreciated!!!!!!!!!!!!!

Hi Smartsoft General user,
I guess you are on SRM-MDM Catalog 3.0
We have the same business scenario as yours. Its working perfectly for us.
1. Donot copy Catalog User role. SRM-MDM UI Config only accepts users assigned under std Catalog User role. You dont need mutiple copies of Catalog user role, anyways it wont work.
2. Create multiple webservices for each Named search. Provide one User (like User1, User2...or your own created ones) and one Named Search as following parameters in each webservice.
 http://<your server:port>/SRM-MDM/SRM_MDM
username User<n>
password <password>
server <your server>
repositoryType M ( for Master ) S (for Slave) - Make sure you are pointing to right repo if you have master/slave
catalog <provide Repository name- make sure you are giving right repository name, I provided it wrong first time>
port <your port>
uilanguage SY-LANGU
datalanguage SY-LANGU
mask < keep blank if you want dynamic search>
namedsearch <Provide exact Named search name as you provided in Data Manager>
HOOK_URL
returntarget _parent
If you are creating 5 different Named searches, create 5 different webservice definitions as above.
3. Now for each Catalog user, you can perform separate search UI layout as you wish.
Let me know if this helps or have any questions. If this worked for me, we will make it work for you.
~Pravin

Printing Shop Papers from Maintenance Order Urgent !!!

Hi All,
I am in need of Printing Shop papers from Maintenance order , i know that the configuration of this thing is done through SPRO
Plant Maintenance and customer service ->
Maintenance and Service Processing -> Maintenance and Service Orders -> Print Control -> Define Shop Papers, Forms and Output Programs
, but i want that when we give Print command through Maintenance order a smartfrom should trigger which i have developmed.
My problem is that i am not able to configure the Print control for SMARTFORMS.
What to do , Please suggest.
Regards,
Rachit Khanna

Amol,
Standard config doesnt provide the functionality to set the default selection dependant on PLANT. You will have to get the help of developer to do an implicit enhancement (Only If you are in ECC 6.0) to accomplish the same.
Reagrds
Narasimhan

KOB1 ALV greyed out checkbox "user specific"

Hi Experts,
following problem, in ta KOB1, during saving a layout the "user specific" check box is greyed out.
the outorization object s_alv_layo (act.23) & s_alv_layr are granted to the user profile.
No outorization problem in su53
the oss-notes: 1667238 1818614 are implemented correctly.
any suggestions are welcome
br
Julius

Hi Julius,
Please check SAP note 331416 - CO line item reports: EXIT_SAPLKAEP_009. This will help to find out whether your system has specific coding activated. Point 3 in note is as follows:-
3. All users may change all layout/display variants in the standard setting.You should now change this so that only the user 'THE_BOSS' has the authorization to make changes.All other users should only be allowed to change user-defined variants/layouts.
              Solution:parameter I_SAVE is responsible for the control of the variant/layout maintenance. Its characteristic values are:
a) ' ' = display variants cannot be saved
b) 'X' = standard save, user-specific saving is not possible
c) 'U' = only user-specific saving
d) 'A' = standard and user-specific saving
              In the standard system, I_SAVE = 'A'. You have to set this to 'U' for all users except for 'THE_BOSS'.Also refer to Note 310293 regarding this problem.
if sy-uname ne 'THE_BOSS'.
    i_save = 'U'.
endif.
Regards,
Anand Raichura

Clear BPS user-specific variable values

Hi,
Is there a way to quicly delete all the variable values (user ID and cost center) for a user-specific variable in BPS without access to the configuration (BPS0) or do I need to write a small piece of ABAP for that ?
Thanks
David

Hello David,
You either have to access the BPS0 and delete each of the variable values or write a little ABAP program. You could include this ABAP in a planning function type Exit so the user can press a button in a web interface or planning folder to delete the settings. The coding using internal methods you need is:
DATA:
lr_variable TYPE REF TO cl_sem_variable.
Get variable instance
CALL METHOD cl_sem_variable=>get_instance
EXPORTING
i_area = 'name of area where the variable is defined'
i_variable = 'name of the variable'
RECEIVING
rr_variable = lr_variable
EXCEPTIONS
not_existing = 1
OTHERS = 2.
IF sy-subrc <> 0.
do s.th., eg send a message
EXIT.
ENDIF.
delete the restrictions
CALL METHOD lr_variable->set_user_restriction
EXPORTING
i_user = 'user name, e.g. sy-uname'
i_delete = 'X'
EXCEPTIONS
failed = 1
OTHERS = 2.
Best regards,
Gerd Schoeffl,
SAP NetWeaver RIG BI

User specific settings for message ME161

All SAP Gurus,
Is it possible to have user specific settings for message like ME161?
We want the message ME161 to be displayed as warning message to one user and the same message to be displayed as an erorr message to another user.
Is it possible?
Regards,

hi,
In addition to the above data:
Messages are defined like this:
Version AG No. Text TYPE
Normally, in std case,
Version will be always 00 for system defined messages....
Now if you wanna make the the same message as authorised,
then copy this exsisting message....
While copying system will ask for version, here enter it it Z*
Now on the other hand make the other settings for user/user grp in SU01 and here set the user parameter as MSV(THIS IS MUST)....
and then try...
Regards
Priyanka.P

User-specific break-point

Hi
while debugging whether it is possible to have a user-specific breakpoint??? 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.

Can't save ALV layout as user-specific

Hi!
Whenever I try to save an ALV layout the option User-specific is grayed out, so all variants will be public.
Users would like to save their own layouts safe from other users, as happens with program variants.
First of all then, is there any authorization object related to the User-specific option that my roles are missing?
I read somewhere that 'user-specific' option is controlled by auth. S_ALV_LAYO, ACTVT = 23, yet I have
this auth object with ACTVT = *.
Second, if this option was available, would this let users create their own layouts so that other users don't
overwrite them?
thanks
gracias
xiè xiè

in the resue FM check the I_SAVE which value are you passing:
Value range
' ' = Display variants cannot be saved
Defined display variants (such as delivered display variants) can be selected for presentation regardless of this indicator. However, changes cannot be saved.
'X' = Standard save mode
Display variants can be saved as standard display variants.
Saving display variants as user-specific is not possible.
'U' = User-specific save mode
Display variants can only be saved as user-specific.
'A' = Standard and user-specific save mode
Display variants can be saved both as user-specific and as standard
variants. Users make their choice on the dialog box for saving the
display variant.

No user-specific shop papers are defined

Similar Messages

Maybe you are looking for