BADI for PO Release

Hi Experts,
I want to save data of PO after its Release.
Can anbody tell me the BADI which will get triggered after PO Release ???
Regards,
Chaitanya

Hi
Goto Se24 and enter CL_EXITHANDLER
in method GET_INSTANCE
  CALL METHOD cl_exithandler=>get_class_name_by_interface
keep break point and check the relevant BADI for you requirement
Regards
Shiva

Similar Messages

  • BADI for PO release through ME29n

    Hi Experts,
    I have to send an IDOC as & when user release the Purchase order from ME29n. I got a user exit 'M06E0004' for release strategy but it sends idoc when i open the Transaction ME29n. Instead of that i have to send it on the click on that release button.
    Can anyone please tell me the BADI for this and the method in which i have to write the code for button click to send the IDOC.
    Regards,
    Manish

    that means there is no BADI for PO release.
    the problem is i dont no these config steps as i never did any config work.
    I will try whatever the thread says.
    Again i want 1 more BADI for repeat output functionality.  Purchase Order to be automatically re-sent (if changes are made) from the Repeat Output function within ME22n messages. If changes are made the relevant personnel will manually trigger a reprint of the order using the Repeat Output function, this needs to trigger the idoc to be re-sent.
    Regards
    Manish

  • User Exit/ BADI for PO release

    Hi Experts,
    Can anyone please tell me about the User Exit or BADI for Sub contract PO release.Also tel me how to proceed for the following 2 requirement ,
    i have to send an IDOC as & when the Sub contract PO releases.
    And automatically resent if changes are made in PO with the repeat output function in ME22N.
    Regards,
    Nik

    Hi,
      Use trx SE19 to implement your BADI: create an ZME_PROCESS_PO_CUST using ME_PROCESS_PO_CUST as definition.
    Now in Interface Tabs you can see the METHODs you can use as "user-exit", in particular there's PROCESS_ITEM to manage items data.
    You have to write your code into this method.
    This method has IM_ITEM like parameter in its interface, and it's like the type IF_PURCHASE_ORDER_ITEM_MM.
    This type has the method IF_LONGTEXTS_MM~SET_TEXT, you can try to use it to set your text in item.
    This is code for example:
    DATA: TLINE TYPE MMPUR_T_TEXTLINES.
    CALL METHOD IM_ITEM->IF_LONGTEXTS_MM~SET_TEXT
    EXPORTING
    IM_TDID = <YOUR ID>
    IM_TEXTLINES = TLINE.
    So you should read the text you want to copy and pass it to TLINE.
    You can use the METHOD PROCESS_HEADER to read the text you need. This METHOD has IM_HEADER as parameter and it's like the type IF_PURCHASE_ORDER_MM, this type has the method IF_LONGTEXTS_MM~GET_TEXT to read header logn text.
    Anyway while you're in implementation of the BADI go to:
    GoTo->Sample Code
    Here you can try an example how to implement the method you need to use.
    Regards

  • User Exit Or Badi for Framework Release PO

    Anyone could tell me about any user exit or BADI for storing the calculated value in Frameork order.
    Since it is storing the GNETW in CEKKO and that is used in releasing procedure.
    First of all i want to calculate the total price according to srat date and end date and then only for framework order put that value in CEKKO-KTWRT field.
    Please Help and suggest some thing about this.
    Thanks & Regards,
    Nitin Malhotra

    Hi,
    Check the following PDF .
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
    May be useful to you.
    Regards
    Sachin

  • Exit / BADI for RFQ Release (ME45)

    Hi all,
             I need an exit or badi when an RFQ got released.
    Can anybody please help me to find the badi when an RFQ has been released.
    Thanks & Regards.
    Ranganadh.

    Hi,
    Exits for RFQ are following-
    AMPL0001            User subscreen for additional data on AMPL
    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
    MM06E011            Activate PReq Block
    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
    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
    Regards,
    Sujit

  • BADI for PO release strategy

    Hi,
    If PO is released than automatically mail should be sent to authorized person.
    How i can achieve this using BADI.Please suggest.And where i have to write the code.

    Hello Priyank
    If you are already working on ERP 6.0 the the BAdI of choice is ME_PROCESS_PO_CUST. Below  I describe schematically how you implement your requirement:
    METHOD IF_EX_ME_PROCESS_PO_CUST~OPEN.
      me->md_trtyp = id_trtyp.  " NOTE: Define MD_TRTYP as instance attribute
    " NOTE: Presumably IF ( id_trtyp = 'H' ). => means PO is created
    ENDMETHOD.
    " Closing Processing
    METHOD IF_EX_ME_PROCESS_PO_CUST~CLOSE.
      CHECK ( me->md_trtyp = 'H' ).  " implies PO has been created
      CALL METHOD me->send_email( ).
    ENDMETHOD.
    Regards
      Uwe

  • User Exit Or Badi for Framework Release

    We have set up Release strategy at PO based on value and Purchase organization. It is working fine for all types of PO except Frame work PO. As per system prospective it is working fine but as per business prospective it is not appropriate.This is beacuse Frame work in our case is created with Invoice plan set up . Ex If PO is created for 5000 USD then with Invoicing plan set up it is assigned for period of 12 months and total invoicing value gets 60000 USD and release strategy gets triggered on the base of header value i.e. 5000 USD.
    So business requirement is that PO release strategy should triggered on the basis of total invoicing plan set up of that PO i.e. 60,000 USD.
    in release procedure they are using CEKKO-GNETW field.
    only for framework PO, i want to calculate the price according to start date and end date and popullate that in CEKKO-KTWRT field so that a new release procedure can be implemented for the same.
    I use M06E0004 user exit, but it is not working.
    as soon as we click check button or save button this user exit is triggering but values of EKKO is comming null inside user exit.
    How to calculate the price since start date and end date is in EKKO table.
    please help in USER EXIT.
    Thanks & Regards,
    Nitin Malhotra

    Hi,
    Check the following PDF .
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
    May be useful to you.
    Regards
    Sachin

  • Badi for Purchase Requisition Release Strategy

    Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to  control the PO Price for a PR release strategy
    Thanks for your help

    This badi is for schedule agreement ?
    BAdI: Release Creation for Scheduling Agreements with Release Documentation
    Use
    You can use this Business Add-In (BAdI) to influence release creation.
    This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
    This BAdI includes the following methods:
    Change Data Before Release Creation (BEFORE_CREATION)
    Change Data After Release Creation (AFTER_CREATION)
    This BAdI is called during manual and automatic release creation.

  • User exit/BADI  for Purchase requisition through release of Process order

    Hi ,
    i need to add some text to the Pur Req.
    The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
    regards

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    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
    MM06E011                                Activate PReq Block
    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
    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
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    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
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
    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_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    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)
    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_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    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
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    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
    Reward points if useful
    Regards
    Anji

  • Badi for release strategy me22n

    details Code for released status strategies on tcode me22n with function module .

    please check there is BADI ME_PROCESS_PO_CUST for PO Process and checks can be built in various method availble in BADI before PO release. For release strategy check user exit EXIT_SAPLEBND_002 .
    In case of any other details do revert back.
    anya

  • BaDI for quotation transaction in SAP CRM

    As per our business process, we need to release quotations from CRM to R/3. Before this is done, the partner functions on the quotation screen have to be updated with new number series.
    In order to prevent wrong release of quotations, we are develping a badi which would check all partners functions with respect to their required number series once user clicks on Save button.
    For this we are implementing badi ORDER_SAVE BUT in this there is one method CHECK_BEFORE_SAVE but in this only GUID is available so how can i check partner function(Sold to Party,Ship To Party) values which user has entered?.Or some other BADI is Available for this CAn anybody help me out.
    CRM Transaction Code is CRMD_BUS2000115.

    Hi Ravi,
    I worked on the same requirement but from a service perspective. So below are the activities I maintained to achieve this.
    1. Create a service order template type (copy of std).
    2. Maintain the copy control settings for both header and items to the service order quotation.
    3. Create Service Order Templates and enter the commonly used items in the template. Release the service order template.
    4. When creating a service order quote - at the item level, you can see the button "Copy from Template". Click on this
    5. This opens up a pop-up where in you can search for all released service order templates.
    6. Select the one you need, the items maintained in that order template is copied over to the service order quote.
    So the user does not need to enter all the items manually. This is how you user order templates. Please note that it copied only the items, not the header details of the service order template.
    Regards,
    Siraj

  • BADI for ME22N

    I have found the BADI for ME22N . It is ME_PROCESS_PO_CUST. In this BADI, when i double click on the interface PROCESS_ITEM, I go in the method where i can write code. In this code i want to fetch the PO item no. which i get at run time. This method has parameter IM_ITEM as parameter. How do i capture the value which comes at run time for this PO item. I am not able to write the syntax for it.
    When i debug , in IM_ITEM ,i get some class names one of which is CL_PO_ITEM_HANDLE_MM  and some variable name PO_ITEM_NUMBER which contains the value of PO Item. But i dont know how to write syntax .

    Priti,
    code looks like this:
    Sample code for a PO Badi:
    BAdI Name: ZCHECK_PO_LINE_ITEM (Implementation name) PO Account assignment
    Definition Name: ME_PROCESS_PO_CUST
    Interface Name : IF_EX_ME_PROCESS_PO_CUST
    Implementing Class: ZCL_IM_BADIN_ACCOUNT_ASSGN
    Method : PROCESS_HEADER
    METHOD if_ex_me_process_po_cust~process_header .
    DATA : re_data TYPE mepoheader.
    *get the item data
    CALL METHOD im_header->get_data
    RECEIVING
    re_data = re_data.
    re_header = re_data.
    IF ( re_data-bsart NE 'ZOC' AND re_data-bsart NE 'ZPC' ).
    IF ( re_data-bsart 'ZIC' AND re_data-bsart 'UB' ).
    IF re_data-bukrs NE '1001'.
    MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'Use only Sipchem Company'
    'Code for External Procurement'.
    ENDIF.
    ENDIF.
    ENDIF.
    ENDMETHOD.
    Method : PROCESS_ITEM
    METHOD if_ex_me_process_po_cust~process_item .
    DATA: v_menge TYPE bamng, " PR Quantity
    v_statu. " PR Status
    DATA : re_data TYPE mepoitem,
    re_data1 TYPE mepoaccounting,
    re_accountings TYPE purchase_order_accountings ,
    header TYPE purchase_order_accounting.
    *get the item data
    CALL METHOD im_item->get_data
    RECEIVING
    re_data = re_data.
    IF ( re_header-bsart NE 'ZOC' AND re_header-bsart NE 'ZPC' ).
    IF re_header-bsart EQ 'ZRL'.
    IF re_data-konnr EQ space.
    MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You cant create a Release order'
    'without a reference to Outline Agreeement'.
    ENDIF.
    ENDIF.
    u2022     IF ( re_header-bsart NE 'ZOC' AND re_header-bsart NE 'ZPC' ).
    IF ( re_data-banfn EQ space AND re_data-anfnr EQ space ).
    MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You can create a Purchase order'
    'only with reference to a PR or RFQ'.
    ENDIF.
    u2022     ENDIF.
    u2022     
    o     call method IM_ITEM->GET_ACCOUNTINGS
    o     RECEIVING
    o     RE_ACCOUNTINGS = RE_ACCOUNTINGS.
    **get the accounting reference variable,this reference is needed to get
    **the GL account *number and Asset number
    *loop at RE_ACCOUNTINGS into header.
    **get the accounting info.
    u2022     call method header-ACCOUNTING->GET_DATA
    this one i have used for our requirement.
    Amit.

  • 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

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

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

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

  • User exits/BAdIs for Forecast consumption by sales order

    Hello Experts,
    My question here is: When Sales Order either new or change comes from ECC to APO, what are key fields considered for Forecast Consumption? Is requirements strategy is considered from location product master or Sales Order brings own data from ECC into it's own structure? I have read from SAP help or documentation that Sales Order coming from ECC does not use requirement strategy from Product Master. Rather it get its own fields like planning strategy/group / requirement class from ECC. It uses location product master only to get consumption parameters like forward/back word consumption days. So I am thinking to use some user exits or BAdIs to enhance the incoming sales orders to consume separate forecast categories in APO.
    My requirement is:
    For the same one product we want sales orders (can have two different order types or identify by a custom field) to consume two different order categories (ie. FA & FC) by enhancing incoming sales orders. So we have regular 1)Forecast key figure which is 'FA' category and 2)Forecast Additional key figure which is FC category. When we release two separate forecasts from DP we release into these two key figures and categories. Now we want incomping sales orders to consume these two categories separately when our sales orders are having two different order types (i.e OR and ZR).
    I want to kow what way we can acomplish this? Are there any user exits or BAdIs for this purpose?
    I looked arount BAdI /SAPAPO/DM_BADI_CSP and I am not quite sure it's going to help. Are there any others?
    I appreciate if anybody explain me the process?
    Thanks in advance!
    Raj

    Standard Logic --- Whatever plant is visible in the Sales Order, the sales order will appear under that Product Location in SNP
    There is no standard way of making the sales order visible in another location.
    Depending on your requirement(Ex: Forecast Consumption, planning etc),using APO-BW we can simulate the requirements in the other plant which can be a nightly run and not immediate.
    Now coming to your question, if the delivering plant is A, how does ECC Delivery document know when the sales order has plant B that the delivering plant is A.
    Can you be more specific.
    THanks
    Kumar

Maybe you are looking for