Info on Screen-exits

hi ,
Can anybody explain me screen & menu exits
Regards,
N Manjrekar

Hi Nikhil,
Refer to the followign links.
http://www.sap-img.com/abap/what-is-user-exits.htm
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Regards,
Priyanka.

Similar Messages

Screen Exit for ME11 (purchasing info record)

Hi,
Please let me know, do we have screen exit for ME11 transaction to add custom fields.
Or
Do we have any other possibilty or solution to add custom fields to ME11 transaction.
Please suggest.
Thanks for quick reply.
Surya

Hi,
Check below link.....
BAPI for transaction ME11 and ME12
Thanks,
Asit Purbey.

Screen exits in HUPAST

Dear All,
I want to add an extra screen in HUPAST main screen which would let you insert the batch number or serial number for each product using a z table.
pls tell me the method & steps to do the above task.
I want to work on screen exit in HUPAST. Does any one know the existing screen exit in HUPAST.
Thanxs

Hi Sanjeev:
How are you ? I have the same requirement to insert serial no. info. into the screen of hupast.
The badi you used-BADI_HU_PACKING_ALWD ,i have tried. But I don't know you said-Z module
pool program you designed. Can you give me more details.
Thanks~~

Screen exits/BADIs available for Tcode-QM02/QM03

Hi Everyone,
                   I have to modify a screen for Tcode-QM02( 'Checklist' tab) and add a drop down field to it.I have not worked on screen exits/BADIs prior to this please let me know how to proceed with this.
      Alsoplease tell me how can I manually go and check out whether a exit or BADI is available for this transaction?
Please reply as its a bit urgent.
Thanks and Regards
Abhishek

hi,
check these exits n badi's.
Transaction Code - QM02                     Change quality notification
Enhancement/ Business Add-in            Description
Enhancement
IWOC0004                                Change single-level list editing PM/QM/SM ALV settings
IWOC0003                                PM/SM authorization check of ref. object and planner group
IWOC0002                                PM/SM notification: Check whether status change is allowed
IWOC0001                                Create PM/SM notification: Determine reference object
IWO10027                                User exit: Generate user-defined settlement rule
IWO10026                                User check on setting status 'Do not perform'
Business Add-in
IQS0_STATUS_MAINTAIN                    Control of Changeability of User Status
IWO1_SUBSCREEN_0170                     Display Additional Data on Object Screen 0170 PhysicalSample
IWOC_LIST_TUNING                        Performance Tuning for Lists in PM/CS
IWOC_OBJECTINFO_CHNG                    Changes to Data of Object Info Screen
WOC_FL_DETERMINE                        Determine Date for Determining Installation Loc. Equi.
NOTIF_AUTHORITY_01                      Additional Authorization Checks for the Notification
goto system - status of ur transaction and find porogram name
then goto attributes of program n find package.
now goto smod or se18 click f4 click information system u will get all exits or badis available.

Screen exit example step by step

screen exit example step by step need.

hI
REWARD IF USEFULL
User Exits in FI/CO
by Tami Becker, SAP Platinum Consultant, SAP America, Inc.
Overview
R/3 provides three "customization spots" that allow you to enhance FI/CO features without modifying the standard code. Although often collectively referred to as "user exits," two of the three have different names. SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. Enhancements were new in release 3.0.
The Open FI Interfaces or Business Transaction Events are also used to expand the standard functionality within SAP. These events are defined in the IMG. Business Transaction Events were new in release 4.0. They are not available for all modules and are not called on all integrated transactions into FI as of release 4.5B. This will change with each release and should be retested.
The older User Exits in FI/CO are "Z" programs that are defined in table T80D for client-dependent user exits, and in table T80I for client-independent user exits. These are also used to expand the standard functionality within the FI/CO modules. These User Exits have been available since the early releases of SAP. All of these FI/CO User Exits are listed in this document in the Configuring User Exits (Older). The list is included because these User Exits are not a part of the Enhancements or Business Transaction Events and do not have an Info System for searching.
Benefits
     Standard SAP functionality can be enhanced without modification to the standard code.
     Upgrades do not erase the functionality and it does not have to be re-transported or re-entered into the system. The enhancements should be thoroughly tested when upgrading to ensure the system will still work as implemented.
