Setting release strategy for PR for mixed requirement

Dear SAP gurus,
I have a mixed requirement for PR release strategy. For instance, there will be 2 types of PR created in my company. One is created manually, the other one created from MRP. The requirement is that for PR created manually the release strategy will kicked based requisitioner data. While for PR created from MRP, the release strategy will be based on MRP controller.
At first I thought that it is possible to have 2 class set for PR (both should be released at header level), but apparently it is not. So I'm forced to create ONE class that supposedly able to cater both condition.
So at first I create one class with 2 chars: MRP controller and requistioner
For PR which is created manually: I put requistioner eq 'FINANCE' and MRP controller blank (with the hope that ALL value doesnt matter),
For PR which is created from MRP: I put MRP controler eq '001' and requsitioner blank (with the hope that it means that ALL value doesnt matter).
However it seems that SAP consider that blank means blank. I tried with * it also not working. How can I configure this kind of scenario?
Please help.
Best regards,
John

The solution that we implement is to have an exit to determine the requisitioner in the PR based on the MRP controller. Thus we have a common solution for both PR

Similar Messages

  • How to set the Release Strategy without classification for PR

    Hi,
    I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
    I crated the Release Codes, however not able to find what options to choose in the following steps :-
    Release indicator
    Assign Release Indicators
    Release Points: Prerequisites
    Determination of Release Strategy
    Regards,
    Yogesh

    1. Release codes                                                            
       Create the release codes.     For  Purch. Officer, Manager and Sr. Manager                                                                               
    Like PO, MG, SM                                      
    2. Release indicators                                                       
       Define release indicators and branch to the detail screen. Here you      
       define whether fixed purchase requisitions may be changed by Materials   
       Planning, for example, and whether an RFQ or a purchase order may be     
       created from the requisition.                                            
       You can also determine the field selection here.                                                                               
    In the area "Changes after the start of the release procedure", you      
       specify whether a requisition may be changed after the release           
       procedure has begun. You specify whether the strategy has to be          
       redetermined after changes, or whether the release procedure has to      
       start all over again from the beginning.                                                                               
    This parameter bears a relation to the parameter "Value change". For     
       example, previous releases are not cancelled if the value of the         
       requisition item after the change does not exceed plus 10% of its        
       original value.                                                                               
    Attention:                                                               
       Be sure to create a release indicator (e.g. B for "blocked") that        
       serves as the starting point for subsequent indicators. Do not set the   
       indicators for release for the issue of RFQs and PO on the detail        
       screen for this indicator.                                               
       Also create a release indicator characterizing the released status.      
       Set the indicators for release for the issue of RFQs and PO on the       
       detail screen.                                                           
    You can use sytem defined indicator in this case you don’t have to do anything                                                                               
    3. Assignment of release indicators                                         
       Assign a release indicator in dependence on the status of the release.                                                                               
    Example:                                                                 
       You create a release strategy S1 consisting of two release codes 01      
       and 02. Release with 01 is a prerequisite for release with 02. If        
       release has been effected with 01, the requisition has been given the    
       "all clear" for the issue of RFQs.                                       
       You have created the release indicators B (blocked), 1 (cleared for      
       issue of RFQs) and 2 (cleared for RFQs and PO).                          
       Now enter the following as assignment:                                                                               
    Strategy   C1  C2  C3 ...                                                
       S1                          B (blocked)                                  
       S1         X                1 (RFQ)                                      
       S1         X   X            2 (RFQ/PO)                                                                               
    4. Release prerequisites                                                    
       Define which release codes are involved in a release strategy. Specify   
       whether a code is set for a release status following release, and        
       whether one release status is a prerequisite for another (+).            
       Example:                                                                 
      Strategy   Code  C1  C2  C3 ...                                  
    S1         01    X                                               
    S1         02    +   X                                                                               
    5. Determination of the release strategy                            
    Determine the conditions under which each release strategy is    
    assigned. The criteria are account assignment category, material 
    group, plant, and value of the requisition item.                                                                               
    Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
    E.G if you will not define the Material group here but it will default in req in that case this will not work that’s the reason you have to work with Classification.               
    <b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

  • Error message if no release strategy is applied for PO

    Dear All,
    In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
    Is there any way to encounter this
    Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
    OR
    While making GRN against this PO, System will give message Like say ...  no release strategy is applied for the PO..
    Please reply  ...URGENT
    Regards,
    Rakesh Shelar

    Dear Thanx.
    my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
    In this, case  system is allowing to take GRN against such POs without release strategies

  • PO Release Strategy not triggerred for particular Total Net Order Value

    Dear,
    I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
    For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
    All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
    But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
    Please suggest for solution.
    Thank you.
    Warm Regards.

    Dear All,
    While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
    But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
    May I know how the value for this field gets calculated.
    Thank you.
    Warm Regards.

  • Configure of New Release strategy in PR for ERSA Mat type

    Dear Friends,
    Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Regards,
    Ask

    ashokkumardash wrote:>
    > Dear Friends,
    >
    > Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Hi,
    Create Characteristic for Material type and Communication structure CEBAN and a create class with 023 and assign character to class and create Release group and code for MRP controller and finally assign this particulate role to the MRP controller User ID and he release the same.

  • Release strategy in sales order is required before MRP run

    Hi Experts,
    My requirement is Release strategy in sales order is required before MRP run. My client is doing the following process:
    1) Creation of Sale order (MTO).  Ex: User creates 10 sale orders per day.
    2) MD04- Stock Requirement List. All 10 Sale orders should be displayed. So no problem here.
    3) MD50-Make to order-Planning . Here when user gives the sale order number and sale order item and press enter, then only the released sale orders should be allowed and the rest sale orders it should throw a error message and it should not allow to process further.
    How this situation can be addressed in SAP.
    Kindly post some hints and comments.
    Regards,
    Kiran.

    Hi Kiran,
    Define and Assign status profile BS02 at sales order detail (line item) lets say with create and release status
    SD>Sales>Sales documents>Define and assign status profile
    Have create status as default while creating SO with item
    And do a user exit change for MD50 with ABAP consultant help and release it when user keys in SO and item.
    For other line item I believe it will give an error
    Pls try and update if it solves your requirment
    Regards,
    Siva

  • Release Strategy in PO for direct materials not driven by MRP

    We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
    Request you to let me know how I can make this work.
    I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
    request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
    Thanks and Regards
    Murali

    Hi Murali,
    Standard SAP provides PO release strategy at header level only and not at item level.
    So you can create a new PO document type and allow use of only this document type for manual PO creation.
    Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
    Hope this will fulfill your requirements.
    -Ravi

  • Release Strategy with Workflow for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Hi Swamy,
    The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
    How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
    Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
    How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
    How to configure?
    Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
    For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
    For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
    Maintain the details u already have in hand:
    For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO.  After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
    Hope this will give you an idea how the workflow works and how to configure it.
    Rgds.

  • Release Strategy not working for MRP generated PR

    I have one qurey. Currently we are release strategy for normal PR.Now client want to activate release strategy for MRP generated PR.
    current Release Strategy for normal PR configured as following.
    Purchase requisition document     RV
    Purchase requisition document     ZADV
    Purchase requisition document     ZIMP
    Purchase requisition document     ZSER
    Purchase requisition document     ZSTD
    Purchase requisition document     ZSTR
    Purchasing group     A01
    Total value of requisition for     > 1.00 INR
    Creation indicator (purchase r     Realtime (manual)
    Overall release of purchase re     Yes
    For MRP generated PR I add creation indicator B - Material requirements Planning.Even after add creation indicator release strategy is not triggering for PR.
    To trigger PR any setting need to do other than add creation indicator.
    Regards
    Sathish

    Hi
    You don't have to include creation indicator as parameter. Check in what documnet type MRP PR is generated. You can see it in t.code OMDT. At document type level also you can manage it. You need to include creation indicator only if a seperate person approves MRP generated PR.
    To know how to configure release procedure see the below link
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
    Regards
    Antony

  • Release strategy not triggering for Specif plant

    Hi Friends
    I configured a release strategy with three charecteristics. P.org, Plant, Net value.
    this stretegy is triggering for specific plants which are under a particular company code, and if I change to my plant and P.org. its not triggering.
    I have deleted all the classifications and release strategies from, no other data in VV_T16FS_2 , AUSP,T16FV,and T16FS tables except this release strategies data.
    do we have any settings at cocode level??????
    please respond if answer known
    Points would be awarded for for your valuable answer.

    Thank you deepak for your quick respond
    Actually There were already release strategies  with same charecteristics, and with the values of other plants and other P.orgs which are under certain companycode.
    these were triggering perfectly for PO
    Now created new strategy for plant and P.org under different plant code of different cocde. this strategy not triggering for PO.
    but if the release strtegy  values replaced by the erlier plants and P.org  again its triggering.
    Now I created new chars, class, and stategies still same problem persists.
    Release stategy working for the values of a prticular company code plants, Porgs.
    and already tried your suggestion Cocode as char. but same its working for only that company code not for my companycode

  • Release strategy not applied for some contracts..

    Dear All,
    At my client place,In some of the contracts release strategy is not applied.
    I have tried evrything...in classification plant,purchasing group,net value and order type (MK and WK)everything is added.
    but some of contracts release strategy is there and for some it is not applied...what could be the reason?
    Please help.
    Amit

    Dear All,
    Please reply....

  • Re-set release strategy of rejected PO,after doing respective changes to po

    Hi friends,
    I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
    Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
    However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
    Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...  
    Here PO printout is possible only after the final approval...
    Pls give some inputs in fixing this issue..
    Thanks in advance....
    Regards
    Shashidhar...

    Hi
    What are the characteristics of your strategy?
    Try to change one of them save and then rechange it to the original
    eg.
    If the strategy depends for example on the Purchasing Group (PG)
    i mean according to different PG's different strategies working
    then with ME22N change the PG save and rechange it again to the original.
    or
    for example If the strategy depends on Materail Groups (MG)
    then do the change with MG
    With ME22N change the MG save and rechange it again to the original.
    I guess this will trigger the strategy again.
    Hope it helps
    Best Regards

  • Setting Release Strategy

    HI GUrus,
    I wanted to set my PO to Release Strategy:
    01 for raw materials
    02 PO with Total net order value less than 100
    03 PO with Total net order value more than 100
    I've set it, but its not working. Is there other ways?
    Thank you.

    Hi,
    Please down load the Configuration guide from the below link..
    it will show you the standard MM config including Release Process for PO
    http://help.sap.com/bp_bblibrary/600/html/J05_EN_IN.htm
    Thx
    Raju

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

  • Release Strategy to be reset for any change in purchase order

    Hi Experts,
    At present the release strategy configured is for any change in the value of the purchase order, the release strategy is reset. Now the the client wants that for even any text change of a word, text, quantity, value, addition, deletion the release strategy should be reset.
    Can any one guide to configure the release strategy for any change. Also please provide the list of standard parameters/scenario (E.g. change of price, change of quantity etc) for which the release strategy can be configured to be reset.
    Thanks in advance.
    AJ

    Hi Diwakar,
    I too have the same problem. I tried with Changeable indicator "1". The system does not allow to make any change to the Purchase Order even after the first level of Release. But the requirement is that the system should Reset the Release Strategy for even minor Change in the PO.
    Regards,
    S.Raghavan

Maybe you are looking for