PR overall release strategy

Hi
Greetings!
Overall all release strategy had already been set up in our system and it is working fine. But When i try to create a new strategy, it is not working.
We have a class for over all PR release with the following characteristics.
1) Purchasing Document type
2) Plant
3) PR total value
4) Cost center
5) Purchasing group
I have made the following settings which are relevant for overall release
1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
2.  Materials Management --> Purchasing > Purchase Requisition>  Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
Is ther any other settings which i am missing? Please help me in resolving the issue.
Gobinathan G

Hi Gobinathan G,
I am aware that you already did the following procedure:
1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
2. Materials Management --> Purchasing > Purchase Requisition> Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
However, since you are moving towards Overall release, what you must complete in order to achieve
the desired result, is to create a new Characteristic,  and use it within the class parameter that
you already created to control the values in your release strategy. Then you have to associate the
new characteristic to the field name GFWRT in table CEBAN. It may be done in the Additional Data
Tabulator of the characteristic.
It worked for me.
Hope it helps.
Alfonso Chakarji

Similar Messages

  • PR overall release strategy with acc. assignment category characteristics

    Hi,
    Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
    see below more details :
    I have created the following PR release strategy with classification.
    PR type concerned " NB": overall release
    Rlease group concerned : overall release
    In this release group i have 1 class
    in this class i have 2 characteristics : PR type and Account assignement category.
    Release strategy 1 :
    PR type = NB
    Acc. assignment cat = P, W
    Release strategy 2:
    PR type = NB
    Acc. assignment cat = K, V
    TEST 1 : PR type NB, 1 item with P category
    OK the release strategy 1 is generated
    TEST 2 : PR type NB, 1 item with W category
    OK the release strategy 1 is generated
    TEST 3 : PR type NB, 2 items with P category
    OK the release strategy 1 is generated
    TEST 4 : PR type NB, 2 items with P and W category
    TEST KO, no release strategy is generated
    => what should i do to solve this issue ?
    Thank you in advance for your quick answers,
    Isabelle

    What is the specific requirement for Overall release strategy?
    Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
    Every line item generates a PO, so logically should be set to a release strategy.
    Bottomline is use release strategy at line item level Unless a specific reason exists.
    Regards,
    Sameer

  • Overall Release Strategy

    Hi Experts
    I am trying to set up an overall release strategy with the following characteristics: total value and account assignment K.
    In order to get the overall release strategy to work I had to set the overall strategy at the document type level (NB).
    Now material PR and consumable PR are subject to an overall release. What can I do to set the strategy for only PR with account assignment K.
    Thanks
    Belle

    Please let us know what have you maintained in CL20N
    Regards,
    Indranil

  • PR Overall Release Strategy Problem

    Hi Expert,
    I have set the following
    Characterisrtic Name:
    1) ZPR_Release_Plant, Char : CEBAN-WERKS (Char format : 4)
    2) ZPR_Release_DOC_Type , char : CEBAN-BSART (Char format : 4)
    3) ZPR_Release_Pur_Grp, Char: CEBAN_EKGRP (Char format : 3)
    4) ZPR_Release_Total_Value, Char: CEBAN-GFWRT   (Curr format : 15 and  EUR)
    I assign the above to Class : ZPR_Overall_Rel
    I created Release Grp R1 and assign the class and tick "Overall Release" checkbox. There is only one class, no others in the list
    I created two Release codes, F1 - Senior Finance Manager, C2, CEO
    I created two purchasing group, LLL and LYL
    I used the standard indicators for S - block  2 - RFQ/PO and I created two release strategies A1 and A2 for Rel grp R1.
    A1 - release Code: F1, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LLL
    A2 - release Code: C2, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LYL
    The problem is when I tried to created the PR, it doesn't work at all. No trigger whether I click the "check" button at the toolbar of the PR (i.e., the release strategy tab not appearing at the header). I also tried saved and display the PR and see if the Release strategy appears at the header but still not triggering.
    Can you folks advise?
    Thanks
    Lo

    Forgot to check the box "Overall Release" forthe Nb doc Type. The problem is now solved.

  • PR overall release strategy (with shared PR document types)

    We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know,  this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

    Hi ,
    The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
    The Plant can be taken as one of the characteristic.
    The view CEBAN gives all the related views.
    check the below LInk for Futher information on the same.
    http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
    hope so it helps
    Regards
    Anjanna.

  • Overall release strategy in purchase requisition

    hi,
    how do i configure overall release in case of  purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics?  is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
    plz help me in details
    regards
    Aniruddha

    Hi
    For PRs, there are two types of release procedures available
    With classification
    With this we can release the PRs both items wise and in their entirety
    Without classification
    With this we can release only at item level
    When you create the Release Group under the release procedure with classification
    you check the box " ov Rel P Req (Overall release of purchase requisitions
    This  Determines that the items in a purchase requisition are all released at
        the same time (rather than individually).
    This should help to relsove your problem.
    Regards
    Vikrant

  • PR Overall release issue

    PR release  strategy issue comes when Line items in PR added by two different persons, PR Release strategy(overall release)  not getting triggered.
    Release strategy is working fine if i create PR with only one user id.
    Both id's maintained in classification.
    Is this sap standard behavior??
    Created PR 4201001933  line item 10. using  User ID  - 20061704
    Triggered correct release strategy TD QH.
    Added line item 20  using user Id  -  345045 --- (release startegy gone)
    classification Maintained  for TD QH

    We have a similar equirement since we have cost center as one of the characteristics in PR overall release strategy.
    In our case we agreed with Business that the CC in the first PR line item will decide the release strategy. (Or the first CC of thefirst line item in case of multiple account assignment.) We wrote a small piece of code to achieve this, to enter that CC in ceban-kostl.
    If your business requirement permits, you may follow this strategy, where user id of the first line item will derive release strategy.
    Regards.
    Satish Patankar.

  • 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 for Future validity period- (Outline agreements)

    Dear All,
    I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
    E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
    I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
    How to set up release strategy in the above case.
    Thanks in Advance.
    Regards
    Amar

    Hi Amar,
    1) if you maintain a target value (EKKO-KTWRT) in the header of the            
    contract this value is the basis for the determination of the release          
    strategy. If the target value is 0, the system will cumulate the               
    values of the items and will use this value for the determination.                                                                               
    2) So if the target value is 0 and you change the price of a condition         
    with a validity period in the future the system will react in the              
    following way:                                                                               
    Example:                                                                       
       the contract contains one item with quantity = 100 and a net price          
    of EUR 5,-.                                                                    
       all contracts with a target value from EUR 0 - 1.000,- should be            
    subject of a release strategy                                                  
       the contract is created and released on October the 1st                     
       ME32K -> October the 2nd you define a new price of EUR 7,- with a           
    validity period from 03.10.09 - 30-10.09 -> you save the contract              
    -> the release strategy is not reset, as the start date is not                 
    reached yet (system date < startdate of validity period)                       
       ME32K October the 3rd you change a field in the contract -> the             
    release strategy is reset                                                                               
    This is system design that a release strategy can only be reset through        
    an action by the user. The determination of the release strategy can't         
    be triggered automatically in the background.      
    If you create a document which is subject of an overall release strategy      
    (e.g. p.o., contract) the determination of the release strategy takes         
    place when the user hits the 'save' button or chooses the 'check'             
    function.                                                                     
    So there must be a kind of event that tells the system that something         
    has changed.                                                                               
    Regards,
    Edit

  • 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

  • PR Status = 04 : FOR OVERALL RELEASE

    Hi Friends ,
    We have PR status in PR ITEM DETAILS (Me53n) - STATUS Tab , which can have following status
    1)Version in Process
    2) Active
    3) In release
    4) release completed
    5) For Overall Release
    6) Release refused
    I wanted to know the meaning of "FOR OVERALL RELEASE" here and when this status gets updated in PR.
    Like to share, we have OVERALL release Strategy ( NOT Item LEVEL) implemented for PRs
    Regards
    Shrey

    Thx for reply ...
    But here in my case , the status "FOR OVERALL RELEASE" is only being appeared for few PRs, for all other PRs either the status is "IN Release" or "Release Completed".
    Although all PRs are subjected to OVERALL Release.
    I couldn't identify the reason why only few PRs have "FOR OVERALL RELEASE".Also like to share all such PRs has already been approved by approvers but instead of "Release complete" , system is showing me status "FOR OVERALL Release"
    Appreciate if you could let me know the reason for the same.\
    regards
    Shrey

  • Overall Release with Cost Centers

    I have a questions concerning the overall release procedure. I was told that we cannot have mulitple Cost centers on the same PR when using the overall release strategy. Is this true? If not how do you get around this problem. The release procedure is working but when I enter in two items with two different cost centers I receive an error. Please let me know

    Hello every company is facing this problem. To avoid this create a Characterics value as BLANK in the CT04. Input thsi BLANK in CL24N for the particular release strategy.
    in SAP; when 2 cost centres are at the line item level; while determining the corect release strategy at header level; the cost centre value cecomes NULL; hence by inserting the BLANK value; the release strategy is picked.
    I have done thsi for one of my clients.
    you can reach me if you need further clarificaion. I am in Bangalore.
    098800 63823

  • Overall Release for PR

    The overall Release strategy of the PR is not coming up, I tcik on the doc type, tick on the release group and also the use CEbAN-GFWRT, buut it is till not working, what am I doing wrong. When I try the item release, it works perfectly. Can I have item release for stock items and oveall release for non-stock items.

    Hi,
    Could you please check the SAP note 365604 which gives very useful information. Please check all these information and if you still can not solve your issue, I would suggest to open a SAP ticket, so that an expert can have a look in your system.,
    Best Regards,
    Arminda Jack

  • Overall release of PR in Release Strategy

    I have created item-wise release of PR using with Classification of Rel Str.
    But when I am creating overall release of PR I am not getting the tab.
    I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
    Pl guide
    regards
    VS

    Hi VS
    Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
    If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
    If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
    Best regards
    Ramki

  • Overall Purchase requisition Release strategy : Changed after Rejected

    Hi All,
        I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
      Problem I have is when PR is rejected .
    When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
    But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point. 
    ME52 changes for PR is not trigerring any event which can trigger the WF.
    Is there any way we can trigger Workflow in this scenerio.
    Please suggest.

    Hi Subhashini,
    This all depend on release strategy. release should reset completely on tha change.
    For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the 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.
    changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
    Sanjeev

Maybe you are looking for