Exit or Badi for FB01 to update KMNAM filed value to BKPF free field

Hi Experts,
Please provide me the correct Exits or Badi for to update KMKPF-KMNAM value to BKPF reference field while posting FB01.
I tired with substitution but it was not solved my requirement.
I have to update the KMNAM value into BKPF-XREF2 field as the user selects account assignment model while posting FB01.
Please advise and share me, is there any other solution you have.
Thanks & Regards
Sankar.

Hi ,
These is not exits or badis or BTE are not available eith import paremeters KMKPF.
So you need to get this value using  Assign statement in any user exit  which contains export parmeter as BKPF .
ASSIGN ('(SAPLSPO4)KMKPF-KMNAM) TO <fs_KMNAM>.
I hope this may helpfull..
Thank you,
Thanks,
AMS

Similar Messages

  • User exit or BADI for MIGO to Update a field in MSEG-KOSTL

    Hi,
    I want to update/change the KOSTL (Cost center) value before creating/posting  the document.
    Please let me know is there any user exits or BADI,  which will export the MSEG structure.
    Regards,
    Ganesh

    Hi
    I believe there isn't a BADI or EXIT allows to change item data, I usually use the exit to change the item text EXIT_SAPMM07M_001 (the BADI MB_MIGO_ITEM_BADI should be the same thing) where I change the data by field-symbols:
    FIELD-SYMBOLS: <KOSTL> TYPE MSEG-KOSTL.
    ASSIGN '(SAPMM07M)MSEG-KOSTL' TO <KOSTL>.
    <KOSTL> = .......
    Max

  • Need exit or Badi for updating Warranty data in IE02 while Prod Order conf.

    Hi All,
    I need a user exit or Badi for updating the Warranty data in IE02(Equipment Master) while production order confirmation(CO15)?
    I need to update the Begin guarantee date from Production order and warranty master type in IE02 while confirming the production order.
    Thanks,
    Sudha

    Hi,
    Are you saying first create notification,then service order
    and then Sales order.
    But the requirement is create notification then sales order and when you go in va02 and while modifying the sales order and create service order.
    Thanks & regards,
    chetan.

  • User Exit or BADI for Updating Tax code (MWSKZ) using ME21N

    Hi all,
    I am trying to fin out an exit or badi for Updating Tax code (MWSKZ) and Unit of Measure in transaction ME21n.
    The scenario is like this...
    For Purchase Orders Tax code will be defaulted from Purchasing info record or contract or parameter id for that item-vendor-plant.
    If the Tax Code is not defaulted and account assignment is blank then tax code on the PO is updated according to the below mentioned table
    Table
    Supplying Plant/              Receiving Plant                      Tax code
    Vendor/Country
    Any plant/vendor/
    country                           5050(NA)                               20
    2300                              6700                                     E0
    If the tax code on PO cannot be updated by the above table, then buyer needs to put tax code on the purchase order manually.
    Thanks,
    Shiva, Bangalore

    Hi Siva.,.,.,
    These r the exits.,..,which will be called while calling ME21N/ME22N/ME23N
    EXIT_SAPMM06E_006
    EXIT_SAPMM06E_007
    EXIT_SAPMM06E_008
    EXIT_SAPMM06E_009
    EXIT_SAPMM06E_012
    EXIT_SAPMM06E_013
    EXIT_SAPMM06E_014
    EXIT_SAPMM06E_016
    EXIT_SAPMM06E_017
    EXIT_SAPMM06E_018
    U want to default some values while the Initial screen will come right,
    while u Enter ME21N in command Prompt.,.,two exits will get triggerd,
    EXIT_SAPMM06E_014
    EXIT_SAPMM06E_016
    If u want to Default some values u can use these two exits.,.
    Try using EXIT_SAPMM06E_016.,.this will solve ur purpose.
    and if the user changes some values on screen.,,and you want them to get reflected .,.,.that means if user changes and saves data .,.
    While saving.,.,EXIT_SAPMM06E_012 and EXIT_SAPMM06E_013 will get triggerd
    Try using EXIT_SAPMM06E_013.,,.it was somehow the same requirement as mine.,.,IN my case it worked fine.,.,
    Regards
    Debasish
    Message was edited by:
            Debasish Das

  • User exit or BADI for ME22N

    Hi,
    I need a user exit or Badi for defaulting Plant at line item level.
    The scenario goes like this: when ever user tries to change an existing Purchase order and tries to add a new line item in it, I need to trigger USEREXIT or BADI , so that it reads the previous line Plant and updates the current line with the same plant.
    I tried with user exit MM06E005 but it didnt seem to work.
    Can any one please help me?
    I am new to BADI, so I am not sure how to find the BADI and use it. It would be great if anyone can help me i this.
    Thanks
    Ramya

    Hello
    The BAdI ME_PROCESS_PO_CUST is the right one. The method PROCESS_ITEM should be triggered whenever the user changes something in the purchase order at item level and executes any kind of function (e.g. ENTER, CHECK or SAVE).
    However, instead of overwriting the user input via the BAdI you should implement method CHECK ( Closing Check ) where you can validate the user input. If any of your validation fails you can send an error message and set CHANGING parameter CH_FAILED = 'X'. This approach is much more transparent for the user.
    NOTE: In order to "send" an error message you need to add the include mm_messages_mac to your implementing class. For an example see class CL_EXM_IM_ME_PROCESS_PO_CUST (should be available on ERP 6.0):
    METHOD if_ex_me_process_po_cust~process_item .
      DATA: ls_mepoitem TYPE mepoitem,
            ls_customer TYPE mepo_badi_exampl,
            ls_tbsg     TYPE tbsg.
      INCLUDE mm_messages_mac. "useful macros for message handling
    * here we check customers data
      ls_mepoitem = im_item->get_data( ).
      IF ls_mepoitem-loekz EQ 'D'.
    * check field badi_afnam
        IF ls_customer-badi_afnam IS INITIAL.
          mmpur_metafield mmmfd_cust_02.
          mmpur_message_forced 'W' 'ME' '083' text-003 '' '' ''.
        ENDIF.
      ENDIF.
    ENDMETHOD.                    "IF_EX_ME_PROCESS_PO_CUST~PROCESS_ITEM
    Regards
      Uwe

  • User exit or BADI for recruitment

    Hi,
    I am new to HCM, can you give me user exit or badi for recruitment.
    Requirement - i have developed an infotype which i am updating through BSP, while the custom infotype is updated it should simultaneously update some of my Z tables. Hoping for positve replies earliest.
    Thanks in advance:-
    Santosh

    Hi,
    <b>Infotype</b>The data fields of HR master data, time management and recruitment are grouped logically into information types or infotypes for short.
    Examples of infotypes are "Family/Related Person", "Organizational Assignment, "Basic Pay".
    The following naming conventions apply to infotypes:
    Infotypes 0000 to 0999 are used for HR master data
    and sometimes for applicant data
    Infotypes 1000 - 1999 for organizational management
    Infotypes 2000 - 2999 for time data
    Infotypes 4000 - 4999 for applicant data
    Infotypes 9000 - 9999 for customers
    <b>Function character of step</b>
    This controls for which types of processing (create, change and/or delete a data record) a dynamic action should be carried out.
    The processing type is indicated by a two-digit numeric value. These values can be added up; in other words, you can enter several processing types for each infotype, subtype or field. A dynamic action can also be carried out independent of the current processing type.
    00 for Independent of the current function carried out
    02 for Change
    04 for Create
    06 for Change and create
    08 for Delete
    10 for Change and delete
    12 for Create and delete
    Examples
    If you enter 06, an action is carried out if the specified infotype was created or changed.
    If you enter 00, an action is carried out irrespective of whether the specified infotype was created, changed or deleted.
    <b>Variable function part</b>
    The variable function part, which depends on the indicator for step, can have the following meaning:
    <b>P - Plausibility checks</b>
    You can enter values for specific infotype fields. Field names must be entered in full. Literals and constants can serve as comparison values. These must be enclosed by inverted commas. Variables can also be used.
    The old value of a field can be used for comparison; the field name must be preceded by PSAVE-.
    If fields of other infotypes are used for comparison, these must be stored in the module pool of the current infotype.
    The following comparison operators are supported:
    = equal to,
    < less than,
    <= less than or equal to,
    > greater than
    >= greater than or equal to and
    <> not equal to.
    Consecutive checks must be linked by a logical AND. Logical OR links must also be indicated by a /X.
    Note:
    Note that all checks with OR links must have a /X.
    If the result of the comparison operation is not "true", then the following commands (I, F, W etc.) are skipped over until a field is reached or a new comparison operation takes place.
    Examples
    Infotype  Field ..... Ind.   Variable function part
    0007      STAT3       P      P0007-STAT3='0'
    0007      STAT3       P      PSAVE-STAT3='1'
    The step is taken if the value in the P0007-STAT3 field changes from 1 to 0.
    0007                     P      P0013-KLKZ1<>'0'/X
    0007                     P      P0013-ALVKZ<>'0'/X
    0007                     P      P0013-RVKZ1<>'0'/X
    0007                    P      P0013-RVNUM=SPACE
    The first three conditions are linked by an OR; at least one of these conditions must be met. Condition 4 must always be met.
    The step is taken if the following holds true:
    P0013-KVKZ1 not equal to 0 or P0013-ALVKZ not equal to 0 or P0013-RVKZ1 not equal to 0, and P0013-RVNUM empty.
    <b>I - Maintain infotype record</b>
    Enter the step, infotype, subtype, object ID, start and end dates of the record and an indicator which defines whether the step is to be run in the background. The possible actions are INS, COP, MOD, and DEL.
    Use commas to separate selection criteria just like the separator in the matchcode. If an entry is missing, the system inserts a comma.
    Separate the indicator for suppressing dialog from other entries by a slash D (/D).
    Constants, such as those for subtypes, are not enclosed in inverted commas.
    Variable entries are also permitted. Fields containing such values must be put in brackets.
    Examples:
    Infotype  Field ....  Ind.  Variable function part
          ....             I    INS,19,01/D
    Step: Create a Dates record, subtype 01, run in the background
          ....             I    DEL,14,M559
    Step: Delete Rec. Payments/Deds. record with subtype (wage type) M559.
    0007 ....                I    INS,8,,,(P0007-BEGDA),(P0007-ENDDA)
    Step: Create a Basic Pay record (0008) without subtype and object ID. The start and end dates are the same as those in the current Planned Working Time record (0007); specify these two fields only if they are filled because the dynamic action was triggered by this infotype.
    <b>W - Default values for new record</b>
    Literals or variables are used as default values.
    Set the defaults for the infotype, subtype, object ID, start and end dates using an I step and not a W step.
    Do not set defaults for Q fields of an infotype because the values for these fields are derived from the corresponding P fields.
    Examples
    Infotype  Subtype  ..... FC  Ind.  Variable function part
    0021       2              04  I     INS,0015,M430
    0021        2              04  W     P0015-BETRG='10000'
    When a Family/Related Person record (0021) record with subtype 2 (child) is created, an Additional Payments record (0015) with a default amount of 100.00 is created.
    <b>V - Cross-reference to another step</b>
    Here, you can combine fields to groups. The variable function part contains the value in the field which follows the "field" column. Steps which are specified only for the following field are also triggered for each of the other fields.
    Examples
    Infotype  Field  ..... FC  Ind.  Variable function part
    0016       PRBZH        06  V     PRBZT
    0016       PRBZT        06  I     DEL,0019,01/D
    Infotype 0019, subtype 01 is deleted in the background when the field PRBZT or PRBZH in infotype 0016 is changed or created (function code 06).
    The following entries are equivalent:
    0016       PRBZH        06  I     DEL,0019,01/D
    0016       PRBZT        06  I     DEL,0019,01/D
    <b>F - Call a routine</b>
    You can call internal (module pool) as well as external routines.
    If you call external routines, type the program name in brackets after the routine name. Do not specify 'using' parameters. When calling an external routine, all data must be declared in a common part. You can use the fields of structure RP50D to return values from the routine. These are not used in the standard system and can only be populated via the routine and then can be used for defaults (W-Commands).
    This allows customer-specific routines to be formulated with all the above steps.
    Example 1:
    Infotype  Field  .....  Ind.   Var.function part
    0016      PRBZT         F      PROBATION
    0016      PRBZT         I      INS,19,01
    0016      PRBZT         W      P0019-VTRMN=PRBEND
    Module pool MP001600 contains the PROBATION routine. This routine uses the entries in the fields P0016-PRBZT and P0016-PRBEH to determine the end of the probation period which it stores in the field PRBEND.
    The system creates a new 'Dates' record with the reminder date = PRBEND.
    Example 2:
    Infotyp ..... Ind. Var. function part
    0001           F      GET_DATE(ZPUDYN01)
    0001          I      INS,19,01
    0001           W      P0019-VTRMN=RP50D-DATE1
    The GET_DATE routine in program ZPUDYN01 calculates a date and enters this date in the RP50D-DATE1 field via "TABLES RP50D" in ZPUDYN01. This date can be user-defined in GET_DATE: if necessary, user-defined infotypes can be read afterwards.
    <b>M - Send a mail</b>
    Enter the name of the feature which defines the characteristics of the mail.
    Example
    Infotype  Field  .....  Ind.    Var.function part
    0001     SACHP         M       M0001
    A mail is sent when the field SACHP is changed. The characteristics of the mail are defined in feature M0001.
    In the standard system, feature M0001 is provided as a model. The documentation on feature M0001 explains how to define the characteristics of a mail.
    <b>ADDITIONAL HINTS</b>
    If you use a date as a constant, enter it as YYYYMMDD (YYYY=year, MM=month, DD=day).
    The table strings T001P, T503 and PSPAR are filled with the values which are valid on the record start date.
    The old values of the infotype are stored in the field string PSAVE. The structure of this string is the same as the Pnnnn structure (nnnn=infotype). The structure is filled with (valid) values only when the delete, change and create functions are used.
    Please read Create dynamic actions in the Implementation Guide.
    Regards
    Bernd

  • User-exits or BAdI for transaction VL10B

    Hello everybody,
    I have to modify an outbound order during its creation from a purchase order in transaction VL10B. The modification is to update the serial numbers and the batch.
    As the process is in background it is quite difficult to debug the process plus the problem that in this project I cannot modify the user-exits / badi just for testing. (they have implemented 'special' rules for these kind of modifications)
    Does anybody know any user-exit or BAdI where I can update these serial numbers in this transaction VL10B?
    Thanks in advance

    Hi,
    Check [ABAP Ninja|http://www.abapninja.org/] it may help you will the search.
    Regards
    Marcin

  • User Exit or BADI for ME21N

    Hi All,
    We are in a situation where in we need to Change the Distribution Channel in the Shipping tab of ME21N transaction.
    Previously, the distribution channel is being picked up form the config (SPRO - Shipping data for plant) but before it picks up from the config we need to change it and update the other distribution channel in the PO.
    We have tried with most of the User exits and BADIs but all of those are of no use for our requirement, as these user exits and badis are triggered after we click on save button. But we need to change the Distribution channel at the point of determination of Shipping data by the system i.e. before save.
    Can any one please help me out with this situation with some User exits or BADIs that are triggered before save button.
    Note: The Shipping data is in EKPV table. We need to change the VTWEG field in EKPV.
    Thanks in Advance,
    Asif Ali Khan

    Asif,
    see these are Exits and BADI for ME21n,
    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)      
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.    
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N                   
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance    
    MM06E001                                User exits for EDI inbound and outbound purchasing documents   
    MM06E003                                Number range and document number                               
    MM06E004                                Control import data screens in purchase order                  
    MM06E005                                Customer fields in purchasing document                         
    MM06E007                                Change document for requisitions upon conversion into PO       
    MM06E008                                Monitoring of contr. target value in case of release orders    
    MM06E009                                Relevant texts for "Texts exist" indicator                     
    MM06E010                                Field selection for vendor address                             
    MMAL0001                                ALE source list distribution: Outbound processing              
    MMAL0002                                ALE source list distribution: Inbound processing               
    MMAL0003                                ALE purcasing info record distribution: Outbound processing    
    MMAL0004                                ALE purchasing info record distribution: Inbound processing    
    MMDA0001                                Default delivery addresses                                     
    MMFAB001                                User exit for generation of release order                      
    MRFLB001                                Control Items for Contract Release Order                       
    LMEKO001                                Extend communications structure KOMK for pricing               
    LMEKO002                                Extend communications structure KOMP for pricing               
    MM06E011                                Activate PReq Block                                            
    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             
    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                             
    M06B0002                                Changes to comm. structure for purchase requisition release  
    M06B0001                                Role determination for purchase requisition release                                                                               
    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
    Amit.

  • User exit or BADI for standard change Log ?

    Is there user exit or BADI for standard change log update ?
    I want to update a customer fields into standard change log table.
    Could someone tell me about it?

    Could anbody tell me ?

  • User Exit or BADI FOR ME59N

    Hi All,
       My requirement is in ME59N if Document Type is ZCD or ZSD it should not consider the Rounding Value (MARC-BSTRF) which is coming from Materrial Master (MRP1 View) and Purchase Info Record (EINE-RDPRF) which is coming from Purchase Info Record(ME12 or ME13), Can any one suggest me the right User Exit or BADI for this, Please go through the requirement.
    Regards,
    Sudhakar .A
    Edited by: Sudhakar Allam on Feb 5, 2010 4:31 AM

    HI Sudhakar ,
                              These are the list of enhancements and Badi's available for ME59N ,
    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
    AMPL0001                                User subscreen for additional data on AMPL
    MRFLB001                                Control Items for Contract Release Order
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    M06B0003                                Number range and document number
    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
    The list of Badi are
    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: 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_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_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Leve
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKK
    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
    regards.

  • User Exit or Badi for MIRO

    Hi
    I need add some validations to data entry in MIRO for send their respective error messages and stop data saving.
    Does somebody knows some User Exit or Badi for make validations in MIRO ?
    Regards
    Frank

    Hi,
    you can use badi MRM_HEADER_CHECK. In order to put error message you can use function module
    PROT_FILL.
    * If there is any error do not allow posting
        DATA: gt_errtab    TYPE TABLE OF mrm_errprot,
              gs_errtab    TYPE mrm_errprot.
        CONSTANTS:     c_errprot(23)   TYPE c VALUE '(SAPLMRMF)TAB_ERRPROT[]'.
        FIELD-SYMBOLS: <fs_errprotj_dt> TYPE table.
        ASSIGN (c_errprot) TO <fs_errprotj_dt>.
        REFRESH gt_errtab[].
        gt_errtab[] = <fs_errprotj_dt>[].
        IF NOT gt_errtab[] IS INITIAL.
          READ TABLE gt_errtab INTO gs_errtab WITH KEY msgty = 'E'.
          IF sy-subrc = 0.
            DATA: c_okqx(17)   TYPE c VALUE '(SAPLMR1M)OK-CODE'.
            FIELD-SYMBOLS: <fs_okqx> TYPE ANY.
            ASSIGN (c_okqx) TO <fs_okqx>.
            CASE <fs_okqx>.
              WHEN 'BU'. "POST
    * This is optional: you can either search for a particular message or
    * do not allow any error message
    * Here search for the message triggered in badi INVOICE UPDATE
                READ TABLE gt_errtab INTO gs_errtab WITH KEY msgty = 'E'
                msgid = 'ZXX' msgno = '030'.
                IF sy-subrc = 0.
                  CLEAR <fs_okqx>.
                  MESSAGE s030(zxx). "While errors exist document will not be posted
                ENDIF.
            ENDCASE.
          ENDIF.
        ENDIF.
    This is used to give error message in case before posting the document.
    KR Jaideep,

  • User Exit or BADI for Material,BOM,Customer,Vendor

    Dear All,
    I have requirement where if User A changes a Material X .It should go for approval by workflow.
    When the Material X is waiting for approval no other User should be able to change the material .It should give him a message
    and restrict him from changing the Material.
    Is there any User Exit or BADI to restrict him from changing the material. The exit or BADI should be called as soon as the Material is entered in MM02.
    I need exit or BADI for BOM, Vendor and Customer also.
    Thank you.

    Hi,
    You can go to Transaction SE80 and check in Function Group MATF. There have been two User Exits which are called during MM02 Transaction execution (via Analysis Transaction SE30) - MATERIAL_FIELD_SELECTION_NEW and MATERIAL_FIELD_SELECTION_COMB.
    BAdI called by FM MATERIAL_FIELD_SELECTION_NEW.
    Thanks and Regards,
    Prabhakar Dharmala

  • User exit or BADI for Tcode ME51N

    Hi All,
    My requirement is i need to check available quantity at the time of Purchase req creation. If PR quantity is available in stock then it should not allow to create new PR.
    Is there any user exit or Badi for this requirement. Kindly send me.
    Regards,
    Paras

    Hai,
    User Exit:  MEREQ001
    Function exit             EXIT_SAPLMEREQ_001  
                                   EXIT_SAPLMEREQ_002  
                                   EXIT_SAPLMEREQ_003  
                                   EXIT_SAPLMEREQ_004  
                                   EXIT_SAPLMEREQ_005  
                                   EXIT_SAPLMEREQ_006  
                                   EXIT_SAPLMEREQ_007  
                                   EXIT_SAPLMEREQ_008  
                                   EXIT_SAPLMEREQ_009  
                                   EXIT_SAPLMEREQ_010  
    Screen exit               SAPLMEGUI           
    Include tables           CI_EBANDB           
                                   CI_EBANMEM

  • User exit or badi for me52n transaction.

    Hi all,
           i have a requirement to write a user exit or badi for me52n transaction. the requirement is in header section, only one plant should be accepted. that is in the first row one plant will be inserted. in the second row if we are inserting another plant other the first row plant, it should not accept it and it should raise an error.
    that is from the second row onwards, every plant should match with the first row plant.
    if any part of this issue is unclear, plz let me know so that i can explain it clearly
    this is urgent requirement.
    please let me know the solution as soon as possible.
    points will be awarded.
    thanking u in advance.
    A.srinivas.

    In this version exit EXIT_SAPLMEREQ_005 should exists (look at OSS <a href="https://service.sap.com/sap/support/notes/843446">Note 843446 - MEREQ001: Cannot call up external service data in user exit</a> this note refers to the exit and is applicable in  4.70. Look also at OSS <a href="https://service.sap.com/sap/support/notes/310154">Note 310154 - ME21N/ME51N: Customer-specific check, generating error log</a>
    Regards

  • User Exit or Badi for CN22

    Hi All
    Can anyone tell me an user exit or badi for Tcode CN22 which gets triggered when i save a network.
    whenever i make changes in the WBS assignment of the network in the activity level then the i need to copy dates to other networks whenever a change in WBS element is done. Please treat this as pretty urgent
    Thanks
    Sowjanya

    Hello,
    Please check and see if the BADI
    <b>"AFABD_CHANGE"</b> suits your requirement
    it has
    <b>AFABD
    Network: Dialog table for AFA</b>
    as a changable parameter....
    and import parameter as
    <b>CAUFVD                       
    Dialog Structure for Order Headers and Items</b>
    Reward if helpful
    Regards
    Byju

Maybe you are looking for

  • Ipod nano not playing songs

    I just got my ipod nano, I downloaded all the new software, downloaded itunes music onto ipod and when done I tried to play music and it doesnt play when it gets to the songs it shuffles through them and goes back to menu. plaese help.

  • How to view an Interactive PDF on an iPad?

    My PDF uses three types of buttons: (1) buttons that go to next/previous or a desination page; (2) Buttons that show or hide other buttons – all of these are generated entirely from InDesign and, (3) Layer visibility buttons - which are created in In

  • Hyperlinks in illustrator work, export to pdf hyperlinks are gone...

    I created some figures in illustrator, added hyperlinks to the figures using the 'attributes' menu, added url etc. When clicking the object, i can see the url is appearing in the attributes window in illustrator. But, i want to export / save the illu

  • Could Latest iTunes and Quicktime Wipe Out Your DVI Monitor

    I have loaded the latest QT and iTunes. After doing this, the monitor comes up with a VGA default driver and is 800x600. I cannot get back to my higher resolution. I have to unistall iTunes and QT and restore my config files back prior to the iTunes

  • Read/get xml data (string)

    Hi I have a XML string that I get from a TCP transfer, I have attached a received string. I have no experience in reading XML data, I have tried looking in the forums and some of the examples in LV, but I cannot get it to work, so I hope that someone