BADI/User exists for versions(snapshots) CN71/CN72

Hello friends!
Is there a BADI/User exists for versions(snapshots) CN71/CN72?
Please let me know the name and your experience using it.
Best regards
Jose Marin

Hi,
Try following user exit for both transaction codes, CN71 & CN72
CNEX0010 (PS: Customer-defined hierarchy in LDB PSJ)
sandeep

Similar Messages

  • Use of Authorizations Tab in User Account for Version 10

    Whats the use of Authorizations Tab in User Account for Version 10. Please find the snapshot attached.

    Hi Pawan,
    SAP Sourcing 10 allow custom script and query-based web services which support OAuth authentication so
    client consumer application will consume this web service and if the OAuth handshake is done successfully, then we can verify by going to the Authroizations tab of the User Account of the user that signed on to Sourcing/CLM and allowed the external program to access the particular webservice.
    For more insights please refer the Web services cookbook of SAP Sourcing 10.
    Hope it helps to some extent.
    Best,
    Kushagra A

  • BADI / user exit for Tcode IW32?

    Hi
    Are there any BADIs  / user exits for changing component data in Transaction IW32 for a maintainance order?
    regards
    cs

    Enhancement                                                                               
    IWO10012                                Maintenance order: Priority handling on central header                                                                               
    Business Add-in                                                                               
    IWO_UI_USEFLEX                          BAdI for Calling Up an Alternative UI                  
    I hope it helps.
    Best Regards,
    Vibha
    Please mark all the helpful answers

  • BADI/User Exit for KO02

    Dear Experts,
    When I'm setting the BUDGETED status manually to Internal Order (With out distributing the Budget to Order in IM52) and after if I m setting RELEASE status the system is accepting. So, I want to stop this without giving the budget in IO, it should not accept to release IO.
    This is not possible with User Status, coz' User may go and set manually "REL" Status.
    can anyone suggest me the BAdi/User Exit for KO02(Internal Order Change) tcode.
    Thanks,
    Sanju.

    When you set a User status , you can assign an Authorization Object on who can change the status .
    Follow the path in SPRO--> Controlling --> Internal orders --> Order Master Data > Status Management> Define authorization Keys for Status Management
    Define Authorization Keys for Status Management
    In this step you define authorization keys which you can use to set up authorization checks when you manually set or delete a user status. When the system sets a user status as a reaction to business transaction, it does not perform an authorization check.
    When you set or delete a user status, the system checks whether the user is authorized for this action. In addition to the status profile and the object type, the system also checks the authorization key assigned to the user status in question.
    Example
    You want to define that certain user statuses can be changed only by a specified employee group.
    To do this, create an authorization key and assign it to the relevant user statuses.
    In the general authorization maintenance you can then assign authorizations for this key via the authorization object B_USERSTAT.
    Activities
    1. Check whether you want to define authorizations for your user statuses.
    2. If necessary, create authorization keys as follows:
    a) Choose "New entries".
    b) Enter a key and an explanatory text in the appropriate fields and choose "Save".
    You have now created the authorization key.
    3. Assign the authorization key to one or more user statuses in your status profile.
    4. Define corresponding authorizations and include them in the relevant authorization profiles.

  • BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE initial screen

    Hi All,
    I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.
    please provide your suggestions.

    Hi,
    here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
      DATA: faelligkeit TYPE d,
            faelligkeit_text type c length 10,
            meldungstext TYPE c LENGTH 100.
      FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
      IF sy-uname = 'XYZ'.
    *    BREAK-POINT.
        READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
          ASSIGNING <it_source>.
        faelligkeit = <it_source>-dfaell.
        CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
           EXPORTING
             DATE_INTERNAL                  = faelligkeit
           IMPORTING
             DATE_EXTERNAL                  = faelligkeit_text
           EXCEPTIONS
             DATE_INTERNAL_IS_INVALID       = 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.
        IF faelligkeit <> sy-datum.
          CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
          CALL METHOD pi_proxy_messages->set_message
            EXPORTING
              pi_message_id       = 'T0'
              pi_message_number   = '101'
              pi_message_severity = 'E'
              pi_message_var1     = meldungstext
            EXCEPTIONS
              OTHERS              = 4.
        ENDIF.
      ENDIF.
    It is not a really nice coding but it shows in a simple way how to use the BAdI.
    Regards
    Robert

  • BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE

    Hi All,
    I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.

    Hi,
    here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
      DATA: faelligkeit TYPE d,
            faelligkeit_text type c length 10,
            meldungstext TYPE c LENGTH 100.
      FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
      IF sy-uname = 'XYZ'.
    *    BREAK-POINT.
        READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
          ASSIGNING <it_source>.
        faelligkeit = <it_source>-dfaell.
        CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
           EXPORTING
             DATE_INTERNAL                  = faelligkeit
           IMPORTING
             DATE_EXTERNAL                  = faelligkeit_text
           EXCEPTIONS
             DATE_INTERNAL_IS_INVALID       = 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.
        IF faelligkeit <> sy-datum.
          CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
          CALL METHOD pi_proxy_messages->set_message
            EXPORTING
              pi_message_id       = 'T0'
              pi_message_number   = '101'
              pi_message_severity = 'E'
              pi_message_var1     = meldungstext
            EXCEPTIONS
              OTHERS              = 4.
        ENDIF.
      ENDIF.
    It is not a really nice coding but it shows in a simple way how to use the BAdI.
    Regards
    Robert

  • BADI/User Exit for custom table update from Delivery

    Hi
    Our requirement is to update a custom table with the delivery number and other related details when the picking status is changed to "C". Kindly suggest BADI/User exit for this requirement .
    Thanks in Advance for your immediate help .

    Hi Joseph,
    See SAP Note 415716 - User exits in delivery processing. It says when you have the document number available, what is permitted, what not, ....
    I hope this helps you
    Regards
    Eduardo

  • BADI / USER-EXIT FOR DEFAULTING THE FIELD VTTK-TNDR_ACTC IN TCODE VT01N

    Hi,
    I require a BADI / USER-EXIT for defaulting the field VTTK-TNDR_ACTC(Currency of Actual Shipment costs) to 'EUR' in transaction VT01N(Shipment Transaction) .
    Please could anyone help me with this .
    Regards,
    Sushanth H.S.

    Hi!
    User Exits in Transportation
    In Transportation, there are enhancements that you can use with transaction CMOD.
    For a detailed description of the individual enhancements, see the documentation on the individual enhancements or function modules in transaction SMOD.
    You can display all enhancements that are available for the area of transportation by choosing F4 in the Enhancement field. Enter V56* in the Enhancement field and choose Execute. Enter V54* to get a list of all enhancements for the area of shipment cost processing.
    Business Add-Ins in the transports
    Business add-ins (BADIs) are predefined user exits. They enable businesses, partners, and customers to add additional softward to the SAP source code. The linkup of SAP's New Dimension Products, such as APO and BW, to the standard system is thus possible.
    Customer-specific functions can be executed before the save time and after the database update.
    The following methods are available for the BADI with the definition name 'BADI_LE_SHIPMENT':
    AT_SAVE: BADI is called up at the time of the save. Checks and return to dialog are possible.
    BEFORE:_UPDATE: BADI is called up right before the data is saved to the database, that is, when all the data is available (for example, internal ly assigned shipment number).
    IN_UPDATE: BADI is called up after the database update.
    Standard Settings
    Creating a BADI method:
    Call up transaction SE19. Enter a name of your choice. Choose "create" and in the dialog box enter the definition name 'BADI_LE_SHIPMENT'. Afterwards, enter a short text for implementation. Save the BADI.
    On the tab page 'Interface', choose the method for implementation by double-clicking on it. Now you can enter your customer-specific program code. Save and activate the code. You can acess the transmission parameters entered in the BADI definition. With the method ***_AT_SAVE you can initiate the exception ERROR_WITH_MESSAGE (description 'An error message has occurred' ) if you wish to return to the dialog.
    Afterwards, go to the heading and activate the interface.
    Regards
    Tamá

  • User Exist for MM - Purchase Order

    Hi ABAP expert,
    is there any user exist for Purchase order, actually i'm want to prevent the user from do the deletion on PO items, as per my understanding we can use user exit.
    can anyone help and how to do the process ?

    Hi,
    1. Just copy and paste this code and execute it.
    2. Give the Tcode "ME21" and you will see the lot of user exits.
    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 HOTSPOT ON,
            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).
    Thanks,
    Reward If Helpful.

  • Reg. User exist for G/L account change

    Dear Experts
    I want to create new contion or user exist for  change the G/L account from consumption account to
    stock account. 
    That is when I create purchase order with account assignment the stock account should be assigned instead of consuption account.
    Without any account assignment mean no problem,that accounts are posted  correctly.Stock account and GR/IR account.
    Thanks
    Rajakumar.k

    While create Purchase order.
    If    Acct assignment  E      -   Stock account - depending on the material type
         Acct assignment and item cat.  E  & L   WIP of material
    Like the above.
    while I create purchase order the consumption account is posted and after enter the sale order
    the G/L for consumption is changed to stock account. I can see the changes directly.
    Thanks
    Rajakumar.k

  • BADI / User exit for Purchase order(ME21N) after saving the document

    Hi expert,
    I need the BADI / User exit for Purchase order(ME21N) after saving the document
    This is for email sending after create the purchase order so PO document number will be the import parameter
    pls help me
    point will be reward
    Regards,
    Ganesh

    Hi Ganesh,
    Could you please share your solution?
    Thanks.
    Hoops
    Edited by: Hoops on Jun 13, 2011 10:51 PM

  • Layouts - Variant &1 does not exist for version &2 of layout module &3

    Hi Sap All.
    when i am trying to create IDOC's of type LAYMOD01 using LSMW with IDOC Object type ,there were some IDOC;s failing in SAP With status 51 saying as  "Layouts - Variant &1 does not exist for version &2 of layout module &3".
    the following below text explain you the error message related to one particular IDOC of type LAYMOD 01 which was failed in sap with status 51 :
    Variant 6325 does not exist for version 0000 of layout module EC-83-0214
    can any one explain me the reason on why the IDOC's were failed.
    regards.
    Varma

    not required any more

  • USER EXISTS FOR F110

    Dear friends,
    Can any body tell me that where we can see the related User Exists for F110 in SAP?
    Thanks,
    Raju

    Hello,
    Here is the list of user exists in F110
    FDTAX001 Enhancement to Transaction FDTA (event after the download)
    FEDI0002 Function exits for EDI DOCS in FI - Incoming pyt adv.notes
    FEDI0003 Function exits for EDI docs in FI - Save PEXR segments
    FEDI0004 Function exits for EDI docs in FI - particular events
    FEDI0006 Function Exits for EDI-docs in FI: Save IDCR Segments
    RFFOX003 Frame for user exit RFFOX003 (in program RFFOM100)
    RFFOX041 Framework for user exit RFFOX041 (in program RFFOBE_I)
    RFFOX042 Framework for user exit RFFOX042 (in program RFFOBE_E)
    RFFOX043 Framework for user exit RFFOX043 (in program RFFOBE_D)
    RFFOX061 Frame for user exit RFFOX061 (in program RFFOCH_P)
    RFFOX062 Frame for user exit RFFOX062 (in program RFFOCH_P)
    RFFOX063 Frame for user exit RFFOX063 (in program RFFOCH_P)
    RFFOX064 Frame for user exit RFFOX064 (in program RFFOCH_P)
    RFFOX065 Frame for user exit RFFOX065 (in program RFFOCH_P)
    RFFOX066 Frame for user exit RFFOX066 (in program RFFOCH_P)
    RFFOX071 Frame for user exit RFFOX071 (in program RFFOCH_U)
    RFFOX072 Frame for user exit RFFOX072 (in program RFFOCH_U)
    RFFOX073 Frame for user exit RFFOX073 (in program RFFOCH_U)
    RFFOX074 Frame for user exit RFFOX074 (in program RFFOCH_U)
    RFFOX075 Frame for user exit RFFOX075 (in program RFFOCH_U)
    RFFOX081 Frame for user exit RFFOX081 (in program RFFOF__T)
    RFFOX082 Frame for user exit RFFOX082 (in program RFFOF__T)
    RFFOX100 Frame for user exit RFFOX100 (in program RFFOUS_T)
    RFFOX101 Frame for user exit RFFOX101 (in program RFFOUS_T)
    RFFOX102 Frame for user exit RFFOX102 (in program RFFOUS_T)
    RFFOX103 Frame for user exit RFFOX103 (in program RFFOUS_T)
    RFFOX104 user exit
    RFFOX105 Frame for user exit RFFOX105 (in program RFFOUS_T)
    RFFOX200 Frame for user exit RFFOX200 (in program RFFONZ_T)
    RFFOX210 Frame for user exit RFFOX210 (in program RFFOAU_T)
    RFFOX211 Frame for user exit RFFOX211 (in program RFFONZ_T)
    RFFOX230 General program for user exit RFFOX230 (in program RFFOJP_L)
    RFFOX240 Enhancement for User Exit 240 (RFFOAT_P)
    RFFOX250 Enhancement for User Exit 250 (RFFODK_E)
    RFFOX901 Framework for user exit RFFOX901 (in program RFFOM100)
    RFFOX902 Framework for user exit RFFOX902 (in program RFFOM100)
    Hope this helps
    Rgds
    Rajendra
    Pls assign points if useful

  • User exists for ME22N

    Hi all,
    Is there any user exists for the ME22N tcode While Saving PO,  excluding  MM06E005 and M06E0004. These exists are M06E0004 inpacting on Release strategy and other MM06E005 is SAP stored the screens in $tmp because of this  impacting on other tcode me41 going to dump.so anybody can suggest any other  user exists.
    Thank u,
    sksk.

    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
    AMPL0001                                User subscreen for additional data on AMPL
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    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
    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
    Regards,
    Madan

  • 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

Maybe you are looking for