Configuring SAP Enhancements
Basic Steps in Configuring an Enhancement
     Find the appropriate Enhancement.
     Enter the ABAP code in the "Z" program within the function module.
     Create a project.
     Add the Enhancement to the project.
     Activate the project.
Example Business Scenario for Enhancements
Company A has a requirement to validate all customer master records created with a U.S. address. The U.S. entity reports on the industry field on the customer master. This is only a U.S. requirement and should not be required for the other countries, so the field status would not work. To accomplish this requirement, Company A will need to set up an Enhancement for the customer master transaction. The necessary steps are detailed below with screenprints. This example was configured in a 4.6C system.
Detailed Steps
1.     Tools   ABAP Workbench   Utilities   Enhancements   Definition   Utilities   List Enhancements
2.     Do not execute this without any parameters! There are too many Enhancements and it will probably time out. Youre searching for a customer master exit. Enter mast in the short text (see Figure 1). Youll start there. Searching for an exit can be tricky, so make sure you try several things before giving up.
3.     Execute the search.
Figure 1. Start Your Search for a Master Exit Here
4.     Look through the list until you find the Enhancement for User exits: Customer Master Data.
5.     Double-click on the enhancement SAPMF02D. This will take you to the details of the Enhancement and list the function modules included in the Enhancement.
6.     To continue, double-click on the function module EXIT_SAPMF02D_001
7.     This will take you to the source code for the function module. Click on the Import tab to review the tables/fields that are available for the Enhancement (see Figure 2).
Figure 2. The Tables That Are Available for the Enhancement
8.     To view the tables/fields that can be changed in the function module, click on the Export and Changing tabs. For this function module, these tabs are empty because you can only validate data. You cannot change any fields in this enhancement.
9.     Return to the Source Code tab.
10.     Scroll down until you see the Include statement in the program. The "Z" program listed after the Include is where your code will be written (see Figure 3).
Figure 3. Your Program Will Begin After the Include Statement
11.      Double-click on the Include. You will be prompted to create the include. Click on Yes to create.
12.      At this point you will be prompted to enter a development class and to create a transport request. If you do not know which development class to use, please contact your technical team.
13.     Enter the following ABAP code into the program (Figure 4):
User exit to ensure that all US customers have a group key
entered on the customer master.
if i_kna1-land1 = 'US' and
i_kna1-brsch = ' '.
message e001(F2).
endif.
Figure 4. The ABAP Code You Need to Enter
14.      Note that the table name matches the table name in the import tab tables.
15.      In this example you are using the standard message class F2 with message number 001. Normally, you will create your own message within your own message class. All customer message classes must begin with a "Z" and are created in transaction SE91.
16.     Save the program.
17.     The next step is to create the project. Go to transaction code CMOD or follow menu path: Tools   ABAP Workbench   Utilities   Enhancements   Project Management.
18.     Enter the project name; begin the name with a "Z."
19.     Click on the Create button.
Figure 5. Click on Create After You Type in the Project Name
20.      Enter in a description for the project.
21.      Click on the Enhancement Assignments button.
22.      You will be prompted to save the enhancement. Click on Yes.
23.      At this point you will be asked for a development class and to create a transport for the project. You may use the same one created when adding the ABAP code to the function module.
24.     Enter the name of the enhancement SAPMF02D (see Figure 6).
Figure 6. Enter the Name of the Enhancement Here
25.     Save the project.
26.     Back out of the enhancement assignment.
27.     Activate the project by hitting the Activate button.
The SAP Enhancement is ready to be tested! Try creating a customer with U.S. as the country and a blank group key. Be sure to test one with a group key to make sure the message is not displayed in error as well.
Configuring Business Transaction Events
Basic Steps in Configuring an Event
     Make sure the application is active for Business Transaction Events.
     Copy the sample interface function module into a "Z" function module.
     Enter the ABAP code into the source code section of the new "Z" function module. You may choose to create a "Z" program to enter the code into and then insert the "Z" program into your function module source code.
     Activate the function module.
     Assign the function module to the event, country and application.
