ALE User Exit

Hi.
Is there a user exit in the event of inbound IDoc creation particularly after saving it to the database. For example an EAI application drops an IDoc in the ALE layer I just want to do some manipulation after the IDoc was saved to the database.
Thanks

Hi,
  enhancement VEDA0001. For include ZXVEDU03 of component EXIT_SAPLVEDA_001
EXIT_SAPLVEDA_002 include ZXVEDU04
Check this link :
Re: BDCDATA for include ZXVEDU04 of EXIT_SAPLVEDA_002?
<b>Reward points</b>
Regards

Similar Messages

  • Badi method to replace ale user exits

    Hi,
    The requirement to convert the ALE User Exits (IN XHAL function group) into BADIs.
    suggest exact BADI and method which can replace below User Exits.
    1. EXIT_SAPLRHAL_004 HR-CA: ALE Inbound Processing: Converting Segment / Infotype
    2. EXIT_SAPLRHAL_003 HR-CA: ALE Outbound Processing: Converting Infotype / Segment
    Help urgently.
    Regards,
    Partha.
    Moderator message: please help yourself first, urgently.
    Edited by: Thomas Zloch on Feb 24, 2011 2:12 PM

    I think this is called in IDOC_INPUT_FINSTA .
    Can you please let me know this is related to what tramsaction.

  • User exit -Note 103678 : ALE Transfer terms of Payment

    Hi,
    We are using Inter--company STOS and intending to use ALE to automatically post the Intercompany A/P MIRO created off of the P.O/SD billing Invoice.
    Base line date was not getting filled and SAP came back saying to check the Note :103678.
    iisue was : Segment E1EDk03 024  date field was not getting filled
    I followed like this..
    I used user exit:ZXM08U26
    in EXIt_SAPLMRMH_015.
    CALL FUNCTION 'FI_TERMS_OF_PAYMENT_PROPOSE'
      EXPORTING
        I_BLDAT         = E_RBKPV-BLDAT
        I_BUDAT         = E_RBKPV-BUDAT
        I_ZTERM         = E_RBKPV-ZTERM
      IMPORTING
        E_ZFBDT         = E_RBKPV-ZFBDT
      EXCEPTIONS
        TERMS_NOT_FOUND = 1
        OTHERS          = 2.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Acxtivated ..
    Still I am having same issue.When i keep a break-point its not stopping at this point..
    Any ideas?
    Regards
    Vara

    Hi Michael,
    Currently I am facing the same problem in my system. I am creating an invoice from external system(SAP SRM) and generates an IDOC in SRM and same is coming to ECC. In ECC for creating invoice we have two mandatory fields house bank(hbkid) and section code(secco). These fileds data is not coming from SRM IDOC so i need to pass these fileds data before posting the IDOC.
    I am using EXIT_SAPLMRMH_015 for passing these fields data. I tried to debug the exit but it is not stopping. Same steps follwoed suggested by you.
    I written the below code for this  but still data is not filling . I request you to give me your suggestions on this.
    DATA: S_RBKPV TYPE  MRM_RBKPV OCCURS 0 WITH HEADER LINE.
    DATA: W_SCACD LIKE LFA1-SCACD.
    S_RBKPV = E_RBKPV.
    IF  E_RBKPV-LIFNR IS NOT INITIAL.
      SELECT SINGLE SCACD FROM LFA1 INTO E_RBKPV-SECCO WHERE LIFNR = E_RBKPV-LIFNR.
      SELECT SINGLE VBANK FROM ZMM_HOUSEBANK INTO E_RBKPV-HBKID WHERE BUKRS = E_RBKPV-BUKRS
                                                                AND   GSBER = E_RBKPV-GSBER.
      IF SY-SUBRC EQ 0.
        E_CHANGE = 'X'.
      ENDIF.
    ENDIF.
    Regards,
    Ravi

  • Sample code  ale/idoc n user exits

    Hi
    could any one post me two objects each for ALE/IDOCs and Enhancements with explanation about business scenarios ,complete code plz....

    I do not see any FM idoc_input_deladv1   ,but i see FM IDOC_INPUT_DELVRY
    There are user exits related to FM IDOC_INPUT_DELVRY
    Check the enhancement : V55K0001
    FM : EXIT_SAPLV55K_001
    Check the enhancement : V55K0002
    EXIT_SAPLV55K_002
    Check the enhancement : V55K0003
    EXIT_SAPLV55K_003
    Thanks
    Seshu

  • User exit for Internal Order SaveReplica or ALE/IDOC

    Hi,
    We're currently copying back internal orders from our PRD environment into QAS using the class method InternalOrder SaveReplica via the distribution model in BD64.
    We've extended table AUFK to include some custom fields and are populating it nicely via the user exit provided.  However, we want to include these values when we replicate the data back in our QAS environment.
    The BAPI for method CREATE contains the "EXTENSIONIN" table so I think I know what to do there, but we are using SAVEREPLICA which doesn't offer any extra fields.
    What is the best way to copy this data back into QAS?
    Would it make sense to put a user exit RFC call in the QAS system to populate the values after reading them from the PRD system at the time of saving?
    I can't find any user exits.  We are doing this based off of change pointers. 
    Would you recommend using basic ALE, doing an extension to idoc type internalorders01 or something?
    Thanks for any suggestions.

    Hi,
    usage of specific combinations of internal orders + cost elements:
    Create FI-validation rule (T-code OB28 or GGB1) using BSEG-HKONT, BSEG-AUFNR for call-up point 2. Assigne this rule to the comp. code(s) needed.
    Best regards, Christian

  • BAPI,BADI ,BDC,ALE ,IDOC,USER EXIT,VALIDATION AND SMART FORMS.

    Dear Experts,
    I am pretty new in BAPI,BADI ,BDC,ALE ,IDOC,USER EXIT,VALIDATION AND SMART FORMS.
    Pls let me know for these topics shall i put the question in this community or should i put in any other form. Pl suggest me .
    Regards
    Shivas

    Plz SEARCH in SCN before posting ,you will get lot of posts .
    Don't use all caps in the subject line

  • ALE - MATMAS user exit

    Hi all.
    I send a material using bd10 (matmas). I need for example add or change some information in receivng system (master data).
    I found the user exits
    EXIT_SAPLMV01_002  
    EXIT_SAPLMV02_002
    I set a break point but how to set up a debbuging mode.
    I only see the receiving idoc in WE02.
    Any help ?
    Thanks
    Bartosz

    Hi Bartosz,
    To be able to use debugging you first have to switch off the 'Immediate processing' in the partner profile for the Idoc in the receiving system (otherwise the Idoc will be processed immediately in the receiving system and you will not be able to debug).
    Be sure to activate the exits by creating an enhancement project and then put a break-point in the exit. Finally send an Idoc to the receiving system and pick it up using transaction BD87. Now your processing will stop at the break-point.
    Regards,
    John.

  • 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 while saving Service Purchase Order

    i want to update one z table from the Service PO, after saving. Hence i require , an user exit, which will give the details of the service tab , of the PO. I am not able to get any exit, where the details of the Service tab, of the transaction me22n.
    Below is the screen of the Service tab of the purchase Order Screen :
                                                                                    <b>Line      DeService numbShort text                   Quantity          Uni    Gross priceCr
        10          3000001     Sub-Con Recruitment Commissio91                DAY1,249.00       IN
        20          3000001     Sub-Con Recruitment Commissio91                DAY1,249.00       IN</b>

    hi,
    check this out .
    Transaction Code - ME21 Create Purchase Order
    Exit Name Description
    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
    LMEKO001 Extend communications structure KOMK for pricing
    LMEKO002 Extend communications structure KOMP for pricing
    MM06E011 Activation of PReq Lock
    No of Exits: 38
    Kishi.

  • User-exit for deletion of line item in PO

    hi group
    i want to delete a line item of purchase order.
    and after that i have to make some changes
    so i want to know which user-exit will be used here.
    please help its urgent.

    Hi,
    Please fine the list of user exits for the transaction ME22.
    If it serves your purpsoe , please close the thread and reward suitable points.
    Regards,
    Irfan Hussain
    Transaction Code - ME22                     Change Purchase Order
    Exit Name
    Description
    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
    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.
    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
    LWSUS001
    Customer-Specific Supply Source Determination in Retail
    MRFLB001
    Control Items in Release Creation
    No of Exits:         33

  • Badi or User Exit to close PR in ME59n

    Dear All,
    I have implemented a enhancement for ME59n(EXIT_SAPLME59_001). Here we club the PR which has same material, vendor, date..... And add the quantity to first PR quantity and create a single PO against all the PR.
    PR No              Material                vendor                     date                Quantity
    1                      ABC                   XYZ                     26.05.2011           100
    2                     ABC                    XYZ                     26.05.2011           200
    3                    ABC                     XYZ                     26.05.2011           300
    Assume the above example and here it will sum up the quantity i.e. 600 total and put against PR 1 and will remove the PR 2 and 3 from the internal table. Now PO will create for PR 1 with 600 as quantity and standard SAP will mark the PR 1 as closed.
    Now we have removed PR 2 and 3 from the internal table during run time after adding the Quantity. But I need to mark PR 2 and 3 as closed.
    Please let me know if there is any right Exit or Badi to achieve it or other way.
    Thanks in advance.
    Arun Kumaram.

    Here are the user exits you can look to http://www.sap-img.com/ab038.htm to and
    AMPL0001            Subscreen usu.p.dat.adicionales p.lista piezas fabr.autoriz.            
    LMEDR001            Ampliaciones programa de impresión                                      
    LMEKO001            Ampliar estructura comunicación KOMK para determinar precios            
    LMEKO002            Ampliar estructura comunicación KOMP para determinar precios            
    LMELA002            Transfer.núm.lote de aviso entrega al contabilizar una EM               
    LMELA010            Entrada aviso de entrega: toma de datos posición de IDOC                
    LMEQR001            Exit de usuario p.determinación fuente aprovision.                      
    LMEXF001            Condiciones en documentos de compra sin recepción d.factura             
    LWSUS001            Determinación fuente aprov.específica cliente en el comercio            
    M06B0001            Determinación de funciones p.liberación solicitud de pedido             
    M06B0002            Modific.estructura de comunicación p.liberación solic.pedido            
    M06B0003            rango de números y número de documento                                  
    M06B0004            rango de números y número de documento                                  
    M06B0005            Modif.estruct.comunicación p.liberación general solic.pedido            
    M06E0004            Modif.estructura comunicación p.liberación docs.compras                 
    M06E0005            Determinación funciones p.liberación doc.compras                        
    ME590001            Agrupación solicitudes de ped.p.partición de pedidos en ME59            
    MEETA001            Determinar clase de reparto (atrasos, nec.inmed., previsión)            
    MEFLD004            Determ.fe.entrega más temprana p.verif.seg.EM (sólo pedido)             
    MELAB001            Crear orden entrega p.suministro: Realiz.plan de transmisión            
    MEQUERY1            Ampliación para resumen de documentos ME21N/ME51N                       
    MEVME001            Cálculo ctd.prop.entr.mercanc.y tolerancia exc./faltas sum.             
    MM06E001            Exit de usuario para EDI: entrada/salida documentos ventas              
    MM06E003            rango de números y número de documento                                  
    MM06E004            Control pantallas datos import. en el pedido                            
    MM06E005            Campos cliente en documento compras                                     
    MM06E007            Doc.modif.p.solicitudes pedido durante conversión a pedido              
    MM06E008            Control del valor previsto p.pedidos p.orden de entrega                 
    MM06E009            Textos relevantes p.indicador "Existen textos"                          
    MM06E010            Selección de campos para la dirección del proveedor                     
    MM06E011            Activación bloqueo de solicitud pedido                                  
    MMAL0001            ALE distribución libro de pedidos: tratamiento salidas                  
    MMAL0002            ALE distribución libro de pedidos: tratamiento entradas                 
    MMAL0003            ALE distribución registro info compras: tratamiento salidas             
    MMAL0004            ALE distribución registro info compras: tratamiento entradas            
    MMDA0001            Propuesta de direcciones suministro                                     
    MMFAB001            Exit usuario para creación orden entrega                                
    MRFLB001            Controlar posiciones p.creación orden entrega

  • Badi & User Exit for ME21N & ME22N

    Hi,
            My requirement is when a Purchase order is created using ME21n or when a line is added or changed using ME22n, the system should copy the vendors tax jurisdiction to the purchase order line items jurisdiction code. I tried badi (ME_PROCESS_PO_CUST) but could not suceed. Can any one tell me if any badi or user exit available for the same???
    Thanks in Advance.

    hi,
    Enhancement/ Business Add-in            Description
    Enhancement
    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
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    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
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Business Add-in
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • User exit/BADI for Return PO item delivery Address

    Hi Guyz,
    We have a requirement where in when a PO item is marked as return PO item(In ME21n/ME22n/ME23n We have check box at item level) and click on enter/Check/Save, In delivery address of item details we have to populate Vendor address. By default SAP populates Plant address. If we manually give Vendor number in item details=>Delivery address tab then it populates vendor address. We want to automate this functionality.
    Is there any Exit/BADI which serve this purpose.
    Note: We need this functionality for few doc types(i.e PO doc type should also be available in the exit).
    Any ideas could be really helpfull.
    Thanks,
    Vinod.

    Hi,
    there are some user-exit & enhancements....
    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
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    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
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Some BADI s:
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • BADI / User Exit after Saving of Business Partner

    Hi Experts,
    Is there a BADI / user exit that is triggered after saving / updating of Business Partner using transaction code "BP"?
    We want to send a XML file thru ALE after creation/modification of BP. We are using CRM WinClient 4.0.
    Thanks.

    Hi Mikhail Khorpyakov,
    Thank you very much for your reply. It was a helpful answer.
    BUPA_GENERAL_EXPORT is triggered before database update of table BUT000 and other related tables.
    Is there a BADI that is called after saving which contains general data of business partner?
    Thanks in advance..

  • User Exit to call program to create IDocs.

    Hi All,
    For any creation/changes of material master using MM01/MM02 (after save ) one of the user exit will trigger.
    From the user exit, I have to call the custom program to create MATMAS IDOCs.
    if any failures in changes/creation of material master. It has to roll back eveything created by program.
    Please let me know how to achieve this with out calling an event.
    Thanks - Vinay

    There are a number of standard methods to automatically create the IDOC.  You can activate the change pointers and depending on need, use BD64 to create a distribution model, and create the necessary WE20 setups to create the outbound IDOC.
    If you have to process the IDOC using custom logic, you can define that as well - although it's not clear why you need a custom generating program.  You can insert code into one of the IDOC user-exits to manipulate the content if needed.  Also, don't overlook the pre-delivered stuff from SAP that provides filtering out of segments and the like.
    There are a few good SAP PRess books about doing ALE distribution -- if this is an unfamiliar area, it's worth the cost to buy one -- if you spend any time around IDOCS, you'll appreciate it.

Maybe you are looking for