11-16-2007 4:37 AM
11-16-2007 4:59 AM
Hi Karthikayen,
Refer this link:
<u>http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction</u>
Thanks
Vasudha
11-16-2007 4:59 AM
Hi Karthikayen,
Refer this link:
<u>http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction</u>
Thanks
Vasudha
11-16-2007 5:45 AM
Hi
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special sub screen areas on a standard R/3 screen and calling a customer sub screen from the standard screens flow logic.
Implementation of Enhancement in Customer System
First, use the project management function to choose the SAP enhancements that you want and create an enhancement project.
Next, edit your individual components using the project management function and document the entire enhancement project.
Finally, activate the enhancement project (this activates all of the project's component parts).
Start the project management function (transaction CMOD) and give your enhancement project a name. SAP recommends that you think up a naming convention for all of your projects. You can, for example, include the project's transaction or module pool in its name. All enhancement project names must be unique. Next, branch to the project's attributes and enter a short text describing the enhancenent project. The system inserts all of the project's other attributes (such as created by, created on, or status).
Assigning SAP Enhancement to customer projects
Use the project management function (transaction CMOD) to assign SAP enhancements to customer enhancement projects. Enter the names of the SAP enhancements you want to use on the appropriate screen.
The search function gives you a catalog-like overview of existing SAP enhancements. From there you can select those enhancements that are of interest to you.
Editing Components
Activating Enhancement Projects
Use the product management function to edit the components of your enhancement project.
Depending on whether the component you are editing is a function module, a menu entry, or a subscreen, you branch to either the Function Builder, a dialog box for entering menu entries, or to the Screen Painter.
Activation of an enhancement project affects all of its components. After successful activation, the project has the status active.
During activation, all programs, screens, and menus containing components that belong to the project are regenerated (programs at the time they are executed). After activation, you can see the enhancements in your application functions.
The Deactivate function allows you to reset an enhancement project's status to inactive.
Business Transaction Events
It is also called as Open FI enhancement technique which is based on the following principle:
Application developers must define their interface in a function module. An assignment table is read in the corresponding (generated) code, and the customer modules assigned are called dynamically.
This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.
Enhancement Framework
The new enhancement concept of the ABAP Workbench enables the integration of different concepts for modifying and enhancing development objects. The enhancement concept is supported by the Enhancement Builder tool and ABAP language elements.
The objective of the Enhancement Framework is to provide a technology to create modification-free enhancements and to unify all possible ways of modifying or enhancing Repository objects.
Multilayer Support
- In contrast to modifications with enhancements it becomes possible to have
enhancements on different development levels, e.g.
- Core development
- Application development
- Add on development
- Customer development
- It is possible to create multiple enhancement implementations on different layers or
to replace an enhancement implementation.
Enhancement Spots
Enhancement Spots can only be of type source code Enhancement or BAdI.
Enhancement Spots manage explicit Enhancement Options
While implicit enhancement options always exist and do not require any special management, explicit enhancement options created in an initial system must be made known to developers in target systems via Enhancement Spots.
Enhancement Implementations
Enhancement implementations manage their enhancements.
Enhancements made by developers in follow-on systems are managed as Enhancement Implementations. This applies to all enhancement options, both explicit and implicit.
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/user_exits_tutorial.html
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
Edited by: Alvaro Tejada Galindo on Jan 8, 2009 4:07 PM
11-16-2007 5:47 AM
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.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
Refer
http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction
Regards