Release strategy triggered

Hi Guys,
We have got an issue from user that he has cretaed the purchase requisition. he has changed the fixed vendor and purchase organization throgh the transaction ME57.
In release strategy, vendor and purchase organisation is not maintained as release strategy parameter.
After saving the PR, it went for approval which it should not be go for approval.
What could be the reason, for triggering the release strategy?
Thanks
Sanjay.

Hi Guys,
I have checked the parameters for release strategy. I have replicated this in mirror server, after changing the vendor in PR, it is not triggring the release strategy, it's working fine.
Please update what cud be the reason?
Thanks
Sanjay

Similar Messages

PR Old Release Strategy - triggering NEW Release strategy any change OLD PR

Dear Gurus,
We have implement item level PR release strategy,
characteristic used: 1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
Please advice
REgards
RS

HI,
If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
Is this is standard behaviour? pleae advice
Regards
RS

Release Strategy Triggered even if the characteric values were not correct.

Hi,
I have configured release strategy based on characteristics
Purchasing group and
Document type
It has 2 release indicators with 3 levels of release.
There are 2 release strategies assigned to same group 01 but have different release codes namely 01,02,03,04
Release Strategy A1has
Doc type NB and Purchasing group 120
Release Strategy A2 has
Doc type ZINT and Purchasing groups 130,131,132,134,135,136,137,138,139
However a strange thing happened.The release strategy was triggered for doc type NB and Purchasing group 190.
This purchasing group is not listed in either of the 2 strategies
Can any one explain why the release strategy got triggered?

That means the old release strategy is not cleraed from the system
do one test
Go to CL30N tocde and enter you release class and class type 032
hit enter
now here enter the value of your char which is in the PO and hit Find in initial class from header
see which release strategy is pulled by the system
here you will see the release strategy and make sure that is not other than what you expect

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

PO Release Strategy - Only for Non MRP generated materials

Hello,
I have a requirement in which any material which was generated via MRP (via PR) should not go through a release strategy at the PO level, but a non MRP generated PR should...
Is this possible at all? I know its possible at the PR level, but not sure at the PO... Would this be a case where we would need to added a field to the CEKKO structure thats for MRP generated PRs ?
Thanks

Hi,
By business any PO created, should follow release procedure as PO a committed document which will further send to vendor.
If you are sure about your requirement, PO created from MRP PR should not follow release strategy, then no need to go for any User Exit.
Just create separate document type for PR (ZMNB) , create separate document type MRP PO( ZMNB) and link MRP PO document type ( ZMNB) with MRP PR document type( ZMNB) in flowing path:
SPRO>MM>Purchasing>Purchase Order>Define Document Types
Now select your ZMNB B Purchase Order Document type and click link purchase requisition document type in Dialog Structure, enter ZMNB Purchase Requisition Document type with a new entry & save.
As you created release characteristics of document type (CEKKO with BSART), then do not keep Value u201CMRP PO document type (ZMNB) u201Cin the release characteristics of document type and design your release strategies.
Now create your PO with MRP PO document type (ZMNB) and see no release strategy triggered.
Regards,
Biju K

New release strategy / Old PReqs

Hi,
New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
Many thanks in advance for your clues.
Regards,
Grzegorz

Hi,
Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

PO release strategy ONLY for change

I have a requirement to only have a release strategy for a purchase order only when it is changed
The problem is that even if I can disable the event to be triggered when created, the release strategy is written down to the EKKO-table when the PO is created meaning that the purchase order still needs to be released before being used for example in MIRO.
How can I avoid having the release strategy written to the EKKO-table when the PO is created?
How can I have it written to the EKKO-table when it is changed?
Good answers will ofcourse be rewarded with points!
Edited by: Snowroller on Feb 11, 2012 4:00 PM

Dear,
Check this and try. Not tested.
Set up Version management for Purchase order and keep all relevant fields of PO relevant for version change.
Add charaecteristics PO_Version value as 00000001. So, When you create PO the version will be 0 so no release strategy. Whenever relevant fields changes the version changes to 0 to 1 and release strategy triggers.
Try this option.
Regards,
Syed Hussain.
Forget to mention please search with 'PO release strategy based on Version Management in SAP' you will get many SDN posts.
Edited by: Syed Hussain on Feb 11, 2012 7:27 PM

P Req. Release Strategy not Transported

Hi,
For Configuring the Purchase Requsition Release Strategy, We have Created Characteristics and Class in the Configuration Development Client. Created Release Groups, Assigned Release Codes with the Release Group, and Assigned Release Group with Release Strategy with Classification. Tested PR Release Strategy for the given Classification Values the Release Strategy triggered.
We have Created same Charateristics and Class in the Testing Development Client (Since the Characteristics and Class are not Transportable). Transported Release Groups, Release Codes and Release Strategy from Configuration Development Client to Testing Development Client. When we check the Release Strategy Classification in the Testing Developmemnt Client, system showing Classification Error.
Please let us know whether the Release Strategy Classification Requests are Transportable or not.
Ravi

Dear Ravi,
The Release Strategy Configurations can be transported, in respect to the requests transported.
But the assignment of the Characteristic Values to the respective classes needs to be done in respective destination clients. Since teh assignment will get transported.
To Do the same, please use transaction CL24N, Enter the classes Used in your release strategy and assign the respective Characteristics Values.
Hope this will serve the need.
Njoy SAP
- Regards,
Saravanaganesh

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.

PO release strategy not triggered after PO printout

Hi Experts,
I have configured PO release strategy and have given 10% tolerance to PO value.
When I change PO value (more than 10%) after releasing the PO, but before taking Print out of PO, the system triggers new release strategy.
But when I change the PO value (More than 10%) after taking PO print out, system do not trigger the new release strategy.
I want the system to trigger new release strategy after PO print out (if its going beyond the tolerance).
Please help.
regards,
Anand

Hi Anand,
you cannot reset the release once the PO is printed.
When the purchase order is printed/faxed the vendor will deliver the goods. Therefore it would make no sense if the system resets the strategy.
Please ensure that changeability of the release indicator should be 5 or 6.
Sanjeev

Release strategy not getting triggered.

Hello,
As per the client request, new Purchase group had to be added to the existing release strategy.
I had added the purchase group in the edit characteristics and in the release strategies: classification.
But now the the release strategy is not getting triggerred.
In CL20n I see that the, status is marked 3 i.e incomplete. The reason to this is not known as customizing done is correct.
In OMGSCK i see that no errors are found with the release strategy.
Please suggest.
Regards,
Neetha

hi,
Sometimes the strategies are taken after restarting the sap system...there has been one same situation before also..at that time the same strategy started working after restarting the sap system...
pls check it may be the same issue with you also..
Regards
Priyanka.P

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

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 triggered in PO

Release Strategy not triggered in PO and also in PR. Release Strategy stimulation is working fine but release tab is not coming in Po and also Pr.
What step I have to do after release strategy stimulation.
Regards
cns

Hi,
Unless you provides details, difficult to suggest an answer.
What are release criteria's you selected for PO and PR release strategy?
What are the release characteristics you have for PO and PR release procedure?
If you configure perfectly the PO and PR release strategy, did you transfers the "Vital Release Values" with your release strategy with release group and release class.
Refer few threads , may help full to you!
http://scn.sap.com/thread/1973324
http://scn.sap.com/thread/3212400
Also refer SCN wikiblog
https://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards,
Biju K

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

Release strategy triggered

Similar Messages

Maybe you are looking for