ME_GUI_PO_CUST for PR

Dear Gurus,
Is there any badi like above for PR.
I need to add 1 field customer refno for PR screen. Can I create additional customer enhancement screen since the existing one has been used by other developments.
SAPLMEGUI                      0014 SUB0     SAPLXM02                       0111
Need help on this, urgently.
TQ.

Thanks Darek for replying back and the BADI   ME_BAPI_PR_CUST looks helpful but could you please help me in understanding how can i create my own custom screens within ME51N / ME52N / ME53N tcode using the BADI , ME_BAPI_PR_CUST.
For example in PO, we have the BADI   ME_GUI_PO_CUST, with several methods like SUBSCRIBE and others which we can make use of for creating screen exits but what in the case of PR fpr BADI  ME_BAPI_PR_CUST. i couldn't find any sample code for implementing this.
Any help is greatly appreciated.
Thanks,
Ameesha

Similar Messages

  • Create new tab in header using badi ME_GUI_PO_CUST for tcode ME21N

    Dear all,
    i have implemented method SUBSCRIBE in ME_GUI_PO_CUST to create new tab in ME21N,
    but the tab is not coming
    following is the code snips, please tell where is the error, or some setting needs to be done
    method IF_EX_ME_GUI_PO_CUST~SUBSCRIBE.
    DATA: ls_subscriber LIKE LINE OF re_subscribers.
    if sy-tcode eq ' ME21N' OR SY-TCODE EQ 'ME22N' OR SY-TCODE EQ 'ME23N'.
      CHECK im_application = 'PO'.
      CHECK im_element     = 'HEADER'.
    CLEAR re_subscribers[].
      ls_subscriber-name = 'Customer-Data'.
      ls_subscriber-dynpro = '0101'.
      ls_subscriber-program = 'SAPLMEGUI'.
      ls_subscriber-struct_name = 'MEPO_SUBSCRIBERS'.
      ls_subscriber-label = 'Customer Data'.
      ls_subscriber-position = 10.
      ls_subscriber-height = 7.
      APPEND ls_subscriber TO re_subscribers.
    ENDIF.
    endmethod.
    Regards
    Sumodh

    Hi...I hv similar requirement.
    I need to show a custom field in the screen for the items.
    I tried using the methods "SUBSCRIBE" and "MAP_DYNPRO_FIELDS" as explained in the sample code.
    Below is my code. I have copied the sample code and changed it lil.
    Method "SUBSCRIBE":
      DATA: ls_subscriber LIKE LINE OF re_subscribers.
    we want to add a customer subscreen on the item detail tab
      CHECK im_application = 'PO'.
      CHECK im_element     = 'ITEM'.
    each line in re_subscribers generates a subscreen. We add one subscreen in this example
      CLEAR re_subscribers[].
    the name is a unique identifier for the subscreen and defined in this class definition
      ls_subscriber-name = subscreen1.
    the dynpro number to use
      ls_subscriber-dynpro = '9000'.
    the program where the dynpro can be found
      ls_subscriber-program = 'SAPLZMMPO1'.
    each subscreen needs his own DDIC-Structure
      ls_subscriber-struct_name = 'ZMM_PO_CUST_SCREEN'.
    a label can be defined
      ls_subscriber-label = text-t01.
    the position within the tabstrib can be defined
      ls_subscriber-position = 13.
    the height of the screen can be defined here. Currently we suport two screen sizes:
    value <= 7 a sevel line subscreen
    value > 7  a 16 line subscreen
      ls_subscriber-height = 7.
      APPEND ls_subscriber TO re_subscribers.
    method "MAP_DYNPRO_FIELDS":
      FIELD-SYMBOLS: <mapping> LIKE LINE OF ch_mapping.
    *- customer fields
      CONSTANTS: mmmfd_cust_01 TYPE mmpur_metafield VALUE 90000000.
      LOOP AT ch_mapping ASSIGNING <mapping>.
        CASE <mapping>-fieldname.
          WHEN 'CLMNO'. <mapping>-metafield = mmmfd_cust_01.
        ENDCASE.
      ENDLOOP.
    I created a function group - "ZMMPO1" and created the subscreen 9000 in that. I placed the custom field in that screen. Tha main program of ZMMPO1 is "SAPLZMMPO1".
    I created a structure also - "ZMM_PO_CUST_SCREEN".
    I want to know whether this is sufficient to display the tab on the screen or am I missing something.
    It is mentioned that the implementation of "ME_PROCESS_PO_CUST" is a pre-requisite.
    could you lemme know the process please.
    Thanks,
    Ram.

  • BADI ME_GUI_PO_CUST for PO screen

    Hello,
    I need to add a button to the ME21n/22/23 transaction to call my own screens. I am trying to identify some screen enhancements through which I can add my push button. I am working on ERP2005. I identified badi ME_GUI_PO_CUST, but it does not have a subscreen name in the subscreens tab. Does that mean that I need to modify the standard to include the subscreen. I am doing the screen enhancements for the first time and would appreciate your opinion. Please let me know if there is any other badi which is best suited for this requirement.
    Thanks in advance.
    Regards
    Malthi

    Hi Malthi
    Even if you have a subscreen you cannot place a button in the subscreen. You can place only input/output fields only on a subscreen.
    So, you can try for a menu-exit and from there call you own screens.
    If you don't find any menu-exit you have to go for a modification only.
    Regards
    Surya.

  • Error in badi ME_GUI_PO_CUST for ME21n/22n/23n

    Dear All,
    I want to add 1 tab in ME21n/22n/23n.
    In that 2 field in EKKO table using ci_ekkodb include is add
    For that I use badi ME_GUI_PO_CUST.
    in that
    MAP_DYNPRO_FIELDS
    TRANSPORT_FROM_MODEL
    TRANSPORT_TO_DYNP
    TRANSPORT_FROM_DYNP
    TRANSPORT_TO_MODEL
    these method find error do to field name passing.
    method IF_EX_ME_GUI_PO_CUST~MAP_DYNPRO_FIELDS.
      FIELD-SYMBOLS: <mapping> LIKE LINE OF ch_mapping.
        LOOP AT ch_mapping ASSIGNING <mapping>.
          CASE <mapping>-fieldname.
            WHEN 'ZZDEPT'.                                            " Field Name
              <mapping>-metafield = mmmfd_cust_03.
            WHEN 'ZZPOGR'.                                            " Field Name
              <mapping>-metafield = mmmfd_cust_04.
          ENDCASE.
        ENDLOOP.
    endmethod.
    Referening **************** - Step by step guide on adding a new tab in ME21N using a BADI
    Replay is appreciable.
    Regards,
    Pooja

    First you go to se18 and read documentation of this badi.
    You have to implement BAdI ME_PROCESS_PO_CUST before implementing this BAdI.
    Sample code is available here.... goto->sample code->display
    In case any doubt u ask..
    Regards
    Sreekanth

  • Me_gui_po_cust for header fields

    HI ALL,
    I have created a tab "CUSTTAB" in ME21n header with 2 additional fileds i.e: zzfields1 & zzfield2 i have also appended them in structure ci_ekkodb of table ekko. I have used BADI'S : ME_GUI_PO_CUST  &  ME_PROCESS_PO_CUST.
    I can see the tab & both the additional fields but the data for these additional fields is not getting saved in  ekko table.
    When i implemented this badi for LINEITEM  the data was getting saved in ekpo table:the method 'IF_EX_ME_GUI_PO_CUST~TRANSPORT_FROM_MODE' of me_gui_po_cust incase of line item was:
    method IF_EX_ME_GUI_PO_CUST~TRANSPORT_FROM_MODEL.
       data: l_item       type ref to if_purchase_order_item_mm,
            ls_mepoitem  type mepoitem,
            ls_customer  type zmepo_badi_examp.
    system asks to transport data from the business logic into the view
      case im_name.
        when subscreen1.
    is it an item? im_model can be header or item.
          mmpur_dynamic_cast l_item im_model.
          check not l_item is initial.
    transport standard fields
          ls_mepoitem = l_item->get_data( ).
    transport customer fields
         call function 'ZMEPOBADIEX_GET_DATA'
           exporting
             im_ebeln = ls_mepoitem-ebeln
             im_ebelp = ls_mepoitem-ebelp
           importing
             ex_data  = ls_customer.
    store info for later use
          move-corresponding ls_mepoitem to dynp_data_pbo.
       move ls_mepoitem-ZFIELD1 to dynp_data_pbo-ZFIELD1.
          move ls_mepoitem-ZFIELD2 to dynp_data_pbo-ZFIELD2.
       move-CORRESPONDING ls_customer to dynp_data_pbo.
         move ls_customer-badi_bsgru to dynp_data_pbo-badi_bsgru.
         move ls_customer-badi_afnam to dynp_data_pbo-badi_afnam.
        when others.
      endcase.
    endmethod.
    can ny1 tell wat changes shud i make in the above code so dat it works for header fields .
    rgds
    points 'll b rewarded

    hi abap user,
       I also have same requirement of an additional tab on PO header with 2 fields inif i have used ME_GUI_PO_CUST and ME_PROCESS_PO_CUST.     in method SUBSCRIBE of ME_GUI_PO_CUST  i have written following code which is same as example code for that method.
    METHOD IF_EX_ME_GUI_PO_CUST~SUBSCRIBE.
      DATA: LS_SUBSCRIBER LIKE LINE OF RE_SUBSCRIBERS.
    we want to add a customer subscreen on the item detail tab
      CHECK IM_APPLICATION = 'PO'.
      CHECK IM_ELEMENT     = 'HEADER'.
    each line in re_subscribers generates a subscreen. We add one subscreen in this example
      CLEAR RE_SUBSCRIBERS[].
    the name is a unique identifier for the subscreen and defined in this class definition
      LS_SUBSCRIBER-NAME = SUBSCREEN1.
    the dynpro number to use
      LS_SUBSCRIBER-DYNPRO = '0001'.
    the program where the dynpro can be found
      LS_SUBSCRIBER-PROGRAM = 'SAPLMEPOBADIEX'.
    each subscreen needs his own DDIC-Structure
      LS_SUBSCRIBER-STRUCT_NAME = 'MEPO_BADI_STRUCT'.
    a label can be defined
      LS_SUBSCRIBER-LABEL = TEXT-001.
    the position within the tabstrib can be defined
      LS_SUBSCRIBER-POSITION = 5.
    the height of the screen can be defined here. Currently we suport two screen sizes:
    value <= 7 a sevel line subscreen
    value > 7  a 16 line subscreen
      LS_SUBSCRIBER-HEIGHT = 7.
      APPEND LS_SUBSCRIBER TO RE_SUBSCRIBERS.
    ENDMETHOD.
    and for BAPI ME_PROCESS_PO_CUST in method INITIALIZE i have written following code which is also same as it's example code.
    METHOD IF_EX_ME_PROCESS_PO_CUST~INITIALIZE.
      BREAK SAB_PARTH.
      CALL FUNCTION 'MEPOBADIEX_INIT'.
    ENDMETHOD.
    NOW my problem is still this additional tab is not visible when i execute ME21n or me22n or ME23n.
        kindly suggest that what code u have implemented for this BADIs..and if i require to implement fsome more method in aby of these BADIs.

  • Implementation Of Badi ME_GUI_PO_CUST for adding fields in Purchase Order

    Hi All
       I am implementing BADI ME_GUI_PO_CUST / ME_PROCESS_PO_CUST to add additional fields in Purchase Order.
    The implementation of the BADI ie the Subscreen of the fields to be added appears in  transaction ME23N but it does not appear in the transaction ME22N and ME21N.
    Can anyone help me on this.
    Thanx.
    Moderator message - Duplicate post locked
    Edited by: Rob Burbank on Jul 10, 2009 12:10 PM

    check the answer
    [New tabs added by Badi ME_GUI_PO_CUST not seen in ME21N and ME22N;
    bye

  • BADI for Customer's own screen for Purchase Requisition.

    Hi All,
    I have a requirement where I need to create a BADI implementation for creating addition screens in the Purchase Requisition Transaction (ME51n/ME52n/ME53n).
    I know there are User exits but we donu2019t want to implement them. Now in case of PO there is a standard SAP given BADI -> ME_GUI_PO_CUST for Customeru2019s own screen but as far as my understanding goes there are no such BADIs for Purchase Requisition.
    Could anyone please advice if I can create a Custom BADI similar to ME_GUI_PO_CUST for PR for adding the screen and throw some light on it like how can this be achieved?
    Thanks,
    Ameesha

    Thanks Darek for replying back and the BADI   ME_BAPI_PR_CUST looks helpful but could you please help me in understanding how can i create my own custom screens within ME51N / ME52N / ME53N tcode using the BADI , ME_BAPI_PR_CUST.
    For example in PO, we have the BADI   ME_GUI_PO_CUST, with several methods like SUBSCRIBE and others which we can make use of for creating screen exits but what in the case of PR fpr BADI  ME_BAPI_PR_CUST. i couldn't find any sample code for implementing this.
    Any help is greatly appreciated.
    Thanks,
    Ameesha

  • How Create "ME_GUI_PO_CUST" Implementation

    Hi Abapers, I need create a new Implementation for BADI "ME_GUI_PO_CUST" (For Extending Tx ME22N), but i see this BADI already has standard implementation activated ,  and i think can't use other.
    how can create another implementation without erasing the previous BADI implementation
    i hope can help me ty.

    Hi,
    It usually has an Example implementation, not a default one. You can simply create you implementation in SE19.
    Regards,
    Custodio

  • Custom screen for ME21n - BADI issue

    hi,
    I had implemented BADI ME_GUI_PO_CUST for ME21n/me22n. The control is going to Subscribe and Map Dynpro methods but the control is not going to other methods like TRANSPORT_FROM_MODEL, TRANSPORT_TO_DYNP, TRANSPORT_FROM_DYNP and TRANSPORT_TO_MODEL.
    Please explain how we can make the control to move to these methods. not sure what is missing in the implementation

    "Customer Data" on ME21N/ME22N uses the SMOD enhancement MM06E005. Screen 0101 is used for Header Customer Data. So, when you navigate through this screen it doesn't go through the TRANSPORT* methods.
    You can also use the BADI ME_GUI_PO_CUST to add your additional tabs in ME21N. You need to use the method SUBSCRIBE to set the Program, Subscreen number and other details. When you do the subscribe method, it would call the TRNSPORT* methods. Check the example code given in the class CL_EXM_IM_ME_GUI_PO_CUST.
    Regards,
    Naimesh Patel

  • Exit for Modifying screen attributes during ME22N

    Hi Experts,
    I need to make some fields output only at item level in transaction ME22N i.e. during PO change. Is there any exit or BADI available for that.
    Regards

    > Hi Experts,
    >
    > I need to make some fields output only at item level
    > in transaction ME22N i.e. during PO change. Is there
    > any exit or BADI available for that.
    >
    > Regards
    This is mainly config.
    Check in SPRO - IMG
    Materials Management > Purchasing > Purchase Order > Define Screen Layout at Document Level 
    Also these BAdis are available:
    ME_PROCESS_PO_CUST - For Custom logic in Enjoy transactions
    ME_GUI_PO_CUST - For Additional Custom screens in ME2xn
    Read the documentation, it will help.
    Also, read the config section about enhancements in Purchasing using old enhancement technology. See below.
    OSS is also a good place for documentation. OSS 496083.
    Good luck!
    Leonardo De Araujo
    Develop Enhancements for Purchasing
         In this step, you develop enhancements for Purchasing.
         The following SAP enhancements are available for the Purchasing area:
         o   AMPL0001
             User subscreen for additional AMPL data (Manufacturer part number)
         o   LMELA002
             Adoption of batch number from shipping notification at time of
             posting of a goods receipt
         o   LMELA010
             Incoming shipping notification: adoption of item data from IDoc
         o   LMEQR001
             User exit for source determination
         o   M06B0001
             Role determination for release of requisitions
         o   M06B0001
             Changes to communication structure for release of requisitions
         o   M06B0003
             Number range and document number
         o   M06B0004
             Number range and document number
         o   M06B0005
             Changes to communication structure for overall release of purchase
             requisitions
         o   M06E0004
             Changes to communication structure for release of purchasing
             document
         o   M06E0005
             Role determination for release of purchasing documents
         o   ME590001
             Grouping of requisitions for PO split in transaction ME59
         o   MEETA001
             Determination of schedule line type (backlog, immediate requirement,
             forecast)
         o   MEFLD004
             Determination of earliest delivery date for checking at time of
             goods receipt (PO only)
         o   MELAB001
             Generation of forecast delivery schedule: realization via creation
             profile
         o   MEQUERY1
             Enhancement for document overview ME21N / ME51N
         o   MEVME001
             Calculation of default GR quantity and over/underdelivery tolerances
         o   MM06E001
             User exits for inbound EDI messages and outbound purchasing
             documents
         o   MM06E003
             Number range and document number
         o   MM06E004
             Control of import data screens in purchase orders
         o   MM06E005
             Customer fields in purchasing documents
         o   MEREQ001
             Customer's own data in purhcase requisitions
         o   MM06E007
             Change document for requisitions when converting into POs
         o   MM06E008
             Monitoring of contract target value in case of release orders
         o   MM06E009
             Relevant texts for "Texts exist" indicator
         o   MM06E010
             Field selection for vendor address
         o   MM06E011
             Activation of requisition block
         o   MM06L001
             Exits for determination of ratings in vendor evaluation
         o   MMAL0001
             ALE source list distribution: outbound processing
         o   MMAL0002
             ALE source list distribution: inbound processing
         o   MMAL0003
             ALE purchasing info record distribution: outbound processing
         o   MMAL0004
             ALE purchasing info record distribution: inbound processing
         o   MMDA0001
             Default values for delivery addresses
         o   MMFAB001
             User exit for generation of releases
         o   MRFLB001
             Control items during release creation
         o   LWBON001
             Enhancement of LIS update through extension of the communication
             structure MCKONA (business volumes and rebate income)
         o   LWBON003
             Change settlement data for end-of-period rebate settlement before
             creation of settlement documents
         o   LWSUS001
             Customer-specific source determination in Retail
         Activities
         1.  Either create a new project or use an existing one and then enter
             the enhancement.
         2.  Activate the project
             Your enhancement will only become effective after activation.
         Further notes
         In contrast to modifications, enhancements are basically
         release-insensitive since they are not implemented in the SAP original
         but in a name range that is reserved for the customer.
         The general procedure for creating enhancements can be found in the
         enhancement transaction at Help -> Application help.
         If you want to display the documentation for an enhancement, choose Goto
         -> Documentation in the enhancement transaction.
    Return ->
         Application

  • Constant re-generation of TimeStream for Customer Unloading Point

    Dear Friends,
    Has anyone beem able to stop the constant re-generation of a TimeStream for a Customer Unloading Point??
    I would like to be able to stop the constant re-generation of a TimeStream (SAPxxxxxxx) so that the TTSTR table for this TimeStream is not updated at all.
    I am testing in QA with setting the Time Stamp field in APO table '/SAPAPO/TSTROBJR' to a future date but I am not sure if in our QA system, I can prove this to work where a future date in the '/SAPAPO/TSTROBJR' table would result in the TTSTR & TTSTRCOMP & TTSTRCOMP tables not being updated.
    Does anyone know if this actually works or know of any other way?
    Thank you.
    Michael Tylisz

    Dear Ms. Delembert,
    at least some enhancements are necessary to make use of the unloading point also for purchase orders as you described it for the SAP for Automotive solution.
    Since R/3 Enterprise, the following Business Add-Ins (BAdI) are available to enhance the purchase order processing: ME_PROCESS_PO_CUST for the business logic and ME_GUI_PO_CUST for the UI.
    From ERP 2005, you could also add an own enhance-points (form MEPO_ITEM_FILL_KONNR in include LMEPOF7G).
    In case you are using purchase orders based on purchasing contracts, you might like to maintain the unloading point to the contract item as it is available for the scheduling agreement.
    From ERP 2005, you could implement an own enhancement replacing the SAP enhancement implementation ISAUTO_SCH_EMM_SAPMM06E (include MM06EO0M_MODIFY_SCREEN).
    If the purchase order item would contain the unloading point, it would be automatically copied to the inbound delivery item (table field LIPS-LGBZO) based on copy routine 202 of delivery processing.
    Best Regards,
    André Nuglisch

  • Adding Field in standard Table control in crmd_order (standard order)

    Hello All,
            I want to add a Field in standard table control in Crmd_order - standard order general tab. Please Let me know it is Possible to add, if Possible Let me know how to achieve this Functionality.
    Thanks,
    Feroz.

    hi,
    If you don't want to access key...then only option is ,you have to search USER Exit or BADi (Try using BADI ME_GUI_PO_CUST) for me22n transaction......to adding the field.
    Regards
    Gaurav

  • What is the BADI to create a new tab in ME21N transaction

    Hi,
    I have created a new document type zbr with the transaction spro.
    I wanted to add a new tab for the given document type zbr. How to create a new tab for the document type.
    How to create a new tab using BADI. what is BADI used to create the tab

    Hi,
    Pls check BAdI 'ME_GUI_PO_CUST'  for your reqmt.
    Pravat.
    <i>*Reward points if helpful</i>

  • Data is not saving in customer subscreen of ME21N

    Hi Friends,
    I have implemented BADI ME_GUI_PO_CUST for adding a tab and subscreen in PO.
    I have also implemented BADI ME_PROCESS_PO_CUST for displaying screen elements.
    Everything is OK except it is not saving in the database through ME21N/ME22N.
    I have added append structure in EKKO, MEPOHEADER and added flag in MEPOHEADERX; tried many things in code but it is not saving.
    Please tell me if i am missing any step...
    Points will be awarded.

    Hi,
    I solved the probelm by mine. We have to create a Z table with the same structure like screen and also with EBELN.
    And save data in internal table TRANSPORT_TO_MODEL and read from internal table if entry saved in TRANSPORT_FROM_MODEL. (ME_GUI_PO_CUST)
    After that in ME_PROCESS_PO_CUST, implement in OPEN method, write code for selecting from Z table.
    Write code in POST method for saving in that Z table.
    Do not forget for all these excersies we have to use function module that will reside in same function group where the subscreen resides.
    Good i should give pat on my shoulder.
    Regards
    Krishnendu

  • Enhancement in ME22N

    Hi All,
             There is requirement to enhancement in  Release strategy (ME22N). If  user increase the OP price the release strategy being changed but he decrease the OP the price release strategy not being changed. The reauirement is there if they make any change in OP price either incrase or decrease, release strategy should be change. therefore there is any User-Exit or BADI which change the release strategies related informantion. I have aslo tried some user exit and BADI but in these exit and BADI  the OP header information not in export parameters (this information is import parameters) so I can not make change it. there is any other user exit or BADI for do that.
    Thanks in Advance
    Jitendra Singh

    I need to make some fields output only at item level
    > in transaction ME22N i.e. during PO change. Is there
    > any exit or BADI available for that.
    >
    > Regards
    This is mainly config.
    Check in SPRO - IMG
    Materials Management > Purchasing > Purchase Order > Define Screen Layout at Document Level
    Also these BAdis are available:
    ME_PROCESS_PO_CUST - For Custom logic in Enjoy transactions
    ME_GUI_PO_CUST - For Additional Custom screens in ME2xn
    Read the documentation, it will help.
    Also, read the config section about enhancements in Purchasing using old enhancement technology. See below.
    OSS is also a good place for documentation. OSS 496083.
    Good luck!
    Leonardo De Araujo
    Develop Enhancements for Purchasing
         In this step, you develop enhancements for Purchasing.
         The following SAP enhancements are available for the Purchasing area:
         o   AMPL0001
             User subscreen for additional AMPL data (Manufacturer part number)
         o   LMELA002
             Adoption of batch number from shipping notification at time of
             posting of a goods receipt
         o   LMELA010
             Incoming shipping notification: adoption of item data from IDoc
         o   LMEQR001
             User exit for source determination
         o   M06B0001
             Role determination for release of requisitions
         o   M06B0001
             Changes to communication structure for release of requisitions
         o   M06B0003
             Number range and document number
         o   M06B0004
             Number range and document number
         o   M06B0005
             Changes to communication structure for overall release of purchase
             requisitions
         o   M06E0004
             Changes to communication structure for release of purchasing
             document
         o   M06E0005
             Role determination for release of purchasing documents
         o   ME590001
             Grouping of requisitions for PO split in transaction ME59
         o   MEETA001
             Determination of schedule line type (backlog, immediate requirement,
             forecast)
         o   MEFLD004
             Determination of earliest delivery date for checking at time of
             goods receipt (PO only)
         o   MELAB001
             Generation of forecast delivery schedule: realization via creation
             profile
         o   MEQUERY1
             Enhancement for document overview ME21N / ME51N
         o   MEVME001
             Calculation of default GR quantity and over/underdelivery tolerances
         o   MM06E001
             User exits for inbound EDI messages and outbound purchasing
             documents
         o   MM06E003
             Number range and document number
         o   MM06E004
             Control of import data screens in purchase orders
         o   MM06E005
             Customer fields in purchasing documents
         o   MEREQ001
             Customer's own data in purhcase requisitions
         o   MM06E007
             Change document for requisitions when converting into POs
         o   MM06E008
             Monitoring of contract target value in case of release orders
         o   MM06E009
             Relevant texts for "Texts exist" indicator
         o   MM06E010
             Field selection for vendor address
         o   MM06E011
             Activation of requisition block
         o   MM06L001
             Exits for determination of ratings in vendor evaluation
         o   MMAL0001
             ALE source list distribution: outbound processing
         o   MMAL0002
             ALE source list distribution: inbound processing
         o   MMAL0003
             ALE purchasing info record distribution: outbound processing
         o   MMAL0004
             ALE purchasing info record distribution: inbound processing
         o   MMDA0001
             Default values for delivery addresses
         o   MMFAB001
             User exit for generation of releases
         o   MRFLB001
             Control items during release creation
         o   LWBON001
             Enhancement of LIS update through extension of the communication
             structure MCKONA (business volumes and rebate income)
         o   LWBON003
             Change settlement data for end-of-period rebate settlement before
             creation of settlement documents
         o   LWSUS001
             Customer-specific source determination in Retail
         Activities
         1.  Either create a new project or use an existing one and then enter
             the enhancement.
         2.  Activate the project
             Your enhancement will only become effective after activation.
         Further notes
         In contrast to modifications, enhancements are basically
         release-insensitive since they are not implemented in the SAP original
         but in a name range that is reserved for the customer.
         The general procedure for creating enhancements can be found in the
         enhancement transaction at Help -> Application help.
         If you want to display the documentation for an enhancement, choose Goto
         -> Documentation in the enhancement transaction.
    Return ->
         Application

Maybe you are looking for