Need Screen exit

Hi Frnds,
my requirement is to add custom fields to VA01 transaction 'Additional data B' tab. so please let  me know if any screen exits available for this and if possible detailed steps also.
thanks n regards,
KP

hi,
first go to se93 provide the tcode then display it wl give you the package in which this tcode is stored then goto se84 ---clickon enhancement --->click on customer exits >click on enhacements>provide the package -->execute it will give u all the exits present now click on each exit and screen whether screen exit is der ot not but i think there is no screen exit exists available for va01but the above steps can help you screen exits for other transaction
and tcode smod/cmod is used to activate the exits
thanks
shivraj
Edited by: ShivrajSinha on Feb 9, 2010 8:34 AM
Edited by: ShivrajSinha on Feb 9, 2010 8:51 AM

Similar Messages

  • Need Screen Exit in "Create Trip" Screen of Tcode TRIP.

    Hi,
    Here i want to develop a screen in "CreateTrip" of TCode TRIP.
    Any suggestions are welcome.
    Thanks in Adv,
    Raju Mummidi

    Hi ,
    Try to use this user exit.
    Use User Exit: FITR0003
    Thanks,
    Mohan rao

  • Screen exit for mi04 tcode

    hi,
    i need screen exit for mi04 tcode .

    Hi Prabhakar,
    Try these User Exit.
    MB_CF001  Customer Function Exit in the Case of Updating a Mat. D
    MBCF0002  Customer function exit: Segment text in material doc. i
    MBCF0005  Material document item for goods receipt/issue slip
    MBCF0006  Customer function for WBS element
    MBCF0007  Customer function exit: Updating a reservation
    MBCF0009  Filling the storage location field
    MBCF0010  Customer exit: Create reservation BAPI_RESERVATION_CREA
    MBCF0011  Read from RESB and RKPF for print list in  MB26
    Regards,
    Vijay

  • Screen exit for FBL3N

    hi,
    i need screen exit for FBL3N

    >
    avinash kodarapu wrote:
    > hi,
    >
    > Refer to this link.....
    >
    > Adding new fields in FBL3N
    If you need to enhance the report displayed, this suggestion worth to try. But if it's the selection screen of FBL3N that you want to enhance, I haven't found any provided enhancement method by SAP.
    I think I was too quickly to assume that you need to enhance the selection screen since you mention screen exit. I think it would be better if you let us know the requirement.
    Regards,
    Abraham

  • Screen Exit for QE01/QE02

    Hi,
    I need screen exit or BADI for QE01/QE02/QE03 .
    I have to insert 3 custom fields on the screen of QE01 and these fields values can be editable in QE02.

    Hi ,
    Please try to use BADI for Screen exit QEEM_SUBSCREEN_5000
    and use User exit  for adding additional functionality EXIT_SAPLQEEM_025.
    Few more BADI is available but not for enhancing screen like:
    QEC_RESULT_COPY Data Transfer to an Inspection Lot
    QE_RESULT_VALUATION Valuation of Single Values
    QE_SAVE Save Results
    QE_SAVE_ADDON Data Backup - Operation Completion
    QM_IDI_INSPPOINT Changing of Inspection Point Processing in IDI and BAPIs
    QM_INPUT_PROCEDURE Input Processing
    Regards,
    Prasenjit Mishra

  • Screen exit help is needed for SCASE development

    Dear forum,
    I need your help to find a possible screen exit for the SCASE transaction. I want to add custom fields in the standard SAP screen since we want to have more fields here than standard. I have identified the program and package as follows:
    Transaction: SCASE
    Program: SAPLSRMCLFRM2
    Package: SCMG_GENERAL
    Can you please help me on how to find a screen exit for this?
    I would really appriciate all help I can get, many thanks in advanced!
    // Par

    Hello again,
    I have seemed to found the following BADI: SCMG_CASE_FCODE_S - Case Frontend: Non-standard Pushbutton
    The documentation states the following:
    This BADI is called if a function code was triggered that s not implemented by the standard of the case.
    This is true if the pushbutton is customer- or application-specific.
    You can create your own pushbutton in the table SCMGFUNCTION by using the maintenance view SCMGV_FUNCTION. If you do so, pay attention to the customer namespace in the table.
    In this table you can control exactly when the pushbutton is active The function code is the processed in this BAdI
    If I now want to create a subscreen with new custom fields and add that as a pushbutton option on the standard screen of transaction SCASE, what would be the next steps to take?
    Best regards, Par

  • Menu Exit  & Screen Exit Implementation Step by Step Implementation Needed:

    Hi Experts,
    I am in need of how to implement Menu Exit and Screen Exit using a simple
    example.If any step by step implementation through snapshots were it will be
    helpful instead just some links that doesn't work after some steps due to version
    changes or not proper steply explanations.Points will be rewarded accordingly.
    Thanks for your help in Advance.

    Hi Sudha,
    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"
    Please check if the thread given below would be of any help.
    http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    Regards
    KK

  • Need user exit / screen exit for SE38 program variant save

    Hi ABAPers,
    Need user exit / screen exit for SE38 program variant save action to log addition details of variant changes done and relavent ticket details in z table.
    Currently table VARID table stores only latest change and not history.
    We need to avoid logging enabling for table VARID  and custom field addition in it.
    Please advice.
    -Nilesh

    HI Nilesh,
    I don't think any Exits available for this.
    Better u go for Implicit Enhancement.
    regards
    Sreekanth

  • 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 - exits - step by step simple examples

    hi ,
    i am new to user exits.
    pls help me by giving step by step example for creating a subscreen with 2 fields , and incorporate with some standard sap transactions.
    there are many who discussed the same topic in the forum ,but i find confusing.
    *so please don't give me the links, take standard transaction and provide me step by step .
    Thank you.
    regards
    Sree

    hi,
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen u2013 where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen u2013 so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool u2013 including subscreens, Tabstrip controls etc.
    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 u2018SAP Applicationsu2019. 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 u2013 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 u2013 20 characters
    Location 2 u2013 15 Characters.
    Model no u2013 20 characters
    Location 2 should start with u2018Lu2019.
    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 u2018CUSTu2019 (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 u2018Lu2019 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 u2018EXIT_SAPLAIST_002u2019, 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 u2018EXIT_SAPLAIST_003u2019, 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 u2013 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 u2018Enhancement Assignmentsu2019 in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to u2018Componentsu2019.
    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 u201CLocation 2u201D, 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 u2013 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 u2018Generalu2019 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 u20181000u2019 and click on folder u2018General Assignment of Layoutu2019.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout u2018SAPu2019 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 u2018SAPu2019 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 u2018Tab page titlesu2019.
    You want to put your custom fields in the tab page u201CGeneralu201D. 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 u201CGeneralu201D are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with u201CUu201D 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 themu2026save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.

  • How to write the code for screen-exits

    halo fellow SAPiens,
    I want to add a screen for t-code AS01......for which i have created a sub-screen in the function grp (related to AS01)........now i need to link the sub-screen with the Standard SAP prgm..........i.e  call the sub-screen........how can i do it...........

    pls send me one example for implementing menu-exits,screen exits and
    Screen exits - Urgent.
    screen exits
    Screen exit
    Please reward points if helpful...

  • Screen exit for transaction VA41

    dear all,
    i want to add two fields to the transaction code VA41 contract creation.can anybody tell me screen exit for this or else how to do it?
    regards,
    Debesh

    Hi Debesh Tripathy,
               In additional data A Tab you have some customer field than you can use it, if these fields don't match with you request you can add fields in Additional data B tab with help of ABAP, since you need to modify the screen the PBO and PAI 8459 of program SAPMV45A. Bear in mind this screen is also used by VA21 and VA01 so you need to put a conditional to doesn't show this field in these others transaction.
    Thanks,
    Mariano.

  • Screen exit for transaction MD14.

    Hi collegues,
    Does anyone know what the screen exit for transaction MD14 is?  I need to add an extra field to the detail screen of transaction MD14.  The field name to be added is MDBA-LIFNR.
    Thanks.

    Exit found.

  • Problem with Screen EXITS.

    Hi,
    I need to to some enhancements to my std screen for T.code IE03.
    I found screen exits and Function exits for that .
    I  create the subscreen in screen exit and linking to the functional exit,
    Whem i am activiting it raises the error
    "Incorrect nesting  Before the Statement module structure  introduced by function must be conclude by endfunction."
    Can any one suggest the solution for this problem.
    Points will be awarded.
    regards,
    Jayasimha

    The Problem can be due to incorrect closing of syntex.. either in function module  or in PBO or PAI module. i.e you might have started by saying function but endfunction is missing or same goes for PBO / PAI module do check it and let us know
    No Rewards Pz..

Maybe you are looking for