Example Business Scenario for Business Transaction Events
Company A would like to copy the group key field from the vendor master into the allocation field on all the line items within a vendor invoice and payments, including the vendor lines. This requirement assumes only one vendor is posted to in a document.
To accomplish this requirement, Company A will use the Business Transaction Event 1130, Post Document: SAP Internal Field Substitution.
1.     IMG Menu Path: Financial Accounting   Financial Accounting Global Settings   Use Business Transaction Events   Environment   Infosystem (Processes).
2.     Find the correct Business Event. You are updating a field, so you select the Processes Info System instead of the Publish and Subscribe Info System.
3.     Execute the search with the defaults.
4.     Find the correct interface for updating a document: Post Document: SAP- Internal Field Substitution (see Figure 7).
Figure 7. Find the Correct Interface for the Business Event
5.     Put your cursor on the event and click on the Sample Function Module button.
6.     You are now in transaction SE37 Function Builder. This is the function module (sample_process_00001130) you will need to copy into a "Z" name function module for your coding (see Figure 8).
Figure 8. This Is the Function Module You Need to Copy Your "Z" Name Function Module
7.     Click on the Copy button.
8.     Enter the "Z" function module name in the To Function Module field (see Figure 9).
9.     Enter a Function Group. If you need to create a "Z" function group, go to transaction code SE37 and follow menu path: Go to   Function Groups   Create Group. A function group is a logical grouping of function modules, and the ABAP code is generated for function groups. You will be prompted for a development class and transport when creating the function group.
Figure 9. Enter Your "Z" Function Module Name Here
10.     In Function Builder (transaction SE37), enter the new "Z" function module. Click on the Change button.
11.     The system will default into the source code screen where you may enter your ABAP code.
12.     Notice the tables available for the code. Additional tables may be declared if necessary.
13.     Enter the following source code (see Figure 10):
tables: lfa1.
data: z_groupkey like lfa1-konzs.
z_groupkey = ' '.
loop at t_bseg.
check for vendor lines. If one is found, read the vendor master and
retrieve the group key field.
if t_bseg-koart eq 'K'.
select single konzs from lfa1 into z_groupkey
    where lifnr = t_bseg-lifnr.
endif.
Move the group key field into all line items allocation field.
loop at t_bsegsub.
t_bsegsub-zuonr = z_groupkey.
modify t_bsegsub index sy-tabix.
endloop. "t_bsegsub
endloop. "t_bseg
Figure 10. The Screen Where You Enter Your Source Code
14.     Save the function module.
15.     Back out to the main Function Builder screen by clicking on the green arrow button.
16.     Activate the function module by clicking on the Activate button (see Figure 11).
Figure 11. Activate the Function Module from This Screen
17.     Assign the function module to the event in the IMG: Financial Accounting   Financial Accounting Global Settings   Business Transaction Events   Settings   Process Function Modules   of an SAP Appl.
18.     Hit enter past the warning messages that this is SAP data.
19.     Click on the New Entries button.
20.     Enter the process for your interface. In your example it is 00001130.
21.     Enter the country the interface is valid for. If it is valid for all countries, leave this field blank.
22.     Enter the application the interface should be called for. If it should be called for all applications, leave this field blank. Please note that not all integrated transactions are programmed to go through these interfaces! You will need to test to find out!
23.     Enter the new "Z" function module (see Figure 12).
Figure 12. Enter Your New "Z" Function Module Here
24.     Save the settings. At this point you will be prompted for a CTS number for the configuration change.
25.     The Business Transaction Event is complete! You are ready for testing.
Configuring User Exits (Older)
Basic Steps in Configuring an User Exit
     Create a "Z" program for the User Exits and enter the necessary ABAP code.
     Enter the new program name into table T80D.
     Configure the application to call the User Exit.
List of User Exits
     Variable Field Movements
     Substitutions in FI, CO, PCA
     Validations in FI, CO, PCA
     Rollups in SPL
     Fixed Field Movements in SPL
     Cost Center Summarization on Detail Screen
     Sets Formula Variables
