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.

Similar Messages

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

User Specific Screen Layout in FB50

Dear Friends,
We are trying to change the sequence of fields in FB50 for a specific user.
Earlier there was an option in to change the screen layout, it was a variant sign on the right hand top side of screen but It is not there in the FB50 screen.
SHD0 does this setting for all the user ?
Is there any way to achieve this for a specific user .
Thanks,
Sapan

Hi Sapan
Mostly it was auth object S_ADMI_FCD with Actiity TCTR for Administrator Function for Table Control Settings
This should resolve hopefully, share the feedback and close the thread incase it does
Br. Ajay M

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 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 Specif Felilds in Routing operation details screen

Hi Techies,
Here I want some information regarding
User Specific feilds:
Here we can have
4 - Text boxes,
2- Value Boxes
2- Quantity Boxes
2-Indicators.
Can any one explain the relevance of these feilds and how can they control the flow..
Thanks in advance
Regards,
Kiran

Hello Kiran,
This user fields are information fields. They don't have any control parametes.Unless you want to influence the process by user exit or any other enhancement, this field are for information only.
The data from this field can be viewed in production order and used in shopfloor docs(print). Orelse the other option was is to use this in confirmation screen(with userexit) for additional information.
Reg
Samson

How to create( end user ) user specific sales order screen ?

Hello Gurus,
We some customer requirement :The pricing condition tab to be disabled for some end users( User specific role ) .can we do this requirement in screen varient or any other methods ?
Looking for your inputs
Thanks and regards
Venkat

Hi,
Correction pls
OSS note 105621
regards,
Siraj

User-Specific Check-box is greyed out in the SAVE LAYOUT popup screen

Hi Experts,
I have created a custom program and used the ALV grid.
In the ALV grid I have included the Layout options menu. (Choose, Select, Save, Manage).
When i try to save the layout, I cannot make it User-Specific. The User-Specific Check box is greyed out.
Please let me know how to enable it.
Appreciate you answers.
Thanks,
Jaffer Ali.S

Did you set the attribute I_SAVE to 'A' ?

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.

Setting user specific contract data while creating sales order using BAPI

Hi all,
I am creating sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2.
Now my problem is that there is no structure for contract data (i.e. VEDA), system automatically set contract data using customization values.
I am doing some validations on cotract data in MV45AFZZ which fails, because these validations are performed on standard values, user specific values r not set.
How to handle this issue, your small clue may help a lot.
Regards,
S@meer

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

How to do a screen sequence for a standard transaction?

Hi experts -
I have a requirement that the business wants a field on transaction VL02N to be grayed out based on specific delivery types. I have been told that that would require a custom screen sequence to be developed.
(1) What is the best solution to accomplish this?
(2) If the solution is a custom screen sequence for the standard transaction code VL02N, then how is that done?
Many thanks!
Mark

When one says "custom screen sequence" an Industry Solution that utilizes BDT, like Insurance or Gas/Oil comes to mind. Are you working with one of the BDT-based Industry Solutions in SAP? If so, customization by field-group or screen or view could be considered, but I think you'd find a much simpler way to do.
If not, one usually does this with an exit that allows control of screen elements, as does SD Order processing, a Badi implementation or enhancement in a PBO module for the screen to set the screen-input value to '0' for that field name.
You should, though, search the forums, since these kinds of questions are often asked....and answered....such as:
[VL0xN exits|VL01N / VL02N Exit;

Transaction SE16: Field selection (User-Specific Settings) is NOT working for ALL tables

Hi Guru’s,
I have an issue in Transaction SE16, Field selection (User-Specific Settings) is NOT working in Tables (ALL tables).
Following is the screenshot attached for your kind reference,
That is in the initial screen of transaction SE16 if I choose Filed Name or Filed Label only the technical details (Field Names) are appearing and not the descriptions like Client, Purchasing Doc, and Company Code Doc. Category Document Type etc…
Right now I am using ECC6 and EHP7 SAP system.
Please help me to resolve this issue by implementing any OSS note or User Role creations or any technical changes required in system.
Hope the requirement is clear and in case need any clarification please revert back.
NOTE: Right now in Development System we don’t have any successful user to compare the settings.
Regards,
Kumar.S

Thanks Patra.
Even I searched in SAP portal and couldn't able to find the relevant OSS note.
Following is my BASIS team response,
"Only you can view Table Field values from higher release"
Can you suggest / guide on this comment as well.
Looking forward to your speedy response.
Regards,
Kumar.S

Strange user-specific display problem

I use my MacBook with an external AG Neovo F-419 19"screen. I have one screen at work and another at home. It works beautifully except for one strange phenomenon: when I log into my account and watch the screen during start up, whereas it starts out having nice even-contrast graphics with a good color range, as the boot progresses it goes through two changes. At the first change the color balance changes, probably reflecting a calibration that I have done in the past kicking in from the Display Preferences info. But then it goes through a second change in which the contrast becomes extreme and the color range perhaps reduced and this then stays and I cannot reverse it by changing the settings in Display Prefs (I can alter the contrast, brightness, color balance etc. but I can't restore the normal color and contrast whatever I do). Bizarrely, however, I can restore things to normal just by rotating the screen and then Reverting to normal orientation.
This is user specific as it doesn't happen if I login as another users and it reappaears when I log back in (andagain gets undone by rotating the screen). It seems not to be a function of a particular Display Profile as I have tried changing them and deleting, ditto for the Prefs file in my User Library. Moreover, the external display does not need to be connected - it happens when I use the Macbook on it's own, which is very annoying because then I cannot rotate the screen to get rid of it!
If anyone has any ideas I would be very grateful as I do not want to transfer thousands of files into a new User account (I should say that I thnk this problem first arose in Tiger when I had another machine and it has migrated along with the User settings!!). Help!!
Andy

Hi,
I think you can only display a maximum message of 128 characters. There is also another function module SCCA_TH_POPUP which also has a message size of max 128 characters.
Danish.

DIfference Between User Exits, Screen Exits, Menu Exits And BADI

Could any one let me know the exact/practical dIfference Between User Exits, Screen Exits, Menu Exits And BADI. ? And why BADIs are more proned to use?

Hi,
User Exits:
A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Menu Exits:
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits:
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
BADIs:
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
And why BADIs are more proned to use?
In contrast to above customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
Regards,
Ferry Lianto

User-specific Selection Variables in Variants

Hi,
I am triing to follow the tutorial in the help.sap.com concerning the variants.
http://help.sap.com/saphelp_47x200/helpdata/en/c0/980386e58611d194cc00a0c94260a5/frameset.htm
I would like to create a User-specific Variables for a variant.
I created set/get param for my report, I also created entries in the user master record. But: In the variants maintenance tool (SE38). First I edit the attributes of my variables and choose the selection variable option for some fields. Second I highlight in green the user specific column stoplight. But clicking F4 doesnt propose any value. Then saving doesnt work neither.
Thank you,
Younes

Umar,
When I click on the button save a modal popup it says "Variables not supplied with values. Save anyway?". I dont know how to supply the variables with values.
With the Function module VARI_USER_VARS_GET I am not able to Read existing variable values. Also in the selection screen of my report the menu Goto -> User variables is not enabled. Maybe I am missing something? Could you help me.
Thanks,
Younes

User- Specific screen sequence in MMR

Similar Messages

Maybe you are looking for