Define user specific updating event in LIS

Hi everyone,
I'd like to define one specific event for one info structure, like the VC,VD....
Could you please tell me how to realize it?
thanks
Eric

It's not possible and, frankly, I don't see what purpose it would possibly serve. All the events are linked to some SD documents. It's not possible to create a completely new kind of document, therefore there is no need to create a new event.
Perhaps you've misunderstood the requirements and what you need may actually be achieved by using a formula, for example, or a different configuration.

Similar Messages

Defining User specific printer

Hi,
Our client uses barcode printing in process orders. Process orders are printed automatically upon order release and also using COPI they reprint the process order.
Now all the users (* - generic) in the Plant'A' uses Printer 'A'(Output Device) which is configured in spool parameters for users in CB85(config).
Issues:
1. If a user defines Printer'B' as Output device in SU3, the process order still prints in Printer'A'. WHY?
2. The other issue is a some users of Plant'A' moves to a new building, so they want to use Printer'B' instead of Printer'A'.
Since it is configuration, should I maintain Printer'B' as output device in CB85 for each user.
3. I am facing difficulty in maintaining output device for each user in Development system because the user doesnot exist in Development client, the user exists only in Production client.
Please advice whether it is required to create users in DEV & move the changes to production client or is it advisable to maintain the changes directly in production system after opening the system for configuration OR is there any other options available.
Your help is highly appreciated.
Thanks,
UK

Hi Prasbobh,
Thanks for your valuable response.
I changed the value from "02" to "01" of Output device in Printer specification. Now it is taking the the printer which I specify in user profile (SU3), ignoring the printer specified in CB85. It is fine now.
But it is not taking the value of "$" for output device in spool parameter for user, it is throwing an error "entry $ doesn't exist". So I have not changed the value of output device.
Even though it is working fine now just want to check maintaining "01" in printer specification is sufficient.
Thanks & Regards,
UK
Edited by: Karthik on Jun 9, 2010 1:03 PM

[E2013][C#] How to prevent user from updating its own events on Exchange

Hi everybody,
I hope you can help me. I have a system based on Exchange / Outlook 2013, and I would like to put on user's calendar some events that they can't delete nor update. I have tried to create appointments using
Exchange EWS with an administrator account, but the problem is that those events can be deleted or updated by users. This is because the events are on user's own calendar, so usually user can update them.
How can I have "some" events to be readonly for a user, but must be visibile in its own calendar? (No other calendar overlay). Is there a way to throw an exception or something similar on Exchange Server when a user modify those events
(some custom property must identify them, of course)? I have looked at transport agents, but I haven't found any example for managing calendar items server side.
I cannot use only an Outlook plugin because users could connect to exchange with smartphone, and they could update appointments from there. I have to prevent updating (from Outlook and from smartphone, basically from everywhere except for
an administrator user) for some events (programmatically created by EWS, for example) which are in user's calendar. Can you help me?
Thanks,
Antonio

Hi Antonio,
bad news for you: It's impossible. A User always has full control over all items in his or her mailbox (including his calendar), no matter what you do.
If it's important enough to you, you can write a service that monitors all those specific appointments and undos all changes the user applies to them (it won't keep the user from changing the Appointment, but it will not have effect for long. Your users
may feel a bit upset about that though).
Cheers,
Fred
There's no place like 127.0.0.1

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

Notification to defined users for Material master specific field changes

Dear All,
I would like to check the feasibility and way to fulfil the below requirement.
We would like to send notification per mail or Pop UP to the defined users whenever there is a change in particular filed in Material Master (Like MVKE-VMSTA) using MM02 Transaction.
Regards
Krishna Prasad

Hi,
You can create an ABAP query to use tables CDHDR and CDPOS tables.
Select the object values as Materials and make the date range as dynamic in the selection screen.
You can also select the table name and field names.
Based on the output field display selection you can find the person who has changed the objects.
Run the query in the background and in the output device you can put as mail and you can define the destination mail id.
This way, the changes made can be notified to the responsible user.
Regards

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.

Weird thing about when user click Update button

