User Exit for putting own stock placement logic in WM (Warehouse Managment)

Hi Techi's,
I have got one requirment for stock placement in Warehouse Managment as below:
If client uses the standared strategy for putting stock in Storage Bin as "Addition to Stock" Then the self life of the coming material is being replaced by the existing material's seft life.
If they use the "Next Empty Bin" strategy than the obove issue is not coming but system always searches for the full empty bin only thus wastage of the existing bin's which already has some space.
Now what my client wants is to use the "Next Empty Bin Strategy" so that self life is not being overwritten but along with system should not search the complete empty bin for placing the stock rather it should search the bin's which already has some space then later move to the empty bin's.
For good reciept they are using MB01.
In summary its a mixture of "Addition to Stock and Next Empty Bin" Strategy.
Please suggest me the Exit for this if available or tell me the code if already has implemented it. Friends its going very hot.
Please please help me.
Thanks in Advance.
-=Maddu=-

Hi Maddu,
If I undertstand it correctly,
System should search for the available Bin Capacity, and if there is space available the next incoming stock also need to be placed in the same Bin (system should suggest the Bin).
Now, let us consider the Physical process involved. Let us say, System suggested Bin A1001 and stock of Material A 500 Qty has been placed in some part of the Bin. Now, next time for the same material while incoming, system let us assume for time being suggested A1001 Bin due to available capacity. The operator should place the stock in the same bin, right. Assume that you have two quants in the Bin so that in system Shelf life date (GR Date) is different for these two different receipts. However, while Issuing even if system suggested Bin based on Shelf Life date, how the Operator will physically identify between the above two stocks. Hence, there should be physically some more identification parameters.
Under this case, either you can have Batch Management, (two have multiple quants) or Storage Unit Management. In this way, system will suggest the Identifier based on GR Date or Shelf life Exp date, also physically some labels placed to identify the different stocks in the same Bin.
I hope, it clarifies your doubt.
Last but not the least, user Exit will not solve your purpose.. instead operation process change involved along with Batch Identifier or Storage Unit Identifier.
Please reward points, if it helps.
Thanks & Regards,
Ramkumar

