Enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22

Hi Experts,
I am writing some logic while PO creation in the user exist ZXM06U22.
As per my understanding this user exit should trigger for all the company code but its getting triggere for only few company code, I am not able to understand why its not getting trigger for all the company code.
its already in use for some other functionality.
Please suggest.
Sagar.

Hi Sagar,
The Enhancement M06E0004 is basically used to change the communication structure, which can inturn be used to trigger the release strategy if you want to calculate few values in runtime.
If the exit is not getting triggered for few company codes i would suggest you to check the functional configuration steps where characteristics, groups, codes, strategies are defined.. may be there are chances that few company codes are not configured for release strategy.
Regards,
deepak.

Similar Messages

  • USER-EXIT,   EXIT_SAPLEBND_002 , ZXM06U22

    I am using the Function module EXIT_SAPLEBND_002, I have to write the code into INCLUDE ZXM06U22.  There i am fetching release group and release strategy, after that I have to  populate those fields while creating a PO.
    Here in EXIT_SAPLEBND_002 there are no export parameters for FRGGR, FRGSX, FRGZU, FRGRL, FRGKZ, how can I export these values out ?
    I m trying to give Info message in the include but it is not triggering.
    Is there any separate way to give info message
    I have seen by searching in SDN, but i did'nt get exact solution.
    Thanks,
    Ajay

    First check if this is the correct exit for you.
    If you want to access variables or the main program, outside the exit you have to use the assign statement.
    See example:
    http://www.sapdev.co.uk/enhance/enhance_fsymbol.htm
    And lastly, You have to create a project in CMOD for your exit and activate the project.
    Then only the exit will work.
    Regards,
    Ravvi

  • Enhancement  M06E0004  P.O. Release strategy

    Hi ALL,
    How to correct the below error message.
    *********SAP log** tcode :OMGSCK
    You must maintain a customer exit for characteristic Z_COSTCENTER
    Diagnosis
    You have linked the characteristic Z_COSTCENTER with field USRN1 of the communication structure CEKKO. In the standard system, this field is not populated. The data must therefor be determined in a customer exit.
    Example
    The person responsible for a cost center in a purchase requisition is to be determined. The name of this person is read from the cost center master record, placed in the field USRC1, and passed on to communication structure CEBAN.
    The following customer exits are available to you:
    Purchase requisition M06B0002
    PO, RFQ, contract,
    scheduling agreement M06E0004
    Procedure
    Check that you have maintained the relevant customer exit.
    if any one has work on I_CEKKO this structure and used USRN1 field to validate some condition.
    Please write me ..
    Thanks ,
    Shravan

    Hi ALL,
    How to correct the below error message.
    *********SAP log** tcode :OMGSCK
    You must maintain a customer exit for characteristic Z_COSTCENTER
    Diagnosis
    You have linked the characteristic Z_COSTCENTER with field USRN1 of the communication structure CEKKO. In the standard system, this field is not populated. The data must therefor be determined in a customer exit.
    Example
    The person responsible for a cost center in a purchase requisition is to be determined. The name of this person is read from the cost center master record, placed in the field USRC1, and passed on to communication structure CEBAN.
    The following customer exits are available to you:
    Purchase requisition M06B0002
    PO, RFQ, contract,
    scheduling agreement M06E0004
    Procedure
    Check that you have maintained the relevant customer exit.
    if any one has work on I_CEKKO this structure and used USRN1 field to validate some condition.
    Please write me ..
    Thanks ,
    Shravan

  • Derelease of Purchase order in case of reducing the value

    Hi Friends,
    When ever we increase the value in Purchase Order it will derelease.
    But we want to derelease the Purchase Orders if we reduce the value
    also. Can we do this with any user exit or BADI.
    We also want to have if any changes happen in perticular field, it shoudl DERELEASE PO, how to do this ?
    Regards,
    Sai Krishna

    Hi,
    We can do using the following logic / BADI / user exit:
    User exit
    During the individual release for purchase requisitions, the user exit is called in function module ME_REL_STRATEGIE_EBAN, in the overall release, it is called in function module ME_REL_GENERAL_STRATEGY_EBAN.
    (Enhancement M06B0002, EXIT_SAPLEBND_001, ZXM06U13)
    During the release for purchase orders the user exit in function module ME_REL_STRATEGIE_EKKO is called, in releases > 3.1X in program MM06EF0S_STRATEGIE_CEKKO (Enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).
    The data is available in the user exit in structure I_CEBAN or I_CEKKO. The transfer from this structure to the calling program runs using structure E_CEBAN or E_CEKKO. In the user exit, I_CEBAN must be copied to E_CEBAN or I_CEKKO must be copied to E_CEKKO anywhere in the user exit, for example E_CEBAN = I_CEBAN.
    Regards

  • PO release strategy based on Account Assignment Cat (CEKKO - KNTTP)

    Hi Experts,
    I want to configure the release strategy for PO on account assignment category.when i  maintaining a characteristic for account assignment cat by inputing CEKKO- KNTTP , sys throughs error message. I looked in to CEKKO but I could not find the field .Kindly tel how maintain teh same .
    Regards,
    Kumar.

    Hi Kumar,
    Account Assignment Category and Item Category belong to the item level and not to the header level of a purchase order (table EKPO). Therefore,   neither Account Assignment Category nor Item Category are available in CEKKO.As work-around you can use the following user-exit:                                                                               
    MM06EF0S_STRATEGIE_CEKKO                                                   
    (enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).                       
    In this user-exit the data are available in structure I_CEKKO.   The hand-over from I_CEKKO to the calling program is via structure E_CEKKO.   In the user-exit I_CEKKO has to be copied to E_CEKKO , e.g. 
    E_CEKKO = I_CEKKO.                                                                               
    Please also see our FAQ note 365604, it is worth reading.  
    Regards,
    Mauro

  • PROBLEMS WITH ME32L

    Hi everyone.
    Iam facing a Problem in release Strategy of PO.We have a requirement like this.when we create a PO and Release the PO through ME29N,after that when u change the value (in change changes the net effective Price(ekpo-effwr) ) of PO in the Transaction ME22N,the released PO should get unreleased.
    For this iam using the Enhancement M06E0004 (Function module EXIT (EXIT_SAPLEBND_002)).
    In the Include ZXM06U22 iam checking for the ekpo-effwr .so when the Value changes in the Transaction ,it will be compared with the database value .If it is not equal iam Populating the E_cekko-uscr1 = 'ME22N'.In the customisation the Functional guys are using for the Release strategy.
    <b>The Problem is this exit is working fine only for the first time after that it is not having efffect on the Release.</b>
    If anyone of you guys have an answer please help us with that solution.
    thank you
    regards
    Fede

    Hi Csound1
    approx every 30 seconds the browser freezes and 'saving' appears in the top bar of icloud mail. The cursor starts spinning and then after about 8 secs I can start typing again. I also fiund that about 5-6 times a day my icloud browser tab showing mail just close and return to the main icloud menu page showing icons for mail, calender, notes etc

  • Vendor account group as PO Release characteristics

    Dear All,
    I want to use Vendor account Grp as PO Release strategy characteristics.
    Whether can i use Vendor account grp as characteristics ? If so, what field to be used in CT04 to create?
    Regards
    Edited by: Venkateshwaran Balaji Kannan on Feb 29, 2012 9:24 AM

    Hi,
    Please take into account that in standard design system only considers
    characteristics from CEKKO structure for release strategy consideration.
    But it will not stop you in selecting the other characteristics.
    Please go through the IMG help of release strategy, will give good
    information.
    I think you have already read the note:
           The characteristics of the class used must all be linked to the
           corresponding fields of structure CEBAN or CEKKO (for purchase
           orders)...."
    Characteristics which are created for the release strategy with
    classification MUST access communication structures CEBAN or CEKKO since
    during the strategy determination, the system cannot access any other
    tables or structures.
    If the characteristics refer to fields which are not contained in
    structures CEBAN or CEKKO, the corresponding fields can be added to
    communication structure CEKKOZZ or CEBANZZ, or an append structure can
    be created for CEKKO or CEBAN in which new fields can be included.
    If you want to use new defined fields as part of the
    release strategy clasification, you should use enhancement M06E0004
    (User exit "exit_saplebnd_002").This user exit allows you to use the
    user fields in strucure CEKKO to include additional data.
    Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and
    control them through user exit "EXIT_SAPLEBND_002. Otherwise new field
    will not work.
    BR
    Nadia Orlandi

  • Chek budget in PO with release strategy

    Hi
    When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
    Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
    Thank's
    serge

    Normally checks like those happen once the PO is released ( example  - output is not allowed etc)...
    You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
    Name of the Enhancement: - M06E0004
    Name of the function module: - EXIT_SAPLEBND_002
    Hope this helps

  • User exit for route determination in Stock trasnport order

    Hi All,
    Can somebody help me with a user exit that I can use for route determination in the Stock transport order.
    Kind Regards
    Chakradhar

    Exit to be used is   EXIT_SAPLEBND_002. Enhancement M06E0004.
    DATA it_ekpo TYPE LINE OF mmpur_bekpo .
    To have controls in system for Standard Cost Estimation under two conditions if SCE is not run then,
    1)      System will not allow creating Process Order (COR1).
    2)      System will not allow Post Goods Issue (VL02N).
    Till date we do not have any control of SCE while creating Stock Transport Order.
    Now we have another control for SCE, that is
    3)      Henceforth system will not allow creating STO (ME21N).
    IF sy-tcode = 'ME21N' OR sy-tcode = 'ME22N'.
      IF i_cekko-bsart = 'UB'.
        LOOP AT it_bekpo INTO it_ekpo.
          SELECT SINGLE mtart FROM mara INTO mara-mtart WHERE matnr = it_ekpo-matnr .
          IF mara-mtart = 'IFIG' OR mara-mtart = 'ISFG'.
            SELECT SINGLE * FROM mbew WHERE matnr EQ it_ekpo-matnr
                                                AND bwkey EQ it_ekpo-werks.
            IF mbew-vprsv = 'S'.
              SELECT SINGLE * FROM mbew WHERE matnr EQ it_ekpo-matnr
                                              AND bwkey EQ it_ekpo-werks.
              IF mbew-stprs > '0.00'.
                CONTINUE.
              ELSE.
                MESSAGE e004(zpp) WITH it_ekpo-matnr it_ekpo-werks.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDLOOP.
      ENDIF.
    Regards,
    Mallick

  • PR Release strategy

    Dear All,
    We want that if any user change account assignment(Cost center,G/L.Order etc..) in PR the release should reset and need reapprovals.
    Please let me know how we can achieve this.
    Thanks.

    Hi ,
               In standard design system only considers characteristics from         
    CEKKO structure for release strategy consideration. But it will not              
    stop us  in selecting the other characteristics.                                                                               
    Please go through the IMG help of release strategy, will give good               
    information.                                                                               
    I think you have already read the note:                                                                               
    The characteristics of the class used must all be linked to the           
           corresponding fields of structure CEBAN or CEKKO (for purchase            
           orders)...."       
    Characteristics which are created for the release strategy with           
    classification MUST access communication structures CEBAN or CEKKO since  
    during the strategy determination, the system cannot access any other     
    tables or structures.                                                     
    If the characteristics refer to fields which are not contained in              
    structures CEBAN or CEKKO, the corresponding fields can be added to            
    communication structure CEKKOZZ or CEBANZZ, or an append structure can         
    be created for CEKKO or CEBAN in which new fields can be included.             
    If you want to use new defined fields as part of the                           
    release strategy clasification, you should use enhancement M06E0004            
    (User exit "exit_saplebnd_002").This user exit allows you to use the           
    user fields in strucure CEKKO to include additional data.                      
    Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and        
    control them through user exit "EXIT_SAPLEBND_002. Otherwise new field         
    will not work.                                                                 
    As you very well know SAP has provided the following customer exits     
    which allow us to change the communication structure for determining    
    the release strategy                                                    
    Purchase requisition                                              
                           M06E0002 - for item wise release             
                           M06E0005 - for overall release                                                                               
    External purchasing document                                      
                           M06E0004                                                                               
    I hope this helps!
    Regards
    Vijayesh V V

  • PO Release strategy on Overall Limit

    HI All,
    Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
    For limit PO it triggered on Exepected value but we want to trigger it on Overall Limit value.
    ( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
    Please help on this.
    Thanks in advance
    Vikas

    Dear Vikas,
    you can use enhancement M06E0004 , Exit EXIT_SAPLEBND_002.
    This allows to change values in structure CEKKO based on specific conditions.
    First after activating you have to put this line:
    e_cekko = i_cekko.
    This means that no change will be made to cekko structure. Then if you want to change gnetw value, do something like this:
    e_cekko = i_cekko.
    If xxxxxxxxxxxxxxx.
    e_cekko-gnetw = xxxxxxxxx.
    endif.
    Maybe you can have multiple items so you will have probably to loop on IT_BEKPO table to get the total  Overall Limit for all items in your document and then transfer the total value.
    Good luck,
    SL

  • How to users from releasing a contract that they have created

    Hi,
    can someone tell me how tp stop users from releasing a contract that they have created and or changed.  It should be released by a different user.
    I've been doing some investigation, and it looks as if function module EXIT_SAPLEBND_002 (SAP Enhancement M06E0004) might be the User-Exit that I may need. Does anyone know if this is correct?
    John

    Hi,
    You posted your query to wrong forum, should be posted to MM forum.
    Anyway probably your users have the authority of transaction code ME35K (Release) and authority object M_EINK_FRG (Release Code and Group (Purchasing)) to be able release contract that they created.
    Regards

  • PO Release strategy User Exit  if value is Reduced

    Hi,
    I need to write a user exit to trigger the release strategy in Purchase order even if the value is "Reduced".
    As you may be knowing releases will only be triggered if the value is increased according to standard SAP functionality.
    So to trigger the release stratgey even if the value of PO is reduced some one suggested me user exit "M06E0004" Program :ZXM06U22.I guess we need to define a new characteristic called "URSC1".But cannot make out how really i can achieve this.
    Can any one please guide,if you have worked on it earlier.
    Thanks.

    Gentlemen,
    Any Ideas....!!!

  • User Exit for Requisition Release Strategy

    Hi All,
    Is anyone able to provide any guidance on determining the release strategy of a purchase requisition via a user exit? It has become neccessary to do this due to certain shortcomings of the classes and characteristic functionality.
    I believe it's possible, I just don't know how.
    Thanks.
    Richard

    go SMOD and enter enhancement M06E0004      it is exit LXM06U13

  • Purchasing document **** cannot be released

    Dear exports,when I implement the Enhancement M06E0004, the Release strategy EKKO-FRGSX   is null ,so i can't release Purchasing document, can anybody help me, and tell me why?

    >
    Chandralekha wrote:
    > Hi,
    >
    > Check the entry EKKO and cehck the status for that FRGSX field. If it is null then try to update the entry using the UPDATE <<TABLE>> set frgsx ='<<value>>'  where ebeln = '<<valkue>>.
    >
    > Pls try to udpate statement and try to set the entry and try to run the exit.
    >
    >
    > Reward if helpful.
    >
    > Best Wishes,
    > Chandralekha
    NO, you do NOT do a direct table update on EKKO to fix a little problem like this - or to fix any problem. 
    The release strategy for your POs is set up for each PO order type in config.  Ask your functional consultant why this is not set in the way you expect.

Maybe you are looking for