PR Rel Strategy scenario

Hello
I have 2 requirements in PR Rel Strategy scenario.
1.No changes should be allowed in the PR once the PO is created.Can we fulfill this requirement by assigning changeability Indicator 1.
2.Once the PR is released and PO created it should not allow to revoke the release.
Any ideas on this?
Regards
Vaibhav Mahajan

Hello Afshad and Swaminathan
Users are revoking the release after the PO is created.With changeability indicator no changes are possible via ME52N but revoke is possible in ME54N.
Bases on the links given by Afshad I am checking if we can use the User Exit but not sure which user exit will work.
Regards
Thanks for the suggestions.

Similar Messages

Po rel. strategy

Hi,
In p.o rel. strategy we have the three stage release status. First A( say) will rel. then B then C. we have released lot of p.o in the same manner. Now we want to change the rel.status to two step. That means A will release then B will rel.the document as the final rel. authority. But in the previous P.O created which was subject to three stage rel. status has been already reduced to two stage. Where is the setting so that it will not effect the old p.o rel. strategy procedure.

Hi,
For this you have to create two release strategies as given below:
1. For old PO's
Add a new characterstic (Say DOCUMENT_DATE) to the old 3 level release strategy having value as before today's date (i.e. <13.06.2011 ).
2. For new PO's
Add a new characterstic (Say DOCUMENT_DATE) to the new 2 level release strategy having value as on & after today's date (i.e. >= 13.06.2011). Rest all the characteristics will be same as the old 3 level release rstrategy.
The characterstic DOCUMENT_DATE will have Table name as CEKKO & Field name as BEDAT (i.e. PO creation date).
So, For Example if you will go for making any changes to PO created before today's date will pick the same old 3 level strategy however for creation or changes to PO's having creation date today onwards will pick the new 2 level release strategy.

Rel.strategy

Dear cons
We have created one user I.D (procurement) for creation of purchase requisition. One person is only able to approve the document. We have created another I.D for finance deptt. For thr Pur. Doc.we want both person can approve the document. i.e- first fi ance deptt. Will approve then procurement deptt. Will approve. Because at the time of creation P.R the purchase deptt. Enters a wrong G/L account. To avoid this first it will come to finance deptt. So how can you make settings in the release strategy. If I create two release code & enter in the rel. strategy of procurement I.d Then How it will come to finance i.d. pl.look into the matter. Without workflow it is possible or not.. Basis people has restricted the user i.d.pl. give some hints.

Hi Nirupama,
Create the 2 release codes for that Release strategy.First release code should be for Finance dept 2nd should be pur dept user.
Give the authorization to 2 user ids with release codes one for Finance dept and another for Pur dept with the help of Basis Consultant.
Once the Pur dept user creates the Pur requisition.In the PR release tab the 2 release codes will appear . Then the first release code should be Finance dept user. Then final release can be Pur dept user.
So that before releasing the PR the finance dept user will correct the G/L account and then release the PR. Then the Pur dept user will finally release the PR for procurement.
Hope you understand
rgds
Chidanand

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
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 most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

Planning Strategy Scenario

We have a pretty straightforward scenario here. Production for the FG is sales order driven, while the Semi-finished products are driven by the sales order re/quirements. What are the best planning strategies used for the FG, the SFS, and even the raw materials?

Hi,
For this requirement:
Planning Stratgy can be used is 20 (Make to Order).
It is not required to input any strategy for SFG & ROH.
These will pic the strategy from the Header Materail i.e FERT.
Revert for further discussion..
Regards,
Siva

Strategy scenario

Dear Guru's
For a particular material I want to do MTO & MTS scenario.
What r all the settings i have to do?
Kindly do the needful.
Helping hands will be appreciated by points.
Arul.

For MTO we have to use strategy 20
For MTS we have to use strategy 10 (or)40
We have to mantain the strategy in MRP 3 view ,and that to for the finished material.
Order types should be defined seperately for MTS and MTO.
Sales view should be mantained and the item category for MTS and MTO differs.
With respect to costing ,settlement rules should be defined.

Contract rel strategy

Gurus,
I have congfig Con rel stg.I rel it.Then i go & change the qty & value.The sys prompts a msg,rel liable to be rest.But when i go try to rel again,the sytem says no suitable documents found.

hi,
check for the release strategy set up options ie, under release indicator settings...
here set the changability option and for fine tuning changebility % value for your release ID....
You can use option 4 or 6 depending whether you want to see relevent changes with regards to output or not...
Regards
Priyanka.P

Rel. strategy is not triggered while creation of PR with cost centr

Hi Gurus,
While creation of PR release strategy is not getting triggered with cost centre BCWSV870. But release strategy of PR triggered for cost centre BCWSV852 (In PR changed only cost centre as BCWSV852 instead of BCWSV870). Both cost centres are similar and the both cost centres are exist in characteristics value in CL20N for the same release strategy.
My question is why for one cost centre triggers release strategy triggers and for other cost centre release strategy is not triggered. Can you please tell how come this and rewarded for answer this.
With regards,
C. Sundar Rajan