Hi,
I got a very weird thing when i want to add some my code in button "1" on click event. I use below code to capture the on click event when user click "Update" button, so i can do some tasks(assign some fix value to a specific field). I found i can capture the event only once. Once the document is updated and i open second recordl then my code is never exexuted then. No error, no exception. Is anyone know what happen?
Thanks,
Lan

Hi All,
Yes, you are right. After i use try block, i can see the error. I thought I should be expected an red exception alert in the B1 info bar.
Thank you !
Lan

Conflict between Client object model and Item Updated Event Receiver in sharepoint 2010

Hello All,
As per my requirement I have a two custom list.
Agent Details
Port Name
Agent Details contains Agent code, Port Name, email, address and phone of Agent. Its possible that one Agent Code is connected with multiple Port Name.
Basically what I am doing is I am getting port name connected with Agent code, using jquery and bind those values with check box(using javascript created dynamically) and bind all with Div tag.
Now when my custom edit form of Agent list open up it shows me different port name binding with checkbox group.
when user select the check box and click confirm button my clicent object model script will run and add this selected value into Port Name list.
After confirm one more button named Save will enable asking user to edit the email, phone or address value and when I click on save my Item updated event fires which update the values of the selected port name(These port name I am getting from port
name list) to Agent Details custom list.
Now when I am trying to update the values my event receiver fires or some times it got stuck(not firing). So could you please help me the possible alternative for this requirements.
Can we user the Ecma Script(Client object model to preserve the value of selectec port) and Item updated event receiver on the same time?
Is anything am doing wrong then please guide me.

Hi,
As I understand, when you updated values in the agent details list the Item updated event receiver got stuck sometimes.
The item update event receiver will fire after the item has been saved, and the client object model script or the Ecma Script runs before the item is saved, so there is no conflict between the client object model script and item update event receiver.
You could find out the reason about the item update event receiver gets stuck by debugging the event receiver.
When you want to debug your event receivers, you have to attach to OWSTIMER.EXE and wait till they are executed. You can control this behavior using the Synchronization attribute. Also, if you’re looking for an easy way to debug an event receiver without
having to manually attach a debugger to your code, you can use the System.Diagnostics.Debugger.Launch() method.
The articles below are about how to debug in the event receiver in SharePoint 2010.
http://sharepoint-kings.blogspot.jp/2013/02/debugging-event-receivers-in-sharepoint.html
http://chakkaradeep.com/index.php/event-receivers-in-sharepoint-2010/
http://sharesaint.com/?p=77
Best regards,
Sara Fan
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Cache Insert for an already existing key is firing two update events

Using an INamedCache I perform an insert to update the values of my item that is already in the cache. I have listeners on the cache, in particular I have a DelegatingCacheListener that listens on EntryUpdated.
On doing this insert once (and only once, I think!) my update event handler gets invoked twice. I have put breakpoints in all conceivable places that might raise this event, do an insert or update this key but it only ever hits my insertion point once.
I have looked at the args of the event and seen that on the first invocation my old value is A and new value is B. For the second invocation my old value is B and New value is C. The second invocation new value object is only different by a single member which is a time value that I set and this difference is only a second. This kind of implies that somehow my own application/code is inserting twice into the cache for the same key/value.
Has anyone seen this symptom before?
Is there somehow that I can see what is inserting into the cache?
Let me know if I can provide more information to help.
Edited by: Kunal on Feb 9, 2011 8:08 PM
Changed the title grammar

Hi Kunal -
First, just to narrow this down, it appears that your code is running in .NET. Is there other logic deployed as part of this application, e.g. application logic on the server side (the "back end") that might be doing something? This would include anything from the incubator (e.g. push replication).
Second, what does your listener do when it receives the event?
Third, are there other listeners for the event that may be doing something when the first change appears?
The event originates from within the cluster, from the server that "owns" the specific piece of data that your are inserting, so unless the value is changing there twice, you should not get two events. I would start by tracking down all of the places that change the time value, since you can see that is the value that is being changed.
Peace,
Cameron Purdy | Oracle Coherence
http://coherence.oracle.com/

Credit memo value Is not updating in a LIS

Hi All,
My Problem Is O am Creating a credit memo by using the billing Document Directly, with out using any return order,Return delivery. When I am seeing in the LIS Its not showing the Actual Credit memo Value for that customer its showing Zero value. I have done all the Settings for LIS.Pls Let me know is there any specific Setting in the LIS for getting the credit memo value in LIS Report.
Thanks in advance.
Regards
satya.