Example Business Scenario for User Exits
Company A would like to add a "Z" field in the Special Purpose Ledger to capture a Business Unit field for reporting. They have used all the standard SAP fields such as Business Area and Profit Center. The field will only be used for reporting and is only needed in the Special Purpose Ledger. You created a special ledger table (ZZSPL1) with field Z_BUNIT and need to populate this field based on a combination of G/L account, fund and functional area.
To accomplish this requirement, Company A will use the Variable Field Movement User Exit. To make maintenance easier, table ZZBUSUNIT was created with the G/L account, fund and functional area fields as key fields, and the business unit field as a non-key field. You generated the table maintenance so the table could be updated using transaction SM30. SAP users update the business unit determination rules in table ZZBUSUNIT by entering the G/L account, fund and functional area, and then the business unit that combination should be posting to. The User Exit will read table ZZBUSUNIT using the G/L account, fund and functional area from the posting transaction and determine the business unit. The steps for using the user exit are detailed below. This example was created on a 4.6C system.
1.     Copy the delivered template User Exit program RGIVU000_TEMPLATE into a "Z" program. Follow menu path Tools   ABAP Workbench   Development   ABAP Editor (transaction code SE38). In early releases, the delivered program was RGIVU000.
2.     You will be prompted for a development class and a transport. Please check with the technical team for the correct development class.
3.     At the initial ABAP Editor screen, enter your new "Z" program name, select the Source Code button and click on Change (see Figure 13).
Figure 13. To Enter Your New Code, Select Source Code and Click on the Change Button
4.     Enter the following code in the User Exit (Figure 14):
FORM E01_MVC USING FROM_FIELD TO_FIELD.
to_field = 'CORP'. "Set a default business unit.
read table zzbusunit to determine the business unit field.
select single z_bunit from zzbusunit into to_field
   where hkont = accit_glx-hkont and
    geber = accit_glx-geber and
    fkber = accit_glx-fkber.
ENDFORM.
Figure 14. Enter Your New Code at This Screen.
5.     Activate the program by clicking on the Activate button.
6.     Change the configuration in the User Exit table to point to your new "Z" program.
7.     Follow the IMG menu path: Financial Accounting   Special Purpose Ledger   Basic Settings   User Exits   Maintain Client Specific User Exits.
8.     The entry to maintain is application area GIMV: Variable Field Movement. Enter your "Z" program (see Figure 15).
Figure 15. Enter Your "Z" Program in the Application Area GIMV: Variable Field Movement
9.     Save the changes.
10.     The final configuration step is to assign the User Exit in the variable field movement for your special ledger table. In the IMG: Financial Accounting  Special Purpose Ledger  Basic Settings  Master Data  Maintain Field Movements. Field movements control how the fields in a special ledger table are populated. They can be populated straight from other fields in a posting or through User Exits.
Figure 16. After You Assign the Business Unit Field and the G/L Account, the Exit Field Should Contain U01.
11.     Assign the business unit field as a receiver and the G/L account as the sender. The Exit field should contain U01 (see Figure 16).
12.     The User Exit number U01 calls User Exit E01_MVC form in the "Z" program.
13.     Save the field movement.
14.     You are ready to test your User Exit!

Urgent - screen exits

HI ,
in miro transaction while posting document ,whenever we select g/l account in next screen instead of assignment field data we need to put corresponding po data
HOw can i do this?
reg

hi
here r the ways to find out the screen exits for a tcode
1. go to the transaction you are workin on.
2. go to system --> status and there you'l find your package name.
3. now go to SE81 --> info systems --> enhancements --> customer exits --> enhancements and give your package name there.
now you'l get your screen exit here.
or
Finding the Exits of a TCode:
1) Goto Program of Tcode and get the Package of that program.
2) Now go to SMOD(TCode) in enhancements press f4.
3) now click on information and give the package u will find all the enhancements. Check the component of enhancement where u will find the function Module of exits.
If u find it useful mark the points
SIRI

Screen exit for cj02

hi all,
i am working on screen exit,i have enhancements related to that are CNEX0007 and CNEX0006.
i need to add a field in the screen 900 which is include wbs elements which comes when we press include wbs button in the hierarchy graphic.how can i get this,please let me know...

Hi Anil,
Screen Exits for Tcode CJ02
SAPLCJWB0205_CUSTSCR1_SAPZSAMPRJ
SAPLCJWB1215_CUSTSCR1_SAP
hopefully this info will be helpful for u
Regards
Karan Arya

