Screen exit for FB60 on header level

hi , i am working on FB60 .  i want to add an extra tab  i.e extra screen on the header level . are there any screen exits for fb60 to add extra screen?

hi praveen,
search this forum on how to implement a badi if you haven't done one before. also, go to transation SE18 and read the documentation on badi_fdcb_subbas01 which clearly says that its used for FB60... see the example how they have used it by going to menubar Implementation->Overview then choose FI_FDCB_SUBBAS01_EX (Example for Screen Enhancement 1 on FDCB Basic Data Screen)...you should look at the method PUT_DATA_TO_SCREEN_OBJECT and tab Subscreens where the screen exits are available to use.
In FB60, if you go to menubar System->Status and check the Program (Subscreen) and Screen Number, you'll see it'll match the program name and screen no. provided in the Subscreen tab of the BADI.
Hope this helps.
Cheers,
Sougata.

Similar Messages

  • Screen exit for ME51N in header

    Hi friends,
    Is there any screen exit for ME51N(Purchase requisition) in header level.I found MEREQ001 enhancement, but this is for item level.please help.
    regards,
    Thoufique.

    Hi Thoufique,
    try the following screen exits:
    EXIT_SAPLMEREQ_001 Export Data to Customer Subscreen for Re
    EXIT_SAPLMEREQ_002 Prepare Customer Subscreen for Requisiti
    EXIT_SAPLMEREQ_003 Import Data from Customer Subscreen for
    Also, for more help on your problem, refer to the following link:
    Re: re: screen exits
    Hope this will help you...

  • Screen exits for XD01 at different levels of customer classification

    Hi ,
          Can anyone help me in getting screen exits for Tran XD01 at differnt levels like in general data , sales area where i need to add custom fields.

    Hi,
    Check the documentation in below :
    Goto  - SPRO - Financial Accounting - Accounts receivable and Accounts Payable - Customer Accounts - Master Data ->
    1) Preparations for Creating Customer Master Data - Adoption of Customeru2019s Own Master Data Fields -Prepare Modification-Free Enhancement in Customer Master Record. Here you will find the BADI's for customer master screens. Check the individual documentation
    2) Preparations for Creating Customer Master Data- Develop Enhancements  for Customer Master Data
    Please note as far as i know, you can create new buttons on the customer master tool bar and then assign your fields to that button on the transaction. Not sure if you can add fields in the existing screens.
    Thanks
    Shiva

  • Screen Exit for FB60

    Hi all,
    I want to know if there is any Screen Exit or BADI provided for T-code FB60.
    Actually If we got to Payment tab on the screen we could see Vendor address an the right hand side. I have to add some more Bank account details ( IBAN code and SWIFT code ) there.
    Could you please check if it is feasible and suggest me how to proceed further.
    Points will be rewarded if useful.
    Thanks and regards,
    Daya.

    Daya,
    have a look at Exit and BADi of FB60:
    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    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                                                                               
    Business Add-in                                                                               
    FBAS_CIN_LTAX1F02                       Tax interface                                               
    FBAS_CIN_MF05AFA0                       EWT - Downpayment Clearing - Tax transfer for CIN           
    FISPLIT                                 Online Split: Cash Discount, Exchange Rate Differences      
    FI_AUTHORITY_ITEM                       Extended Authorization Check for Document Display (FB03)    
    FI_DOC_DISP_LI                          Diversion to Document Items (FB03)                          
    FI_FB08_SUBST_BUDAT                     FB08: Check Posting Date for Reversal of FI Doc. with FB08  
    FI_GET_INV_PYMT_AMT                     BAdI for determining the payment amount for an invoice      
    FI_HEADER_SUB_1300                      Screen Enhancement for Document Header SAPMF05A             
    FI_PAYREF_BADI_010                      BAdI: Payment Reference Number                              
    FI_RES_ITEM_CURRENCY                    Document of Residual Item with Invoice Currency             
    FI_TRANS_DATE_DERIVE                    Derive BKPF-WWERT from Other Document Header Data           
    FVFZ                                    Replacement for Function Modules of Function Group FVFZ                                                                               
    INVOIC_FI_INBOUND                       BADIs for Inbound IDoc INVOIC FI (Vendor Invoice)          
    RFESR000_BADI_001                       BAdI for Own Processing of POR Item                        
    BADI_DRB_CONV_AWREF                                                                               
    BADI_DRB_CONV_BORID                                                                               
    AC_QUANTITY_GET                         Transfer of Quantities to Accounting - Customer Exit       
    ADJUST_NET_DAYS                         Change to Net Due Date                                     
    BADI_ENJ_ALT_ADR                        Go to alternative vendor/customer data                     
    BADI_F040_SCREEN_600                    Screen Enhancement on F040 0600 Document Header            
    BADI_FDCB_SUBBAS01                      Screen Enhancement 1 on FDCB Basic Data Screen (010, 510)  
    BADI_FDCB_SUBBAS02                      Screen Enhancement 2 on FDCB Basic Data Screen (010, 510)  
    BADI_FDCB_SUBBAS03                      Screen Enhancement 3 on FDCB Basic Data Screen (010, 510)  
    BADI_FDCB_SUBBAS04                      Screen Enhancement 4 on FDCB Basic Data Screen (010, 510)  
    BADI_FDCB_SUBBAS05                      Screen Enhancement 5 on FDCB Basic Data Screen (010, 510)  
    BADI_MIRO_SPLT_ADD                      Append additional fields of ACCVS to ACCIT                 
    BADI_PRKNG_NO_UPDATE                    BAdI for Deactivating Update of Parked Documents           
    F050S008                                FIDCC1, FIDCC2 Inbound IDoc: Update Comparison Ledger
    Amit.

  • Screen exit for me32k for header and for items

    hi experts,
    i need a screen exit  from me32k to add subscreen in :
    1. items
    2. header
    thanks in advanced,
    dana.

    Hi,
    Just some information on screen exits:
    Screen Exit:
    How to implement screen exit for a SAP standard transaction
    Introduction
    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 – 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 – 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 – 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 ‘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.
    Original Source: ittoolbox.com
    User Exits:
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written 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>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    Suppose you need to find out all the user exits related to a tcode.
    1. Execute the Tcode.
    2. Open the SAP program.
    3. Get the Development Class.
    4. Execute Tcode SE84.
    5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
    6. Enter the Development class and execute.
    Check out this thread..
    The specified item was not found.
    1. Type the transaction : system->status-> <PROG. NAME>
    2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
    3. Open CMOD utilities->SAP enhancements
    EDIT->All selections
    4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
    5. The displayed list contains the enhancements names for the transaction You were looking for.
    6. Create a project in CMOD and the code in default include->activate.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.planetsap.com/userexit_main_page.htm
    User-Exits
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/ab038.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
    These links will help you to learn more on user exits.
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.allsaplinks.com/user_exit.html
    www.sap-img.com/abap/what-is-user-exits.htm
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    2. Finding User Exits...
    http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
    3. List of all User Exits...
    http://www.planetsap.com/userexit_main_page.htm
    Reward if found helpfull,
    Cheers,
    Chaitanya.

  • Screen exit (for newTabstrip) for ME21 TRANSACTION CODE AT ITEM LEVEL

    Hi All ABAPERS,
    I had a urgent requirement that I need to provide new tabstrip in ME21 tcode at ITEM level.
    note: not in Item overview.
    So, friends could you please tell me what is the screen exit for it and if you have steps for it please give me the solution as early as possible and good points will be rewarded.

    use this enhamcement MM06E005
    go to se51 give program name SAPLXM06 and create 0111 screen and mention subscreen under attributes of screen.
    and go to layout define ur fields in the layout..
    use exit_sapmm06e_013 for getting data .
    also create ci_ekpo structrure and write the req logic to update that strucutre so that values will go and sit in stadard ekpo table.
    after creating that structure dont forget to activate ekpo thr se14.
    and go to se80 and give function group of exit_sapmm06e_013(this fm) and u will find under includes some z*top where u can declare all ur screen fields .

  • Screen Exit for Header ME51N

    Hi experts, there is some screen-exit for HEADER of ME51N??
    I've found only MEREQ001, but it has a screen exit only for item requisition...
    Thanks.
    Alexandere

    Hi,
    check the following screen exit Information for Enhancement "MEREQ001"
    Calling screen     No.   Area       Called screen     No.
    SAPLMEGUI       0014 SUB0     SAPLXM02        0111
    also find the following user-exits
    EXIT_SAPLMEREQ_001             Export Data to Customer Subscreen for Re
    EXIT_SAPLMEREQ_002             Prepare Customer Subscreen for Requisiti
    EXIT_SAPLMEREQ_003             Import Data from Customer Subscreen for
    Regards
    Sreeni

  • Exit for  FB60 and MIR7 Transactions.

    Hi All,
       I need exit for FB60 and MIR7 transactiosn to below functionality.
    For each line item in FB60 and MIR7 need to populate pop-up screen to enter the
    data G/L account and Material group.  And G/L account will be populated by selectiong the search help on Material group.
    thanks,
    rao

    Transaction Code - FB60                     Enter Incoming Invoices
    Exit Name           Description
    RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00            Line item display: Checking of selection conditions
    RFKORIEX            Automatic correspondence
    SAPLF051            Workflow for FI (pre-capture, release for payment)
    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
    F180A001            Balance Sheet Adjustment
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    FEDI0001            Function Exits for EDI in FI
    No of Exits:         14
    Transaction Code - MIR7                     Park Invoice
    Exit Name           Description
    LMR1M001            User exits in Logistics Invoice Verification
    LMR1M002            Account grouping for GR/IR account maintenance
    LMR1M003            Number assignment in Logistics Invoice Verification
    LMR1M004            Logistics Invoice Verification: item text for follow-on docs
    LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
    LMR1M006            Logistics Invoice Verification: Process XML Invoice
    MRMH0001            Logistics Invoice Verification: ERS procedure
    MRMH0002            Logistics Invoice Verification: EDI inbound
    MRMH0003            Logistics Invoice Verification: Revaluation/RAP
    MRMN0001            Message output and creation: Logistics Invoice Verification
    No of Exits:         10
    USER EXIT
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.sap-img.com/ab038.htm
    http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
    Rewards if useful.........
    Minal

  • Screen exits for tcode vl31n.

    Hi,
    I need to add push button(Print) in VL31N tcode.
    Please provide any screen exits for that.
    Thanks,

    Hi
    Use BADI LE_SHP_TAB_CUST_HEAD for delivery header.
    Method: ACTIVATE_TAB_PAGE
    Use BADI LE_SHP_TAB_CUST_ITEM  for delivery item
    Method: ACTIVATE_TAB_PAGE.
    In the method specify the caption, program name and screen number as below.
    ef_caption = 'Customer Data'.
    ef_program = 'Z_IBDELIVERY'.
    ef_dynpro  = '9000'.

  • Screen Exits for VA21

    I have to add a field(date) in the screen in the transaction VA21 .
    Is there any Screen exit for transaction VA21 ? if not how do i go about doing the same

    Hello Amit,
    The requirement is can be met as follows....
    U can add the required field in the Additional data tab for header.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, This screens contain the Include screens SAPMV45A 8309 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    This should resolve ur problem.

  • Screen exit for f-29

    Hi all
    want to do a screen exit for the transction f-29  (payment Header data ) in which the data has to store in bseg .
    here i want to insert one parameter named personal no ...
    here i am not able to find the exit ..
    can u help me out

    .

  • Any BADI or Screen Exit for BBP_VENDOR_CREATE in SRM?

    Any BADI or Screen Exit for BBP_VENDOR_CREATE in SRM?
    Want to add new field in "Manage Vendor Data" screen. (screen 400)

    hi,
    > Its not possible to have the authorization for PR at storage location level...
    > you can have authorisations for Puchase organisation EKORG, plantWERKS, puchase group EKGRP, puchase document type BSART ...
    > and authorisations objects are:
    >M_BANF_BSA :   Document Type in Purchase Requisition
    > M_BANF_EKG :  Purchasing Group in Purchase Requisition
    > M_BANF_EKO :  Purchasing Organization in Purchase Requisition
    > M_BANF_FRG :  Release Code in Purchase Requisition
    > M_BANF_WRK :  Plant in Purchase Requisition
    Regards
    Priyanka.P
    Edited by: Priyanka Paltanwale on Apr 27, 2009 3:01 PM

  • Menu exit  ( or ) Screen exit  for tcode VF01

    Hi,
    Can you tell me menu exit or screen exit for this tcode VF01.
    Thanks,
    Prathap.

    Hi,
    der r total 17 exit.
    J_3RSINV
    SDVFX001            User exit header line in delivery to accounting
    SDVFX002            User exit for A/R line in transfer to accounting
    SDVFX003            User exit cash clearing in transfer to accounting
    SDVFX004            User exit G/L line in transfer to accounting
    SDVFX005            User exit reserves in transfer to accounting
    SDVFX006            User exit tax line in transfer to accounting
    SDVFX007            User exit: Billing plan during transfer to Accounting
    SDVFX008            User exit: Processing of transfer structures SD-FI
    SDVFX009            Billing doc. processing KIDONO (payment reference number)
    SDVFX010            User exit item table for the customer lines
    SDVFX011            Userexit for the komkcv- and kompcv-structures
    V05I0001            User exits for billing index
    V05N0001            User Exits for Printing Billing Docs. using POR Procedure
    V60A0001            Customer functions in the billing document
    V60P0001            Data provision for additional fields for display in lists
    V61A0001            Customer enhancement: Pricing
    Hope it helps.
    /sachinkumar.

  • 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 for transaction XK01

    Hi,
      I want to add a field for the transaction 'XK01'.
      How to find out the screen exit for this transaction.
      If we dont have screen exit for this transaction, is there any other way to add the field.
      Ps help regardng this.

    Hi,
    Check the BADI CUSTOMER_ADD_DATA_CS , this is used to add a tab screen with the custom fields.
    VENDOR_ADD_DATA Additional Vendor Data
    Vendor Master (XK01) Screen Exit
    check the foll link,
    userexits be..
    RFKRRANZ User exits: Accounts Payable Information System
    SAPMF02K User exits: Vendor master data
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    Regards
    Kiran Sure

Maybe you are looking for