Release Strategy - Reset
Dear Team,
My purchase order / PR release strategy should be reset, due to following reasons.
1. Any changes in Item Text / Header Text
2. Any changes in PVC / LD clauses & Base dates
3. Any changes in Retention / Advance %
4. Changes in Delivery Date
Could any one pl suggest on this and how to do it.
Thanks & Regards,
R.Saravanan
Hi,
Put proper release indicator against the release group .
You can set a control within Config. there is a parameter called as release indicator.
Follow this IMG path:
SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
1 Cannot be changed
2 Changeable, no new determination of strategy
3 Changeable, new release in case of new strategy
4 Changeable, new release in case of new strat. or val. change
5 Changeable, new release if new strategy/outputted
6 Changeable, new rel. if new strat. or value change/outputted
Changeable, new release in case of new strategy
Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
Similar Messages
-
PR release strategy reset after change in quantity/inclusion of line item
If a user adds a line item or increases the quantity of an existing line item to a fully released purcahse requisition, then the system does not render the PR for reapproval. Is there any way to configure SAP such that the release strategy resets if any of the above changes are made in a fully approved PR?
Hi,
the release strategy will ONLY be reset if one of the fields that are contained in your classification are changed.
For example
If you strategy is determined by Plant and value, if the plant or value doesn't change then the release strategy will not be affected.
So if you change qty and do not change value then the release strategy will not be reset. This is a basic limitation of the design.
But if you ARE changing one of the characteristic values of your strategy and you are saying that the release strategy is not being reset, then something else is wrong.
Steve B -
Invoicing Party - Release strategy reset
Goodmorning.
In a PO already approved, if I fill in the Invoicing Party (IP) in tab PARTNERS, the Release Strategy will be reset and start again from the beginning. Why?
Thanks for your reply.
FabioHi Bob,
this is the first time I use this forum so I apologize if I'm in the wrong one.
I explain what I did this morning.
I have a Purchase Order already approved but I will receive the invoice from a partner different from the vendor. I forgot to put this information in the PO.
I enter in transaction ME22N (Modify Purchase Order), I select tab "Partner" in the Header and I add function PI (Invoicing Party).
When I save the PO the release strategy starts from the beginning, it will be reset. I don't understand why.
If I'm in the wrong forum, could you please indicate me the right one?
Thank you very much.
Fabio -
Release strategy on doc. level isn't working because different values for B
Hi,
At my company we just created a new release strategy (3rd) for PR's. The old strategies were on item level, the new one is on document level. This is the third strategy in the system and with every new PR the strategy is decided based on the creation date (table EBAN field BADAT). For example:
Strategy 1 - BADAT < 2009.01.01
Strategy 2 - BADAT >- 2010.01.01 AND BADAT < 2011.01.01
Strategy 3 - BADAT >2011.01.01
These selection criteria are stored in the class.
This used to work fine between the 1st and 2nd strategy but now it doesn't. Whenever a new line item is added on a different day than the other line(s) the value's for BADAT will be different within the PR and the system isn't able to select a strategy. It's like no value is used for BADAT because there are more than 1 available. As a result the release tab will disappear and the PR will be ready to create a PO from it.
For example:
Line 1 BADAT 15.09.2011
Line 2 BADAT 15.09.2011
No problem releasing the PR
Line 3 BADAT 17.09.2011 added (release strategy reset)
Release tab disappears so no release can be done. However, this PR line 3 can now be converted into an PO without being ever released.
One solution we thought about is using the PR number BANFN. But no ranges are allowed in the class so it doesn't seem to work. Another option is to delete al the old strategies but what will be the consequences for all the old PR's?
We are not sure what to use. Maybe someone else worked out this issue before or has an idea?Hi,
First of all why you want to release a PR based on Creation date ?
Anyhow, as I understand from the above explanation, since you have created your 3rd strategy @ header/document level. You are facing this issue.
If you have a strategy @ document level then why you want 2 separate strategies @ item level.
Following are the possible solutions as per my understanding
1. You can make the 3rd strategy as item level itself so that the different creation date for different items wont be a problem.
2. You don't have to delete the Old release strategies instead you can remove the characteristics assignment so that release strategy wont be determined @ item level & you can keep the new release @ document level. But in this case you cannot have creation date as a characteristic since it will result in the same issue..
Thanks & Regards, -
Release strategy should revert
hi
in PO we r using only release strategy not version management .
our scenario is like this , once a PO has released and if any body tried to do any change in PO after that , then those release strategy should revert to unreleased status.
guide us where to do right configuration .
what currently happening is , if in changing mode we are giving Quantity more then previous it is reverting release strategy other wise not .
regards
sachin sharmaSachin,
As SAP standard, release strategy will be reset if:
- the changeablity of relesae indicator set to '4' incase of PR and '4' or '6' in case of another purchasing doc (PO, RFQ, contract)
-the document stii subject to previous release strategy
-the new TOTAL NET ORDER VALUE is higher then the old one
For release strategy reset in PO i suggest to use user exit.
Reward if useful -
ME38 resets Release strategy of Scheduling agreement
Hello,
It seems when the users change the delivery date in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
I cannot understand why this happens.
Has anyone encountered such a problem before.
Thanks
SunilBelow are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this -
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.
AJHi 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 -
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.Raghavanhi 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 -
Cannot reset release strategy for RFQ
Dear SAP gurus,
I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
Best regards,
John.Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
Lakshman -
Source Determination resets the release strategy of the PR
Hi
I am trying to automate the Purchasing Cyle by running ME57 as a batch job along with ME59n for stock items on contract, however when I create the PR and approve it, when ME57 picks this approved PR it assigns the source automatically but removes the approval! I am having the ABAP consultants debug this, however is there something elementary that I have left out?
Regards
Thasmei ReddyCheck if u have release strategy based on vendor - FLIEF. This could be a reason. When u change the vendor or assign a vendor, the release strategy is getting reset .
-
Mass po reset release strategy
i want to know transaction or program or function module name or any other ways for performing
" mass po reset release strategy " , please helpHi Veeru,
You can release the PO's all at once. Please sit with your technical consultant and ask him/her to write the code which takes the inputs of the Release Codes and the indicator Released and pass this information (PO number, Release Code, Release Indicator etc what ever is required) in the BAPI_PO_RELEASE. Some coding needs to be done to do this.
Hope this helps.
Regards,
Saroopya. -
Reset Of Purchase Requisition Release Strategy
Dear Peers,
Release strategy for PR at header level is defined (Overall Release). If we make any changes or add another line item to the same PR, the release strategy is required to get reset to unreleased state. But this is not happening.
Same for PO is valid & working ok
Please suggest
MayankRead this -- With the Changeability indicator, you specify the effects of
changes to a requisition. For example, certain changes may require
a new release strategy to be determined for the requisition.
Via the Value change field, you can cause the release strategy to
be re-started if the value of a purchase requisition item is
increased by more than a certain percentage (e.g. 10%). To do so,
set the Changeability indicator to "4 - Changeable, new release in
case of new strategy or value change" and enter a percentage in the
Value change field.
<b>
The release stra can be reset in one case only and that is whenever you change the reqs which changes teh value of reqs then system will reset the release back to original statu and to do that you have to set the changebility indicatior to 4 and changes 0.1 that means whenever req change and value is changes to .1 % then ystem will reset the req to relase again </b>
Hope this will help you -
Release strategy does not reset after PO change - tried changeability 4 & 6
Hi,
After my PO is released, I change the item quantity/price such that the net PO value (increased) is changed MORE than the tolerance % set in the changeability. I expect that the PO release should be reset but it does not.
However if my PO value is changed (increase) such that my PO value is now in a different "release bracket/range" -- as it falls into a different release strategy, then the release is reset.
Could anyone advise me what is wrong? I tried everything - i tried changeability = 4 and 6. i deleted the whole release class, release strategies and recreated -- nothing.
According to OSS note 493900 below, it should reset when the tolerance % is breached.
I'm on SAP 4.7.
Anyone could advise?
thanks!
3. Question :
Why is the release strategy not reset ?
Answer :
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
case of a purchase requisition and '4' or '6' in case of
another purchasing document (purchase order, request for
quotation, contract, scheduling agreement),
- the document is still subject to the previous release
strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.Hi,
Thanks.
The release strategies are able to be determined correctly when the PO is created so I guess that means its all setup correctly?
The issue is only with PO change - how to cause the reset when the PO value increases by more than the tolerance %.
cheers. -
Resetting of PO Release Strategy
Hi,
I configured all the needed step to activate PO release strategy.
But its not working in scenario whereby a completely release PO should reset thePO amount/qty will be increase after its complete release.
My setting for Release Indicator are below
1- Release, 4- Changeable , no percentage indicated..
Did i missed out anything?
Thanks in advance.
Rgds
SheHi,
I use below characteristic.
CEKKO-BSART
CEKKO-BUKRS
CEKKO-EKGRP
CEKKO-GNETW
still nothing happen even i increase the PO price after its complete release..
i feel i have completed the config needed but still not working fine.. -
Reset Purchaser Order release strategy
Hi All
Does any one knows how to configure the Resetting of Release Strategy when the PO value/amount is reduced? We are in 4.6C, is it standard or are there any settings or transaction code?
Please help.
Thank you
JesielleHi,
Use release indicator '4' or '6" during designing of release strategy.
And
If you want PO release strategy should trigger for reduced value ,then you can for User exit OR modify standard function module which help to reset existing release strategy for reduced/increased and/or values.
For more check the SAP note:493900
Regards,
Biju K
Maybe you are looking for
-
My iPhone 5S says it's disabled and to connect to iTunes, iTunes says it needs 4 digit pass code. I tried to restore it but device wasn't recognised. Any ideas? I only got it yesterday.
-
Hello, I have a question for anyone whom has gotten the XLIFF tranlation working. Per Oracle, they are stating that we need to install language packs for each language we want to use in translation. I was confused as to why, because XLIFF is just usi
-
Determining web item parameters in JavaScript
Hi there Is it possible to determine the parameters of a web item using JavaScript? I know there are commands to SET the parameters in JavaScript, but I need to determine a parameter first, then set it accordingly. Any ideas? Cheers, Andrew
-
I have bought a BT Graphite 1500 - is this a new model?? The main question - can I adjust the volume of the handset for incoming calls? I hope someone can help. Stuart
-
Hello Sorry if this question has already been asked/answered before but I was wondering, how do I change the work space area on Paint and then save it so everytime I go to AppleWorks paint it will be that size? Thank You, Holly