Release strategy retrigger for all non significant changes

HI,
My client has the below requirement:
The Purchase requsitions and Purchase orders are released by different approval authorities. Any change made to any field like material short text, cost centre, payment terms, material long text, etc. the sytem has to cancel all the previous releases and release strategy need to be retriggred from the beginning.
I request all to provide me with an user exit or badi if any available in the system to achieve this.
Regards,
Rayeesuddin

Dear Ray,
First discuss this with your functional consultant (MM) from functional point is there is any setting.
Regards,
D.Srinivas.

Similar Messages

  • Release Strategy Processor Names under Release Strategy tab for a PReq

    Hello Experts,
    We have situation in Release Strategy for Purchase Requsitions in which we need to display all approvers names under the Release strategy tab for a Purchase Requisition.
    Senerio work as follows.
    Based on the Release strategy customization settings,Purchase Requisition subjected to release strategy selects the approver names from a custom table.
    In the Custom table we have names of the approvers with release codes.
    Purchase Requisition displaying the names of the approvers according to alphabetical order.Hence it displays First one user or approver name under the release strategy according to the approver alphabetical order from the custom table.
    Can we display name of all approvers in one line according to initial investigation there is room for 40 characters under the release strategy tab.
    Let me know if any Standarad OSS notes available for this.
    Amogh

    Hi amogh if you configure with workflow the strategy and the name of the persons are in transaction SU01, you don´t need to put nothing. The release strategy shows the names of the persons that release the document, but if you change one person in the release strategy, the system don´t save history for this, all old documents that have been released for this person, release strategy is blank. You have to do a non standard report that shows what person releases what document.
    I hope that this information help you
    Rose

  • Release Strategy/Workflow for MB21 Reservation

    Hello Gurus,
    I know as per Standard SAP it is not possible to have a release strategy/workflow for MB21, but if any of you have come across this requirement where material reservation should be approved by related dept heads before the material is issued for those reservations, please reply back with the possible options to configure release strategy or work flow for MB21 even thru development or any other work around.
    Your expertise advises will be very helpful for me to work around this requiremnt.
    Thanks in advance, looking forward for your reply

    Hi Anoop,
    Reservations in SAP is just a logical value, which does not have any impact on any stock type. It would be interesting to know why the business needs approval process for reservations.
    Anyways even if you need approval process, what you have to do is develop a custom object, where in when ever the business creates a MB21 reservation, assign a unique number to each reservation number.
    As a dept head, the business will run the ZMB21, checks the reservation to which he needs to approve. In the back groud call up the unqiue id assigned and place approve button where in dept head can approve the same.
    The authorization to this custom tcode should be given as per your requirement.
    Hope this helps
    Ilyas

  • PO Release Strategy - Only for Non MRP generated materials

    Hello,
    I have a requirement in which any material which was generated via MRP (via PR) should not go through a release strategy at the PO level, but a non MRP generated PR should...
    Is this possible at all? I know its possible at the PR level, but not sure at the PO...   Would this be a case where we would need to added a field to the CEKKO structure thats for MRP generated PRs ? 
    Thanks

    Hi,
    By business any PO created, should follow release procedure as PO a committed document which will further send to vendor.
    If you are sure about your requirement, PO created from MRP PR should not follow release strategy, then no need to go for any User Exit.
    Just create separate document type for PR (ZMNB) , create separate document type MRP PO( ZMNB) and  link MRP PO document type ( ZMNB) with MRP PR document type( ZMNB) in flowing path:
    SPRO>MM>Purchasing>Purchase Order>Define Document Types
    Now select your ZMNB B Purchase Order Document type and click link purchase requisition document type in Dialog Structure, enter ZMNB Purchase Requisition Document type with a new entry & save.
    As you created release characteristics of document type (CEKKO with BSART), then do not keep Value u201CMRP PO document type (ZMNB) u201Cin the release characteristics of document type and design your release strategies.
    Now create your PO with MRP PO document type (ZMNB) and see no release strategy triggered.
    Regards,
    Biju K

  • PO release strategy ONLY for change

    I have a requirement to only have a release strategy for a purchase order only when it is changed
    The problem is that even if I can disable the event to be triggered when created, the release strategy is written down to the EKKO-table when the PO is created meaning that the purchase order still needs to be released before being used for example in MIRO.
    How can I avoid having the release strategy written to the EKKO-table when the PO is created?
    How can I have it written to the EKKO-table when it is changed?
    Good answers will ofcourse be rewarded with points!
    Edited by: Snowroller on Feb 11, 2012 4:00 PM

    Dear,
    Check this and try. Not tested.
    Set up Version management for Purchase order and keep all relevant fields of PO relevant for version change.
    Add charaecteristics PO_Version value as 00000001. So, When you create PO the version will be 0 so no release strategy. Whenever relevant fields changes the version changes to 0 to 1 and release strategy triggers.
    Try this option.
    Regards,
    Syed Hussain.
    Forget to mention please search with 'PO release strategy based on Version Management in SAP' you will get many SDN posts.
    Edited by: Syed Hussain on Feb 11, 2012 7:27 PM

  • PO Release Strategy - Only for non material based

    Experts,
    I have a requirement to implement a release strategy for a single plant for POs for NON material based purchases ( only for using account assignments, cost centers etc).
    The release strategy I configured is working only for the specific plant I want... However, it works whether its a material based PO or a non material based PO.
    How do i get the strategy to work for only the service based purchases, and not the material ones?

    Thanks for the replies but I'm not sure if they are applicable...
    I did create a characterstic for item categories and added the one's I wanted to have... I did NOT include a blank because i thought that would make the difference between the material based PO and non PO. When we I create Po with material (even with no account assignment) it still goes through release.
    Any reason why that is?
    I dont believe the material group solution will not work either because we require material group for material and non material based POs..
    Side note - when i try to use CEKKO with KTTNP, i get a "KTTNP does not exist error." So i used EKPO - KTTNP... hopefully thats ok, but please let me know if its not.
    Edited by: farmerj3 on Jan 30, 2012 3:36 PM
    Edited by: farmerj3 on Jan 30, 2012 3:39 PM
    Edited by: farmerj3 on Jan 30, 2012 3:48 PM

  • Release strategy does not reset after PO change - tried changeability 4 & 6

    Hi,
    After my PO is released, I change the item quantity/price such that the net PO value (increased) is changed MORE than the tolerance % set in the changeability.  I expect that the PO release should be reset but it does not.
    However if my PO value is changed (increase) such that my PO value is now in a different "release bracket/range" -- as it falls into a different release strategy, then the release is reset.
    Could anyone advise me what is wrong?  I tried everything - i tried changeability = 4 and 6. i deleted the whole release class, release strategies and recreated -- nothing.
    According to OSS note 493900 below, it should reset when the tolerance % is breached.
    I'm on SAP 4.7.
    Anyone could advise?
    thanks!
         3.  Question :
         Why is the release strategy not reset ?
         Answer :
         A reset of the release strategy only takes place if
                -  the changeability of the release indicator is set to '4' in
                   case of a purchase requisition and '4' or '6' in case of
                   another purchasing document (purchase order, request for
                   quotation, contract, scheduling agreement),
                -  the document is still subject to the previous release
                   strategy,
                -  the new TOTAL NET ORDER VALUE is higher than the old one.
         The total net order value is linked to CEKKO-GNETW for a purchase order,
         CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
         for a purchase requisition overall release.
         If you have maintained a Tolerance for value changes during release
         (V_161S-TLFAE), the release strategy is reset when the value of the
         document is higher than the percentage you have specified and if the
         document is still subject to the previous release strategy.

    Hi,
    Thanks.
    The release strategies are able to be determined correctly when the PO is created so I guess that means its all setup correctly?
    The issue is only with PO change - how to cause the reset when the PO value increases by more than the tolerance %.
    cheers.

  • Release strategy reversal for the purchase requisition.

    Hi all,
    I have a scenario were we have three release levels to release the PR through ME54N tcode.
    After all the levels are released,If at the first level the PR release is cancelled all other levels are automatically cancelled.
    Now my concern is until the 3rd release cancellation is done, 2nd and 1st level should not be allowed to cancel the release of PR. and until 3rd & 2nd release cancelltion is done, 1st level should not be allowed to cancell the release of PR.
    Please Let me know if any BADI or any enhancement is available to acheive this back release strategy for PR.
    Regards,
    Kumar
    Edited by: kumar g on Jul 16, 2009 6:21 AM

    -

  • PR release date capturing for all levels

    Hi,
    I have activated PR release strategy at Header level.  There are about 4 levels of release are there.  In custom PR print program, I want to capture the details of all levels corresponding release dates.  Can you help me how I can go about it.
    Munna.

    Hi
    PR release date is not relevant to Release strategy.
    Purchase Requisition Release Date
    Specifies the date on which the purchase order should be initiated on the basis of the purchase requisition.
    The release date is based on:
    The purchasing department processing time defined for the plant
    The planned delivery time from the material master record or purchasing info record
    The delivery date
    The goods receipt processing time from the material master record
    Note
    The planned delivery time from the purchasing info record and the GR processing time are only taken into account if the purchase requisition was generated via materials planning.
    Example
        Processing time   Planned del.   GR processing
           Purchasing         time           time
    Release       PO                    Delivery    Date
    date         date                   date    required
    Date required:                     10.01.96
    GR processing time:                 2 days (working days)
    Planned delivery time:             10 days (calendar days)
    Purchasing dept processing time:    2 days (working days)
    For the material to be available on the date it is needed, the purchase requisition must be released on 09.11.96 (requirement date less GR processing time, planned delivery time, and purchasing department processing time).
    Hope it helps
    Thanks/karthik

  • Release strategy determination for PO item level characteristic value

    Hi Experts
    I have user material group as release characterstic for PO.
    I have created two line items with two different material groups.
    How the release strategy determination occurs when the two different material groups are linked to two different strategies?
    regards
    ramSiva

    Hi,
    in this case system is NOT able to find the release startegy.
    Please take care of the following explanation (see note 365604)
    o  For OVERALL RELEASE (purchase order and purchase requisition) the
       item fields such as Plant and Material Group will be aggregated
       to header level.
       For example you use Plant/material group
    as one of your characteristics. If all
    items do not belong to the same plant/material group
    then
    *******the relase strategy will not be found***********
    unless you have maintained a blank value as one
    of your allowed values for the characteristic Plant/material group
    . If all items
    belong to the same plant7material group
    then that plant is aggregated to the
    header; if one or more is different then a blank is aggregated to
    the header.
    If you use an overall release strategy all
    characteristics which you have defined in the customizing (CEKKO-MATKL
    must have the same value. If one item has material class x and the
    other y the system does not know with which material class it should
    look for a release strategy. Now the system sets the material class
    to 'blank' and tries to find a release strategy. If you do not have
    defined a blank entry in the customizing (Transaction: OMGS
    : OLME >release procedure for PO > rel. strategy ) the
    system won't find a release strategy.
    you need
    to add a blank value to your allowed characteristic values in your
    release strategy.  To do this you can define a blank value in your
    characteristic (CT04).  On the values screen leave the char.value
    blank and add a description and save.  Now in OMGS you can select
    this value as an allowed value for the characteristic.
    (Example:
    To avoid this you can do the following:
    - go into transaction CT04
    - enter the characteristic 'CEKKO-MATKL'
    - click on the tab 'values'
    - set a flag in 'additional values'
    - in the column 'Char. value' do not enter anything
    - in the column 'Description' enter a text like 'no material class'
    - save this setting
    Now
    - go into transaction OMGS -> button 'release strategy'
    -> button 'classification'
    - double click on CEKKO-MATKL' and set a flag in 'no material class' )
    Please also have a look into the attached note 365604 point  2d).
    BR
    Nadia Orlandi

  • Release strategy & EBAN for project systems, purchasing

    Hi
    We have 2 different scenarios for which we use same account assignment category "Z".
    1) Purchase Requisitions for capital expenses (Account assignment category "Z") - this is part of project systems requisition attached to WBS elements
    2) Purchase Requisitions for expensed items (Account assignment category "Z")
    I have configured release strategy with classification with following characteristics
    1) plant
    2) cost centers
    3) total amount in PR
    4) account assignment category
    all 4 characteristics are same in both areas (capital and expensed)of purchase requisitions, account assignment category Z decides whether it is capital purchase or expense related purchases. Z uses order number that is internally tied to WBS element.
    my question is - if some one has similar scenario then what is the best solution to handle invocation of release strategy.
    how release strategy can be determine, do I need to use user exit and if yes what best user exit is available.
    EBAN fields, I have researched and I cant use fields like "requisitioner" for determining release strategy.
    I would like to invoke different release strategy for capital projects and different release strategy for expensed items in PR. there is a workflow attached to this later.
    Please reply
    Thanks and regards
    Umesh

    Umesh,
    Well, there needs to be some way to differentiate the 2 types of purchase requisitions for you to use 2 different release strategies.
    I am not sure if you have the option of using a different document type to differentiate the 2 requisitions. I would definitely look at this possibility and include the document type (CEBAN-BSART) as a characteristic in the release strategy.
    Other options would be to look at using the purchasing group (CEBAN-EKGRP) or the requirements tracking number (CEBAN-BEDNR) as characteristics in your release strategy.
    Hope this helps.
    H Narayan

  • Wrong release strategy assigned for a PM work order

    Hi
    Would like to seek your inputs on this.
    I have created a work order that has a settlement rule for a WBS element. I then created a material, RELEASE the work order then SAVE.
    I found out when going back inside the work order that the PR number generated was having a different release strategy, which is not appropriate for the approval.
    The only time when you can fix the issue is when you do a change on the work order or you have to create the order, save, then open again the work order then release it, and save.
    Have you had this same scenario? Can you please share any suggestion to address this issue?

    Hi Nazarene
    You may need to give us a background of how your organization have set up the release strategies. Some organization uses User Exits or Work Centers to set up release strategies. Either your work order is not picking the correct work Centre or if the work center is new you have to change the work order (IW32) and save it to pick the correct release strategy. 
    Alternatively you may need to check your workflow and the release limits.
    Regards
    Gibson

  • Acrobat X Pro error "font not found" for all non-Adobe programs

    I'm running Win 7 64-bit, Extensis Suitcase 3 (current version).
    Having difficulty printing to PDF from all non-Adobe applications- everything from MS Word to Notepad. I can PDF fine from InDesign and Illustrator, whether using the File/Adobe PDF Presets or print-to-PDF. The problem occurs for me on all PS fonts that I have tested, whether very old or new. The fonts and files can be printed to Postscript printers with no problems- no missing fonts or substitutions. The problem only happens when trying to PDF in Acrobat.
    I have two associates with printing issues, too. They are on XP and still use ATM 4.1. They've had similar PDFing problems since they were moved up to Acrobat Pro X.
    Thanks for any assistance.

    Does Distiller know all of the font locations?

  • No release strategy tab for purchase requisition

    Hi Gurus
    i have a user who is complaining about the release strategy not appearing after saving the requisition, but when i try to test it from dev using his profile, it works fine. he can create the req fine on other pc's but not on his pc. i have check his patch level and if he is using the latest gui version and he has both.
    what could be causing this issue?
    Please help
    thank you in advance

    Hi Roy
    thanks for the reply
    am i  supposed to check this on his profile? he is the only person getting this issue other users are working fine. so my assumption is that it must something to do with his sap settings but i dont know the technical side of sap
    please help

  • Nokia can't release fw 40 for all device!nokia bra...

    Hi, i have Nokia 5800 device but is a brand Tim and my last firmware version is 30.0.011, this version it's full of bug and telco tim (telecom italia mobile )don't release new version 31 or 40 and i can't install ovi free maps because required fw version 31!
    I buy a nokia telephone or a tim telephone????
    nokia can't give the same support for all nokia telephone???
    I'm very angry for this nokia politic isn't good!
    Message Edited by mario5588 on 03-Feb-2010 11:06 AM

    I bought it from o2 but without contract, thus i payed the same price as i would if i bought directly from nokia. Additionally, its Nokia who has to fix that, not Telco!
    Guarantee is provided by the manufacturer ONLY. Warranty is provided by the dealer ONLY. If your dealer rejects providing warranty (eg. not publishing updated firmware) you have the right to get guarantee.
    My provider here is o2 and cause of this topic i called them and asked why their latest firmware is still 11.0.021 while current official is 21.0.045. They told me that the o2 services would not run with the official firmware (ROFL) thus they release updates after 1 year !!! That means o2 N97 users are getting 21.0.045 at 02.02.2011.
    BUT
    After i told them that all o2 services are running well with the official firmware and that they should release updates faster for Nokia phones (because they're containing the most bugs compared to other manufacturers) they told me to write a letter (or fax) to them explaining the facts again so they can "debrand" my phone officially.
    So, i would write a fax to TIM and tell to release the latest update. If they don't agree i would tell them to debrand your phone. If they still disagree i would force an law issue against them.
    Nokia Bug Tracking System @ http://dev.an3k.de/bugtracker/

Maybe you are looking for