Release Strategy disappear in a purchase requisition

Please assist if a purchase requisition is created with different account assignments the release strategy disappear from the requisition.
What might be the problem?

I have the same problem.  If the purchase requisition contains 2 account assignment categories (K and Y), it does not create a release strategy.  I can create a new requisition and get a release strategy if I try to use them separately (not in the same req). 
If i use CL24N, I can see where the RELEASE STRATEGY/CLASS R1 R1 shows a AccountAssignmentCategory value of K and Y.  Why can't I use them in the same purchase requisition?
Thanks!

Similar Messages

  • Release Strategy vs. Delete (Purchase Requisition)

    When my Purchase Requisition hasn't got a Release Strategy I can mark it as deleted using BapiDelete from the Purchase Requisition business object. But when is has got a Release Strategy I can not. Is it right? Am I missing something? Or maybe haven't I got the privileges to delete an Item?

    I am assuming that you are using the BAPI_REQUISITION_DELETE. If I look at the code, there is a comment that says '<b>Requisitions with dependent reservations won't be processed</b>'.
    So if your requisition item creates a reservation then you will not be able to delete the item. It doesn't give you any error message but gives a warning message <i>'Subcontracting item & & not processed due to reservations'</i>for that. Here is the condition that it is checking.
    <i>IF xeban-pstyp EQ 3 AND xeban-rsnum NE space.</i>
    So if you are deleting more than one item at the same time and one of them meets that above criteria, then it will not be processed for deletion, but you will see a success message because the other items are processed correctly. If you look at the entire return messages, you might find a warning message in there for the item that didn't get deleted.
    Srinivas

  • 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

    -

  • Release Strategy and workflow in Purchase Requisition

    Hello All,
    My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
    Thanks in advance for your help!!

    You will need to activate the user exit. This will keep the PO release strategy simple.
    Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
    In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
    Just a couple of points:
    1) What will you do if one item in PO is created with reference to PR and the another item is not?
    2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
    Hope this helps
    Lakshman

  • 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

  • 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

  • Incorrect Release code called which is not defined in a Release Strategy!

    Dear Gurus,
    I am facing a problem in Release strategy for a specific Purchase Requisition document type. My Release Strategy has two Release Codes for the Approval of a PR. When i create that document type of Purchase Requsition, Same Release Strategy is called, system picks the Two release codes from my Strategy but also pick another Release code which is not defined in my Release Strategy.
    Kindly help me and let me know.
    Thanks in Advance.
    Johi Kapoor

    Hi,
    In Release Simulation (segment of Release Statergy), just  click and you will have small pup up screen and there just double click the release codes all you have and you can see all unwanted release codes will be dissapeared and you have only now needed release codes what you configured for the release statergy. Now similuate  release & set/reset release .
    Regards,
    Biju K

  • Release strategy for MRP generated PR.

    Dear friends,
    Can we have release strategy for MRP generated purchase requisitions.....
    What are the steps required if yes.....
    Plz. suggest....
    Thanks in advance
    Navin

    HI,
    IF you want to characteris MRP genrated PR then you have to define different document type other than the standrad one.
    For this MRP define the release stratergy has usual procedure.
    In case if ou dont have a different document type also the standard release procedure which you have conffigured will hold good.
    Thanks & Regards,
    KIran

  • Reset release strategy PR

    Hi!!!
    How can I do to reset an strategy when the document is modified in some level of approval in a document PR.
    Thanks in advance!!!

    Hi,
    I have a similiar problem.  We are running ECC6 and have noticed that when a user with no release approval makes a change to a PM work order (change of work order basic start date, TECO the work order etc) then the release strategy on the associtated purchase requisitions is reset.
    This is causing PRs to be set as "blocked", even though the PR lines are deleted on TECO of the work order.
    The opposite also occurs, where a user with release approval greater than the value of a released requisition changes the PM work order, it then deletes the PR release strategy as the release strategy would not have been initiated if that user created it in the first place.
    Our release indicator "2 - RFQ/Purchase Order" has the changes after start of release set to 4 (changeable, new release in case of new strategy or value change) and 0.0% value change set.
    As there are no changes to value when the date or PM work order status is changed, why does this reset the release strategy?
    Any help will be greatly appreciated.
    Matt

  • Purchase Requisition with wrong purchasing group - release strategy

    Hello
    There is a lot questions about release strategies but I cannot find answer.
    I have release strategy based on:
    - Plant
    - Purchasing Group
    If I create Purchase Requisition with right purchasing group release strategy is assigned to PR item.
    When use wrong purchasing group - release strategy is not assigned.
    How to easy set control – if user use wrong purchasing group system automatically set one strategy which not allow to create purchase order.
    There is too many plants (150) and purchasing groups (60) to create all combinations in strategy. So I cannot do that.
    Maybe there is some useful user-exit?
    I use SAP ECC 6.0
    My problem occurred because SAP allow to create PO with reference to PR which have no assigned strategy.
    Thanks in advance for help
    Arek

    Yes it is solution
    But as I wrote before – there is too many incorrect combination.
    Example
    PG A1, A2, A3, A4…. A50
    Pl 2200, PG A1 – OK
    Pl 2200, PG A2 – OK
    Pl 2200, PG A3..50 NOK
    For this example I have to set 48 combinations (strategy with S).
    I noticed that I would have to set about 200 strategies. Client don’t want accept it.
    You wrote – “set up one unique strategy”. How? As I know I need 200 strategies (or there is something I don’t know
    Kind regards
    Arek

  • Purchase Order not subject to release strategy

    Good day everyone!
    I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
    After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
    My question is: How to assign purchasing document to release strategy?
    Please help. Thank you in advance.
    Anisah

    hi
    yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
    now below i am giving u one by one steps , follow and let me know .
    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   0
                            1
    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
    ravikant dewangan

  • Purchase Requisition Release Problem

    Hi All,
    I have a release procedure set up, and the strategy pulls up correctly when a PR is made.  When I view collective release from ME55, the PR's show up, and I am able to release line items from that screen.  However, when viewing the PR from ME53N, in the Release Procedure tab there is no green check next to the release code with which to release the line.  Also, if I do release the PR from ME55, I cannot go to ME53N and cancel the release from the Release Procedure tab. 
    I am a user with all security access, so it is not an authorization role problem.  The release group is also configured to release by line item, so that is not the problem.  I have set up other release procedures which allow the release/cancel release function from ME53N before... what could be the problem this time?
    Thanks,
    J

    hi.
    There are two ways of releasing purchase requisitions:
    Individual release  (Tcode - ME54)
    You release items of an individual purchase requisition or - if the requisition has to be released in total - by releasing one item you simultaneously release all the others.
    Collective release (Tcode- ME55)
    You release all requisition items or complete requisitions that are awaiting processing by your release code. This is the preferred method if you frequently have to effect release.
    Display PR -with release status  (Tcode-ME53N)
    One can only see release status in ME53N & can not change release.
    hope it helps to you.
    Regards,
    Rahul

  • Perform check after release step of purchasing requisition

    Hi,
    does anybody have a suggestion where to place best some logic which needs to be performed after a release step is performed successfully.
    background: we use different types of Purchase requisitions, while each one is assigned to a static release strategy. I like to change it in more dynamic way by adding certain logic after a release step is performed.
    example: if preceeding release step was 10 and purchase requisition is of type x then check purchase value and account assignment in order to process the current stepo automatically.
    Currently the logic runs during a nightly job, but I would like to add it immediately after a release has been performed. I would imagin something like user exit, BusinessAddIn, or an event which I can use assign the job.
    Can anybody suggest something?
    Thanks in advance
    Best regards
    Torsten
    Edited by: Torsten Hübsch on Apr 29, 2011 10:36 PM

    Hi,
    Enhancement  M06B0005 is relevant for PR in case of overall release
    Check on trx SMOD  :
    Enhancement        M06B0005
    Short text         Changes to comm. structure for overall release of requisistion 
    --> Function module                Short Text
    EXIT_SAPLEBND_004              Changes to Communication Structure for Over.
    Enhancement        M06B0002 is for item-release
    Short text         Changes to comm. structure for purchase requisition release
    --> 
    Function module
    EXIT_SAPLEBND_001
    BR
    Nadia Orlandi

  • Release approval procedure and purchase requisition

    Hello gurus,
    just now I discovered a strange behaviour (in my view) in one of our client's system:
    There is a release strategy for certain purchase requisitions. When I create one of those, the release strategy is applied and the Requisition Processing State is set to "In release" automatically.
    But now comes the strange part: I can create a PO and copy that same purchase requisition item into it and save the PO! I.e. I can order the item, even though there was no prior release of the purchase requisition.
    Unfortunately I cannot try myself right now, but this is not standard behaviour, or is it? Where is the sense in having a release strategy when the item can be ordered anyway, even without release?
    Thanks in advance
    Alicia

    Hi Alicia,
    Go to transaction OLME -> Purchase Requisition -> Release Procedure         
    -> Procedure with Classification -> Set Up Procedure with                   
    Classification -> press button 'RELEASE INDICATOR', make                    
    'double click' in your last release indicator and check if the flag         
    'REL.FOR ORDENING' is set or not.                                                                               
    Go to transaction OLME -> Environment Data -> Define Attributes of          
    System Messages, and see if you have defined the message                    
    06 055 as warning or error?                                                 
    Please check additionally if you have in EBAN (for the requisition) the fields FRGKZ, FRGZU, FRGST filled with entries.
    Also deactivate your user exits and check the behaviour again (see note 365604).
    Regards,
    Edit

  • Reset Release Strategy for any change in the Purchase Order

    Hi,
    Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
    If so, where do we need to make the configurations.
    I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
    Thanks in Advance.
    S.Raghavan

    hi sandesh,
    sorry, i know it's too late.
    i tried your suggestion, it works blocking the purchase order after release strategies are setted.
    sandesh, raghavan:
    i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
    regards
    f

Maybe you are looking for