Reset contract release strategy ME32K

Hi Gurus,
I need to reset the release strategy of the contract everytime some value on the item screen EKPO got changed.
I've already implemented the EXIT -> EXIT_SAPLEBND_002, but it only changes the header EKKO with the structure CEKKO.
Please help me ASAP.
Thanks.

For PR's, there is no header level data. Because vendor number is optional since it is internal document .
If you are releasing all line items at a time, need header level release.
If you release line item by line item, need item level release.
But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
That's vendor number is at header level field and line item in the PO are related to the single vendor.
You can release all the  items in the PO or u can reject entire PO, not a single line item.
That's why, only header level release is possible for the PO/Contract/SA.
Other  than this information  please  for through this  link
PO release at item level ? | SCN

Similar Messages

  • Contract Release Strategy - field Requisitioner

    Hello,
    I will start to use the Contract release strategy and I need the field Requisitioner (EKPO-AFNAM), because this field is part of my PO release strategy.
    This field isn't available in the transactions ME31K and ME32K.
    Can you tell me, if it's possible to show it in these transactions?
    In other case, where can I fill this field? How is the BAPI, BADI, etc?
    Thank you,
    Meire

    Hi,
    Please, be so kind to refer to note 373361. This field was only                 
    available in purchase requisitions and due to requirements of                   
    SRM (formerly BBP business tons business procurement  ), it has                 
    been added into the new enjoy transaction                                       
    ME21N/22N/23N for purchase orders.                                              
    It is not available for contracts.                                                                               
    The contract is  not  the last document in the procurement.In bussiness               
    process the requirement of requisitioner in contract is less important.         
    It is enough if you don't know the requisitioner at the time of contract but              
    you know it at the time of PO creation.                                                                               
    This is the standard SAP design.   Please do not use this field in the contract release strategy: create a new release group for the contract release strategy, delete the value entry for EKPO-AFNAM in the "Change view - release strategies - classificaion". The characteristic for EKPO-AFNAM should appear as black and not as blue on the screen. Save your strategy.
    Regards,
    Edit

  • Contract Release Strategy - Adding New Line

    I have a question regarding Contract Release Strategy - How can i force a release reset if a new line is added to the contract. I dont see a field in CEKKO - Any suggestions?

    Hi
    Version mangement is activated with Version Zero only. When you select Version 0 Ok
    If you have selected this indicator, version '0', which is generated automatically when a purchase requisition or external purchasing document is created, is automatically flagged by the system as Completed.
    If version '0' is completed automatically, the system does not check whether the version data includes any mandatory fields.
    If you have not selected the indicator, version '0' must be manually flagged as Completed.
    Only if this indicator has been selected for the current version:
    Can a requisition be converted into a PO (for example)
    Does the release procedure commence
    Thanks & Regards
    Kishore

  • Contract Release strategy

    Dear Guru,
    We have three types of contracts like A type, B type, C type......with these three types of contracts we have release strategy with different conditions.
                   For A type of contract : Release Strategy should trigger on cost center and value base.
                   For B Type of Contract :  Same conditons like above.
                   For C type of contract : it should trigger on duration base like.....if contract create for one year itshould trigger manager........if one year to two years it should trigger to director........if above two years it should trigger to CEO.
              This is my requirement.....how to configure this pls explain me.
    Best Regards,
    Bhaskar.

    Hi,
    You can only have one class and so you will have to use all of the characteristics from each type of check that you want.
    So you would need a characteristic of Cost centre, one for Value and one for start and end date. (in addition to whatever characteristic you are using to determine if the contract is type A, B or C.)
    With the release strategies you need to ensure that for type A and B contracts the date range characteristic is not checked and so you need to specify that all date ranges are included (so if the difference between the two dates is one day to 999 years).
    then on the release strategy for the type C contract, make sure that the cost centre and value characteristics are set to include all too (so cost centre 0000 to ZZZZ and value from 0.01 to 9999999, if you don't want either to be checked).
    this should work, the basic idea is that you ahev to have ALL characteristics included in every strategy but you use the values to make sure that you ignore certain characteristics in certain situations.
    Steve B

  • Reset the Release Strategy of PO when Terms of Payment key is modified

    Hi All,
    Please let me know how to reset the Release Strategy of PO, whenever the Terms of Payment Key value id modified.
    Thanks in advance.
    Regards
    Naveen

    Hi,
    This is not possible in SAP standard.
    You have to use User Exit;
    M06E0004 - Changes to communication structure for release purch. doc.
    And Function Module;
    EXIT_SAPLEBND_002 - Changes to Communication Structure for Release of Purchasing

  • Source Determination resets the release strategy of the PR

    Hi
    I am trying to automate the Purchasing Cyle by running ME57 as a batch job along with ME59n for stock items on contract, however when I create the PR and approve it, when ME57 picks this approved PR it assigns the source automatically but removes the approval! I am having the ABAP consultants debug this, however is there something elementary that I have left out?
    Regards
    Thasmei Reddy

    Check if u have release strategy based on vendor - FLIEF. This could be a reason. When u change the vendor or assign a vendor, the release strategy is getting reset .

  • Resetting RFQ Release Strategy

    Dear colleagues,
    We are using RFQ release to select appropriate bid among set of biddings. Suppose an RFQ is approved, letu2019s say RFQ number 10, within a set of RFQsu2019. After negotiations with vendorsu2019 new bids are made, letu2019s say RFQ number 20 and 30, which has fewer prices than the approved one. In this case RFQ release should be reset, but it does not.
    I know that SAP considers PO, RFQ, and Contract as purchasing documents and logic of release strategy are same.
    Is there any way to achieve this requirement?
    Regards
    Metin

    Hi,
    You are trying to use release for which it is not supposed to be.
    Release is for only for the approval of an RFQ before it is issued to Vendor.
    In your case if you are having multiple quotes for an item based on the negotiations carried out with vendor, the same should be updated to the existing RFQ created.
    For example you created RFQ-R1 for vendor V1 and RFQ-R2 for Vendor V2.
    When you first receive the quotations you maintain using ME47 for RFQ R1 and R2.
    Now when you negotiate with V1 and get a better price the same should be updated in R1.
    So this way R1 at any point of time will have the latest negotiated price.
    The item changes recorded when doing the changes can be viewed if you require. You may have to create a custom report to view these.
    Similarly the Me49 might need to be customized to suit to your comparison needs.
    Hope this clarifies.
    Regards

  • Contract Release Strategy - error

    Hi Guys
    I have one problem in Defining Release Strategy for Contract.
    scenario : i want to create RS for PR,Contract and PO for all the three.
    Well i am able to create RS for PR and PO but when i try to make RS for contract , it doesnt work.
    it give information message : - Purchasing document XXXXXXXXX not subject to RS. and "Message no. ME298"
    I am using the Same Table CEKKO for making the RS of contract.
    Characteristic
    1) GNETW - >=000*
    2) BSTYP - A CHECK BUTTON COMES FOR SELECTION:
    K Contract
    *F Purchase Order
    3) BSART - A CHECK BUTTON COMES FOR SELECTION:
    MK/ WK - Contract
    NB Purchase Order
    I have make the RS like this :
    Class : Est_lib_CEKKO
    Release Group : CO - for Contract/ PA and PB - for PO
    Release Code : CA/ AA/AB
    WHERE : CO -> CA, PA and PB --> AA/AB
    Release Indicator : 0 - RELEASE
    1 - BLOCKED
    in classification for CO
    1) GNETW : >=00,1
    2) BSTYP : K
    3) BSART : MK/WK
    If someone knows how to fix it, please i thank you.
    Regards
    Antonio Oliveira

    Hi,
    PO release strategy working fine, then you should not have any problem now for contract also as you have separate release group for contract CO, have own release indicators( PO & Contract)  and have following in RS of contract in classification
    1) GNETW : >=00,1
    2) BSTYP : K
    3) BSART : MK/WK
    Just change <=000 in GNETW and save, now try creating contract to have difference.
    Generally value are to be in GNETW others follow as per business (it may differs company to company) are as like example <=100000, 100000.01-1000000.00 & 1000000.01-20000000.00, > 20000000.00
    Regards,
    Biju K

  • Reset PR release Strategy - ME55

    Hi,
    Can someone advise if ME55 can be used to reset the PR release strategy collectively? If not, is there a transaction code that can do so. Till now, i can only ME54 to single reset the PR release strategy. Thanks.

    ME55 is to collectively release the PR not for resetting . so you have individually go in each pr and reset the release . there is no such tcode for collective reset.

  • Deleting of message type after reseting of release strategy

    Dear Team,
    My requirement is when the PO is finally release and outputted to vendor, its relaese indicator is set to 'R'(i,e, Relaesed, no changes) . Now if for any reason i have to do some modification , I have to repeat the output via ME9F so as it seems that PO is again ready to output. Now using transaction 'ME28'', I will goto derelaese the the PO
    Now I have the requirement, is there any way that just after dereleasing from ME28, the message type that I have added which allows me to reset the release, got deleted.
    That when now i goto ME22N, for making the modification, their must not be any preconfigured message type and genereated when do any changes.
    This is required to print the amendment in PO,
    So please suggest if their is any modification or enhacement available to achieve the above
    Regrads
    SAPABAP

    Hi,
    1st try with standard functionality and if not possible then go for enhacement. You needed in ME22N,if you do or make the modification in PO ,no preconfigured message type should be triggred automatically or no output genereated.
    Lets example you have PO message type ZNEU and its clear that you need preconfigured message type should be triggred automatically for PO output for PO creation ONLY. Use the below path:
    SPRO->MM->Purchasing>Message->Output control->Message tyoes-> Define message type for Purchase Order--->Fine-Tuned Control: Purchase Order
    As you needed,then DO NOT make entry or if entry is there,just DELETE for PO change not to trigges any message type
    {Indicator for print----
    condition type
    2----
    ZNEU}
    NOTE: Then think about how you will have PO print after any changes in PO.But you can think of not having automatically  PO message type on PO creation or PO changes and can ONLY enter PO message type manually for PO print.So do not select u201CAccess to conditionu201D check box in NACE t.code for your PO message type ZNEU.
    Regards,
    Biju K

  • Contract Release Reset when decreasing the Value

    Hi,
    As per our client requirement we need to reset the contract Release Strategy when there is a change in Total Value of contract.
    As per standard behaviour on decreasing the total value of the contract release is not reset.
    How we can acheive this.
    Regards,

    As you already have the answers in your question..
    That release strategy will never re-set if the value is decreased.
    It always gets reset if the value is increased with earlier value.
    Why you want to reset the release when the value is decreased, as the system value which was set earlier already had been released by your approver.
    And contract is ready to proceed for further process.
    The system behaves like even you decrease the value which was falling under the old value so it will not trigger the release again.
    If you want to reset the release again then you need yo increase the value which has not been released earlier..

  • ME38 resets Release strategy of Scheduling agreement

    Hello,
    It seems when the users change the delivery date  in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
    I cannot understand why this happens.
    Has anyone encountered such a problem before.
    Thanks
    Sunil

    Below are the (changed) item fields :
    Purchasing Document Item Change Date   AEDAT
    Item Delivery Date   EINDT
    Schedule Line is "Fixed  "FIXKZ
    Below are the (changed) header fields :
    Release Indicator: Purchasing Document  FRGKE
    Release status  FRGZU
    Purchasing document processing state PROCSTAT
    Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on  document type level ,I am also confused on this .
      Please assist  on this

  • Release strategy of PO creation under contract

    Hi,
    if PO creation without any contract, release strategy is required. However, if PO is created from contract, no release strategy should be used. Pls advice how to configure it. thanks

    The best option is you differentiate the PO document type i.e. create a seperate document type (ZNB) for those PO which are created wrt contract...Now while creating PO release strategy use PO document type (BSART) as one of the characteristic and there don't use this new PO document type (ZNB)
    Regards,
    Indranil

  • Release Strategy to be reset for any change in purchase order

    Hi Experts,
    At present the release strategy configured is for any change in the value of the purchase order, the release strategy is reset. Now the the client wants that for even any text change of a word, text, quantity, value, addition, deletion the release strategy should be reset.
    Can any one guide to configure the release strategy for any change. Also please provide the list of standard parameters/scenario (E.g. change of price, change of quantity etc) for which the release strategy can be configured to be reset.
    Thanks in advance.
    AJ

    Hi Diwakar,
    I too have the same problem. I tried with Changeable indicator "1". The system does not allow to make any change to the Purchase Order even after the first level of Release. But the requirement is that the system should Reset the Release Strategy for even minor Change in the PO.
    Regards,
    S.Raghavan

  • Reset Release Strategy for any change in the Purchase Order

    Hi,
    Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
    If so, where do we need to make the configurations.
    I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
    Thanks in Advance.
    S.Raghavan

    hi sandesh,
    sorry, i know it's too late.
    i tried your suggestion, it works blocking the purchase order after release strategies are setted.
    sandesh, raghavan:
    i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
    regards
    f

Maybe you are looking for

  • LV 8.2 Config File with Enum bug

    Please refer to attachment. Set the Enum and run the VI. The Enum is converted into string and then saved into a config file. The file is immediately read and the key is converted back to enum. It works fine until you choose index 32 in the enum. Eit

  • Are GPIB (PCMCIA) drivers available for Windows CE (H/PC2000)​?

    I am trying to install a gpib card in an HP jornada 720

  • Maximum Number of Substitutions in UWL

    What is the maxium number of substitutions you can set in the Universal Worklist? Thanks WB

  • How can i pass OCP 10G?

    i passed 1z0-042 exam. i wanna pass 1z0-043 or ocp 10G. tell me, how can i pass this exam?

  • Library transfer

    I have been using iphoto for a while now and have downloaded the trial aperture version. I imported my entire iphoto library into the aperture library, and now I'd like to delete my iphoto library to free up space. However I've noticed that when I go