Missing English documentation for WPUE0002 enhancemnt user-exits

Hi all,
I'd like to change some segment fields data before processing IDoc type WPUWBW, and I thought user-exit  EXIT_SAPLWPUE_141 from WPUE0002 enhancement could help me to do so.
But, when I search for documentation on this module it doesn't exist in English, only in German. How can I get it in English?
Or, anyone could tell me how to use it? Any examples?
Thanks very much in advance,
Maite.

Hello Maite,
just a brief summary of the documentation:
Function module to check and/or modify IDOCs, before the POS inbound processing
The original IDOC is transfered in table INPUT_IDOC_SEGMENTS of parameter I_INTERFACE. Only the modified segments have to be exported in table OUTPUT_CHANGED_IDOC_SEGMENTS.
Log of modifications (if not switched off via parameter O_NO_LOGGING_REQUIRED):
- EDI log - logs the modified segments (same as for modifications in EDI editor)
- POS log - logs the modifications for each field
   O_NO_LOGGING_REQUIRED  =
   'P' write only POS log
   'X' write only EDI log
   'A' write minimum EDI log (one record per change transaction, independant from the no. of changes)
Use parameter O_STOP_IDOC_PROCESSING to stop the IDOC processing. POS-Status 4 "refused by system" is set for the IDOC. For IDOCs with POS status 4, the user can decide, to process the IDOC. In this case, the parameter shouldn't be set again. The import table I_INTERFACE-WPLST contains records with "VERBUCHUNG" (UPDATE?) = '4' for the segments, the user decided to process again.
When the IDOC has been processed, it cannot be refused completely. If parameter O_STOP_IDOC_PROCESSING is set in this case, the processing will be cancelled and message WP032 is written to the log.
Messages for the processing logs can be exported in table OUTPUT_ERROR_MESSAGES.
- Raising exceptions will cause a short dump. You can use MESSAGE ... RAISING to transfer error messages into the protocol.
- Commit work not allowed
- All database changes have to be done by update modules.
Best regards
Stephan