Hi,
In regard to problematic PR with cost center BCWSV870, was your PR maintained with only one line item? or multiple line items?. In additions, when defining cost center as part of the release strategy structure, did you enter all cost centers with leading zeros? Tak a further look into OSS Note 365604 for your further investigation.
Cheers,
HT

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.

Problem in rel.strategy

I created two doc. Type for P.R. i.e- zno1, zno2. I have one user i.d- MMCONS. For releasing P.R Document (ZNO1) we have rel code-01 & for releasing P.R Document (ZNO2) WE HAVE REL. CODE -02.WE HAVE CREATED CHARACTERSTICS FOR DOCUMENT TYPE, PLANT & USER I.D. Is it possible to give authorization in one user i.d. to release the different doc. type P.R in a single user I.D.waiting for your early response.
nrk

Hi
Try with assigning release code 01 and 02 to same user in authorization
Vishal...

Release strategy:ME53N : Older PR documents shows, modified PR rel.strategy

Hi Friends
We have updated the sequence of release codes for certain PR release strategies. But when we moved the changes production, i observe that all the older PR documents (Which were released last year and completed) also shows the updated release strategy in transaction ME52N/ME53N.
Can someone pls some explain? Is this normal?
SAP doesnt store the release strategy and its sequence of release codes, which were determined at the time of document creation?
Thanks for your help...Raj

Hi,
There is no change in the older documents.
The documents are older by few years.
I have checked few documents randomly, the tcode ME53N shows only the updated release strategy.
I did some investigation today on this.
i think system will not keep the release strategy pertaining to document creation.
It will just store Release Group and Release strategy in the Purchase Requisition tables (like EBAN).
And when ever we try to display the document it will go and read the release strategy sequence from relevant tables.
Hope someone helps to validate if my investigation is correct.
Good day..

Rel strategy for PR

I want to create Release Strategy for PR as follows:
For Standard PR (NB) one level of release is always required.
(eg HOD will have to release all the PRs of a department)
How shall I proceed pleae guide in detail.
regards
VS

Hi,
Release Process for PR is as below
1 Create the Characteristics for your release strategy based on fields of table CEBAN.
2 Create a class of class type 032. You have a free choice of names for the new class
3. Assign your characteristics to the class on the tab page Characteristics.
4. Create Release Groups
5. Create Release Code -HOD in your case
6. Create Release indicator -all type of PR or selective
7. Define Release prerequisites
Hope you will explore after this overview on RS.
Regards,
Ashish

PR rel strategy

I want to create Release Strategy for PR as follows:
For Standard PR (NB) one level of release is always required.
(eg HOD will have to release all the PRs of a department)
How shall I proceed pleae guide in detail.
regards
VS

Hi
I have created a release procedure for PR by maintaining 4 levels. Have made all the necessary conf. in SPRO & then trying to release the PR in ME54N. But iam unable to release it as iam getting an error
Pr No1 can't be released & Msg # MEPO822.
pls. i neeed a solution for this.
shouldn't i select 4 levels to approve a standard PR
Vineeth

Issue while configuring PO Rel Strategy with more than 17 rel conditions

Hi all,
I am trying to change a PO Rel startegy which has 8 release codes and about 25+ different release conditions already defined. When I am trying change the release status configuration tab I can only see upto 17 conditions. I don't see any work flow activation and I am not sure how intially they maintained all these conditions. Please let me know how to over come this issue.
Thank you for your time,
Srav

Hi all,
I am trying to change a PO Rel startegy which has 8 release codes and about 25+ different release conditions already defined. When I am trying change the release status configuration tab I can only see upto 17 conditions. I don't see any work flow activation and I am not sure how intially they maintained all these conditions. Please let me know how to over come this issue.
Thank you for your time,
Srav

Workflow for PO Release Strategy

Hi all Workflow experts
We are on ECC 6.0. We have created a 3 level Rel strategy PO and are creating the workflow for this scenario.
The business object we are using is BUS2012 and WF Template is WS20000075.
Each time a PO is created/changed workitem will be sent order we have defined, ie. L1, L2,L3. Each time mail goes to the inbox of the concerned approver.
The problem is when the final approver cancels the release. Under activity 'Release of PO canceled, Task TS20000167 we have assigned the agent as Originator of PO. However at this instant mail does not go into the originator's mailbox.
Approver is cancelling the release in ME28 as it should be, I presume.
Are we missing something here? Is there any additional settings required to trigger the mail to the originator?
I would be happy if the responses from you all does not point to SAP .htm files! since I have already gone through them but it is very hard to understand some simple things!
Thanks in advance.
Regards,
Raghu

All,
I gather that ver 4.7 onwards, SAP has supported the PO rejection/cancellation feature. Since I am working on client's server which is 4.6 c I am not able to implement this. Unfortunately, in the process of doing R&D within the sandbox I seem to have damaged the template WS000075. Now I am getting an error message at the first approval level saying "relase written to buffer".
Can anyone tell me what does this mean? Also is there a way to retrive the original template form the development clients?
Regards,
raghu

PR Rel Strategy scenario

Similar Messages

Maybe you are looking for