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

Similar Messages

  • User Exit IDOC creation - When purchase order gets created

    Hi All,
    The requirement is whenever user creates a Purchase Order in the current SAP system an IDOC needs to get created and be sent to another SAP system where a Sales Order will be created.
    Can anybody suggest the correct User exit/enhancement at the time of Purchase order creation which could be used ?
    Also the function modules for creating the IDOCs within the user-exit.
    Thanks for your help.

    Hi Meghna,
    Your requirement is SAP standard function which means you don't have to use any user exit.
    What you need to do is configure output control, then when a PO saved, a idoc will send to vendor automaticly.
    Here is a step brief
    1. configure output type in NACE
    2. Add condition record in NACE
    3. Setup partner profile in WE20
    if you need detailed doc, give me your email, I can send you.
    Regards,
    Brown

  • Regarding Purchase order User-exit

    Hello friends,
    Here is the situation.
    when we create purchase order ... I need to modify the planned delivery field value under delivery tab at item level.
    For this I found user exit. 'EXIT_SAPMM06E_016' and I have written the logic in the include program.
    when I tested in debbugmode... the cursor is not at all comming to that point. It was failing always at the function module 'MODX_FUNCTION_ACTIVE_CHECK'.
    I don't know alwys active field showing blank. I think we need to activate the user exit some where. how to do and where to do?
    plese help me ..
    extract the code --from include program MM06EF0C_CUSTSCR1_ITEM_SET_D03
    User-Exit für Positionsfelder versorgen (PBO)
    FORM custscr1_item_set_data_pbo USING im_no_screen LIKE fc_call.
      DATA: l_enj_call TYPE c.
      STATICS: first_call(1) TYPE c VALUE 'X',
               active        LIKE sy-calld.
      IF NOT first_call IS INITIAL.
        CLEAR first_call.
        CALL FUNCTION 'MODX_FUNCTION_ACTIVE_CHECK'
          EXPORTING
            cprogname  = 'SAPMM06E'
            funcnumber = '016'
          IMPORTING
            active     = active
          EXCEPTIONS
            not_found  = 1
            OTHERS     = 2.
        IF NOT sy-subrc IS INITIAL.
          CLEAR active.
        ENDIF.
      ENDIF.
      CHECK NOT active IS INITIAL.         ==========================> always active sowing blank
      IF fc_vorga EQ cva_en.
        l_enj_call = 'X'.
      ELSE.
        l_enj_call = space.
      ENDIF.
    *-Define Fields:
      DATA: l_ci_ekpo LIKE ekpo_ci,
            lt_usr_tekpo LIKE bekpo OCCURS 0,
            lt_usr_teket LIKE beket OCCURS 0,
            lt_usr_tekkn LIKE ekknu OCCURS 0,
            lt_usr_tkomv LIKE tkomv OCCURS 0.
    *-Copy Tables:
      MOVE-CORRESPONDING ekpo TO l_ci_ekpo.
      lt_usr_tekpo[] = pot[].
      lt_usr_teket[] = ett[].
      lt_usr_tekkn[] = knt[].
      lt_usr_tkomv[] = tkomv[].
    *-User Exit
      CALL FUNCTION 'EXIT_SAPMM06E_016'
        EXPORTING
          i_ekpo      = ekpo
    ===============
    thanks in advance
    Regards
    Raghu

    Hi Raghunath
    I hope you have included your enhancement in a project and activated the project.
    1-Needed help
    2-SMOD and CMOD
    Hope it is helpful.
    Regards
    Neha

  • User Exit-Idoc extension customising

    Hello all,
    Can anyone tell me how I can establish a Link between a Basic idoc type and Idoc Extension?
    I wrote a INCLUDE programme in the USER EXIT SAPLVV01.
    I really appreciate your help.
    Note: Points for sure.
    Thank you

    Joslyn-
    The link between Basic IDOC type and IDOC extension is done in the partner profile first (WE20). After you have created an extension for your IDOC, you need to provide the same under Extension IDOC type in the outbound parameters of partner profile.
    I am not sure about your requirement but from the user exit you are using, I guess you have more than one extension for customer master IDOC and you want to choose one based on certain parameters. The import and tables parameters of this exit should provide you enough information to do the same.
    Let us know with specific questions if you need more info.
    KK

  • Query regarding User Exit

    Hi exps
    Could you please tell me , which user exits get triggered when I save
    Invoice List (T code  : VF22) producing Idoc.
    Also tell me whether the exit EXIT_SAPLVEDF_002 get triggered during this
    process or not ?           
    Let  me know soon
    Regards
    Tulip

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

  • User exit for incoming PO - (PO is created by CIFing TLB order to R/3)

    Hi All,
        I need to find out the APO INBOUND user exit for reciving the PO information from the connected R/3 system. Initially a TLB order is created in APO and CIFed to APO and after the PO is created in connected R/3 system this PO number and related information is CIFed back to APO and this TLB order is replaced by the R/3 PO number.
    Please help me outto gain full points.
    Thanks in Advance,
    Chandan Dubey

    Hi,
    I am not clear with ur query and therefore check out the list of Inbound and outbound Idoc user-exits:
    IDoc Inbound User Exits
    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
    IDoc Outbound User Exits
    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)
    Link for the same:
    http://erpgenie.com/abaptips/content/view/302/62/
    Pls reward helpful points.
    Regards,
    Ameet

  • User-exits for PO and MIGO

    Hello Experts
    i am having a requirement where in i will have to perform certain validations before posting PO and material document (MIGO). If these validations fail, PO or Material document should not be posted.
    i managed to find certain BADI and user-exits (MB_CF001 and MB_DOCUMENT_BADI) typically for MIGO but when tested they use to get triggered once these doucment numbers are generated.
    what i am looking at is cancel the process by giving the hard-error.
    thanks in advance.
    regards
    rajeev

    Hi,
    <b>User exits for MIGO:</b>
    MBCF0002 Customer function exit: Segment text in material doc. item
    MBCF0005 Material document item for goods receipt/issue slip
    MBCF0006 Customer function for WBS element
    MBCF0007 Customer function exit: Updating a reservation
    MBCF0009 Filling the storage location field
    MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0011 Read From RESB and RKPF For Print List in MB26
    MBCFC003 Maintenance of batch master data for goods movements
    MBCFC004 Maintenance of batch specifications for goods movements
    MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
    <b>User eits for PO:</b>
    These are the User exit for CO01 ( Create PO)
    CCOWB001 Customer exit for modifying menu entries
    COIB0001 Customer Exit for As-Built Assignment Tool
    COZF0001 Change purchase req. for externally processed operation
    COZF0002 Change purchase req. for externally procured component
    PPCO0001 Application development: PP orders
    PPCO0002 Check exit for setting delete mark / deletion indicator
    PPCO0003 Check exit for order changes from sales order
    PPCO0004 Sort and processing exit: Mass processing orders
    PPCO0005 Storage location/backflushing when order is created
    PPCO0006 Enhancement to specify defaults for fields in order header
    PPCO0007 Exit when saving production order
    PPCO0008 Enhancement in the adding and changing of components
    PPCO0009 Enhancement in goods movements for prod. process order
    PPCO0010 Enhancement in make-to-order production - Unit of measure
    PPCO0012 Production Order: Display/Change Order Header Data
    PPCO0013 Change priorities of selection crit. for batch determination
    PPCO0015 Additional check for document links from BOMs
    PPCO0016 Additional check for document links from master data
    PPCO0017 Additional check for online processing of document links
    PPCO0018 Check for changes to production order header
    PPCO0019 Checks for changes to order operations
    PPCO0021 Release Control for Automatic Batch Determination
    PPCO0022 Determination of Production Memo
    PPCO0023 Checks Changes to Order Components
    STATTEXT Modification exit for formatting
    I am giving you the list of all user exits available for ME21N:
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    M06B0004 Number range and document number
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06E0004 Changes to communication structure for release purch. doc.
    M06E0005 Role determination for release of purchasing documents
    ME590001 Grouping of requsitions for PO split in ME59
    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.
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    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
    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
    MRFLB001 Control Items for Contract Release Order
    For your purpose you can probably try MM06E005. Or you can also try BADI ME_PROCESS_PO_CUST.
    You can also check this BADI available for PO:
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    ME_BAPI_PR_CHANGE_01 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Chan
    ME_BAPI_PR_CHANGE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Chan
    ME_BAPI_PR_CREATE_01 BAdI: Enjoy BAPIs for Purchase Requisitions
    ME_BAPI_PR_CREATE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Crea
    ME_BSART_DET Change document type for automatically generated POs
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standa
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Cust
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Custom
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PURCHDOC_POSTED Purchasing Document Posted
    ME_RELEASE_CREATE BAdI: Release Creation for Sched. Agreemnts with Rel. Do
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_REQ_POSTED Purchase Requisition Posted
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Orde
    SMOD_MRFLB001 Control Items for Contract Release Order
    Transaction codes for BADI are:
    SE18 - Business Add-ins(BADI’s): Definition transaction
    SE19 - Business Add-ins(BADI’s): Implementation transaction
    SE24 - Class Builder
    Link for all user exits in SAP:
    http://www.easymarketplace.de/userexit.php
    Pls reward helpful points.
    Regards,
    Ameet

  • User Exit/ BADI for FB01

    Hi friends,
    The requirement is something like this.
    When we post a document using tcode FB01, in few cases we get a warning message
    "Tax entered incorrect (code P1, amount           0.00)". We get this Warning message, when we click on Save button.
    Now, the requirement is to capture this warning and replace this with an Error Message. If that is not possible, then when we get this warning, posting of document should not be allowed.
    I searched for some User Exit/ BADI with which i can acheive this, but could not find any. Could any one of you let me know how to acheive this?
    Thank you.
    Best Regards,
    Ram.

    Hello,
    user exits
    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
    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)
    BADIs
    AC_QUANTITY_GET      Transfer of Quantities to Accounting - Customer Exit
    BADI_ENJ_ALT_ADR     Go to alternative vendor/customer data
    BADI_F040_SCREEN_600 Screen Enhancement on F040 0600 Document Header
    BADI_FDCB_SUBBAS01   Screen Enhancement 1 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS02   Screen Enhancement 2 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS03   Screen Enhancement 3 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS04   Screen Enhancement 4 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS05   Screen Enhancement 5 on FDCB Basic Data Screen (010, 510)
    BADI_PRKNG_NO_UPDATE BAdI for Deactivating Update of Parked Documents
    F050S008             FIDCC1, FIDCC2 Inbound IDoc: Update Comparison Ledger
    FBAS_CIN_LTAX1F02    Tax interface
    FBAS_CIN_MF05AFA0    EWT - Downpayment Clearing - Tax transfer for CIN
    FI_AUTHORITY_ITEM    Extended Authorization Check for Document Display (FB03)
    FI_GET_INV_PYMT_AMT  BAdI for determining the payment amount for an invoice
    FI_HEADER_SUB_1300   Screen Enhancement for Document Header SAPMF05A
    FI_PAYREF_BADI_010   BAdI: Payment Reference Number
    FI_TRANS_DATE_DERIVE Derive BKPF-WWERT from Other Document Header Data
    INVOIC_FI_INBOUND    BADIs for Inbound IDoc INVOIC FI (Vendor Invoice)
    RFESR000_BADI_001    BAdI for Own Processing of POR Item
    Thank u,
    santhosh

  • User-Exit for the Me22n

    Hi,
       I am Mohan. I faced on Problem with the User Exit. I write the user exit for the ME21n for PO Creation. While Creation of the PO the Purchase Requition is mandatory. it is working for the ME21n. But PO creation is another two ways is there. Those are ME22N (Purchase order---> Create) and ME23N
    (Purchase order---> Create) for this case also my condition applicable but it is not working for this case. How to write the Code for this. by using Sy-ucomm  also. but it is not working.
    Please help me.
    Regards,
    Mohan

    Following the user exit's related to ME22N transaction.
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    M06B0004 Number range and document number
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06E0004 Changes to communication structure for release purch. doc.
    M06E0005 Role determination for release of purchasing documents
    ME590001 Grouping of requsitions for PO split in ME59
    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.
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    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
    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
    MRFLB001 Control Items for Contract Release Order
    Regards.

  • 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

  • Difference in user exit , fm and includes

    HI,
    What is user exit , function module and includes? What is the difference among them? When and how to use them? Please provide example.
    Regards,
    Pramod

    Hi Pramod,
    user exits, function modules and includes can not be compared to each other. Each one of them carry their own purpose and functionality.
    User exit's help you in achieving the additional functionality that standard SAP doesnt offer.
    For example, if your client requirement is add another tab in sales order in addition to the existing ones............it can be done using the user exit.
    SAP has provided several user exits through which you provide the additional functionality to the client without disturbing the SAP standard code.
    you can view SAP standard user exits using t-code: SMOD
    Function modules help you in carrying out a specific task. They can be called into a program to perform a particular task and are resuable any number of times i.e. can be called into any program to perform the same task.
    SAP has already provided many function modules, for example -  for determining exhange rates, reading texts etc.
    Apart from the SAP standard ones, you can also develop your own function module using transaction code SE37 and use them appropriately.
    Includes can be defined as sub programs.........they are part of a program. Include can either be local or global i.e. can be restricted to be used in a particular program and can be made available to other programs.
    Basically, a main program is divided into several includes for a better understanding.
    REWARD POINTS IF HELPFUL
    Regards
    Sai

  • User exit in F110

    Hello, in F110 transaction we need to modify the document type used by the payment run depending on the document type of the invoice (without using different payment methods). For example:
    Doc. type invoice 1 = IN   --> Doc. type payment doc. = PN
    Doc. type invoice 2 = IO   --> Doc. type payment doc. = PO
    Do you know some user-exit, BADI, BTE, etc we can use to influence this way in the payment run?
    Thanks in advance.
    EnriqueCC

    Dear EnriqueCC,
    Please check this sample program from other thread to find BADI and enhancement for a given transaction code. You just need to create a custom program in your system by cut and paste below codes.
    REPORT ZTEST.
    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.
    ENDCASE.
    Alternatively, you can do the following:
    1. For what ever transaction u want the enhancement .. just check for the System-->status (menu) and find out the PROGRAM name....
    2. Double click on to the program name and go inside the program (Abap editor)
    3. Search for "Call Customer-function " ... and u'll get some search results .. If u get results then u have enhancement in that tcode .....
    4. Then it actually calls a Function module .... copy the Function module name .... go to SE80 (object navigator) click on "Repository Information system" then Customer Enhancements .... Give the Function module name in the "Components" field and click Execute ....
    ull get a list of Enhancements related to that Componene....
    5. Choose which ever enhancement will suit ur business need ..
    6. Go to CMOD... create a project .... assign ur enhancement ... and then code ur logic.... activate ur enhancement in CMOD ....... Ur Buisness need will be solved...
    For a user exit......
    Finding whether there is any User Exit or not for tcode VA42
    1. For what ever transaction u want the user exit .. just check for the System-->status (menu) and find out the PROGRAM name.... ( The program name would be for our scenario "SAPMV45A" )
    2. Double click on to the program name and go inside the program (Abap editor)
    3. Search for the word "USEREXIT" .... u ll find all the user exits in the search result .. and find ur's then ...
    Hope this will help.
    Regards,
    Naveen.

  • User exits for tcode FBV0

    Hi,
    My requirement is that the user who has parked the document should not be able to post the parked document through tcode FBV0.
    Is there any user exit where in I can validate the current system user and the user who has parked the document?
    I have tried the user-exit SAPLF040,but this does not suffice my requirement.
    Also is it possible to define our own exits in tcode OB28?
    Regards,
    Rajeev

    Info on user exits can be found here http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    Transaction Code - FBV0                     Post Parked Document
    |Exit Name          |Description                                                              |
    |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                    |
    |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)                       |
    No of Exits:         13
    These are the user exits possible for FBV0
    <b>we can find user exit for any transaction, copy and run the following code in SE38</b>
    report z_find_userexit no standard page heading.
    *&  Enter the transaction code that you want to search through in order
    *&  to find which Standard SAP User Exits exists.
    *& Tables
    tables : tstc,     "SAP Transaction Codes
             tadir,    "Directory of Repository Objects
             modsapt,  "SAP Enhancements - Short Texts
             modact,   "Modifications
             trdir,    "System table TRDIR
             tfdir,    "Function Module
             enlfdir,  "Additional Attributes for Function Modules
             tstct.    "Transaction Code Texts
    *& Variables
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    *& Selection Screen Parameters
    selection-screen begin of block a01 with frame title text-001.
    selection-screen skip.
    parameters : p_tcode like tstc-tcode obligatory.
    selection-screen skip.
    selection-screen end of block a01.
    *& Start of main program
    start-of-selection.
    * Validate Transaction Code
      select single * from tstc
        where tcode eq p_tcode.
    * Find Repository Objects for transaction code
      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 = enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
        endif.
    * Find SAP Modifactions
        select * from tadir
          into table jtab
          where pgmid    = 'R3TR'
            and object   = 'SMOD'
            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:/(95) sy-uline.
          format color col_heading intensified on.
          write:/1 sy-vline,
          2 'Exit Name',
          21 sy-vline ,
          22 'Description',
          95 sy-vline.
          write:/(95) sy-uline.
          loop at jtab.
            select single * from modsapt
            where sprsl = sy-langu and
            name = jtab-obj_name.
            format color col_normal intensified off.
            write:/1 sy-vline,
            2 jtab-obj_name,
            21 sy-vline ,
            22 modsapt-modtext,
            95 sy-vline.
          endloop.
          write:/(95) sy-uline.
          describe table jtab.
          skip.
          format color col_total intensified on.
          write:/ 'No of Exits:' , sy-tfill.
        else.
          format color col_negative intensified on.
          write:/(95) 'No User Exit exists'.
        endif.
      else.
        format color col_negative intensified on.
        write:/(95) 'Transaction Code Does Not Exist'.
      endif.
    * Take the user to SMOD for the Exit that was selected.
    at line-selection.
      get cursor field field1.
      check field1(4) eq 'JTAB'.
      set parameter id 'MON' field sy-lisel+1(10).
      call transaction 'SMOD' and skip first screen.

  • User Exits in Inquiry

    Hi Friends
    We are creating an inquiry(Special case) with reference to billing document.
    In inquiry we have to enter reason for rejection and enter the requested delivery date or first date and save the record.
    Whenever I give reason for rejection there should be a POP UP message like 'enter REQ DEL DATE' and I should able to enter the Date in the pop up.
    Which user exit would be used to meet the requirement exactly.
    Warm regards
    Naresh

    Go [here|http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm] to see documentation on user exits for sales document processing.  You should be able to find a place here to put the code.  These same user exits apply to all kinds of sales order documents, so make sure you specify in the code that it only applies for Inquiry.
    Hope it helps,
    Brian

  • User Exit/Badi for CATS

    Hi Experts,
    Our requirement is to trigger an email notification to the Employee after his time sheet is approved using the CATS approval WF.
    We are using the portal to raise the time sheet and approve the same. We want to determine a User Exit/ Badi when the approver clicks on the approved button in the UWL.
    We tried looking into the user exits/badi's etc. given but they are defined only for the R/3 system  using the CATS transaction and not via the portals.
    Could you kindly guide us with any Badi/User Exit that could be used when it is approved via the portal (i.e) when the approver clicks on the approve button in the UWL.
    Cheers,
    Belinda Clarke

    Hi,
    Are you sure that those possible badis or user exit that you found are not also for Portal? Many times there is no difference whether something is done from backend transaction or a portal application - finally the same code/function is used and thus the same badis & user exits are executed. Of course not always, but plenty of times.
    If if you cannot find anything, please check also the possibility to use enhancement. Check which RFC function is called during the approval (put RFC trace on) and put a break point there, and see what the code does and if you could put your stuff into some place.
    Pay attention also the CATSDB table. That includes the cats entries and if remember correctly, you can find the work item ID there for each CATS entry. Maybe you can build some kind of report based on this table to send the emails instead of using some user exit or whatever.
    Regards,
    Karri

Maybe you are looking for