Similar Messages

  • User Exit for Put Away for multiple storage type

    Hi All ,
    we are using the exit EXIT_SAPML03T_002 for doing some capacity calculation and bin selection while doing a put away process in Ware house .
    now i want to have two different type of storage types
    say
    A and B ,
    if their are no empty bins in storage type A , then as per storage section search strategy the material should go in B storage type.
    Both the storage type has next empty bin search strategy with user exit activated.
    The difference between the two storage type is their individual capacity which is maintained in a custom table .
    I am facing the problem that the exit is getting triggered only once .
    ie. it will check for storage type A if the criteria is not met at a later stage while bin allocation , the system is not triggering the exit for B storage type .
    do i need to do all validation and possibilities of not getting placed in storage type A in the exit . or does this exit will trigger for each storage type as per strategy if for any reason the stock is not placed in the previous storage type ?

    Hi Experts
    Thanks for the response,
    As i tested for the 561 movement (initial upload) we need to do the put away manually.
    So the system will not suggest Full qty to move to one Bulk and partial to different.
    But for normal Goods receipt process the goods will be automatically placed to different storage type
    based on the search strategy and in the Bulk structure we need to unchek the  partial pallet allowed.
    If anybody has difference pls revert
    Regards
    Depin

  • User exit for PR

    hi all
    what we need is if the stock is available at other plants then the user should not able to create the PR
    is there any user exit for checking the stock at all plant while creating the PR,

    Are you talking about stock materials?  If it is stock material, normal practise is to create a reservation and not PR by manual creation.
    Normally Purchase Requisition is created by Plant users.  So they will just create the PR, as per their requirement, and they are not bothered about availability at other plants.  It is the job of inventory controller to see whether any stock is available t other plants. If any such stock exists at other plants, then he will advise plant perople to cancel the PR or this PR can be converted to STO.  So logically, we should not stop creating PR if stock is available at other plants.

  • User exit for f-42

    Dear Experts,
                          I have a one business requirement. During the transfer posting i.e. f-42 in vendor invoice, client want an billing document number with refrence to  accounting document number. So i want to add field in vendor invoice screen which shows billing document number.
                         So can anybody help me regarding this requirement? Is there any user exit available for f-42?
                         Thanks in advance.
    Regards,
    Sunil.

    Hi
    Exit Name           Description
    F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002            FIDCC1: Change IDoc/do not send
    F050S003            FIDCC2: Change IDoc/do not send
    F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006            FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001            Balance Sheet Adjustment
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    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)
    these are all user exit for tcode f-42  place break-point in all exits and run tcode see where it is trigger
    Thanks
    T Bharat

  • User exit for Stock transfer order

    Hi,
    My requirement is : i want to create a Stock transport order in which i have to set an error message based on the Document type and receiving plants country name.
    Say for an e.g. if my  doc type is STPO and plant is pl10(which belongs to Germany)then no error will come, but if
    doc type is STPO and plant is pl11 ( which does not belongs to Germany) In that case error has to occur.
    I want to put the logic in the code.
    Kindly provide me program name and user exit where i can implement this.
    Regards
    Utsav

    hi
    Please discuss with ur technical consultant and given ur functional need in Functional spec form for user exit .
    In that u have to mention eaxactly what u need i.e ur requirement regarding the user exit for STO process.
    So it can be done with ABAPer with you as functional consultant.
    Thanks
    SAP_MM

  • Logic and User Exit for Availabilty Check in Sales Orders,

    Hi All,
    I have a requirement of creating a Sales order from an Inbound IDOC. Before saving i need to do all the validations for the sales order including the availabilty check for the sales orders. If it is not  fulfilled i need to reject the sales order creation.
    I am trying to search for the logic for the availabilty check of the sales order but i am not able to find one. Please help me out with that and also i need the user exit for the availabilty check for the sales orders. Please help me out with that one too.
    Regards,
    Sharadendu

    See this function Module for message type ORDERS
    IDOC_INPUT_ORDERS all validations are there in this Function Module .
    Please reward if useful.

  • User exit for me 51 to put field descryption  for ekbn-sakpto in screen 505

    hi .
    i have a requirement to put field descryption in screen 505 for me51 tcode(program sapmm06b) for field g/l account in screen 505(Account Assignment for item 00010).
    waiting for your resposne.
    bye.
    sita.

    Hi Seetaram,
    Hi,
    By using the below code you can find the User exits for a particular TCODE.Execute this program and the TCODE in selection screen.
    REPORT z_find_userexit NO STANDARD PAGE HEADING.
    *& Enter the transaction code that you want to search through in order
    *& to find which Standard SAP® User Exits exists.
    *& Tables
    TABLES : tstc, "SAP® Transaction Codes
    tadir, "Directory of Repository Objects
    modsapt, "SAP® Enhancements - Short Texts
    modact, "Modifications
    trdir, "System table TRDIR
    tfdir, "Function Module
    enlfdir, "Additional Attributes for Function Modules
    tstct. "Transaction Code Texts
    *& Variables
    DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
    DATA : field1(30).
    DATA : v_devclass LIKE tadir-devclass.
    *& Selection Screen Parameters
    SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP.
    PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN END OF BLOCK a01.
    *& Start of main program
    START-OF-SELECTION.
    Validate Transaction Code
    SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
    Find Repository Objects for transaction code
    IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'PROG'
    AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
    SELECT SINGLE * FROM trdir
    WHERE name = tstc-pgmna.
    IF trdir-subc EQ 'F'.
    SELECT SINGLE * FROM tfdir
    WHERE pname = tstc-pgmna.
    SELECT SINGLE * FROM enlfdir
    WHERE funcname = tfdir-funcname.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'FUGR'
    AND obj_name = enlfdir-area.
    MOVE : tadir-devclass TO v_devclass.
    ENDIF.
    ENDIF.
    Find SAP® Modifactions
    SELECT * FROM tadir
    INTO TABLE jtab
    WHERE pgmid = 'R3TR'
    AND object = 'SMOD'
    AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
    WHERE sprsl EQ sy-langu
    AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
    WRITE:/(95) sy-uline.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    WRITE:/(95) sy-uline.
    LOOP AT jtab.
    SELECT SINGLE * FROM modsapt
    WHERE sprsl = sy-langu AND
    name = jtab-obj_name.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    WRITE:/1 sy-vline,
    2 jtab-obj_name 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).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
    Reward if helpful,
    phani

  • User Exit for Transfer Order

    Hi,
    I have a requirement to set the TO for the following raison :
    After the visual check of confirmed production the user have to check the HU to be  automatically transferred  to the bin already assigned in advance (principally for the completed HU)
    The incomplete pallet will be transferred  manually 
    Please suggest me the correct user exit, where I can put in my code, for this enhancement.
    Thanks in advance.
    Olfa

    I am not sure about your requirements, but you can try these enhancements:
    MWMTO001 Enhancements for end of transfer order generation
    MWMTO003 Own stock placement strategy

  • User exits for delivery picking confirmation and transfer order creation

    Hi
    We have a scenario for which we need help.
    This is to do with replenishment from plant to plant.
    We have sales sets.
    The sales sets needs to be replenished from one plant to another. We want the componenets of the sales sets to picked from the issuing plant. For this we need a transfer order. this needs tobe confirmed and then the goods issue should take place from the issuing plant. Its a two step process.
    we are doing Sales sets in STO. The explosion takes place in STO. However when we create deliveries for this. Only the sales set header item without its components are flowing into the delivery.
    The Tranfer order does not contain the components either.
    However post  the goods issue we  can create a TO with reference to the TR. This is is not acceptable because we want the picking and confirmation to occur before PGI from the issuing plant.
    Could anybody help: We want the TO to be created with the components even though in the delivery only the Sales set header appears. Can u suggest a user exit in which when we create the TR from the delivery the components of the set.
    After confirmation of the TO then we want the picking status to be put as C.
    Supreeth

    Hi,
    Check the following users exits.
    MWMRFSSG            user exit for sorting TOs in RF system-guided transaction
    MWMRFUP             Customer defined general purpose pushbutton called from scr.
    MWMRP001            Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
    MWMRP002            Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
    MWMRP003            Customer Exit for Replenishment using RLLNACH1
    MWMRP004            User Exit for Replenishment using RLLNACH4
    MWMTO001            Enhancements for end of transfer order generation
    MWMTO010            Exit: Calculation of Total Planned TO Processing Time
    MWMTO011            Correction of Planned Processing Time for TO Item
    MWMTO012            Correction of Sorting and Split Transfer Order
    MWMTO013            Stock Removal for Sev. Storage Types as in Stringent FIFO
    MWMTOAU3            Separate selection of posting changes for autom.TO creation
    MWMTR001            Exits at the end of transfer rqmnt creation (IM,PP interf.)
    MWMD0001            Transfer order print via RLVSDR40
    MWMD0002            Transfer order print as multiple process with RLKOMM40
    MWMIDI07            Enhancement for Output WMPIHU (Create Pick-HU) Inbound
    MWMIDO11            Enhancement for message WMTORD: TO with several items
    MWMIDO12            Enhancement for Output WMPIHU (Pick-HUs) Outbound
    MWMIDO13            Extension for WMMBXY (subsequent tasks after goods movement)
    MWMPP001            Enhancement WM/PP Interface (automatic TR generation)
    Regards,
    Murali

  • User exit for Credit Management check on SD document

    Is it possible to enhance and put in some custom logic during CREDIT check on SD documents?
    Can some one tell me which User exit can I used?

    Hi,
    Yes, I think you can do. Here is what SAP help says....
    If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    User exit for availability check
    User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
    This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
    Hope this helps
    Thanks
    Mukund S

  • User Exit for Partner Determination in VA01, VA02 transaction ( Sales order

    Dear All,
    I have an issue in which i need to determine partner for every change in ship to party both at header and item level during sales order creation or change.
    Can you please suggest an appropriate user exit for the same.
    I have tried
    EXIT_SAPLV09A_003
    EXIT_SAPLV09A_004
    but they get triggered only when we enter into VA01 transaction and not when the ship to party is manually changed.
    If possible i want to avoid MV45 exits as there are chances of regression due to too many different functionalities already present in my system.
    In worst case scenario please specify the place wherein i need to code in MV45 exits and what are the fields i need to change.
    Most probably i filtered out on "USEREXIT_MOVE_FIELD_TO_VBAP" but i am not 100 percent sure on this, please suggest.
    Thanks in advance
    Ronak

    Hi,
    please use User exit function: EXIT_SAPMV45A_003
    Put your coding in include: ZXVVAU05 (create it by double clicking, if not already created) and activate.
    Regards,
    Sanjay Gogikar

  • Badi & User Exit for ME21N & ME22N

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

    hi,
    Enhancement/ Business Add-in            Description
    Enhancement
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Business Add-in
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    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
    Rgds,
    Naren

  • How to maintian user exit for a wage type

    Hello Experts,
         I would like to maintain a user exit for a particular wage type in infotype 14. As the business rules of the client are specific...So, please help me with ur views...
    thanks

    Hi
    Check the LTA , I am not sure but still you can configure for the medical also .
    Now to lapse is again a issue.
    Well i think you can do it .
    Now how is the main thing , suppose i can give you one example you can get the better way your own.
    Now How you are going to put the values from IT 90--- to 15 are you going to put directly ?
    Now there is std prog pc00_mXX_remc  /  remp now check with this program which is suitable for you and add the codings whatever required in the the customized program which you using to put the values to IT15 .
    You got it now.
    It can be done .
    All the best.
    Manoj Shakya.
    <b>Reminder : Points should be given on answers.</b>

  • How to find user exits for a specific field

    hi,
        How can we find a user exit for a specific fields .
    as i know Three ways to search user-exits
    1. SE80 look includes in a packages with name user-exits
    2.  by zreport which will fetch user-exit in a T-CODE
    3. SMOD
    but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
    Please suggest me.
    Thanks and  Regards ,
    Rahul Singh.

    Hi Rahul,
    Here is the procedure to create field exits.
    Step by step procedure for creating Field Exits
    There are eight steps to creating a field exit:
    Step 1: Determine Data Element
    Step 2: Go To Field Exit Transaction
    Step 3: Create Field Exit
    Step 4: Create Function Module
    Step 5: Code Function Module
    Step 6: Activate Function Module
    Step 7: Assign Program/Screen
    Step 8: Activate Field Exit
    Step 1: Determine Data Element
    u2022     Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
    Step 2: Go To Field Exit Transaction
    u2022     The transaction to create field exits is CMOD.
    u2022     You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
    u2022     From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
    u2022     After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
    NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
    Step 3: Create Field Exit
    u2022     From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
    u2022     After choosing this menu path, a dialog box will prompt you for the appropriate data element .
    u2022     Enter the data element name and click the u2018Continueu2019 pushbutton.
    u2022     Now, you will be able to create the function module associated to the data elementu2019s field exit.
    Step 4: Create Function Module
    u2022     You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
    u2022     In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
    FIELD_EXIT_<data element>
    u2022     You can add an identifier (an underscore followed by a single character ).
    u2022     The first function module for a data elementu2019s field exit must be created without an identifier.
    u2022     To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
    u2022     After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
    u2022     Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
    Step 5: Code Function Module
    u2022     From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
    u2022     Here you will add your desired functionality for the field exit.
    u2022     Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
    u2022     You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
    Step 6: Activate Function Module
    u2022     After coding the function module, you must remember to activate it.
    u2022     Use the Function module -> Activate menu path to activate the function module.
    u2022     At this point, you can return to the field exit transaction.
    u2022     You should be able to 'green arrow' back to this transaction.
    u2022     When you return to the field exit transaction, you will see an entry for the newly created field exit.
    u2022     At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
    u2022     Also, the field exit will not be triggered yet because it is inactive.
    Step 7: Assign Program/Screen
    u2022     This step is only needed if you want to make a field exit local.
    u2022     To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
    u2022     In the dialog box , indicate the appropriate program name and screen number.
    This information indicates that the field exit is local to the specified screen in the specified program.
    u2022     In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
    u2022     If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
    u2022     If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
    Step 8: Activate Field Exit
    u2022     The field exit must be active for it to be triggered by the system.
    u2022     Activate the field exit by choosing the Field exit -> Activate menu path.
    u2022     After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
    NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
    Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
    Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
    then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
    and in the coding part, You can write your logic to display the output of that field. and activate it.
    once you complete the above,
    Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
    Hope it helps.
    Regards
    Radhika
    Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

Maybe you are looking for