Screen Exit Custom Tab Title Change

I have enabled the screen exit PPCO0012 ( Production Order CO03, CO02, CO01 ) custom tab for additional fields. After enabling the screen
SAPLCOKO1 0900 SSCR115 SAPLXCO1 0100
I am getting the custom tab.
But it showing the tab title as "Customer Screen" I wanted to change to my own name.
How ? any info ?
a®

Resolved.
We need to change in under menu exit
SAPLCOCU +COI
a®

Enhancement - Screen exit

Hi All,
Requirement is to add couple of fields in Standard transaction.
Please let me know the steps of finding the Exit and development steps.
Thanks in advance.
Ravi

Hai Ravi
User Exits
Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data.
It is determined be SAP where the sub screen will be displayed.
The syntax is: CALL CUSTOMER-SUBSCREEN
The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project,
and the project has been activated.
Note:
Function codes are only processed in the main screens flow logic
You are not allowed to enter a name for the subscreens command field
You are not allowed to define GUI stauses
You are not allowed to enter a value for Next screen
The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules.
These function modules belongs to the same function group as the subscreen Subscreens are edited with transaction CMOD.
When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next
time you display the calling screen
The developer must create the subscreen and the corresponding PBO and PAI modules
How to identify screen exits
Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify.
Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits
MENU EXITS
Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu
entries in the GUI interface. The developer can add his/her own text and logic for the menu.
Function codes for menu exits all start with "+"
Example
We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will
run report ZTEST.
Goto transaction SE43 Area Menu Maintenance
In Area Menu Paramenter type 'S000' (S triple Zero)
Select Change and ignore all the warning screens
Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"
Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01
Goto transaction SE93 and create transaction +C01 that calls report ZTEST.
Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.
USER EXITS
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen by the developer. You are not writing the code directly in the function module,
but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is: EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as: CALL CUSTOMER.-FUNCTION <3 digit suffix>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
2. How to find user exits
Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.
Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.
3. Using Project management of SAP Enhancements
We want to create a project to enahance trasnaction VA01
Go to transaction CMOD
Create a project called ZVA01
Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only
be used i 1 project. If the enhancement is allready in use, and error message will be displayed
Press Save
Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155"
Have look at this links
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf
http://www.sapgenie.com/abap/ole.htm
http://help.sap.com/saphelp_46c/helpdata/en/59/ae3f2e488f11d189490000e829fbbd/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf
User Exist Finding
Go to se93 and give the tcode to find the main program associated to it.
Go to se38 and give the main program.
Find the package associated to it.Go to->Object Directory Entry.
Go to smod transaction.
Press f4.
Press Information System Button.
Give the Project(Dev Class).
Press enter.
Find the enhancements associated
User Exist System Tables
1. MODSAP & MODSAPT is the table.
2. Where we can give the enhancement name.
3. Component type will be E
for getting the FMs.
E Function exit
S Screens
T Tables
C GUI code
Field Exist Creation
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
- Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
- An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press F1 for field-level help.
Click on the Technical info pushbutton (or press F9) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
- The transaction to create field exits is CMOD.
- You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
- From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
- After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
- From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
- After choosing this menu path, a dialog box will prompt you for the appropriate data element .
- Enter the data element name and click the Continue pushbutton.
- Now, you will be able to create the function module associated to the data elements field exit.
Step 4: Create Function Module
- You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the Continue pushbutton.
- In the Function module field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
- You can add an identifier (an underscore followed by a single character ).
- The first function module for a data elements field exit must be created without an identifier.
- To create the function module, click on the Create pushbutton, choose menu path Function module -> Create, or press F5.
- After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing Enter, you will be able to go ahead and create the function module.
- Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
- From the function modules attributes screen, click on the Source code pushbutton or choose the Goto -> Function module menu path to the code of the function module.
- Here you will add your desired functionality for the field exit.
- Remember that field exits function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
- You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
- After coding the function module, you must remember to activate it.
- Use the Function module -> Activate menu path to activate the function module.
- At this point, you can return to the field exit transaction.
- You should be able to 'green arrow' back to this transaction.
- When you return to the field exit transaction, you will see an entry for the newly created field exit.
- At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
- Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
- This step is only needed if you want to make a field exit local.
- To make a field exit local, select the field exit and click on the Assign prog./screen pushbutton.
- In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
- In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the Fld. Exit field.
- If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
- If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
- The field exit must be active for it to be triggered by the system.
- Activate the field exit by choosing the Field exit -> Activate menu path.
- After assigning the field exit to a change request, its status will change to Active and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Thanks & regards
Sreenivasulu P