Check with transaction code 'MCVV' as to which all info-structures are being updated.
Check the stats groups are correctly assigned to the sales document, header, item and the billing document is Relevant to Statistics
Also, download this document for complete understanding of LIS.
Regards,
Gauravjit.
Reward points if the solution helps.<a href="http://www.sapfinancialsexpert.com/downloads/11-02.doc">LIS set-up</a>

User- Specific screen sequence in MMR

Hi
I need to create a User-specific screens in Material master record.That is for one user the basic data 1 should be there and for the other user it has to be blocked i.e he should not do any changes to that field.
Kindly suggest me a solution ..........
Regards
Siva

Hi
You can achieve it by following configuration steps in SPRO
1.Define Structure of Data Screens for Each Screen Sequence
2.Assign Secondary Screens
3.Maintain Order of Main and Additional Screens
4,Assign Screen Sequences to User/Material Type/Transaction/Industry Sector.
5.Maintain User Settings
Custamization path for the above configuration in SPRO is
Implementation Guide for R/3 Customizing (IMG)> Logistics - General>Material Master-->Configuring the Material Master
Please let me know if you need further inputs.

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 - User specific - this needs to be unchecked.

Dear friends,
We have created a Layout in the Report. By default, User-specific tick is coming while saving the Layout. Others are not able to select this report. How to uncheck this tick ??
Regards
KVKR

It is most definitely an authorization issue. You, like any security auth issue, should be able to type in /NSU53 and see what authorization objects you have and which ones were checked that failed. That should give you the auth object/value you need to maintain global display variants. Please note though that a lot of companies lock this down heavily as having this access not only gives you the ability to create new variants but also update other global layouts and change the default settings.
From what I have typically seen IT has the global display authorizations and per the user requests creates them and makes them available for others. Where this isn't in place I've seen the global layouts get all out of whack and we got many phone calls saying "this never used to look this way before so fix it!"
Check out OSS Note 409190 but in summary "There is the authorization object S_ALV_LAYO with the authorization field 'ACTVT' (activity) and the value '23' for "Maintain".All ALV versions (Classic, Grid Control and Grid in fullscreen) perform an authorization check against this object.Users whose profile contains the value '23' are then allowed to create and maintain standard layouts and save them as defaults.
The authorization object can be checked via transaction SU21, object class BC_Z, S_ALV_LAYO and only exists from Release 46C."
Hope that helps.

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.

Layout which is not user specific

Hello All,
Can I save a layout as a default layout for all my users. Actually its not my code its the output of std report RCS15001. I want to save my layout as not user-specific but the checkbox is greyed.Kindly help me out.
Thanks in advance,
Regards,
Anju

ok..then go for user-exits...
Enhancement/ Business Add-in            Description
Enhancement
PCSD0013                                Customer-specific processing of an explosion for BOM browser
PCSD0012                                Customer - Mat. number/mat. number during material exchange
PCSD0011                                Knowledge-based order BOM, parallel update
PCSD0010                                Order/WBS BOM, determine explosion date
PCSD0009                                Order/WBS BOM, determine URL page
PCSD0008                                WBS BOM: Customer-specific explosion for creating
PCSD0007                                Check changes in STKO
PCSD0001                                Applications development R/3 BOMS
PCSD0002                                BOMs: Customer fields in item
PCSD0003                                BOMs: Customer fields in header
PCSD0004                                BOM comparison
PCSD0005                                BOMs: component check for material items
PCSD0006                                Mass changes user exit
Business Add-in
BOM_EXIT                                BOM User Exit
BOM_IPPE                                iPPE Checks Within BOM Maintenance
BOM_UPDATE                              Maintain BOMS
CEWB_BOM_CUS_FIELDS                     EWB: Customer Fields with BOM Header (Screen Enhancement)
CEWB_BOM_UPDATE                         Check Bill of Material on Saving
CEWB_ITM_CUS_FIELDS                     EWB: Customer Fields with BOM Item (Screen Enhancement)
No.of Exits:         13
No.of BADis:          6

Define user specific updating event in LIS

Similar Messages

Maybe you are looking for