Release Strategy - question about requisitioner??

Hello,
I have set up a release strategy for my PR based also on the requisitioner (CEBAN/AFNAM).
If specific requisitioners (listed into my characteristic RELEASE_REQUISITIONER) create a PR, the PR should be released before creating the PO.
BUT if an other requisitioner who creates a PR doesn't belong to my release strategy, this requisitioner is allowed to create this PR without any release procedure behind it, and then he's free to create the PO.
How can I avoid this ?
How can I say to my characteristic to take in charge ALL requisitionner (I tried with * or xxxx or... but however I don't know if there is a specific word to say "all").
Thank you for your help...
François.

Unfortunatelly this is not the case.
On the PR, when I change the requisitioner with one who doen't belong to the defined release strategy, the release strategy tab disapears from the PR and I get this warning "Requisition not subject any release strategy following changes"
The PR is automatically ready for PO....
In fact I would like to work like this:
If requisitioner is AAA or BBB, work with release strategy X
For all other requisitioner from my company, work with release strategy Y
But this is "all other requisitioner" I cannot translate to my release strategy...
Thank you for your help

Similar Messages

  • PO Release strategy question

    Hi,
    In PO release startegy,
    Plant- XXXX
              YYYY
              BLANK
    Purchase group, Total net order value, order type are the characteristics currently defined.
    PO is created at company code level..with multiple plants-i mean, XXXX, YYYY.
    rekease strategy does not work in case, if line items have account assignment and item category.
    pl help

    CEKKO is a structure for purchase order header.
    The plant in purchase order header is only filled in case of UB stock transport order, where you do not have a vendor, here you would only have the supplying plant.
    You are talking about plant in item level, which is requesting plant, not the supplying plant.
    You can never reach your goal until you CHANGE your design.
    you either create only POs which have only items of one single plant (must be controlled via user exit) or you just cannot have a release strategy that works. It is just black or white.

  • ME54N Release strategy question over delivery tolerance limits

    I set up a release strategy base on the over delivery tolerance level. My problem is when a Purchase requisition is saved as rejected, and i click on the button cancel reject it deletes the last release strategy level because now it is looking at the actual total value disregarding the over delivery tolerance level.
    It works fine when the Purchase requisition is not rejected, and i can cancel or reject the purchase requisition without saving it and it does not delete the last line of the release strategy taking into account the over delivery tolerance level. I am using the user exit ZXM06U13.
    Can someone give me some insight into this ? Thanks.

    Hi Siva:
    You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
    Good luck
    Z.T

  • Another Release Strategy Question - Multi currency

    Hello,
      I have been searching for an answer to my delema to no avail on this board, but no answer yet.
    My problem:
      We have a Purchase Req. strategy with approval by Plant, Cost Center, and Total PR Value.
    The PR Value Characteristic is in US Dollars, but one of our companies is in Europe so we also need to have a PR Value Characteristic in Euros.
    Currently we have:
      Characteristic:  Z_PR_AMT referencing field CEBAN-GFWRT.  This is in US Dollars.
                             Z_PR_WERKS referencing field CEBAN-WERKS
                             Z_PR_KOSTL referencing field CEBAN-KOSTL.
      Class:              Z_PR_CLA with references to Characteristics: Z_PR_AMT, Z_PR_WERKS, and
                             Z_PR_KOSTL.
      Release Group: A1  that is assigned to class Z_PR_CLA
    Also, currently all PR's under $1000 (US Dollars) go through Workflow for release, and if the PR is over $1000 (US Dollars), requires a 2nd release.
    But, since we have a company in Europe, we also need to be able to have a Release Characteristic for Euros so that PR's in Europe under 1000 Euros go to a new release strategy, and PR's in Europe over 1000 Euros go to a 2nd release strategy.
    Can I add a new Characteristic to the Z_PR_CLA refering to the same CEBAN-GFWRT field, but use currency EUR (lets say Characteristic ZPR_AMT_E).  Then in CL20N (Classifications) when I am adding the actual values, leave the value information blank for the European Amount  characteristic and fill in the US Amount and assign to a US Release Strategy.   Then leave blank the US Amount charastieric field and fill in the European Amount characteristic field for Europe Release Strategies?
    Will this work?
    Thanks in advance.

    That is the problem we are trying to avoid.  We do not want to have to put in a manually converted 1,000 Euros to US Dollars.
    Currently we have a US Dollar limit for our European plant set at $1,474.30 which is to represent 1,000 Euros.  But this number changes with the fluxuation of the currency rates.
    So far in testing I do have 2 Characteristics defined for Currency, one for US Dollars and the other for Euros.  Both Characteristics have amounts loaded in them (via the CL20N screen).
    I do see in my debug sessions that there is a currency conversion to foreign currency in the LEBNDF01 include program, but since I have 2 Characteristics for Currency in the CL20N screen for this particular Release Strategy, this is messing up the conversion to foreign currency.
    I still have more debugging to go.

  • Release Strategy Question

    Hi,
    Can anyone explain me with example, why is it that we can have only one class and not more, when configuring groups in the release strategy.
    Why is it mandatory to have only one class for overall and one class for line item release, can someone explain with examples.
    The system allows creation of multiple groups, but all have to use the same Class when it comes to overall release/ Line item release.
    I am not able to understand the reason behind this restriction as of now, can someone share some insights.
    Thanks
    Shailesh

    Hi,
    Better & always keep one release class ....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.Under each separate class keep your requires characteristics.Then do necessary confuguration for release statergy.
    For more check the links:
    /people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
    Re: Class and release group and code in release strategy??
    Regards,
    Biju K

  • Acknowledging old P.O's : retriggers Release Strategy?

    Hello,
    I know that when you acknowledge an old Purchase Order in the Confirmations tab, it can retrigger the Release Strategy, therefore disapproving the P.O.
    Does this apply also if we acknowledge a P.O line item that has the Account Assignement Category "Y" (Non-Recurring)?
    Example:
    P.O line item #1: part number ABC, already acknowledged
    P.O line item #2: "Y" non-rec charges, not acknowledged
    If we acknowledge line item 2, will it retrigger the Release Strategy?
    Patricia

    Hi,
       The release strategy re-triggering depends on the release indicator used and it will re-trigger only if there is a value change or new strategy is determined. If you are simply flagging acknowledgement in a PO, it wont make any value change / new strategy and hence new release wont be triggered. Please check the note: 493900 - FAQ: Release Strategy Question number 3
       Also, please check whether version management is activated for the PO document type and version number is used as release characteristic. The release strategy will reset when version is set to complete and the new total net value is higher than the old net value. Refer the note: 1961482 - Reset release strategy when version number is set as Characteristic in Customizing
       You may note the above two points and analyze whether new strategy will be triggered for the corresponding changes in PO.
    Regards,
    AKPT

  • Release strategy H8 Update

    Hi Experts,
    We wanted to know who changed the release strategy H8 value  in our SAP system.
    Found that PRD System release strategy GT value has been updated somehow with in six months.
    please let us know how to check find out who updated value?.
    Thanks
    Malai

    Hello Malai,
    I think that for "Release Strategy" questions you should opan a thread under category SAP Community Network Forums » SAP Solutions » ERP - Logistics Materials Management (MM).
    Please, go to  and formulate your question.
    Best regards,
    Rafa

  • About PO Release Strategy Workflow : WS20000075

    Hi,
    I want a workflow for PO release strategy. I believe that there is a standard workflow WS20000075 for the same.
    But I am unable to use it.
    I am not a functional guy and there is no one else to assist.
    Can somebody tell me how I should go about?
    Thanks.

    Hi,
    WS20000075 this std. Workflow for the PO this has multiple levels of approvals, Depends on the no. of approvals it will flow.
    The approver can be picked using the User Exit M06E0005 (EXIT_SAPLEBNF_001 - User Exit ZXM06U51), here you have to write logic to pick the Approver.
    The approval workitem comes to SAP Inbox, once the approver click the workitem it will open the Transaction, there the user can approve.
    To see the status of the Workflow, Go to ME23N, in the top left a button, Service Object, click on that, a drop down appear in Workflow > Workflow Overview, you can see the status here.
    Regards,
    Surjith

  • Contract Release Strategy - field Requisitioner

    Hello,
    I will start to use the Contract release strategy and I need the field Requisitioner (EKPO-AFNAM), because this field is part of my PO release strategy.
    This field isn't available in the transactions ME31K and ME32K.
    Can you tell me, if it's possible to show it in these transactions?
    In other case, where can I fill this field? How is the BAPI, BADI, etc?
    Thank you,
    Meire

    Hi,
    Please, be so kind to refer to note 373361. This field was only                 
    available in purchase requisitions and due to requirements of                   
    SRM (formerly BBP business tons business procurement  ), it has                 
    been added into the new enjoy transaction                                       
    ME21N/22N/23N for purchase orders.                                              
    It is not available for contracts.                                                                               
    The contract is  not  the last document in the procurement.In bussiness               
    process the requirement of requisitioner in contract is less important.         
    It is enough if you don't know the requisitioner at the time of contract but              
    you know it at the time of PO creation.                                                                               
    This is the standard SAP design.   Please do not use this field in the contract release strategy: create a new release group for the contract release strategy, delete the value entry for EKPO-AFNAM in the "Change view - release strategies - classificaion". The characteristic for EKPO-AFNAM should appear as black and not as blue on the screen. Save your strategy.
    Regards,
    Edit

  • A question about item "type and release" of  source system creation

    Hello expert,
    I have a question about item "type and release" of  source system creation.
    As we know,when we create a web servie source system,there will display a pop-up which includes three items as "logical system","source system"and "type and release".
    About the item "type and release",when we push "F4" button,there will be three default selections as below:
    "ORA 115     Oracle Applications 11i
    TLF 205     Tealeaf 2.05B
    XPD 020     SAP xPD".
    Who can tell me when and how should I use the three selections.
    And also I attempted to input the item by some optional letters except the default three selections and it seems that I can input it freely.
    Thank you and Best Regards,
    Maggie

    Hello DMK,
    Thank you very much for your answer.It is very helpful for me.
    Can I ask you further about it?
    I got that it is a semantic description item.
    You said the default selections are set by our basis people.Would you like to tell me how should we creat a new value except the default ones for item "type and release"?Only by inputing the value in the item directly?But you see we canot see the new value item we created by ourself when we push "F4" button next time ,is that ok?Or do we have to ask basis people to define one new value item just like the default seletions before we use it.
    Also if possible would you like to describe detail about "This becomes important when you are troubleshooting certain issues especially when RFC connection problems."
    Thank you and Best Regards,
    Maggie
    Message was edited by: Maggie

  • How to Display PO Release Strategy in Enjoy Screen

    Dear all,
    I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
    However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
    In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
    Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
    Thanks a lot.

    Thanks 4 the reply Rahul.
    I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
    In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
    So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
    I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
    Thanks and appreciate if anyone could help.

  • PO release strategy report

    Dear Experts,
    we are creating one report.
    PO release strategy report for Audit purpose.
    Who created
    When created
    TIme should be display
    user id and user code.
    for example, we have 4 levels for PO release.
    All 4 persons should approve for this PO.
    we need to know level wise when they released who released.
    how to take this

    Moderator message: Basic frequently asked question - Please search forum for answers and read the docu in help.sap.com
    See as well our rules of engagement: http://scn.sap.com/docs/DOC-18590
    This blog describes how to use the SCN search:http://scn.sap.com/community/about/blog/2012/12/04/how-to-use-scn-search
    Another good way to search the forum is with google. See this blog with details for a good search
    http://scn.sap.com/community/support/blog/2012/04/16/getting-the-most-out-of-google-optimizing-your-search-queries
    The discussions are not a replacement for proper training
    Thread locked

  • Questions about SRM PO in Classic scenario

    Hello All
    I have a number of questions about the SRM PO in classic scenario.
    1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
    for the same?
    We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
    Our requirement is not have an approval initially once the PO is created, but only for the changes
    2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
    for this to happen. Should SAP XI be required for this?
    3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit?
    We are using SRM 7.0
    Regards
    Kedar

    Hi,
    1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
    for the same?
    We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
    Our requirement is not have an approval initially once the PO is created, but only for the changes
    Sol: In ECC6.0 if the P.O is changed and release strategy is there in ECC6.0 then it follows the ECC6.0 Approval Route.
    2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
    for this to happen. Should SAP XI be required for this?
    XI is mandatory
    3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit.
    Once P.O is created in ECC 6.0 for the P.R in Sourcing Cockpit, cancelling/reduction will not have a updation in the sourcing cockpit in SRM.
    Eg  100 nos P.R is in SRM sourcing cockpit for which  you have createdaa P.O for 40 nos is ECC6.0
    for the remaining 60 nos PR ,you can create a P.O in ECC6.0
    Regards
    Ganesh

  • PO release strategy Classification

    Dear all,
    I have a question about PO release strategy would like to ask, hope you can give me some advice.
    I have about ten release strategies which is used for different requirements.
    For each release strateg, there are several Classification.
    I am going to set a new release strategy, which only concern some of the Classifications, for the non-used Classifications, I have set a '*' to be the value, but the release strategy does work.
    I would like to know is it all Classification should be provided a value?
    Many Thanks
    Sunny

    Hello Biju,
    Firstly, many thanks of your idea.
    Let me make an example.
    I have a clasification (GROUP 1) which has predefined values ('A', 'B', 'C', 'D', 'E', ' ' ), and this clasification was already used in many release strategys.
    A release strategy is defined to trigger the release when the value of the clasification (GROUP 1) is value 'A' and a release strategy is defined to trigger the release when the value of the clasification (GROUP 1) is value 'B' ..etc.
    For this new release strategy, it does not concern the values of the clasification (GROUP 1). In my setting, if I set a value '*' in the release classification, the release never triggers. What should I set if I would like to ignore this classification for this release strategy?
    Thanks your advice again
    sunny

  • Release strategy & EBAN for project systems, purchasing

    Hi
    We have 2 different scenarios for which we use same account assignment category "Z".
    1) Purchase Requisitions for capital expenses (Account assignment category "Z") - this is part of project systems requisition attached to WBS elements
    2) Purchase Requisitions for expensed items (Account assignment category "Z")
    I have configured release strategy with classification with following characteristics
    1) plant
    2) cost centers
    3) total amount in PR
    4) account assignment category
    all 4 characteristics are same in both areas (capital and expensed)of purchase requisitions, account assignment category Z decides whether it is capital purchase or expense related purchases. Z uses order number that is internally tied to WBS element.
    my question is - if some one has similar scenario then what is the best solution to handle invocation of release strategy.
    how release strategy can be determine, do I need to use user exit and if yes what best user exit is available.
    EBAN fields, I have researched and I cant use fields like "requisitioner" for determining release strategy.
    I would like to invoke different release strategy for capital projects and different release strategy for expensed items in PR. there is a workflow attached to this later.
    Please reply
    Thanks and regards
    Umesh

    Umesh,
    Well, there needs to be some way to differentiate the 2 types of purchase requisitions for you to use 2 different release strategies.
    I am not sure if you have the option of using a different document type to differentiate the 2 requisitions. I would definitely look at this possibility and include the document type (CEBAN-BSART) as a characteristic in the release strategy.
    Other options would be to look at using the purchasing group (CEBAN-EKGRP) or the requirements tracking number (CEBAN-BEDNR) as characteristics in your release strategy.
    Hope this helps.
    H Narayan

Maybe you are looking for