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

Similar Messages

  • Graphical view in Purchase order release strategy

    Hi Experts,
    I have added new position in existing Purchase order release strategy which is running properly.
    I am facing the problem of visual display in header on tab release stratege for the PO which are already released by respective authority.
    It is showing final release balance all though release indicator set to "1".
    For e.g.
    PO number 123 was released by 4 persons in past.
    As per new modification release agencies are 5 nos.
    for this PO release flag set to "1"
    As 4 persons involved in PO release the graphical display shows 5 agencies for release but release tick infront of these show only 4.
    My Problem is client wants correction in this graphical display.
    Please help me on this.
    Regards
    Dhananjay

    TELL THE SOLUTION DEAR ..SO ANOTHER WOULD GET HELP IN FUTURE.
    REGRDS
    MANOJ

  • Release strategy for POs:

    Hello
    My customer is asking to have a released PO submitted againt to a release strategy if the item description (short text) is modified.
    any idea how can this be set up?
    thanks in advance
    Kind regards

    Hi,
    The MAIN problem is that PO release strategies are at the HEADER level and not the item level and so you cannot have item fields in the strategy (It does actually allow this but it takes the first line only and ignores the rest) so the short answer is that you can't do this.
    If this was a header field, to get the release strategy rechecked after a change, the field being changed MUST be one of the characteristics used in the release strategy.
    You would not have to actually use the field in the release strategy check, you can have it so that ALL valid entries are allowed (i.e the value of the characteristic is set to 0 to zzzzzzzz or similar) This would mean that it plays no active part in deciding the strategy but if it is changed, the system could be made to recheck the strategy.
    So, I am sorry but I don't think that you can achieve your requirement (without a modification or user exit)
    Steve B

  • Send purchase order e-mail with release strategy

    Hi!!
    I have a problem with sending e-mails in purchase order that are blocked with release strategy.
    I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
    Somebody knows what is happening?
    I would like to send e-mails without previous modification of the purchase order.
    Thanks for your help.

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • Sap release strategy

    dear gurus,
                 I have created a release strategy. it is working fine.  if i edit it in such a manner, that  the po value increases, it goes for re-releasing. but the issue is, if i edit it in such a manner that the PO Value decreases it does not go fo re-release.
                  so my requirement is that, if the PO value goes down it should go for re-releasing
    thanks
    ujwal

    Hi,
    please see the note 662993  Resetting an already occurred release.                                                                               
    "When you reduce quantities or values the system only resets the release         
    if another release strategy is determined for the lower quantity or the          
    lower value.                                                                     
    If no other release strategy is determined by the reduction of the               
    amount or value, the system will keep already existing releases.                 
    This is a standard functionality and is desired.                                 
    A change of this functionality is only possible by means of a                    
    customer-specific modification."                                                                               
    In standard there is no customizing setting to change this behaviour.             
    You need to use userexit EXIT_SAPLEBND_002 or modify             
    the standard function module ME_REL_STRATEGIE_EKKO for this. 
    Regards,
    Edit

  • Need workaround - Release strategy

    Hi,
    I have done three release strategy(R.S.) for PO.
    First R.S. is from 0 t0 9,999
    Second R.S. is from 10,000 to 99,999
    Third R.S. is from 100,000 to 500.000.
    When the PO value is 250,000 the third R.S. comes to picture and it is released by people concern.
    When the same PO value is decreased from 250,000 to 90,000 the PO is de-released and it goes back to second R.S.
    wherein the enduser is not comfortable as the PO is already released with third R.S..
    Enduser do not want to release again using second R.S.
    Please suggest to stop from derelease after it is released by third R.S.....

    Hi Vishnu,
    See Note 662993 on conditions based on which release strategies are reset.
    When quantities or values are decreased, the system resets the release
    only if a different release strategy is determined for the lower
    quantity or the lower value.
    If no different release strategy is determined due to the quantity or
    the value decreasing, the system retains the releases that already
    exist.
    This is the desired standard system behavior.
    As it also says: "This function can be changed only by a customer-specific modification."
    So there is no standard way of achieving this.
    Hope this helps.
    Purnima.

  • PR Release Strategy tab processor field is not getting displayed

    Hi Experts,
    While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
    SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
    release strategy - Release code  -work flow 1
    That processer name is not displaying
    Thanks
    chandoo

    This is the workflow forum.

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

    Hello everyone,
    I've run into an interesting problem:
    We have defined several PO release strategies.  Most of these work in the traditional manner, requiring manual approval by a given user.  One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
    We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
    If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
    If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
    What would cause this discrepancy?  The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
    Thank you ahead of time for your help.
    -Jarrod

    Configuration issue/user error.

  • PO Release strategy

    Hi,
    I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
    Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
    After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
    Any suggestions are highly appreciated to fix this issue.
    Regards
    Sudhakar

    Hello,
    After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
    regards
    anand

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • 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

  • Release Strategy for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

  • Release Strategy for Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

Maybe you are looking for