Release strategy for PR with materials having different prices

Hai Gurus
Can we make a release strategy for a variant configured material ?
I mean create a strategy in such a way that price is critical factor and the materials what ever we choose for the PR has different characteristics dependencies like for example ( A chair having different characteristics like color, material ( like steel, leather etc) and other features like wheels etc and whatever characteristics we choose has a different price.......... so when v come to the release strategy it has to be approved by the next level if it reaches $ 1000 and so on.
please help me out in this issue

Hello Arif Mansuri
thanks for your reply, yes I have taken it as total value only. The scenario is I am asked to use three different characteristics ( total value, materials, MRP Controller) and assign them to a class and if the customer picks any number of different materials and if the price is more than 1000 then it has to reach to the next level for approval. i thought i am suppose to use object dependencies here......... can we do this in a normal release order if so how would be the strategy played here?
thanks for your time

Similar Messages

  • Release strategy for PR with multiple item category

    Hello,
    I'm trying to create a global release strategy for a PR based on the item category.   I have defined a caracteristic with different item categories (A and K).
    If I create a PR with item category A, the correct strategy is triggered as well as for an PR with item category K.  The problem is when I create a PR with 2 positions, one A and one K, there is no strategy triggered.
    How can I change my settings that there is also a strategy triggered in this case ?
    Thank you in advance for you help.
    Kind regards

    Hi,
    Solution is very small. Please maintain a blank entry too in the characteristics value. It will start working.
    Sanjeev

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • 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

  • Release Strategy for STO

    Hello Experts,
    We have a requirement to configure release procedure for STO scenario. Release procedure needs to be captured in STO PO's.
    We have 6 plants - A,B,C,D,E,F, and each plant is having different approving authority individually.
    When STO PO is created, it has to be approved by Issuing plant authority & receiving plant authority as well. The major concern here is for eg., approval authority for plant A can be a issuing authority at one instance & receiving authority at another instance.
    How to configure release strategy for this.
    We believe ,creating those many release strategies for all the combinations of plants  will be a hectic task & still it'll multiply with the introduction of more number of plants.
    Hence looking for a more simpler & feasible workaround/solution.
    Regards
    Mahesh.C.R

    Hi,
    you can use Supplying plant ( RESWK) and issuing plant (werks) both as characteristic and with these combination you can configue release strategy.
    Or you can use User field format character for release strategy (USRC1)as per your requirement.
    YB

  • 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

  • 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 contracts.

    Hi gurus,
    Good day,.
    Please help on this.
    We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
    Example.
    Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
    Thank you.

    Dear Acel,
    The example you given was working just fine and correct.
    a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    -> The release strategy will only be reset if the total net value for the contract was higher the previous
    value but not lower.
    As your example, quantity was updated to 1200, then it will reset when changing from 1000
    to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
    release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
    In system, it always assume if you had approved for the total value of the higher 1 before, then
    it should be fine for the lower total net value for your management and therefore not need to re-approve
    again for redundancy job. This was very logic in common business scenario in many companies.
    However, like in your example , if you had define a different release strategy for a value that met the
    the 1100 quantity, it will redermine the different release strategy. For example:
    USD 1 for every quantity = 1
    Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
    USD 1200 for quantity = 1200.
    Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
    Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
    Release strategy C for 1200 , characteristics from USD 1200 onwards
    Then if you change the quantity from 1200 to 1100, it will redetermine the release
    strategy B which means from Release strategy C to Release strategy B. If you
    only had Release strategy C that had a characteristics from 1000-1200, then
    it will keep the Release strategy C as released and it won't be reset unless
    if you had change it and the condition of the total net value was higher than any value
    before.
    Hope this will explain the logic.
    Ian Wong

  • Cannot reset release strategy for RFQ

    Dear SAP gurus,
    I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
    But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
    Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
    Best regards,
    John.

    Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
    However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
    Lakshman

  • Release Strategy for Condition Records

    Hi,
    This is a requirement from my client. The client needs to give 4 levels of release strategy for the condition records created. The selling price for the products will be entered by person 1. This has to be approved by the sales execute (person 2); then by the sales manager (person 3); finally by the General Manager (Person 4). The selling price of the products ranges from 10 lakhs to 40 lakhs. so, the release strategy is needed. This type of release strategy is available in MM for PR and PO. Please let me know whether similar facility is available in SD. Any alternative is also solicited.
    Regards,
    K Bharathi

    Hi,
    Thanks for your valuable reply.
    I defined 3 Processing status (Menu path: SPRO >> SD >> Basic Fn >> Pricing >> Define Processing status). They are EU-End user, KU-Key user, MD-Final authority. These processing statuses are assigned to Release status. First two processing status EU, KU were assigned to A (Blocked). The third processing status MD was assigned to Blank (Released). The purpose is: at processing status EU one person will upload the price master. Second person will check the price and will change the processing status to KU if he satisfies with the accuracy of the price master. The third person (final authority) will check the price and set the Processing status MD. Once the condition record gets the status MD, the prices can be used for creating sales order because it is released.
    In the condition record for PR00, when I enterthe processing status  EU or KU the release status shows 'Blocked' release statuses. When I enter MD in the processing status, the release status show 'released'.
    My question is how can assign the responsibilities of changing the processing statuses EU to KU, KU to MD to two different persons.
    Regards,
    K Bharathi

  • PR release strategy for material group

    Hi,
    I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

    Hello
    In PR you can set up this release strategy without classification release strategy.
    w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
    Laxman

  • Release strategy for GR?

    Hi,
    My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
    Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
    Any help will be appreciated.
    Best regard

    Hi Yosea,
    Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
    My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
    But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
    Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
    I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
    Note: Controll always suggested at the time of making agreement  (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
    Hence there is no logic is going for that option
    Hope it clarifies,
    Regards,
    Sapsrin

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Ashok

  • Purchase Order not subject to release strategy for contract rel. strategy

    Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
    So I have checked this release strategy with this codes:
    CL24N ok,
    CT04 ok,
    CL30N ok,
    CL20N ok,
    Release simulation in release strategy works,
    Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
    Thank you for your help in advance.

    I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
    I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
    Also compare your release strategy settings with many existing documents in SCN.
    Check your Classification should be like that.
    You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Maybe you are looking for