Runtime error in MIRO while using User/Screen exit

Hello,
I have implemented an exit in ABAP for MIRO which when transported to Quality server through runtime error.
I have used EXIT (SMOD) : LFDCB001 which contains FM -> EXIT_SAPLFDCB_001 and include -> ZXM08U31. In this exit I have written my code to disable Inv. Party field. This field exist in Details Tab in Miro Transaction.
Location of the field: MIRO -> Details (tab) -> Inv. Party (Field)
Code written in include ZXM08U31 is:
LOOP AT SCREEN.
IF screen-name = 'INVFO-LIFRE'.
    screen-input = 0.
    MODIFY SCREEN.
ENDIF.
ENDLOOP.
This exit is assigned to a project in CMOD and I tested the same in Development system. It is working perfectly.
Now I transported the TR (Includes program ZXM08U31 and Customer enhancement projects ZMIRO). Now when I run MIRO in quality server it triggers the my logic and then through runtime error.
Runtime error says:
Short text
    Dynpro does not exist
Error analysis
    The system attempted to use dynpro 0400 in program "SAPLXM08".
    This dynpro does not exist.
I agree that screen 400 does not exists in program for MIRO but it does not exists in development system as well. So if the runtime error is valid in QEC server then why not in DEV server. And when it can run successfully in DEV server why cant it run in QEC server.
Hope I have explained all the things in detail.
Please provide me the solution since user can bombard anytime for the MIRO dump everytime in QEC.
Regards,
Harjeet Grover

Hi Harjeet,
Reason of your Dump is that the enhancement "LFDCB001" which you used contains one Function module exit "EXIT_SAPLFDCB_001" and another one screen exit in calling screen "SAPLFDCB" number 0150.
So when you activate your project these above mentioned both components were activated.
So when you execute transaction SAP looks for called screen "SAPLXM08" No-0400 but as you havn't created and program go for DUMP.
Solution - Just Create called screen "SAPLXM08" No-0400 and activate.
Thanks,
Vijay

How to find out a screen exit

hi seniors
can any one tell me abt screen exit n thier search.
pls hurry
points will be rewarded
offer valid for today only.
Sameer

hi,
How to Find a Screen Exit in a Given SAP Standard T-code
Program
REPORT YSMOD2 .
TABLES: MODSAP, MODACT, TSTC.
PARAMETERS: INPUT1 LIKE TSTC-TCODE DEFAULT ' ',
            INPUT2 LIKE MODSAP-TYP DEFAULT ' '.
DATA: SEARCH1(6),
      SEARCH2(3),
      SEARCH3 LIKE MODSAP-MEMBER.
DATA : FIRST_ROW VALUE 'Y'.
CONCATENATE: '%' INPUT1 '%' INTO SEARCH1,
'%' INPUT2 INTO SEARCH2.
SELECT * FROM TSTC WHERE TCODE LIKE SEARCH1.
FIRST_ROW = 'Y'.
CHECK TSTC-PGMNA NE SPACE.
CONCATENATE '%' TSTC-PGMNA '%' INTO SEARCH3.
SELECT * FROM MODSAP WHERE TYP LIKE SEARCH2
AND MEMBER LIKE SEARCH3.
SELECT SINGLE * FROM MODACT WHERE MEMBER = MODSAP-NAME.
IF FIRST_ROW EQ 'Y'.
   WRITE: /0 TSTC-TCODE, 6 TSTC-PGMNA, 16 MODSAP-NAME, 32 MODSAP-TYP,
          45 MODSAP-MEMBER, 70 MODACT-NAME.
   FIRST_ROW = 'N'.
ELSE.
   WRITE: /16 MODSAP-NAME, 32 MODSAP-TYP, 45 MODSAP-MEMBER, 70 MODACT-NAME.
