PO Release Strategy trigger based on PR value

Hello All,
We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Pls advise.
Rgds,
AC

We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Hi,
You can try doing it with a WorkFlow as you identified communication structures differ.
Regards
Shiva

Similar Messages

  • PO release strategy workflow based on plant

    Hi Gurus,
    I am setting up PO release strategy workflow.  We have purchasing at plant level.  Fg. plant 1234's PO should be sent to the plant 1234's purchasing dept.  Plant 5678's PO should be sent to the plant 5678's purchasing dept.  In PR release strategy workflow config. screen, there is a plant field.  However, plant field is not showing in the PO release strategy workflow screen.  they are both in the table T16FW, and plant field is define in the table.  Pls help and explain how we can get plant field in the PO release strategy workflow config.  Or if this is what SAP design, then is there any other way to accomplish what we want?  Thanks a lot!

    We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
    Hi,
    You can try doing it with a WorkFlow as you identified communication structures differ.
    Regards
    Shiva

  • PR Release Strategy- transport of charact/class/ values using ALE

    Does anyone have the information relative to ALE set up for release strategy-
    I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
    I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
    This will be a great help.
    Thanks
    Raj

    Hi Raj,
    Please check the below notes for more inrofmation:
      86900 -  Transport of Release strategies (OMGQ,OMGS)
      799345    Transport of release strategy disabled
      10745     Copying classification data to another client
      45951     Transporting class data: system / client. - has details of what you are looking for.
    Hope this helps.
    Regards,
    Ashwini.

  • Can a release strategy be based on a formula?

    Hi,
    A retail client i'm working on wants the release strategy PO to be based on a formula, i.e. the release strategy should have OTB check.
    Is this possible?
    Thanks in advance for your help

    Hi,
    Thanks, I didn't know what OTB means.
    I do not know how this OTB is maintained in the system (is it development?) but I assume it should be stored in a data table (data tables). If it is so, I think you should be able to extract it (this data) via the ABAP code in the mentioned user exit - but this is just my opinion, it's better you ask your ABAPer to check it in a sandbox system.
    Regards,
    Csaba
    Edited by: Csaba Szommer on Jun 23, 2010 9:23 PM

  • How to initiate a trigger based on threshold value from DAQ

    Hello,
             can anyone please tell me how to start a counter/trigger based upon a threshold value/??i would like to measure the amount of time
    the particular input value is greater than the threshold value...
    I tried out the simple VI attached, but the start time and the end time show the same values... can anyone please suggest/???
    Now on LabVIEW 10.0 on Win7
    Attachments:
    trigger.vi ‏103 KB

    sorry, attached the wrong VI,
    here you go,,, this should work....
    Now on LabVIEW 10.0 on Win7
    Attachments:
    Trigger Counter.vi ‏143 KB

  • Contract & PO Release Strategy

    Hi All,
    We are in the process of designing the release strategy for contract and PO. I  would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
    The release conditions for Contract required are
    1)Porg
    2)Pgroup
    3) Value
    Also, for quantity contract how can we make the release strategy trigger based on value.
    The release conditions for PO required are
    1)Porg
    2)Pgroup
    3)Material Group
    4)Value
    The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
    Request your help.
    Regards,
    Kannan

    Hi Kannan
    Yes your requirement is possible...
    While creating Charectristics in CT04 for External Purchase Documents...Create one more Value  for your Document Category...ie) Table as :CEKKO   and Field  as BSTYP   and choose the Purchase Doc. Category  values K  and F.
    Then create Charecteris for  CEKKO - EKORG,  CEKKO - EKGRP   and   CEKKO - GNETW, CEKKO- MATKL...  and assign these all 4 Chareteristices in your release class.
    And Configure your release statergy according to your requirement...
    Reward if useful
    Regards
    S.Baskaran

  • Cost Center based Release Strategy for PR's

    System :4.6c
    At this time, we have PR release strategy with classification configured for over all release.
    Created a new characteristic for cost center , assigned the values for the cost center characteristic, with zeros at the beiginnig.
    Now when I create a PR with multiple line items and with multiple cost centers, the system is not deriving the release strategy defined. But if I create multiple line items with the same cost center, the system is able to find the right release strategy.
    Does it have to be the same cost center in all the line items to trigger the right release strategy?
    Thanks.

    Hi,
    Looking at your question it seems you are using overall release strategy. If the characteristic value is not same for all line items then during overall release strategy determination, the system uses "BLANK" value for this characteristic.
    In order for a release strategy to be found, when you have different
    cost center in different PR items you need to add a blank value to your allowed characteristic value for the cost center in your release strategy. Also use Account Assignment Category (KNTTP) as one of your characteristics and define K as an entry, so that release is triggered only when it determines cost center blank with account assignment K.
    But if for diff cost centers there is diff strategy then you better opt for Item level Release.
    Please give this a Try.
    Regards
    Chandra Shekhar

  • NUMBER OF CHARACTERISTICS AND VALUES IN RELEASE STRATEGY

    Hi there, how R U.
    Please, can any body help my with this one ?
    How many characteristics may I have in a release estrategy for purchase order an contracts ?, how many values could a characteristic have ?, if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
    An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
    I hope you can help me.
    Have a nice day.

    How many characteristics may I have in a release estrategy for purchase order an contracts ?,
    You can have as many number of characteristics you want for release strategy, no restirction
    how many values could a characteristic have ?
    You can have as many as you want, no restiction
    if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
    Release code you can define only 8 and if oyu want more release code than create new release group and assign more release code
    An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
    the release strategy can hold only 8 release code but every release strategy you can have more than 8 charcteristics and each char can have n number of values and that can be decied at char creation level

  • User exit for triggering release strategy

    Hello Experts,
    My requirement is when changes are made in purchase order (ME22N) then once again release strategy will have to get trigger.
    is the user exits exists for this purpose,if yes, What is it?. I searched alot but not able to find right exits.

    Hello ,
    I think you can achieve this via configuration .Basically you want the release strategy to get redetermined based on the changes in the item or if the price of these items increase a certain level .if you  have the release startegy as changeble in the SPRO ticked it will automatically go for new release strategy if you have the value of release indicator set .This can be done SPRO->MM->Purchase order->Release procedure for purchase order->Define release procedure->Release indicator.
    Set  the appropriate value  .
    Remember you need to know what is that it retrigger that release strategy .
    The link below deals with similar requirement ....
    [http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/retrigger-release-strategy-for-purchase-requisition-with-any-change-1858101]
    Thanks
    Anjaneya .
    Edited by: Anjaneya Bhardwaj on Aug 31, 2011 8:21 AM

  • PO release strategy is not triggering if Quantity pre.Qty

    Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
    Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.

    Hi.
    According to  note 493900, question 4, release strategy is reset only
    for some specific case. Alternatively, please question 5 from this note
    release strategy might be redetermined. However in order to determine a
    new release strategy the field that is changed in PO must be included
    as one of the fields in the strategy. Thus there is no standard way
    for resetting/redermining release strategy for a change of e.g. text
    on header or item level.
    Please also kindly refer to other 2 useful notes for this area:
    662993     Resetting an already occurred release
    365604     FAQ: Release strategies in purchasing
    BR
    Nadia Orlandi

  • Release strategy for PO and Service Entry Sheet

    Hi
    I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
    should I maintain the same characteristics for service entry sheet ?
    the approval will be the same for both

    Hi,
    The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
    Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
    Note: The release strategy must be based on the structure CESSR.
    The PO release strategy is based on the structure CEKKO.
    For the SEs release strategy you must create a different class.
    Regards,
    Edit

  • Release Strategy should be effected even if the PO Price is lowered?

    Hi users,
    Another doubt of mine is based on the release strategy (the Purchase order goes for rerelease) only in case of the increase in the PO Order Price (that is if the price is manually increased in a PO or if it indirectly increased by the increase in quantity)
    Requiremnent: the current requirement is the po should go for a rerelease even if there is a decrease in the po price. alternately any change in the PO effecting a rerelease would also be acceptable.
    anticipating an rearly answer.
    thanks and regards
    vinay

    This is standard SAP. Release strategy will be reset only on increase in value.  You have to make the release strategy think that the value has increased (even if it has decreased).
    Please see (the second part of) my comment in
    Re: release strategy is not reset in PO?
    Reproduced here for your ease:
    You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
    Hope this resolves.
    Lakshman

  • Release strategy modification

    Hi all,
    I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document  & 2. Purchasing Group .
    Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field  in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
    My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
    To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
    Please help! How can I achieve this...
    Thanks,
    Rajan U

    Hi,
    As needed, you created one more charterictics CEBAN - CFWRT and included it  in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
    Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
    1.     <= 5000 INR
    2.     > 5000 INR
    Craete release group as PO and create two release codes C1 & C2.
    Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
    When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
    Regards,
    Biju K

  • Issue with Purchase Requisition Release strategy

    Hi Gurus,
    We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
    1.     Creation Indicator of PR-R (Configured only for manually created PRs)
    2.     Purchasing Group
    3.     Value of the PR
    As a result of PM module implementation, there is requirement of additional 30 release strategies.
    We configured them but one more field of doc type was added in the characteristics fields.
    Now the release strategy was based upon following fields:
    1.     Creation Indicator of PR-R (Configured only for manually created PRs)
    2.     Purchasing Group-(Configured against new purchasing groups )
    3.     Value of the PR
    4.     Document type of purchase requisitions.
    Classification data was accordingly maintained that is for older release strategies,
    Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
    The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
    Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
    We are in testing phase. Many of the test scripts failed due to this issue.
    Quick response will be appreciated!!!
    Thanks & Regards,
    Niti

    Dear Niti,
    Please check if your "overall release" indicator is consistent for document type and release group:
    a)SPRO:MM-PUR-PR-Define Document Type
    "overall release" indicator
    b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
    ->Release group
    "overall release" indicator
    Regards,
    ian,Wong Loke Foong

  • Release Purchase Requisition - "Release strategy"

    Hi there,
    I am trying to release a purchase requisition. I looked in the table "EBAN" and i can see the entry or in other words, the requisition i created. In the Release indicator, Release status and Release strategy fields, these are empty. How do i add information to these fields which appear to have missing data?
    Speedy repsponse would be very much appreciated.
    Thanks
    Motolani Fatuga

    Hi Motolani
    spro>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release strategy
    Select release strategy> Go to details>classification
    here check what are the charactaristic and what are the values maintained for it
    Check this for all release strategy
    Mostly PR release strategy is based on Document type and PR Value
    Check whether UR PR fits in release strategy criteria
    Suppose Total value of requisition is maintained as 1000-2000
    If UR PR value is less than 1000 Then PR will not subject to release
    Vishal...

Maybe you are looking for