Similar Messages

  • Hi Can body send links & Material For  Bapi, Badi,User-exits

    Hi Abapers,
                       Can body send links & Material For  Bapi, Badi,User-exits, This is my mail id [email protected]
    With Regards
    Bhaskar rao.M

    Hi Bhaskar,
    User Exit
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.planetsap.com/userexit_main_page.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    USER EXITS
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
    BADI(Business Add-In) is the object oriented method of user exits...
    Each BAdI has a definition and more than one implementation. The definition means the methods(in class concept) that are used for performing various functions. The BAdI definition can be viewed in SE18 transaction(for standard ones) and user-defined BAdIs can be created in the same transaction as well.
    When you create a BAdI definition, an class interface will be automatically created and you can define your methods in the interface. The implementation of the methods can be done in SE19 transaction
    Check these links for info about badi..
    BADI's
    BADI's
    http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm
    http://support.sas.com/rnd/papers/sugi30/SAP.ppt
    BADI's
    BADI's
    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
    http://www.esnips.com/web/BAdI
    http://www.allsaplinks.com/badi.html
    New to Badi
    Intro.....
    http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
    diff betweem badi n customer exits........
    http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
    BAPI
    BAPI
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    List of all BAPIs
    http://www.planetsap.com/LIST_ALL_BAPIs.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sappoint.com/abap/bapiprg.pdf
    http://www.sappoint.com/abap/bapiactx.pdf
    http://www.sappoint.com/abap/bapilst.pdf
    http://www.sappoint.com/abap/bapiexer.pdf
    http://service.sap.com/ale
    http://service.sap.com/bapi
    http://www.planetsap.com/Bapi_main_page.htm
    http://www.topxml.com/sap/sap_idoc_xml.asp
    http://www.sapdevelopment.co.uk/
    http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
    Regards,
    Priyanka.

  • Name of the structure needed for sales order user exit

    Hi,
    I am planning to write a user exit which will insert the data into my ztable the moment the new sales order is created and is saved.
    I have identified FORM USEREXIT_SAVE_DOCUMENT as the necessary user exit. But the problem is that while inserting the data into the ztable I cannot insert the data from vbak as the data will be inserted into this table after the SO is saved.
    Thus I need to identify a structure which is used to populate the vbak table so that it simultaneously inserts the data in the ztable as well. Can anyone help me with the name of the structure so that these fields i.e. vbeln, vkorg, vtweg, spart are inserted into my ztable?
    Also need to know how to convert the net value i.e. vbak-netwr in Indian Rupees as it gets stored as Dollars ....
    Thanks,
    Vinod.

    Hi,
    One of the structure being used is RV45A, there are several other str's being used as well for various calculations,
    check out program SAPMV45A for the same.
    & in order to convert vbak-netwr to rupees use the below statemetnt,
    WRITE vbak-netwr TO zvbak-netwr CURRENCY INR.
    Regards,
    Raghavendra
    Message was edited by:
            raghavendra ay

  • Request for info. on USER EXIT/BADI for FB60

    Hi,
    This is with reference to FB60 user exit/badi for with holding tax.I want to use the customized table for withholding tax.
    ]Please guide some alternative solution rather than user exit and badi.
    I dont think the following user exit and badi are used for withholding tax.
    I done some analysies.I didnt find any user exit/badi related to withholding tax.I found the following
    F050S001 FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002 FIDCC1: Change IDoc/do not send
    F050S003 FIDCC2: Change IDoc/do not send
    F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005 FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006 FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007 FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001 Balance Sheet Adjustment
    FARC0002 Additional Checks for Archiving MM Vendor Master Data
    FEDI0001 Function Exits for EDI in FI
    RFAVIS01 Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00 Line item display: Checking of selection conditions
    RFKORIEX Automatic correspondence
    SAPLF051 Workflow for FI (pre-capture, release for payment)
    Badi
    FQST_CALC_COUNTRY,FQST_CIN_WITHITEM are related with withholding tax and they are for country specific such as India.
    Every expert answer will be rewarded.
    Thanks in advance
    Cra

    Try Business Transaction Events. Transaction code BERP.
    Regards,
    Zoltá

  • Help me for finding out user-exits in sap

    hi,
    i am subhasis . i want to know how u will know where the user-exits available.
    please replay.

    Hi,
    Go through this program and another way is there go through that also.
    1) Open CMOD(Project maintenance) Transaction. Enter a project name starting with Z. Press enter.
    2) Goto Enhancement window by clicking the enhancement button in the application tool bar.
    3) Write SUSR0001 in the enhancement column and press enter.
    4) Goto Components window (It will show all the exits included in this enhancement), in our case only one Function Exit will be shown.
    5) Double click on the Function exit EXIT_SAPLSUSF_001.  
         The following function source code will be displayed in the function editor
    just run this report u get badi
    REPORT ZNEGI16 .
    TABLES : TSTC,
    TADIR,
    MODSAPT,
    MODACT,
    TRDIR,
    TFDIR,
    ENLFDIR,
    SXS_ATTRT ,
    TSTCT.
    DATA : JTAB LIKE TADIR OCCURS 0 WITH HEADER LINE.
    DATA : FIELD1(30).
    DATA : V_DEVCLASS LIKE TADIR-DEVCLASS.
    PARAMETERS : P_TCODE LIKE TSTC-TCODE,
    P_PGMNA LIKE TSTC-PGMNA .
    DATA wa_tadir type tadir.
    START-OF-SELECTION.
    IF NOT P_TCODE IS INITIAL.
    SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.
    ELSEIF NOT P_PGMNA IS INITIAL.
    TSTC-PGMNA = P_PGMNA.
    ENDIF.
    IF SY-SUBRC EQ 0.
    SELECT SINGLE * FROM TADIR
    WHERE PGMID = 'R3TR'
    AND OBJECT = 'PROG'
    AND OBJ_NAME = TSTC-PGMNA.
    MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
    IF SY-SUBRC NE 0.
    SELECT SINGLE * FROM TRDIR
    WHERE NAME = TSTC-PGMNA.
    IF TRDIR-SUBC EQ 'F'.
    SELECT SINGLE * FROM TFDIR
    WHERE PNAME = TSTC-PGMNA.
    SELECT SINGLE * FROM ENLFDIR
    WHERE FUNCNAME = TFDIR-FUNCNAME.
    SELECT SINGLE * FROM TADIR
    WHERE PGMID = 'R3TR'
    AND OBJECT = 'FUGR'
    AND OBJ_NAME EQ ENLFDIR-AREA.
    MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
    ENDIF.
    ENDIF.
    SELECT * FROM TADIR INTO TABLE JTAB
    WHERE PGMID = 'R3TR'
    AND OBJECT in ('SMOD', 'SXSD')
    AND DEVCLASS = V_DEVCLASS.
    SELECT SINGLE * FROM TSTCT
    WHERE SPRSL EQ SY-LANGU
    AND TCODE EQ P_TCODE.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) P_TCODE,
    45(50) TSTCT-TTEXT.
    SKIP.
    IF NOT JTAB[] IS INITIAL.
    WRITE:/(105) SY-ULINE.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    Sorting the internal Table
    sort jtab by OBJECT.
    data : wf_txt(60) type c,
    wf_smod type i ,
    wf_badi type i ,
    wf_object2(30) type C.
    clear : wf_smod, wf_badi , wf_object2.
    Get the total SMOD.
    LOOP AT JTAB into wa_tadir.
    at first.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 SY-VLINE,
    2 'Enhancement/ Business Add-in',
    41 SY-VLINE ,
    42 'Description',
    105 SY-VLINE.
    WRITE:/(105) SY-ULINE.
    endat.
    clear wf_txt.
    at new object.
    if wa_tadir-object = 'SMOD'.
    wf_object2 = 'Enhancement' .
    elseif wa_tadir-object = 'SXSD'.
    wf_object2 = ' Business Add-in'.
    endif.
    FORMAT COLOR COL_GROUP INTENSIFIED ON.
    WRITE:/1 SY-VLINE,
    2 wf_object2,
    105 SY-VLINE.
    endat.
    case wa_tadir-object.
    when 'SMOD'.
    wf_smod = wf_smod + 1.
    SELECT SINGLE MODTEXT into wf_txt
    FROM MODSAPT
    WHERE SPRSL = SY-LANGU
    AND NAME = wa_tadir-OBJ_NAME.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    when 'SXSD'.
    For BADis
    wf_badi = wf_badi + 1 .
    select single TEXT into wf_txt
    from SXS_ATTRT
    where sprsl = sy-langu
    and EXIT_NAME = wa_tadir-OBJ_NAME.
    FORMAT COLOR COL_NORMAL INTENSIFIED ON.
    endcase.
    WRITE:/1 SY-VLINE,
    2 wa_tadir-OBJ_NAME hotspot on,
    41 SY-VLINE ,
    42 wf_txt,
    105 SY-VLINE.
    AT END OF object.
    write : /(105) sy-ULINE.
    ENDAT.
    ENDLOOP.
    WRITE:/(105) SY-ULINE.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No.of Exits:' , wf_smod.
    WRITE:/ 'No.of BADis:' , wf_badi.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(105) 'No userexits or BADis exist'.
    ENDIF.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(105) 'Transaction does not exist'.
    ENDIF.
    AT LINE-SELECTION.
    data : wf_object type tadir-object.
    clear wf_object.
    GET CURSOR FIELD FIELD1.
    CHECK FIELD1(8) EQ 'WA_TADIR'.
    read table jtab with key obj_name = sy-lisel+1(20).
    move jtab-object to wf_object.
    case wf_object.
    when 'SMOD'.
    SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
    when 'SXSD'.
    SET PARAMETER ID 'EXN' FIELD SY-LISEL+1(20).
    CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
    Hi Crm_learner,
    gothrough this navigation.
    se93->provide for which transaction code u want to impliment the badi->display option->copy the package name.
    next
    se18->press f4 help->information system->provide the package name->enter
    It will display the all the badis.
    provode the badi name->select implimentation option in menubar->create->prvide the implimantation name->enter
    provide the implimantation shrt text->save the badi.
    Go for the interface option->double click onthe method->provide the coding in between method and endmethod. and active the badi.
    program automatically call this badi and execute u code.
    This is the badi.
    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. 
    Rewards some points.
    Rgds,
    P.Naganjana Reddy

  • Need Logic for writing the User exit

    Hi Gurus,
    I am writing the User Exit code to populate the 'Valid to' field in the data source.
    Technical Name - DATUB  and Type- DATS
    I am using the FM 'GET_STPO"
    My extract structure has following fields.
    MANDT
    MATNR
    WERKS
    STLAN
    STLNR
    STLAL
    STLTY
    STLKN
    STPOZ
    DATUV
    IDNRK
    PSWRK
    MEINS
    MENGE
    MTART
    DISMM
    DATUB
    I am not getting the DATUB value for some of the BOM Node Numbers(STLKN).
    Please suggest me as How Can I write the code?
    Thanks a lot.
    Shalaka.

    Hi ,
    You can also try this :
    int countold = 0;
    int countnew = 0;
    int k = 0;
    for(int i =0;i<var1.length;i++)
    countold = countnew + 1;
    countnew = countnew + Integer.parseInt(var1<i>);
    for( int j = countold-1 ;j<countnew;j++)
    result.addValue(var2[k]);
    k++;
    result.addContextChange();
    Regards,
    Ganesh

  • BPS Variable for hierarchy type User-Exit

    I try to make this type of variable.
    The variable is NCSTOPU, hierarchy is
    NHSTOPU like
    NHMAIN
    -- 4
        -- 401
        -- 402
        -- 403
      -- 5
         -- 501
         -- 502
         -- 503
    So The ABAP is
    FUNCTION ZCCB_AHR_VAR_HIER.
    *"*"Ëîêàëüíûé èíòåðôåéñ:
    *"  IMPORTING
    *"     REFERENCE(I_TYPE) TYPE  UPC_Y_VAR_TYPE
    *"     REFERENCE(I_AREA) TYPE  UPC_Y_AREA
    *"     REFERENCE(I_VARIABLE) TYPE  UPC_Y_VARIABLE
    *"     REFERENCE(IS_HIE_KEY) TYPE  UPC_YS_HIE_KEY
    *"  EXPORTING
    *"     REFERENCE(ET_HIE_NODES) TYPE  UPC_YT_HIESEL
    DATA ZHIER type upc_ys_hiesel.
    *CHANM  UPC_Y_CHANM
    *HIENM     UPC_Y_HIENM
    *HIEVER     UPC_Y_HIEVER
    *DATETO     UPC_Y_DATETO
    *NODENAME     UPC_Y_NODENAME
    *HIECHA     UPC_Y_CHANM
    *DUMMY_LEAF     UPC_Y_DUMMYLEAF
    *TO_CHADEP     UPC_YTO_CHADEP
    ZHIER-CHANM      = 'NCSTOPU'.
    ZHIER-HIENM      = 'NHSTOPU'.
    ZHIER-NODENAME   = '5'.
    ZHIER-HIEVER     = 'A'.
    ZHIER-HIECHA     = '5'.
    ZHIER-DUMMY_LEAF = ''.
    ZHIER-DATETO     = '99993112'.
    INSERT ZHIER INTO TABLE ET_HIE_NODES.
    ENDFUNCTION.
    But it doesn't work.
    The mistake is
    Selected node 5 does not exist
    The node 5  selected as the start value for characteristic 5 with the specified compound table does not exist in hierarchy NHSTOPU.
    What is the problem?

    Configuration of the variable:
    Variable Type - Hierarchy node,
    Characteristic - NCSTOPU,
    Hierarchy - NHSTOPU,
    Replacement type - user-exit,
    FUNCTION MODULE NAME - ZCCB_AHR_VAR_HIER.
    In the planning level the characteristic NCSTOPU is set with this variable.
    In the Layout  1) the characteristic NCSTOPU - Lead Column,
                         2) Hierarchy in the lead column -  Hierarchical Data Model, BW Hierarchy

  • BEx Analyzer : missing Selection screen for NON- SAP_ALL User

    we have upgrade our BW from 3.1 to BI 7.0. Now we are testing and detect that Queries which are started by User who has user specific roles (not SAP_ALL like we as developer) this Selection Screen is missing. This leads to a complete selection of all data of the cube and this leads to very long runtime or auto logout.
    What is wrong in our configuration?
    Has anybody made the same experience ?
    Thank You, Frank HInzmann
    Schindler Informatik Ebikon (Switzerland)

    Frank,
    Any chance that somehow that user has set personalisation on all the variable values?
    Regards
    Gill

  • Generic Table to a formal type - for master data user exit class

    Hello,
         I am attempting to setup an ABAP OO framework for extending master data with the CMOD exit, EXIT_SAPLRSAP_002.  My goal is to create generic base class, upcast to the actual extraction structure, apply the customizing data fields, and then return the full table to the exit.    The problem is that I_T_DATA, the internal table for return values is untyped and therefore generic.   I tried using a class parameter as “type ref to DATA”, but the upcast if failing is failing.  Can any one suggest:
    What parameter type should I use for the class method parameter?
    How do you upcast to the formal extract structure type?
    How do you assign the result back to the generic type?
    Thanks very much for the help!

    I ended up figuring out the answer after a bit more work.  In case it helps others, the keys points are:
    I_T_DATA exposed in EXIT_SAPLRSAP_00x is a dynamic internal table
    The reference to the table can be passed to a method parameter as a generic type, “TABLE”
    Though, to store the value in the class as a formally typed value, such as required by an attribute, the type must be cast to the type, “DATA”.
    For example:
    Public section
    Method CONSTRUCTUR
         IMPORTS
          PT_DATA TYPE TABLE.
    Assign data pointer to attribute
           GET REFERENCE OF PT_DATA INTO A_T_DATA.
    Endmethod.
    protected section.
      data A_T_DATA type ref to DATA .
    Hope that helps.

  • COPA Report Changes in KE30 for Configured materials - User Exit

    Dear all,
    We are having a configured material with BOM and we are using COPA Report.
    For a given material type we need the row "Other cost of Goods Sold" to be zero since it does not take into account the child materials.
    Is there any userexit to make this happen ??
    Thanks in advance.
    Regards,
    Vivek.

    Hi Vivek,
    KE30 is a Transaction code. If you want to copy a Report associated with this Transaction code then go to transaction code KE30 Provide the data a initial screen. Then go to Utilities->status. A popup screen will be displayed. In SAP data tab There is a field called Program. Copy that program name & go to transaction code SE80 & provide the program name & go for display. Here all the related screens, fields, tables etc. will be displayed then right click on the program name & select copy & provide the target program name starting from Z. Save & activate it.
    Note you can copy the standard program & copy it also but I think it will not take place the standard porgram, you will have to run the progam manually.
    I think BADI or BTE may be available for this transaction.
    Ashven

  • How to define a global field for use in User exit

    Hi All,
    I want to define a global flag field (say my_flag) in Function group VEDA. I need to set/reset it in exit EXIT_SAPLVEDA_003 and check its value in EXIT_SAPLVEDA_002.
    Can anyone help me out in this. Where can I define this field?
    Thanks.
    Regards,
    Riyaz

    I have created a customer table zflag1 which has one field z_flag and the correspopndiong data el;ement is 'zflag' and i also ccreated parameter ID in table TPARA and assigned tht parameter ID 'ZFLAG' to my data element.
    reward points if helps..
    in the Z include of Exit function 3 write -
    data :g_global like zflag1-z_flag.
    G_GLOBAL = 'X'.
    set parameter id 'ZFLAG' field g_global.
    and in the Z include of exit function 2 write  -
    DATA G_GLOBAL LIKE ZFLAG1-Z_FLAG.
    GET PARAMETER ID 'ZFLAG' FIELD G_GLOBAL.

  • Whether to go for bdc or user exits???

    hi,
    I have a reqirement like given below how should i proceed plz help me out.
    If pre-tax contribution percentage in field EEPCT from table P0169  is less than 6%, only first sequence of  customizing table V_74FF_C should run. It means, for employer contribution rule out of two sequences only one sequence shown  should run and stop, the rule variant should not process the next sequence shown.

    So, readiing between the lines, you've been given some work to do and you have no idea where to start or how to do it and you want someone on here to explain it for you?
    Why don't you go and sit down with your functional consultant and go through it with them - they should be able to explain what to do and where to do it.  You can then work with this and convert it to ABAP.

  • 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..

  • User Exit for credit management  at confirmed quantity in sales order

    Dear All ,
    kinldy tell how to define a user exit and where i can write for credit check to be done to the confirmed quantity in the sales order .
    Also pls tell me that how to define the user exit and attach to customer reserve field in the customising for automatic credit control .
    regards
    Baranidharan Ramar

    Hi
    The following is the information from the sap documentation...you can also refer from IMG - SD - System modification - userexit - userexit for credit check
    Credit Check
    If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    User exit for availability check
    User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
    This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
    Thanks,
    Ravi

  • User Exit for F-92 transaction!

    Hi everyone,
    I hope you all fine!
    I hope you guys could help me with this.  This is about user exit, I need one for the transaction F-92, when the user wants to sale a fixed asset I need to catch the fixed asset number to validate it, but I don't know if I'm doing something wrong with this user exits that I found here in the forum none of them stops when a type a break-point sentence.
    SAPLF051 Workflow for FI (pre-capture, release for payment)
    RFKORIEX Automatic correspondence
    RFEPOS00 Line item display: Checking of selection conditions
    RFAVIS01 Customer Exit for Changing Payment Advice Segment Text
    FEDI0001 Function Exits for EDI in FI
    FARC0002 Additional Checks for Archiving MM Vendor Master Data
    F180A001 Balance Sheet Adjustment
    F050S001 FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002 FIDCC1: Change IDoc/do not send
    F050S003 FIDCC2: Change IDoc/do not send
    F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005 FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006 FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007 FIDCCH Outbound: Influence on IDoc for Document Change
    Does any body know if there's any more user exit that are not listed in here for this transaction? or in the user exit listed above there's one that could stop at the break-point. but I'm not doing it correctly!
    I hope you guys could help me with this, I'll really appreciate it.
    Thanks for your time.
    Regards,
    Guillermo E.

    Hi Vinod,
    Thanks for your reply, I also tried as you told me to use the transaction OB28, but I'm having some problems to understand how to use it.  I found this documentation to create a user exit, here is the link:
    http://www.richard-harper.me.uk/Kb/showtext.aspx?id=0007c
    I followed the steps that it says, but the functional consultant can't see the new user exit that I'm trying to use.
    I hope somebody could help me to understand how to set up a user exit with the transaction GCX2, and how to set parameters to make to make a query to a custom table and return a value to trigger the validation.
    Or if I'm supposed to use another way to do it.
    Thanks for your time!
    Regards,
    Guillermo

Maybe you are looking for