Shoul order type be part of release strategy or WF logic?

Hi,
In our release strategy for purchase order we have set up anything that is > £500 needs approving. This kicks of the standard PO wf, but the workflow should also only start if the order type = NB or 8000.
Can anyone tell me if the order type should be part of the release strategy or the workflow logic?
Thanks
Forhad

Hi,
See its purely based on the requirement, if you maintain at the release strategy level then the release strategy itself will not be available for those kind of PO's.
so its better to restrict this at Wf level thru start conditions.

Similar Messages

  • Deleting of message type after reseting of release strategy

    Dear Team,
    My requirement is when the PO is finally release and outputted to vendor, its relaese indicator is set to 'R'(i,e, Relaesed, no changes) . Now if for any reason i have to do some modification , I have to repeat the output via ME9F so as it seems that PO is again ready to output. Now using transaction 'ME28'', I will goto derelaese the the PO
    Now I have the requirement, is there any way that just after dereleasing from ME28, the message type that I have added which allows me to reset the release, got deleted.
    That when now i goto ME22N, for making the modification, their must not be any preconfigured message type and genereated when do any changes.
    This is required to print the amendment in PO,
    So please suggest if their is any modification or enhacement available to achieve the above
    Regrads
    SAPABAP

    Hi,
    1st try with standard functionality and if not possible then go for enhacement. You needed in ME22N,if you do or make the modification in PO ,no preconfigured message type should be triggred automatically or no output genereated.
    Lets example you have PO message type ZNEU and its clear that you need preconfigured message type should be triggred automatically for PO output for PO creation ONLY. Use the below path:
    SPRO->MM->Purchasing>Message->Output control->Message tyoes-> Define message type for Purchase Order--->Fine-Tuned Control: Purchase Order
    As you needed,then DO NOT make entry or if entry is there,just DELETE for PO change not to trigges any message type
    {Indicator for print----
    condition type
    2----
    ZNEU}
    NOTE: Then think about how you will have PO print after any changes in PO.But you can think of not having automatically  PO message type on PO creation or PO changes and can ONLY enter PO message type manually for PO print.So do not select u201CAccess to conditionu201D check box in NACE t.code for your PO message type ZNEU.
    Regards,
    Biju K

  • Send purchase order e-mail with release strategy

    Hi!!
    I have a problem with sending e-mails in purchase order that are blocked with release strategy.
    I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
    Somebody knows what is happening?
    I would like to send e-mails without previous modification of the purchase order.
    Thanks for your help.

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • Issue with PO Release strategy

    Hi experts,
    I have problem with Po release strategy in 5 to 10 purchase orders, i have created few purchase orders(2000 Po's) with same document type and company code ..etc and saved, then release strategy has been triggered.
    For few purhcase orders release strategy has not been triggered.
    If i take 1 po from that few purchase orders(Release strategy has not triggered) as reference and again if i create PO,new purchase order have getting created with release strategy.
    Can some body tel how this ican be possible, hope this might be standard syatem behaviour.
    Hope i should delete thos e purchase orders and i should create new PO's instead of of old PO's (Without release strategy).
    Some experts can share their experiance in this regard.
    And how i should proceed further with this issue.??
    Thanks

    Hi,
    You issue in your system has 2000Nou2019s purchase orders  with release strategy has been triggered but 5 to 10 purchase orders do have release strategy.
    & when you are creating a new PO with reference to old purchase orders (which release strategy has not triggered) and on saving NEW PO created with triggering release strategy.
    Cause for above:
    PO which release strategy does not trigger because the purchase orders are created before setting release strategy for PO. Those PO triggered release strategy and all are created after setting release strategy for PO.
    Action:
    Its completely business call for business users to go for options:
    Option-- >1# You can use same old PO which release strategy does not triggered, do GR and all other process
    Option-- >2# You can create new PO with reference old PO which release strategy does not triggered and upon saving you will have new PO number with release strategy triggered, then release PO & do GR and other related process.
    Regards,
    Biju K

  • Purchase Requisition Release strategy for MRP based Requisition

    Hello Gurus
    We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
    Thanks
    Nick

    Hi,
    If you want include the MRP related PR in Release strategy.
    You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
    So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
    there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
    But it will  not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
    I think first one is best suited.
    rgds
    Chidanand

  • No Release Strategy determined - Message no. Z_MESSAGES032

    Hi All,
    I am trying to creat PO without reference to PR and facing error:
    No Release Strategy determined
    Message no. Z_MESSAGES032
    This is for newly created PO type and new cost center.
    We don't have any PR, we are creating PO directly
    please advice

    Hi Vishal,
    As you mentioned you have created new PO type so I think release strategy is not created for this document type. You can go to the IMG ==> MM ==> Purchasing ==> Purchase Order ==> Rlease Procedure for Purchase order ==> Define Release Procedure for Purchase Order.
    Select Release Strategies option and create new Strategy. Selecte the newly created strategy and go to details and click on Classification and then Add your document type and other information. If you have any existing release strategy you can select that and add another document type in the classification.
    I hope this will help.
    regards,
    Ajay Mishra

  • 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

  • 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

  • Cancel PO - Release strategy remains active... WHY?

    Sometimes, when I cancel a Purchase Order with the bin, the release strategy remains active and the approver finds the PO among the ones he has to approve, even if it has been cancelled. In many other cases, instead, when I cancel a PO the release strategy correctly disappears.
    Could someone let me know why the release strategy remains active?
    Thank you so much.
    Fabio

    Thank you for your reply but I don't agree at all with you.
    In many cases, the most cases, when I delate a PO the release strategy disappears. Sometimes it remains active and I don't understand why.
    The approver shouldn't see these delated PO's among the ones he has to approve.
    Thanks again.
    Fabio

  • PO release strategy is not triggering if Quantity pre.Qty

    Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
    Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.

    Hi.
    According to  note 493900, question 4, release strategy is reset only
    for some specific case. Alternatively, please question 5 from this note
    release strategy might be redetermined. However in order to determine a
    new release strategy the field that is changed in PO must be included
    as one of the fields in the strategy. Thus there is no standard way
    for resetting/redermining release strategy for a change of e.g. text
    on header or item level.
    Please also kindly refer to other 2 useful notes for this area:
    662993     Resetting an already occurred release
    365604     FAQ: Release strategies in purchasing
    BR
    Nadia Orlandi

  • Why PO is automatically assigned with release strategy?

    I created a PO with PO document type NB and NB is not assigned with any release strategy.
    But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO.  Why?
    And only when the PO is in held status, there is no release strategy assigned to NB PO.
    Is the normal ERP behavior?
    I only assigned a release strategy to PO document type DB, which means dummy document type.

    Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
    Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
    Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

  • User exit for triggering release strategy

    Hello Experts,
    My requirement is when changes are made in purchase order (ME22N) then once again release strategy will have to get trigger.
    is the user exits exists for this purpose,if yes, What is it?. I searched alot but not able to find right exits.

    Hello ,
    I think you can achieve this via configuration .Basically you want the release strategy to get redetermined based on the changes in the item or if the price of these items increase a certain level .if you  have the release startegy as changeble in the SPRO ticked it will automatically go for new release strategy if you have the value of release indicator set .This can be done SPRO->MM->Purchase order->Release procedure for purchase order->Define release procedure->Release indicator.
    Set  the appropriate value  .
    Remember you need to know what is that it retrigger that release strategy .
    The link below deals with similar requirement ....
    [http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/retrigger-release-strategy-for-purchase-requisition-with-any-change-1858101]
    Thanks
    Anjaneya .
    Edited by: Anjaneya Bhardwaj on Aug 31, 2011 8:21 AM

  • Release Strategy Characteristic Upload through LSMW.

    Release Strategy Characteristic Upload through LSMW.
    Introduction:
    In case of Purchase order, we need to maintain Release Strategy each year. This is due to organizational changes. Due to huge organization, this is around one week activity for us. Reason, we need to maintain characteristics for around 300 different release strategies. Since, we can't transport "Characteristics" from one system to other, we need to maintain them in Quality as well as in Production system.
    Issue: We tried to use option of LSMW to maintain these "Characteristics". But, system is giving error as "Logical Path is not available".
    Question: Who is responsible to create this "Logical Path" and where it can be done?

    Hi,
    I think you moved LSMW from test to production and this might be happening due to this fact. Please redo steps in LSMW for:
    Specify Files
    Assign Files
    Read Data
    Create completely new paths, and allow system to recreate (you need the right authorization). This might help I hope.
    Regards,
    Tomek

  • Change release strategy

    Hi!
    I have a problem with release strategy.
    When i create purchasing order, i need to change release strategy.
    How can i do that? I'm trying use exit M06E0004 (EXIT_SAPLEBND_002) but i don't know how fill this fields.
    Anybody has any example?
    I need to change the fields "Release group" and "Release strategy" in ME22N.

    Hi,
    Open the existing PO's in change mode and close . New Strategy will become effective
    Regards
    Reward Points if useful

  • Release strategy to STO - Order type UB

    How to apply release strategy for STO for order type UB ? Except UB order type I'm able to apply release strategy. Is there any Config for exclusition ?
    What is the userexit for STO Creation i.e. ME27 / ME21 ?
    Regards,

    http://www.sap123.com/showthread.php?t=59
    check UB is existing or not in the existing characteristics or any combination characteristics stops you.
    you need to create a characteristic with CEKKO--BSART and assign the same in your class and further use this characteristic in your release strategy.
    br
    muthu

Maybe you are looking for