Tcode: /SCWM/VEH --Finding screen exits/enhancements in eWM
Hello All,
I need to add a dropdown or F4 help button on a custom screen in transactoin /SCWM/VEH related to SCM eWM. I did not finf any screen exits for this transactoins. Please suggest is there any way in acheiving this?
Also can anybody explain how to achieve Batch to Batch transfer posting technically in eWM.
Please suggest me where can i found good tech document related to eWM.
Thanks In Advance.
Anil
Edited by: anil007 on Nov 11, 2009 10:13 AM
Hi,
Check these:
MGA00001 - Material Master (Industry): Checks
and Enhancements
MGA00002 - Material Master (Industry): Number
Assignment
MGA00003 - Material Master (Industry and
Retail): Number Display
Check with 'BADI_MATERIAL_REF'
Refer
http://www.****************/Tutorials/ExitsBADIs/MM/MM01.htm
https://forums.sdn.sap.com/click.jspa?searchID=7217830&messageID=3313524
Regards
Similar Messages
-
Issue with Method to find Screen Exit
Hi all,
I am planning to add 2 custom fields to item details tab in ME51N .
I tried to find screen exits using development class of ME51N i.e ME
I went to smod and tried to find enhancements using ME development class and from the list of enhancements i tried to find a screen exit but i could found one.
I found an enhancement
MEREQ001 Customers' Own Data in Purchase Requisition
Which had a screen exit as well and this is what i was exactly looking for.
But my question is that
MEREQ001 is under development class MEREQ
So that means the way i was trying to find the screen exits is wrong or is there a better way to find screen exits
Let me know
ThanksHi,
U will find that if u try this program.
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.
End
Regards,
Jagadish -
How To Find Screen Exit & Menu Exit
Hi Friends,
How can we find Screen Exit & Menu Exit?
Kindly do not specify the report which is prevailing all over.
And does class CL_EXITHANDLER also return exits apart from BADI names ?
Regards,
PradeepHi,
Check this...it will help u to create menu exit...
Creating Customer-Specific Menus
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
Procedure for Creating MENU Exits:
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
screen exists
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Regards
Kiran Sure -
Hello,
I want to know the procedure to find out the Screen exits available for a particular Txcode? Please to know this Concept.
ThksHi,
Finding Screen Exit:
1. in se11, goto table MODSAP
View table contents
2. in Type field, enter 'S' (for screen exit)
3. For that tcode, u should know the program name
or the CALLING SCREEN.
eg. SAPLLMOB
4. then type SAPLLMOB* and execute
For Further:
ERPGenie.COM -> SAP Technical -> ABAP -> Tips and Tricks -> SAP ABAP Field Exits
V4.6c onwards no longer supports field exits!!! In any case here's how to activate them:
Activation of the field exits and assignment of the dynpros is carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see below for documentation).
Field Exits for Data Elements
Description
Maintenance transaction for creating and activating field exits
As part of the extension concept, SAP allows you to install a field exit for each screen field. Similar to the conversion exit, the system branches at the field exit at DCI (DATA COMMUNICATIONS INPUT) to a function module, if the field is an input field and a function code was triggered. The function module must adhere to the following naming convention:
Prefix: FIELD_EXIT_
Infix: <Data element name>
Suffix: _0 to _9 (optional), _A to _Z
The interface is automatically generated during the creation of the function module, and has 2 parameters:
Import parameter: INPUT
Export parameter: OUTPUT
After a function code has been triggered the contents of the field are made available to the FB via the "INPUT" import parameter. You can edit this and, when changed, make it available to the ABAP/4 processor in "OUTPUT". The input field contents are usually passed on: you can simply write OUTPUT = INPUT.
If, e.g., you have activated the field exit for the data element 'PROGRAM', then the fields of all the screens, which refer to the data element 'PROGRAM', branch to the function module FIELD_EXIT_PROGRAM. This includes the field 'Program' of the initial screen SAPMS38M0100 in transaction SE38, for example.
If you do not want the function module to be accessed from all screens, assign particular screens to the data element PROGRAM. By allocating an exit number, it is also possible to branch to other function modules with the corresponding suffix _0 ... _Z.
Example: You have assigned screen SAPMS38M0100 and exit number 5 to data element 'PROGRAM'. The corresponding field on SAPMS38M0100 branches to FIELD_EXIT_PROGRAMM_5.
As soon as you activate an exit, the corresponding screens are invalidated.
Note: Field exits are only taken into account during screen generation if the parameter abap/fieldexit = 'YES' is set in the system profile.
Requirement
Set the profile parameter abap/fieldexit = 'YES' before system start.
Limitations
The following ABAP statements are not allowed in the function modules of field exits:
BREAK-POINT,
CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
COMMIT WORK, ROLLBACK WORK,
COMMUNICATION RECEIVE,
EXIT FROM STEP-LOOP,
MESSAGE I, MESSAGE W.
Note:
Field exits cannot be edited with the debugger.
You should not use any external Performs in field exits. The ABAP processor shares the table work areas of externally called programs with those of the first caller. This could lead to errors at field exits that can hardly be analyzed, as field exits are sometimes slipped into the flow of the program at unforeseen events.
Questions and answers on field exits
1. A field exit was created with the CMOD and activated, but it does not get executed when the screen is called.
Since the field exit is not executed until DCI, some action must occur in the screen (e.g. press Return, saving....).
Set the abap/fieldexit profile parameter to YES and start the system again.
After the FIELD_EXIT... function module has been activated and the field exit has been activated, the transaction in whose screen the field exit is to be executed must be terminated. The screen is not generated until it is called.
Do not work on different application servers, otherwise there may be a delay before the field exit becomes active.
The profile parameter must be set either on all application servers or on none.
If the field exit is to be active in certain screens only, then you should check whether you have selected the correct program and the correct screen number (Careful with SUBSCREENS Do not rely on the F1 information for the field!
2. How does setting abap/fieldexit affect the performance?
If a screen is generated and the profile parameter is set, then the system checks in 2 tables (TDDIR, TDDIRS) to see whether a field exit has to be generated for the field. In practice the screen load after a Put is not generated until the screen is called. The user will not experience a noticeable delay, since screen generation is extremely fast.
3. Can the contents of other screen fields be read in a field exit?
In principle all fields can be copied to global variables in the TOP or the function group. However, since the order in which the field exits are called is not guaranteed, this possibility should not be used.
4. How does the field exit work in step-loop fields?
After data input to DCI the field exit will be called as many times as fields are visible on the step-loop. The SY-STEPL system variable is incremented each time. If a new value is assigned to be field, then it will be visible in the module between LOOP. ENDLOOP. This module will also be called as many times as there are visible step-loop lines.
5. Can field exits be debugged?
No. Field exits have to be tested in isolation in the development environment. To analyze problems that occur only in the screen environment, the relevant variables can be written to the file system using TRANSFER... and can be analyzed there.
6. What should one do if the field contents are not getting transported to ABAP/4?
Check whether you have assigned a value to the OUTPUT field.
7. When does the field exit get called in the case that there is a conversion exit attached to the data element?
The field exit will be called after the conversion exit. This means that the INPUT field contains the data in the same form as that in which the ABAP/4 program also gets them.
Regrdas,
Shiva Kumar -
Hi,
how i can find screen exit for a given transaction code.
plz provide me the steps.
Thanks,
kishScreen 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.
plz refer this (the same question asked here)
screen exit -
How to find screen exit for a screen?
Hi,
If you know the transaction, how to find if there is a screen exit exists or not?
Here even I know the screen number also. I have opened it in screen painter. How can I see if there is a screen exit for the screen?
Thank you.Hii
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.
Screen exit
Regards
Naresh -
Screen Exit - Enhancement MM06E005 - Transfer input data back to program
I have implemented enhancement MM06E005 to create a subscreen on the PO header. I have created the screen and I see it on the POs tcodes (ME2#n). However, I can't figure out how to "save" the data that the user inputs. By save I mean bringing the data back to the calling program (tcode). When the PO is saved the input data goes away; it is there until the save. I realize that I am missing something but I can't figure how where/how to transfer the data in the FMs EXIT_SAPMM06E_007 and/or EXIT_SAPMM06E_008.
I have read the SAP documentation but that isn't much help. I also have a book from SAP on modifications/enhancements (from an SAP course) and that isn't of any help either.
Any ideas?
Regards,
DavisHello,
i think you can found an answer to your question in the thread below :
[MM06E005 functional exit;
Particularly, the post of Padmam is saying : "You incorporate your customer fields for the Document Header in the INCLUDE CI_EKKODB (in table EKKO)."
Have you add the customer fields (those displayed in the subscreen you create) in the include CI_EKKODB ?
Cordialement,
Chaouki. -
Implementing ME21N / ME22N screen exit (Enhancement MM06E005)
I've just implemented enhancement MM06E005 and have extended a new field to CI_EKKODB. The subscreen is in place and the project has been activated without issues. I can populate the DB via the new field in 'customer data' tab. The only problem I have is I don't see my new value after saving the PO and re-accessing it in change mode ME22N. The new field is blank. I can see the record's new field has the value in SE16N and I see the value when debugging EXIT_SAPMM06E_006. My assignment statement in EXIT_SAPMM06E_006 for the new field is similar to: i_ci_ekko-zzvbeln = i_ekko-zzvbeln. What have I missed?
Edited by: Steve Fenske on Oct 13, 2009 11:45 PMHi steve ,
In addition to the function exit u r doing , u have to code the bellow exit also .
See the documentation of this exit , it explains u clearly in the document.
EXIT_SAPMM06E_006 Export Data to Customer Subscreen for Purchasing Document Head
EXIT_SAPMM06E_008 Import Data from Customer Subscreen for Purchasing Document
The dynpros are linked to the standard program via function modules.
There are function modules that provide your subscreen with data
(export) and function modules that fetch data from your subscreens
(import).
o Header screens:
- EXIT_SAPMM06E_006 Export data to customer subscreen for header
(PBO)
- EXIT_SAPMM06E_007 Export data to customer subscreen for header
(PAI)
- EXIT_SAPMM06E_008 Import data from customer subscreen for
header
Rajendra -
Hi All,
I need to enhance the Standard SAP FB03 screen by adding an custom pushbutton. Kindly can some body help me in finding Screen Exit.
I have searched for User Exits for FB03 in SMOD but could not find out an exact one.
If any body has step by step Screen Exits document - that would be a great help me.
Thanks a lot for help.SAPLF051 :- Workflow for FI (pre-capture, release for payment)
RFKORIEX :- Automatic correspondence
RFEPOS00 :- Line item display: Checking of selection conditions
RFAVIS01 :- Customer Exit for Changing Payment Advice Segment Text
FEDI0001 :- Function Exits for EDI in FI
FARC0002 :- Additional Checks for Archiving MM Vendor Master Data
F180A001 :- Balance Sheet Adjustment
F050S001 :- FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
F050S002 :- FIDCC1: Change IDoc/do not send
F050S003 :- FIDCC2: Change IDoc/do not send
F050S004 :- FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
F050S005 :- FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
F050S006 :- FI Outgoing IDoc: Reset Clearing in FI Document
F050S007 :- FIDCCH Outbound: Influence on IDoc for Document Change
OR
U GO SE80
AND WRITE REPORT NAME RFBUEB00 OR SAPMF05L
THEN
IN TREE SELECT SCREEN
AND CHEK SCREEN EXIT -
Hi,
I want to add two field named Invoice and Invoice item in the transaction QM01, tab reference object. Could you please help me out with any screen exit in which I can insert the field.
Thanks in advance!
ParulHi,
Goto Tcode QM01,
Menu Bar> System>Status, double click on Program
It will take you to the Program, agin on Menu bar>Goto>Object Attributes, in that copy the Package.
Goto SE84 Tcode, Enhancements > Customer Enhancements,
In Package, give the copied package name,
It will give you list of Customer Exits.
Double click on each enhancement, and look for any enhance ment in Screen of any particular enhancement.
(or)
How to find screen exit
Search in these tables
MODSAP
MODSAPA
MODSAPT -
Hi, Friends,
How to find out Menu and Screen Exits for a particular transaction in version 4.7.Hi,
These threads explains how to find the menu exits and screen Exit.have a look at it.
How to find Field Exit, Menu Exit and Screen Exit in a given TCode
How to find Menu Exits?
Reward points if helpful.
Manoj. -
hi everyone,
For custom field creation and linking the existing system fields with my custom fields i like to know about User Exit and screen Exit. Kindly give me the suggestion.
Thanks & Regards
R.Vijaihi,
this will help you find screen exit for a tcode.
[https://forums.sdn.sap.com/click.jspa?searchID=19171273&messageID=6151259] -
Screen exit for transation ks01,02 or 03,
Hi everyone,
Can any one tell how to find screen exit for transaction ks03, as i need to add one additional tab in the the transaction
thanks
NikeshHi
here is a list of exists for ks03
Exit Name Description
COCCA001 Customer enhancement to cost center authoriza
COCCA002 Customer Functions for Organizational Authori
COOMEP01 CO-OM: Information system -> line item report
COOMKA01 Customer Fields for Cost Element Master Data
COOMKS01 Customer Fields for Cost Center Master Data
COOMKS02 Cost Center: Checks When Saving
COOMKS03 Cost Center: BAPI Enhancements
COOMLA01 Customer Fields for Activity Type Master Data
To find exit go to ks03 ->system->status->double click on program name ->goto->attributes ->copy package name
then go to transaction SMOD click on F4 help ->information systems->put in the package name and youll get all the exits available -
Hi All,
I am trying to add a push button ( screen Exit ) field on IL02 transaction.
I have understood that i need to do the following.
a) Use the Exits ITOB001 ( EXIT_SAP_LITO0_001 and 002) .
But I dont know how to proceed with doing it. Can any one explain or guide?Hi,
you can use the below code to find out the screen exit for any transaction code..
Just copy and paste in your new program. and execute to find screen exits for a give transaction code.
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: / 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 : / tstc-tcode, 6 tstc-pgmna, 30 'No exits found'.
endif.
clear tstc.
endselect.
end-of-selection.
clear: search1, search2, search3.
Regards,
KK -
Hi,
I can't find screen exits on MIRO. My requirement is to display popup but i can't use field-exit and i need create a screen exit . Please let me know the screen-exit for the same. Regards
ByeHi Marcos,
Please make a habit of searching in SCN first. On this topic, you will find lot of material. As you are new to the SCN, therefore for your help, refer to the following links:
User exit in Standard transaction
Screen Exit
Hope this will help you...
Maybe you are looking for
-
Bridge won't open some tiff & jpg files in RAW
Most of the time bridge opens tiffs and jpgs in camera raw, but sometimes it won't for certain images. Anyone know a workaround?
-
JDBC - ORA-12514 TNS:listener does not currently know of service requested
Hi, I am using JDBC driver in Java for connecting to my Oracle XE 11g database on Windows 2008 Server R2 Standard, but I am receiving the following error +java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS
-
HT3702 trouble activating card on itunes keeps asking for correct security code
what am i doing wrong if i'm putting in security code and it tells me different
-
Hey... When I attempt to resize photos in Preview... sometimes it works, but more often it doesn't. I can try to save the image after the resize, or I've tried closing the image and forcing the Preview Save dlg box... either way... sometimes it works
-
Pictures are showing up "x ray"
Picasa and photos taken are showing up x ray.