Interface ref in user-exit.

hi friends,
     iam working with a user-exit in which one parameter is declared with type ref to  interface.
how can i use this parameter with out a class .i think we can implement that inerface in a class only.
how is it possible in fm.

Hi Sudheer,
for what t.code your using User exit.
Regards,
Venkat.

Similar Messages

  • User exit/BADI to change the Accntg doc which gets created during Billing

    I am trying to do the following . Is this possible ?
    When a delivery related billing document is created an accounting document is created in the background , I want to modify the line items in the accounting document, Just before posting the accounting document.
    I am using  exit EXIT_SAPLV60B_008  as suggested but I don't see the accounting line items in any of the internal tables in this exit.
    My accounting document when it gets created looks like this. And I want to modify one of these lines before the document is posted.
    Thanks in advance.
    Regards,
    Ankur Bhandari
    1 01 32517 Jaaaa 3,700.83 USD
    2 50 3100000 MERCHANDISE SALES 3,199.96- USD
    3 40 3100000 MERCHANDISE SALES 160.00 USD
    4 50 3200000 DELIVERY INCOME 132.00- USD
    5 50 3200000 DELIVERY INCOME 10.00- USD
    6 50 2170156 SALES TAX COLLECTED 198.87- USD
    7 50 3400000 WARRANTY INCOME 320.00- USD
    8 15 32517 Jaaaa 3,700.83- USD
    9 40 1117217 RECV. VISA/MCARD Sto 3,700.83 USD
    Any answers on how can I delete line 1 8 and 9 and add another line which balances the amount ?
    Need to do this just before the accounting document gets generated.
    Is this possible ?

    Hi Ajay,
    I just want throw a light on your issue.
    There are couple of other user-exits also available here.
    Just check the required data is available or not?
    EXIT_SAPLV60B_001              User Exit AC Interface (Header Line)               
    EXIT_SAPLV60B_002              User Exit AC Interface (Customer Line)             
    EXIT_SAPLV60B_003              User Exit RW Interface (Cost)                      
    EXIT_SAPLV60B_004              User Exit AC Interface (GL Account Item)           
    EXIT_SAPLV60B_005              User Exit AC Interface (Accruals)                  
    EXIT_SAPLV60B_006              User Exit AC Interface (Tax Line)                  
    EXIT_SAPLV60B_007              User Exit AC Interface (Customer Line)             
    EXIT_SAPLV60B_008              User Exit AC Interface Transfer Tables             
    EXIT_SAPLV60B_010              User Exit Item Table for the Customer Lines        
    Thanks,
    Ramakrishna

  • CO11N User Exit

    I am using the CONFPP05 enhancement to do some variance checking on production order at time of save.
    The program checks all material planned qty and actual qty and if there is a variance of more than 5%, A BTCI is triggered into transaction CO03 -> GoTo > Costs > Analysis and the document is sent to the printer.
    This works fine for all material checking.
    One more requirement is to check planned labor qty vs actual labor qty. However at time of save (in CO11N) the user has the ability to change actual labor qty. The database does not reflect these changes until after save (once user exit has finished processing), this means my program always finds variance AND the costs analysis report does not get updated with the actual labor qty.
    Is there a workaround for this or a way I can get the costs analysis report updated before printing. Is there any way I could print the report Post Save processing for CO11N?

    Hi,
    Refer Re: User Exit for CO11n

  • USER EXIT ON Posting RMCA documents FI-CA Interface

    Hi all,
    I have to fill some custom fields in RMCA documents during the FI-CA interface.
    I used the events 61, 4000, (transaction FQEVENTS) but there isn't any billing information (VBRK).
    That's all.
    Thanks for your help.
    Bye Enzo

    Hi Enzo,
    do you have debug your user-exit and check if in a calling program you have this information ?
    if yes, you can access this information with a little tip&trick.
    Rgd
    Frédéric

  • User Exit for CO11N to populate the Ref Order in Prod Order when Rework Ord

    HI All,
    I created a Production Order(100023) using TCode CO01 with 10 Qty.
    When i am creating a Production Order confirmation using TCode CO11N, i Confirmed 9 Qty and 1 Qty for Rework Order, it is confirming the 9Qty and creating a new Production Order (100024) for 1Qty.
    As per the requirement it is working fine. While system creating a Production Order (100024) for the Rework Qty, i need to populate the Reference Production Order number (100023) in the field Ref. Order in Control Data tab in the Production Order.
    Can any one suggest me how to populate this field? Is this possible by any USER EXIT or BADI ?
    Or Can we do it by configuration?
    Regards,

    Hey all: I already have solved it. This was solved using a batch input application: before is launched the MIGO transaction, we print the smartorm using ME38 transaction with SHDB.

  • How to read data which is not on interface of user-exit

    Hi experts,
    the data which I need is not on interface of user-exit. I can do export table to memory id and than in user-exit import that. Does this work always?
    I have seen that sometimes is possible to see data with
    (include-name)table-name. Can I always use this?
    In detail: in transaction ME51N is new tabstrip created with customer fields.I have to know the purchase order for the selected item which is filled on another tabstrip.
    Can anyone help me?
    Thanks.
    Best regards,
    Danijela

    Hi Danijela,
    To answer your question about the "(module)object" approach:
    Have you been in a user exit function and the data you need wasn't passed on to you? You can easily grab the data from the memory stack using this little trick. Let's say that you need some IDoc information that was created from the function IDOC_INPUT_DELVRY... You can get it directly from the call stack like this.
    The code was written in R/3 4.6C but should work in any SAP version.
    DATA: i_EDIDC like EDIDC,
          i_EDIDD like EDIDD occurs 0 with header line.
    CONSTANTS:
          c_EDIDD(21)  value '(SAPLV55K)IDOC_DATA[]',
          c_EDIDC(21)  value '(SAPLV55K)IDOC_CONTRL',
          c_E1ADRM1(7)      value 'E1ADRM1'
          c_SHPCON(6)  value 'SHPCON'.
    Field-symbols: <FC>, <FD> .
    clear: i_EDIDC, i_EDIDD.
    refresh: i_EDIDD.
    * Get the Control Record from memory
    assign (c_EDIDC) to <FC>.
    if SY-SUBRC = 0.
      i_EDIDC = <FC>.
      IF i_EDIDC-MESTYP = c_SHPCON.
    *   None of the partner information can be passed directly from
    *   the IDOC function, so we'll get it from memory.
    *   Get IDOC data records from memory
        assign (c_EDIDD) to <FD>.
        i_EDIDD[] = <FD>.
    *   Now you have the entire IDOC available to you without making
    *   a DB select.
        read table i_EDIDD with key SEGNAM   = c_E1ADRM1.
    *   Load new value HERE...
      ENDIF.
    ENDIF.
    I found this a long time ago on the web and used it successfully multiple times in the past.
    Hope this helps,
    Guenther

  • Regarding documentation on User Exits, IDOCS, Interfaces etc.

    Hi Friends,
    Can any one help me if any documentation on User Exits(MM/WM related), ALE IDOCS/ INTERFACES etc available which shall help in understanding the above concepts.
    Quick help will be highly appreciated and rewarded pls.
    Thanks in Advance
    Regards,
    Prasanna.

    this info is spread though all channels SAP has, but unfortunatly not  consistent,  thats why it is so hard to find something.
    You can find info at help.sap.com
    e.g. this link (see the menu on the left as well)
    http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm
    Further you can find info at SAP MArketplace (OSS notes)
    Or directly to the coding in SE37 and SE38.
    IDOC and ALE documentation can be found here:
    http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
    and
    http://www.logosworld.com/www5/books/IDocBook/IDocBook.htm
    Edited by: Jürgen L. on Oct 24, 2008 12:21 PM

  • Need a User Exit for OCI Interface in case of Multiple Views

    Hello Friends,
    I need a help in finding the User Exit / BADI for passing the Catalog ID when you click on Catalog Button in Purchase Requisition , PM Order ( IW32) and Purchase Order.
    1. We have number of Views and we need to implement Custom logic for releavant Catalog ID and same should be passed to third party System.
    2. Creation of Custom Conversion module and how these will be called in MM.
    3. How the sequence number will work in Assigment of Conversion module.
    4.In case of Custom fields in RIHFCOM-CUSTFIELD1( Ex :  EBAN-ESTKZ ) / RIHFCOM-CUSTFIELD2,how this will be mapped to Standard fields in SAP
    Please help in this regard
    Thanks in Advance.
    Regards,
    Kishore,

    Hi,
    Exit Name Description
    SDTRM001 Reschedule schedule lines without a new ATP check
    V45A0001 Determine alternative materials for product selection
    V45A0002 Predefine sold-to party in sales document
    V45A0003 Collector for customer function modulpool MV45A
    V45A0004 Copy packing proposal
    V45E0001 Update the purchase order from the sales order
    V45E0002 Data transfer in procurement elements (PRreq., assembly)
    V45L0001 SD component supplier processing (customer enhancements)
    V45P0001 SD customer function for cross-company code sales
    V45S0001 Update sales document from configuration
    V45S0003 MRP-relevance for incomplete configuration
    V45S0004 Effectivity type in sales order
    V45W0001 SD Service Management: Forward Contract Data to Item
    V46H0001 SD Customer functions for resource-related billing
    V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
    SDAPO001 Activating Sourcing Subitem Quantity Propagation
    <b>Reward points</b>
    Regarsd

  • Badi's or user exits

    i am extending my question on other topic..
    now badi's or user exits.. or both...
    thanks..
    raj

    Hi
    DEFINING THE BADI
    1) execute Tcode SE18.
    2) Specify a definition Name : ZBADI_SPFLI
    3) Press create
    4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
    multiple use.
    5) Choose the interface tab
    6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
    7) Dbl clk on interface name to start class builder . specify a method name (name,
    level, desc).
    Method level desc
    Linese;ection instance methos some desc
    8) place the cursor on the method name desc its parameters to define the interface.
    Parameter type refe field desc
    I_carrid import spfli-carrid some
    I_connid import spefi-connid some
    9) save , check and activate…adapter class proposed by system is
    ZCL_IM_IM_LINESEL is genereated.
    IMPLEMENTATION OF BADI DEFINITION
    1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
    2) Specify aname for implementation ZIM_LINESEL
    3) Specify short desc.
    4) Choose interface tab. System proposes a name fo the implementation class.
    ZCL_IM_IMLINESEL which is already generarted.
    5) Specify short desc for method
    6) Dbl clk on method to insert code..(check the code in “AAA”).
    7) Save , check and activate the code.
    Some useful URL
    http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
    http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
    http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
    http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
    www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
    http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
    Now write a sample program to use this badi method..
    Look for “BBB” sample program.
    “AAA”
    data : wa_flights type sflight,
    it_flights type table of sflight.
    format color col_heading.
    write:/ 'Flight info of:', i_carrid, i_connid.
    format color col_normal.
    select * from sflight
    into corresponding fields of table it_flights
    where carrid = i_carrid
    and connid = i_connid.
    loop at it_flights into wa_flights.
    write:/ wa_flights-fldate,
    wa_flights-planetype,
    wa_flights-price currency wa_flights-currency,
    wa_flights-seatsmax,
    wa_flights-seatsocc.
    endloop.
    “BBB”
    *& Report ZBADI_TEST *
    REPORT ZBADI_TEST .
    tables: spfli.
    data: wa_spfli type spfli,
    it_spfli type table of spfli with key carrid connid.
    *Initialise the object of the interface.
    data: exit_ref type ref to ZCL_IM_IM_LINESEL,
    exit_ref1 type ref to ZIF_EX_BADISPFLI1.
    selection-screen begin of block b1.
    select-options: s_carr for spfli-carrid.
    selection-screen end of block b1.
    start-of-selection.
    select * from spfli into corresponding fields of table it_spfli
    where carrid in s_carr.
    end-of-selection.
    loop at it_spfli into wa_spfli.
    write:/ wa_spfli-carrid,
    wa_spfli-connid,
    wa_spfli-cityfrom,
    wa_spfli-deptime,
    wa_spfli-arrtime.
    hide: wa_spfli-carrid, wa_spfli-connid.
    endloop.
    at line-selection.
    check not wa_spfli-carrid is initial.
    create object exit_ref.
    exit_ref1 = exit_ref.
    call method exit_ref1->lineselection
    EXPORTING
    i_carrid = wa_spfli-carrid
    i_connid = wa_spfli-connid.
    clear wa_spfli.
    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
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Need user exit when deleting an invoice using MIR6 transaction

    Hi all,
    I m trying to delete an Invoice using MIR6 transaction. And I need a user exit to be triggered  on deletion of an Invoice.
    Can anybody help me and let me know if any user exit is available there?
    Points will be rewarded.
    thanks
    Ashish

    Hi
    Business Add-Ins
    Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
    As with customer exits (SMOD/CMOD [Page 40]), two different views are available:
    • In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
    • In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
    In contrast to customer exits, Business Add-Ins no longer assume a two-system infrastructure (SAP and customers), but instead allow for multiple levels of software development (by SAP, partners, and customers, and as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
    SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
    The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time.
    In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example). All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard.
    A single Business Add-In contains all of the interfaces necessary to implement a specific task. In Release 4.6A, program and menu enhancements can be made with Business Add-Ins. The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects
    DEFINING THE BADI
    1) execute Tcode SE18.
    2) Specify a definition Name : ZBADI_SPFLI
    3) Press create
    4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
    multiple use.
    5) Choose the interface tab
    6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
    7) Dbl clk on interface name to start class builder . specify a method name (name,
    level, desc).
    Method level desc
    Linese;ection instance methos some desc
    8) place the cursor on the method name desc its parameters to define the interface.
    Parameter type refe field desc
    I_carrid import spfli-carrid some
    I_connid import spefi-connid some
    9) save , check and activate…adapter class proposed by system is
    ZCL_IM_IM_LINESEL is genereated.
    IMPLEMENTATION OF BADI DEFINITION
    1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
    2) Specify aname for implementation ZIM_LINESEL
    3) Specify short desc.
    4) Choose interface tab. System proposes a name fo the implementation class.
    ZCL_IM_IMLINESEL which is already generarted.
    5) Specify short desc for method
    6) Dbl clk on method to insert code..(check the code in “AAA”).
    7) Save , check and activate the code.
    Some useful URL
    http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
    http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
    http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
    http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
    www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
    http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
    Now write a sample program to use this badi method..
    Look for “BBB” sample program.
    “AAA”
    data : wa_flights type sflight,
    it_flights type table of sflight.
    format color col_heading.
    write:/ 'Flight info of:', i_carrid, i_connid.
    format color col_normal.
    select * from sflight
    into corresponding fields of table it_flights
    where carrid = i_carrid
    and connid = i_connid.
    loop at it_flights into wa_flights.
    write:/ wa_flights-fldate,
    wa_flights-planetype,
    wa_flights-price currency wa_flights-currency,
    wa_flights-seatsmax,
    wa_flights-seatsocc.
    endloop.
    “BBB”
    *& Report ZBADI_TEST *
    REPORT ZBADI_TEST .
    tables: spfli.
    data: wa_spfli type spfli,
    it_spfli type table of spfli with key carrid connid.
    *Initialise the object of the interface.
    data: exit_ref type ref to ZCL_IM_IM_LINESEL,
    exit_ref1 type ref to ZIF_EX_BADISPFLI1.
    selection-screen begin of block b1.
    select-options: s_carr for spfli-carrid.
    selection-screen end of block b1.
    start-of-selection.
    select * from spfli into corresponding fields of table it_spfli
    where carrid in s_carr.
    end-of-selection.
    loop at it_spfli into wa_spfli.
    write:/ wa_spfli-carrid,
    wa_spfli-connid,
    wa_spfli-cityfrom,
    wa_spfli-deptime,
    wa_spfli-arrtime.
    hide: wa_spfli-carrid, wa_spfli-connid.
    endloop.
    at line-selection.
    check not wa_spfli-carrid is initial.
    create object exit_ref.
    exit_ref1 = exit_ref.
    call method exit_ref1->lineselection
    EXPORTING
    i_carrid = wa_spfli-carrid
    i_connid = wa_spfli-connid.
    clear wa_spfli.
    check the following user exits for MIR6
                                                                                    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      
    Regards
    Anji
    Message was edited by:
            Anji Reddy Vangala

  • Enhancements, User Exits

    Hi all,
    where can u find all the userits & enhancements available in Materials Management.
    thanks

    Dear Sridhar,
    ME590001 |Grouping of requsitions for PO split in ME59                |
    MEAG0001
    Distribution of Contract/Scheduling Agreement from CRM
    MEETA001
    Define schedule line type (backlog, immed. req., preview)
    MEFLD004
    Determine earliest delivery date f. check w. GR (only PO)
    MELAB001
    Gen. forecast delivery schedules: Transfer schedule implem.
    MENUCRQ0
    QM: Enhancement in CRQ0 Menu (Work Center)
    MENUQA00
    QM: Enhancement in QA00 Area Menu (Quality Inspection)
    MENUQB00
    QM: Enhancements in QB00 Area Menu (QM in Procurement)
    MENUQD00
    QM: Enhancement in QD00 Menu (Archiving)
    MENUQM00
    QM: Enhancements in QM00 Area Menu (Quality Notification)
    MENUQMM0
    QM: Enhancements in QMM0 Menu (Material-Related Q. Planning)
    MENUQP00
    QM: Enhancements in QP00 Area Menu (Inspection Planning)
    MENUQS00
    QM: Enhancements in QS00 Area Menu (Basic Data)
    MENUQT00
    QM: Enhancement in QT00 Area Menu (Test Equipment)
    MENUQV00
    QM: Enhancements in QV00 Area Menu (QM in SD)
    MENUQZ00
    QM: Enhancements in QZ00 Area Menu (Quality Certificate)
    MEQUERY1
    Enhancement to Document Overview ME21N/ME51N
    MEREQ001
    Customers' Own Data in Purchase Requisition
    MEVME001
    WE default quantity calc. and over/ underdelivery tolerance
    MGA00001
    Material Master (Industry): Checks and Enhancements
    MGA00002
    Material Master (Industry): Number Assignment
    MGA00003
    Material Master (Industry and Retail): Number Display
    MGV00001
    Material Master (Industry): ALE Distribution
    MGV00002
    Material Master (Industry): Read Values for Filter Objects
    MGV00003
    Material master (retail): ALE distribution
    MGW00001
    Material Master (Retail): Additional Data
    MGW00002
    Material Master (Retail): Number Assignment
    MKKS0001
    Variances: Automatic Job Scheduling in Subsequent Period
    MM06E001
    User exits for EDI inbound and outbound purchasing documents
    MM06E002
    IDOC processing for contracts in inbox
    MM06E003
    Number range and document number
    MM06E004
    Control import data screens in purchase order
    MM06E005
    Customer fields in purchasing document
    MM06E007
    Change document for requisitions upon conversion into PO
    MM06E008
    Monitoring of contr. target value in case of release orders
    MM06E009
    Relevant texts for "Texts exist" indicator
    MM06E010
    Field selection for vendor address
    MM06E011
    Activate PReq Block
    MM06L001
    Exits to determine ratings in vendor evaluation
    MM08R001
    User exits for ERS
    MM08R002
    User exit for tolerance checks
    MM61W001
    User exits in function module FORECAST environment
    MMAL0001
    ALE source list distribution: Outbound processing
    MMAL0002
    ALE source list distribution: Inbound processing
    MMAL0003
    ALE purcasing info record distribution: Outbound processing
    MMAL0004
    ALE purchasing info record distribution: Inbound processing
    MMDA0001
    Default delivery addresses
    MMFAB001
    User exit for generation of release order
    MPKB0001
    User's own functions in the Kanban processing
    MPKB0002
    Customer defined display in kanban board
    MPKC0001
    User exit for kanban calculation
    MPKD0001
    Kanban output as EDI
    MPKP0001
    Customer Defined Display in Kanban Board
    MPKR0001
    Customer fields in kanban control cycle
    MPR10001
    User Exits in TA MPR1 (External Forecast Transfer)
    MPRO0004
    Postprocessing of forecast errors and exception messages
    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
    MSSTV001
    Customer Exit 'Team Viewer': Exclude Manager
    MV56AINI
    Initialization of transaction control for transportation
    MVEIPREF
    User exits - Preference determination
    MWM2S001
    Exit to Determine 2-Step Picking Characteristic
    MWMBAP01
    Enhancement for BAPI WarehouseTransOrder.GetDetail
    MWMBAP02
    Enhancement for BAPI WarehouseStock.GetDetail
    MWMD0001
    Transfer order print via RLVSDR40
    MWMD0002
    Transfer order print as multiple process with RLKOMM40
    MWMIDI01
    Enhancement for error handling with IDOC inbox
    MWMIDI02
    Enhancement for mssge WMTOCO (Confirm transfer order) Inbox
    MWMIDI03
    Enhancement for mssge WMCATO (Cancel transfer order) Inbox
    MWMIDI04
    Enhancement for mssge WMBBIN (Lock storage bin) Inbox
    MWMIDI05
    Enhancement for mssge WMTREQ (Create transfer req.) Inbox
    MWMIDI06
    Enhancement for mssge WMSUMO (Move storage unit) Inbox
    MWMIDI07
    Enhancement for Output WMPIHU (Create Pick-HU) Inbound
    MWMIDO01
    Enhancement of IDOCs WMTOID01 (Transport request) Outbox
    MWMIDO02
    Enhancement of IDOCs WMCAID01 (Cancel transfer req.) Outbox
    MWMIDO03
    Enhancement of IDOCs WMRRID01 (release ref. no.) Outbox
    MWMIDO04
    Enhancement of IDOCs WMIVID01 (system inventory rec.) Outbox
    MWMIDO07
    Enhancement for error handling for IDOC inbox: PDC
    MWMIDO08
    Enhancement for message WMMBXY (goods movement)  Inbox
    MWMIDO09
    Enhancement for msg. WMINVE (count data, phys. invnt.) Inbox
    MWMIDO10
    Enhancement for msg. WMTORD (Generate transfer order) Inbox
    MWMIDO11
    Enhancement for message WMTORD: TO with several items
    MWMIDO12
    Enhancement for Output WMPIHU (Pick-HUs) Outbound
    MWMIDO13
    Extension for WMMBXY (subsequent tasks after goods movement)
    MWMK0001
    Warehouse management: Customer exit for storage unit number
    MWMMOB01
    Enhancement for Verification Field in the Warehouse Master
    MWMMOB02
    Extension for Barcode Translation
    MWMPP001
    Enhancement WM/PP Interface (automatic TR generation)
    MWMRF001
    RF: Influence Display of material description
    MWMRF100
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0100)
    MWMRF101
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0101)
    MWMRF102
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0102)
    MWMRF104
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0104)
    MWMRF105
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0105)
    MWMRF106
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0106)
    MWMRF107
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0107)
    MWMRF108
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
    MWMRF151
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
    MWMRF152
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
    MWMRF153
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
    MWMRF170
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0170)
    MWMRF202
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
    MWMRF203
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
    MWMRF204
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
    MWMRF205
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
    MWMRF212
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
    MWMRF213
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
    MWMRF221
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
    MWMRF302
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
    MWMRF303
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)
    MWMRF304
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0304)
    MWMRF305
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0305)
    MWMRF312
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0312)
    MWMRF313
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0313)
    MWMRF321
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0321)
    MWMRF400
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0400)
    MWMRF402
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0402)
    MWMRF403
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0403)
    MWMRF404
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0404)
    MWMRF405
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0405)
    MWMRF406
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0406)
    MWMRF410
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0410)
    MWMRF411
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0411
    MWMRF412
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
    MWMRF502
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0502)
    MWMRF503
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0503)
    MWMRF504
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0504)
    MWMRF505
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0505)
    MWMRF600
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0600)
    MWMRF601
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0601)
    MWMRF630
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
    MWMRF631
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
    MWMRF632
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
    MWMRF633
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0633)
    MWMRF634
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0634)
    MWMRF650
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
    MWMRF651
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0651)
    MWMRF700
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
    MWMRF701
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0701)
    MWMRF702
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
    MWMRF703
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0703)
    MWMRF704
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0704)
    MWMRF705
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0705)
    MWMRF760
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0760)
    MWMRF761
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0761)
    MWMRF762
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0762)
    MWMRF763
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0763)
    MWMRF764
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0764)
    MWMRF765
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0765)
    MWMRF766
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0766)
    MWMRF767
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0767)
    MWMRF768
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0768)
    MWMRF769
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0769)
    MWMRF777
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0777)
    MWMRF800
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0800)
    MWMRF801
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0801)
    MWMRF802
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0802)
    MWMRF803
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0803)
    MWMRF804
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0804)
    MWMRF805
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0805)
    MWMRF806
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0806)
    MWMRF807
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0807)
    MWMRF888
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0888)
    MWMRF889
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
    MWMRF998
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0998)
    MWMRF999
    ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0999)
    MWMRFCOD
    Enhancement for function codedisabling
    MWMRFDLV
    select delivery by user criteria
    MWMRFPRT
    Enhancement for printing
    MWMRFSRT
    ENHANCEMENT FOR TO SORTING
    MWMRFSSG
    user exit for sorting TOs in RF system-guided transaction
    MWMRFUP
    Customer defined general purpose pushbutton called from scr.
    MWMRP001
    Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
    MWMRP002
    Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
    MWMRP003
    Customer Exit for Replenishment using RLLNACH1
    MWMRP004
    User Exit for Replenishment using RLLNACH4
    MWMTO001
    Enhancements for end of transfer order generation
    MWMTO002
    Enhancements at end of transfer order confirmation
    MWMTO003
    Own stock placement strategy
    MWMTO004
    Own stock removal strategy
    MWMTO005
    Underdelivery
    MWMTO006
    Overdelivery and with restriction, also underdelivery
    MWMTO007
    Palletization and storage type search for stock placement
    MWMTO008
    Storage type search for stock removal
    MWMTO009
    Prevent the TA items being deleted
    MWMTO010
    Exit: Calculation of Total Planned TO Processing Time
    MWMTO011
    Correction of Planned Processing Time for TO Item
    MWMTO012
    Correction of Sorting and Split Transfer Order
    MWMTO013
    Stock Removal for Sev. Storage Types as in Stringent FIFO
    MWMTOAU1
    Own sel. of transfer reqs. for auto. transfer order creation
    MWMTOAU2
    Own selection for auto. transfer order creation via ref. no.
    MWMTOAU3
    Separate selection of posting changes for autom.TO creation
    MWMTR001
    Exits at the end of transfer rqmnt creation (IM,PP interf.)
    MYCATS01
    Enhancement of Picklists for CATS notebook
    MYCATS02
    Send Customer Table or Standard Texts to CATS notebook
    MYCATS03
    Supplement Offline Time Data
    MYCATS04
    CATS notebook: Influence Synchronization Messages
    Hope this will help.
    Regards,
    Naveen.

  • User exit for Purchase requisition

    Hello team
    At the time of creating the purchase requisition we want to know how much qty in order unit with their UOM .
    How to get this functions , Any user exit , Any sort of input will be highly appreciated
    Thanks
    JJ

    BAdI: Customer BAdI for Enjoy Purchase Requisition BAPIs
    Use
    This Business Add-In is used in the component MM-PUR.
    It makes available the two methods INBOUND and OUTBOUND.
    The INBOUND method (method for changing the import data of the Enjoy PR BAPIs) is invoked when the BAPIs PurchaseRequisition.CreateFromData1 and PurchaseRequisition.Change1 are invoked, before the data is passed on to mapping. Call up transaction code SWO1 and choose the business object BUS2105 (inbound delivery).
    The Inbound method (method for changing the export data of the Enjoy PR BAPIs) makes available the parameters passed on to the function modules BAPI_PR_CREATE and BAPI_PR_CHANGE.
    The Outbound method offers the parameters that can be returned to the function modules BAPI_PR_CREATE, BAPI_PR_CHANGE, and BAPI_PR_GETDETAIL.
    For more information, refer to the interface documentation: IF_EX_ME_BAPI_PR_CREATE_02
    Standard settings
    The BAdI can be used multiple times.
    There is no default implementation.
    Information about the implementation of BAdIs in the context of the Enhancement Concept is available in the SAP Library for SAP NetWeaver under BAdIs - Implementation.
    Example
    The class CL_EXM_IM_ME_BAPI_PR_CUST is available for an example implementation.

  • User Exits for Inbound Process

    hi all
    can any one please give some example user exits in inbound process and explain the omportance of user exits
    Thank you,
    Swapna

    hi
    Userxits allow us to add our own functionality to SAP standard program
    without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
    Types of User exits
    1. Menu Exits
    2.Function exits
    3.Table exits
    4.Screen exits
    5.Keyword exits
    6.Field exits.
    also refer to the links below.. can get more info on user exits
    list of user exits
    http://www.planetsap.com/userexit_main_page.htm
    can also get the list of user exits thru..
    Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
    User Exits Notes:
    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://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    below are some of the useful invound and outbound userexits
    <b>IDoc Inbound User Exits</b>
    1.     ACC_BILLING
    Accounting: Post invoice (OAG: LOAD RECEIVABLE)
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    2.     ACC_EMPLOYEE_EXP
    FI/CO: HR posting GL (AcctngEmplyeeExenses)
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    3.     ACC_EMPLOYEE_PAY
    FI/CO: HR posting AP (AcctngEmplyeePaybles)
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    4.     ACC_EMPLOYEE_REC
    FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    5.     ACC_GL_POSTING
    Accounting: General G/L account posting
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    6.     ACC_GOODS_MOVEMENT
    Accounting: Post goods movement (OAG: POST JOURNAL)
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    7.     ACC_INVOICE_RECEIPT
    Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
    •     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    8.     ACLPAY Accounting: Inbound invoice
    •     ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
    •     ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
    •     ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
    9.     ACLREC
    Accounting: Billing document
    •     ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
    •     ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
    •     ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
    10.     ACPJMM
    Posting in accounting from materials management
    •     ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
    11.     ARTMAS
    Create and change of material master (Retail)
    •     MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
    12.     BLAOCH
    Purchasing contract change
    •     MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
    •     MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
    •     MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
    13.     BLAORD
    Purchasing contracts
    •     MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
    •     MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
    •     MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
    14.     BLAREL
    Release order documentation for distributed contracts
    •     MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
    15.     COND_A
    Conditions: master data for price determination
    •     VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
    •     VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
    16.     CREMAS
    Distribute vendor master
    •     VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
    17.     DEBMAS
    Customer master
    •     VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
    18.     DELINS
    Delivery schedule/JIT schedule
    •     VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
    •     VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
    •     VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
    •     VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
    19.     DESADV
    Delivery: Shipping notification
    •     LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
    •     MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
    •     V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    •     V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    •     V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    •     V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    •     V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    •     V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    20.     DOCMAS
    Master document
    •     CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
    21.     DOLMAS
    Document-object links
    •     CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
    22.     EDLNOT
    EDL delivery notes
    •     VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
    •     VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
    •     VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
    •     VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
    23.     FIDCC1
    Send entire FI documents (user exit 003/4)
    •     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    •     F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
    •     F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    •     F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
    24.     FIDCC2
    Send entire FI documents (user exit 005/6)
    •     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    •     F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
    •     F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    •     F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
    25.     FIDCMT
    Sending single items for FI-GL
    •     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    •     F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    26.     FINSTA
    Bank Statement
    •     FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
    •     FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
    27.     FIROLL
    General ledger rollup for FI-GL (delta f. line items FIDCMT)
    •     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    28.     GSVERF
    Cred. memo procedure
    •     VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
    •     VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
    •     VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
    29.     HRMD_A
    HR: Master data and organizational data (appl. system)
    •     RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
    •     RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
    •     RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
    30.     INFREC
    Purchasing info record
    •     MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
    •     MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
    31.     INVOIC
    Invoice / Billing document
    •     FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
    •     FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
    •     FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
    •     FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
    •     FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
    •     FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
    •     FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
    •     FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
    •     FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
    •     FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
    •     MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
    •     MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
    •     MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
    •     MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
    •     MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
    32.     LIKOND
    Listing conditions
    •     WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
    33.     MATMAS
    Material Master
    •     MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
    34.     MRESCR
    Create reservation
    •     SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
    35.     ORDCHG
    Purchase order/order change
    •     MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
    •     MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
    •     VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
    •     VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
    •     VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
    •     VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
    •     VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
    •     VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
    •     VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
    •     VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
    •     VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
    •     VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
    •     VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
    36.     ORDERS
    Purchase order / order
    •     MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
    •     MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
    37.     ORDERS
    Purchase order / order
    •     MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
    •     MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
    •     VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
    •     VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
    •     VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
    •     VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
    •     VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
    •     VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
    •     VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
    •     VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
    •     VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
    •     VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
    •     VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
    •     WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
    38.     ORDRSP
    Purchase order / order confirmation
    •     MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
    •     MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
    •     MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
    •     WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
    39.     PORDCR
    Create purchase order
    •     SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
    40.     PREQCR
    Create purchase requisition
    •     SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
    41.     PROACT
    Stock and sales data
    •     WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
    42.     REMADV
    Payment advice
    •     FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
    •     FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
    43.     REQOTE
    Inquiry
    •     VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
    •     VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
    •     VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
    •     VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
    •     VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
    •     VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
    •     VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
    •     VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
    •     VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
    •     VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
    •     VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
    44.     SBINV
    Credit memo procedure with invoice creation
    •     VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
    •     VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
    •     VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
    •     VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
    •     VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
    45.     SDPACK
    Packing confirmation
    •     VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling -  Inbound IDoc
    •     VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
    46.     SDPICK
    Picking confirmation
    •     VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling -  Inbound IDoc
    •     VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
    47.     SHP_IBDLV_CONFIRM_DECENTRAL
    Confirmation (Inbound Delivery)
    •     V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
    48.     SHP_IBDLV_SAVE_REPLICA
    BAPI Function Module for Duplication of Outbound Deliveries
    •     V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
    49.     SHP_OBDLV_CONFIRM_DECENTRAL
    Confirmation (Customer Delivery)
    •     V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
    50.     SHP_OBDLV_SAVE_REPLICA
    BAPI Function Module for Duplication of Outbound Deliveries
    •     V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
    51.     SHPCON
    Delivery: Shipping confirmation
    •     V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    •     V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    •     V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    •     V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    •     V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    •     V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    52.     SHPMNT
    Shipping outbound
    •     V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
    •     V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
    •     V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
    53.     SRCLST
    Source List
    •     MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
    •     MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
    54.     SRVMAS
    Master data service master
    •     BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
    •     BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
    55.     TPSSHT
    Shipping planning system: Transfer planned shipments
    •     V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
    •     V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
    •     V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
    56.     WHSCON
    Delivery: Stock confirmation
    •     V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    •     V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    •     V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    •     V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    •     V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    •     V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    57.     WMBBIN
    Block Storage Bins
    •     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
    58.     WMCATO
    Reversal/Reversal request for transfer order
    •     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
    59.     WMINVE
    Inventory count input
    •     MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
    •     MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    60.     WMMBXY
    IDoc Report goods movements in IM
    •     MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
    61.     WMSUMO
    Move storage unit
    •     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
    62.     WMTOCO
    Transfer order
    •     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
    63.     WMTORD
    Transfer order
    •     MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
    •     MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
    64.     WMTREQ
    Create/Cancel transfer order
    •     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    •     MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
    65.     WPUBON
    POS interface: Upload sales documents (compressed)
    •     WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
    •     WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
    •     WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
    66.     WPUFIB
    POS interface: Upload Fin.Acc. interface SRS/POS
    •     WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
    •     WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
    67.     WPUFIB
    POS interface: Upload Fin.Acc. interface SRS/POS
    •     WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
    68.     WPUKSR
    POS upload cashier data
    •     WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
    •     WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
    •     WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
    69.     WPUUMS
    POS interface: Upload sales data (compressed)
    •     WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
    •     WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
    •     WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
    70.     WPUWBW
    POS interface: Upload goods movements
    •     WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
    •     WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
    •     WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
    •     WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
    71.     WVINVE
    Store physical inventory / sales price revaluation
    •     WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
    •     WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
    <b>IDoc Outbound User Exits</b>
    72.     ACCONF
    Confirmation of IDoc processing from the application
    •     ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
    73.     ACLPAY
    Accounting: Inbound invoice
    •     ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
    •     ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
    •     ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
    •     ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
    74.     ACPJMM
    Posting in accounting from materials management
    •     ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
    •     ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
    75.     ARTMAS
    Create and change of material master (Retail)
    •     MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
    76.     BLAORD
    Purchasing contracts
    •     MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
    •     MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
    77.     BLAREL
    Purchasing contracts
    •     MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
    78.     COND_A
    Conditions: master data for price determination
    •     VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
    •     VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
    79.     CREMAS
    Distribute vendor master
    •     VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
    80.     DEBMAS
    Customer master
    •     VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
    81.     DELPKB
    KANBAN call
    •     MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
    •     MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
    82.     DIRDEB
    Preauthorized withdrawal
    •     FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
    83.     DOCMAS
    Master document
    •     CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
    •     CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
    84.     DOLMAS
    Document-object links
    •     CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
    •     CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
    85.     FIDCC1
    Send entire FI documents (user exit 003/4)
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    •     F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
    •     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    86.     FIDCC2
    Send entire FI documents (user exit 005/6)
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    •     F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
    •     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    87.     FIDCMT
    Sending single items for FI-GL
    •     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
    88.     FIPAYM
    Payment data
    •     FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
    •     FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
    89.     FIROLL
    General ledger rollup for FI-GL (delta f. line items FIDCMT)
    •     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
    90.     GSVERF
    Cred. memo procedure
    •     MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
    91.     HRMD_A
    HR: Master data and organizational data (appl. system)
    •     RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
    •     RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
    •     RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
    92.     INFREC
    Purchasing info record
    •     MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
    93.     INVOIC
    Invoice / Billing document
    •     LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
    •     LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
    •     LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
    •     LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
    94.     KANBAN
    KANBAN call
    •     MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
    •     MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
    95.     LIKOND
    Listing conditions
    •     WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
    96.     MATMAS
    Material Master
    •     MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
    97.     ORDCHG
    Purchase order/order change
    •     MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
    98.     ORDERS
    Purchase order / order
    •     MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
    •     MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
    99.     ORDRSP
    Purchase order / order confirmation
    •     MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
    •     MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
    •     MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
    •     SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
    •     SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
    •     SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
    •     SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
    •     SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
    •     SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
    •     SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
    •     SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
    •     WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
    •     WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
    100.     PAYEXT
    Extended payment order
    •     FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
    •     FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
    •     FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
    •     FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
    101.     PICKSD
    Picking data confirmation to customer delivery
    •     VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
    102.     PRDCAT
    Product Catalog
    •     WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
    103.     PRDPOS
    Product catalog item
    •     WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
    104.     PRICAT
    Price list / catalog
    •     VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
    •     VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
    •     VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
    105.     PROACT
    Stock and sales data
    •     WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
    106.     REMADV
    Payment advice
    •     FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
    107.     REQOTE
    Inquiry
    •     VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
    •     VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
    •     VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
    •     VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
    •     VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
    •     VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
    •     VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
    •     VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
    108.     SRCLST
    Source List
    •     MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
    109.     SRVMAS
    Master data service master
    •     BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
    •     BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
    110.     SYPART
    Partner profiles
    •     SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
    •     SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
    •     SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
    •     SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
    •     SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
    •     SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
    •     SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
    111.     TPSDLS
    Shipping planning system: Transfer delivery
    •     V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
    •     V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
    •     V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
    •     V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
    •     V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
    •     V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
    •     V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
    112.     WBBDLD
    Assortment list: Material data
    •     WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
    113.     WMCATO
    Reversal/Reversal request for transfer order
    •     MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
    114.     WMINVE
    Inventory count input
    •     MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
    115.     WMRREF
    Release reference number
    •     MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
    116.     WMTORD
    Transfer order
    •     MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
    117.     WP_EAN
    POS interface: Upload / Download EAN assignments
    •     WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
    118.     WP_PER
    POS interface: Upload / Download person data
    •     WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
    •     WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
    119.     WP_PLU
    POS interface: Upload / Download material master
    •     WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
    •     WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
    120.     WPDCUR
    POS interface: Download exchange rates
    •     WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
    121.     WPDNAC
    POS interface: Download products
    •     WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
    •     WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
    122.     WPDSET
    POS interface: Download set assignments
    •     WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
    123.     WPDSET
    POS interface: Download set assignments
    •     WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
    124.     WPDTAX
    POS interface: Download tax rates
    •     WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
    125.     WPDWGR
    POS interface: Download material group master
    •     WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
    •     WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
    126.     WPUBON
    POS interface: Upload sales documents (compressed)
    •     WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
    127.     WTADDI
    Additionals
    •     WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
    128.     WTADDI_CVB1
    Additionals w/o 06
    •     WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
    General IDoc User Exits
    •     ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
    •     ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
    •     BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
    •     KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
    •     KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
    ===
    User exits for Pricing.
    1.•USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
    2.•USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
    3.•USEREXIT_FIELD_MODIFICATION
    4.•USEREXIT_FIELD_MODIFIC_KZWI
    5.•USEREXIT_FIELD_MODIFIC_KOPF
    User exits for Sales order
    1•USEREXIT_DELETE_DOCUMENT
    2•USEREXIT_FIELD_MODIFICATION
    3.•USEREXIT_MOVE_FIELD_TO_VBAK
    4.•USEREXIT_NUMBER_RANGE
    5.•USEREXIT_SAVE_DOCUMENT
    User exits for billing
    1.•USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
    2.•USEREXIT_ACCOUNT_PREP_KOMPCV
    3•USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
    4•USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
    5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
    ====
    Reward if USeful
    Thanx & regards
    Naren..

  • Debugging inbound idoc user exit

    Hi all,
    I have a client who wishes to do some data validation when creating an inbound idoc.  We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
    The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
    Cheers,
    Stephen

    go thru the below information.
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    You need to excahnge data between systems you need an interface as medium for data transfer.
    IDoc also treat one of the interface options for data transfer.
    Check this link
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    IDOC Debugging:
    1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
    2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
    For outbound function module debugging you can use the following:
    1) RBDMIDOC - for master IDocs configured via change pointers.
    2) RSNASTED - for transaction IDocs with output/message control.
    3) RSEOUT00 - For IDoc whose status is "to be processed".

  • Bapi,idoc,user exits

    hi, im learner i want to need  some idea in  user exits,bapi,idoc any body having documents on above topics plz to send me...............plz

    Check these links..
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    New to enhancements
    creation of table in ecc6
    for Function module exits
    New to ABAP Enhancements
    For menu Exits and screen exit
    USER EXIT
    Search through www.enips.com.
    You can find lot of material there.
    BADI's
    http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm
    http://support.sas.com/rnd/papers/sugi30/SAP.ppt
    http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
    http://members.aol.com/_ht_a/skarkada/sap/
    http://www.ct-software.com/reportpool_frame.htm
    http://www.saphelp.com/SAP_Technical.htm
    http://www.kabai.com/abaps/q.htm
    http://www.guidancetech.com/people/holland/sap/abap/
    http://www.planetsap.com/download_abap_programs.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
    /people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
    /people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
    User Exits
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    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
    TO find all BADI's
    Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
    1) Goto se24 (Display class cl_exithandler)
    2) Double click on the method GET_INSTANCE.
    3) Put a break point at Line no.25 (CASE sy-subrc).
    Now
    4) Execute SAP standard transaction
    5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
    6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
    7) This way you will find all the BADIs called on click of any button in any transaction.
    A. BAdI Definition
    1. SE18
    2. Enter the name for the BAdI to be created in customer namespace and press "Create".
    3. Enter a definition for your BAdI and on the interface tab enter a name for the BAdI interface. SAP proposes a name and it is pretty good. Meanwhile a BAdI class is also created which is not in our concern.
    e.g for "ZTEST", SAP proposes "ZIF_EX_TEST" for the interface and "ZCL_EX_TEST" for the class.
    4. Save your BAdI.
    5. Double-click on the interface name. It will pass to a Class Builder session to make you implement your interface. If you are not familiar to the Class Builder; it's a bit like Function Builder and it will be easy to discover its procedure.
    6. Save and activate your interface.
    B. Calling your BAdI from an application program
    1. Declare a reference variable with reference to the Business Add-In interface.
    e.g. DATA exit_ref TYPE REF TO zif_ex_test.
    2. Call the static method GET_INSTANCE of the service class CL_EXITHANDLER. This returns an instance of the required object.
    e.g.
    CALL METHOD CL_EXITHANDLER=>GET_INSTANCE
    CHANGING instance = exit_ref .
    3. After those two steps, you can now call all of the methods of the BAdI where it is required in your program. Make sure you specify the method interfaces correctly.
    C. BAdI Implementations
    1. SE19
    2. Enter the name for the BAdI implementation to be created in customer namespace and press "Create".
    3. It will request the BAdI definition name to which this implementation will be tied.
    4. Enter a definition for your implementation and on the interface tab enter a name for the implementing class. Again SAP proposes a name and it is pretty good.
    e.g for "ZIMPTEST", SAP proposes "ZCL_IM_IMPTEST".
    5. Save your implementation.
    6. To implement a method, just double-click on the method name and you will be taken to the Class Builder to write the code for it. Here you redefine the BAdI interface methods.
    7. You must activate your implementation to make it executable. You can only activate or deactivate an implementation in its original system without modification. The activation or deactivation must be transported into subsequent systems
    Regards,
    Balaji Reddy G
    ***Rewards if answers are helpful