ENDIF.
CLEAR : MODSAP, MODACT.
ENDSELECT.
IF SY-SUBRC NE 0.
   WRITE : /0 TSTC-TCODE, 6 TSTC-PGMNA, 30 'No exits found'.
ENDIF.
CLEAR TSTC.
ENDSELECT.
END-OF-SELECTION.
CLEAR: SEARCH1, SEARCH2, SEARCH3.
Regards
Sudheer

Creation of sales order- screen exit

Hi all,
I have a requirement like while creation of sales order need to develop one screen field in additional data B.i developed that field. and now while creation of sales order it will save in vbak table. now the problem is that screen field will be enable in that particular sales order type only otherwise it will be disable. how to do this. screen exit.

Hi
See SAP Note 209278 - Display of customer-specific fields in sales doc
Check also, SAP Note 302497 - Additional cust. fields not displayed in 'Additional data B' and SAP Note 386694 - Additional data not displayed in screen 8459 and 8309
Regards
Eduardo

Screen-exit for profit center creation - transaction KE51.

Hi All,
Background: The client has the requirement of importing profit centre master data from legacy system into SAP ECC system. Few of the legacy data could not be filled into existing sap fields, hence the requirement has been to populate the data into custom fields.
The client also has the requirement, that the same fields are required during online entry. For this we need to enhance the profit centre creation screen (transaction code KE51) with two additional custom fields.
Requirement: To enhance profit centre creation screen with custom fields. Screen-exit for KE51 transaction.
Pre-work: Program SAPLRKPM in SAP ECC system is the main program. It does not have any screen or sub screen area for custom fields addition. Debugged the program to check for screen-exits, found none.
Below user-exits are not either screen-exits or cannot be used for enhancing profit center screen.
PCA00001 EC-PCA: Document changes for data transfer
PCA00002 Profit Center Accounting: derivation of representative mat.
PCA00003 Derive Partner Profit Center for External Deliveries
PCA00004 Check valuation for invoice verification with transfer price
PCA00005 Check valuation for invoice verification with transfer price
PCASELEK EC-PCA: Selection criteria for data transfer
Solution required for: Could anyone please let me know if it is possible to enhance the profit center creation screen. If yes, please provide the names of the screen-exit/ badi exit.
(Just a thought, modifying the standard seems to be the only solution, this should be the last option and i agree, please provide your inputs.)
Thanks in advance.
Warm Regards,
Goutham.

Thank you Manohar for the response.
The requirement is to display custom fields on standard sap screen and there are no screen-exits. So, i suppose the standard screen has to be modified.
Could you please provide brief explanation on
May be you should consider maintaining custom mapping table instead of going for chaning standard.
With Regards,
Goutham.

Screen exit/BADI for adding custom field in IW31/IW32

Hi all,
The requirement is to add the permit field in the Header component of IW31. Searched SDN and found user exit IWO10018 for the same which includes a screen exit.
The activation of the same is adding a tab in the screen while user wants the field under header Component tab.
How this can be done. Any suggestion.
Thanks
anya

Hi,
You can perform append structure to add your custom field(s)in VBAP table. Next step, go to SE51 (Screen Painter)to modify SAP Program SAPMV45A Screen number 4459 for Additional data A or Screen number 8459 for Additional data B to add your append structure custom fields.
Once the above steps done, you can place your logic to populate custom fields in include program MV45AFZZ. i.e USEREXIT_MOVE_FIELD_TO_VBAP.
At the end, please ensure all program and screen are activated. Hope this will help.
Regards
Kiran Sure

How can i add field to screen exit ?

ver 4.7
trans. me21n
add field in screen exit .
i implement screen exit MM06E005->SAPMM06E->0111
in the layout i try to add field by pressing
button in the toolbar ( dictionary field window ) ,
but when i press "save" in me21n ,
i get message "No data changed".
i choose in the dialog window
field from structure "ci_ekpodb" , field that i already
been add .
thanks .

Hi
You have to implement the exit to import/export the data into/from screen-exit:
EXIT_SAPMM06E_016 and EXIT_SAPMM06E_018
Max

Info on Screen-exits

Similar Messages

Maybe you are looking for