Maybe you are looking for

  • Essbase Dimension build error and Unable to Stop/Start Application

    Hi All, I am trying to build the dimendion in the ASO application it is throwing the Error meaasage " Dimension Biuld failed , ther may be problem in allocating memory". While i am trying to and Start/Stop my respective Application it is throwing the

  • Text ID to be copied automatically in other Ssles Document.

    Hi Guru's, I want to know that a Text ID - 0001 is created and included in the Text Procedure which is assigned to Sales Order Type, the same Text ID - 0001 is also included in the Text Procedure which is assigned to for a billing Type - F2. Now the

  • Vertically align middle input text in a text box

    I'm creating Flash-based software that has text boxes where users write in the answers to questions. I want the text that the user types to be vertically aligned to the middle of the text box, so that even if the response is two or three lines, it is

  • Exporting RAW masters of RAW-JPEG Pairs

    Is there any way to export only the RAW master of a RAW-JPEG pair?  I always shoot both RAW and JPEG.  In my workflow, I first import into Aperture the JPEG's.  I then group into stacks, choose my stack picks, and finally rate all my stack picks.  I

  • Error in bringing up the database instance

    Hi When I try to bring up the database using the addbctl.sh script in 11i following errors are shown : ORA-16014: log 4 sequence# 14351 not archived, no available destinations ORA-00312: online log 4 thread 1: '/apps/prodapps/proddata/log04a.dbf' ORA