PR status as Active - after implementing Release Strategy

Dear Gurus,
We have implemented PR release Strategy and it work fine extacly, we are using material group as one of characteristic to trigger release strategy.
if user or through MRP route, the Material group is not corrrect, the PR is created with Status as "ACTIVE" and PR can be processed for RFQ and PO. How to stop this, Please advice
Thanks
RS

1- Create Rel Grp ZZ with description Strategy Error.
2-Create Rel CodeZX with description Error .
3-Create Rel Strategy ZF with description Forbidden Strategy.
4-Maintain material group characteristic in classification if it is blank then release status not released.

Similar Messages

PR to be deleted after PO release strategy with pr.

Hi,expert some pr to be deleted as release strategy already trigered as well as po had been done.
Pls help.Any suggestion?

Hi,
You can use transaction SARA with the archiving object MM_EBAN.
You can follow the instructions from help.sap.com:
http://help.sap.com/saphelp_46c/helpdata/en/8d/3e5c48462a11d189000000e8323d3a/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/8d/3e4f1d462a11d189000000e8323d3a/frameset.htm
Best Regards,
Arminda Jack

PO status if you change the release strategy procedure

What will happen to the half released PO/PRS if we change the release strategy?

Hi,
It won't Happen for Half release PO Document. The rerelase will get affect once the final release done or No release initiated to the document.
SAM

Why is inventory count Doc's status still active after posting difference

Thanks,
Linda

Sounds like inventory management.. I found document is still active through MI02 after I am done with posting difference through MI20.
Here is what I did,
MI31 create inventory count sheet (100000207)for warehouse
M104 Enter inventory count
Mi11 recount for some items in 100000207
Mi20 post difference
Question: why 100000207 is still active since I alreay completed posting difference? Now the only option I have to deactive is to delete it, however when I am trying to do so, system give me a warning sign saying deletion will errase the evidence to posting difference. Is there any steps I missed so 10000207 is still active?
thanks,
Linda
Edited by: LindaSAP on Dec 2, 2009 5:00 PM

After Creation of PO Release strategy is missing

Hi Experts,
We have a problem that we have created a PO but we found after that release strategy is getting missed out.
What could be the possible causes for this?
Note: We have checked in CL20N everything seems to be in place.
Cheers,Kumar.S///

Hi Jurgen,
Very sorry for the late reply as i was not in office.
I have checked the following char in CL20N transaction,
Plant,Purchasing group,order type,total net order value,Purchase organisation,Vendor account group.
This is FYI.
Please reply ASAP.
Cheers,Kumar.S///

Precautions to be taken before going for new PR Release strategy

Dear all,
We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
Need your advice on
1)If we go for new release strategy as off with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
3)Any other which I missed out, please suggest me
Thanks
RS

Hi,
It is better to release all existing PRs using your current procedure without classificaton and clean up.
If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
REgards
Ram
Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

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

Request is active after all the records loaded

Dear Experts,
I am extracting data from R/3 through custom Data source. While creating data source, I used custom Function Module.
I have checked in RSA3, 9565 Records are available.
When I start extract from BW side all the records (9565) fetched, but request still in yellow. Same way I have checked in R/3 side in SM37 job status is Active (After 5 Hours also).
Please provide the solution.
Thanks in Advance.
Regards,
Selva

hi,
in the monitor screen select that requestselect refresh request for 1 more 2 minutes. otherwise come out the screenwait for some time-go to that request check it out.
select your requestselect details tabsee error.
if helpful provide reward points
regards
harikrishna N

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

Release strategy for auto created PO's

Hi Guys,
I have a requirement to implement release strategy for automatically created PO's.
PR's are created automatically and we have a program which create PO's automatically.
we would want to release them before generating output to vendor.
could anyone please have any inputs here.
regards
mittu

Hi!
You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
Hope this helps! =)

New po release strategy

hi,
i am having xxxxx class for po release strategy with 3 characteristics-(plant, po value and document type)
now i want to have only 2 characteristics with document type and PO value.
again i want to use new release codes for my new strategy, keeping the same class for release strategy.
can i define new release strategy using the new codes?, then what shall be the impact of the same on below
1. already released PO, now want to amend,(after new release strategy implimented)- what would be the effect on PO?? which release codes shall hit the same?
2. already release PO(i understand there wont be a problem in GR, as release ia already effected)
3. new PO shall catch the new strategy- no problem with the same.
for implimenting the new strategy using the same class, can i delete the old release strategy with codes or i just need to remove the value mentioned in the classification view of the release proceedure.

thank u.
my point is while re-defining the release proceedure.
earlier i had 150 release strategies and arround 40-50 release codes. now only 12 release codes
i just need to get confirm, if i create a new release code and assign a new release strategy using the same class(only deleting the plant characteristics), what will happen to old po(released) for which now we are amending.
i assume i need to delete/remove all the data of old release strategy available in classification view, and keeping the release codes as it is in release pre-requisites fr old release strategy.
or just any body briefe me what are all the condition for changing the exsiting release strategy.if i need to create new release code,release strategy by using the same release class.

Authorization roles for release strategy FRGSX

Hi guys,
we are using R/3 4.7. We are going to implement release strategy for Purchase orders in our company .
We have customized different release groups, for several release strategies and release codes, without implementing any workflow.
We have a problem on authorization roles because we assigned for each combination of release group and release code a authorization role but it is not sufficient to restrict the role for users because we don't take into consideration the release strategy.
We had a look on the system but we didn't find any object related to release strategy (techical name FRGSX).
Could you someone help me?
Thanks in advance
Vir

When assigning user authorization for PO release strategy each user is assigned to release group and release code. You cannot make a connection between specific release strategy to user.
Pay attention that the authorization needed are also for change PO (ME22N) - meaning you can limit the users by all the authorization values of the ME22N objects.
Use t.code SU24 to explore what auth. are checked in each transaction.
Nir

Old PR release strategy - release completed status change

Dear Gurus,
We have impletemented Item level release strategy for PR.
There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
Please advice
Regards
RS

Hi,
Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
Check the value of Changeability of purchasing document during/after release ( 1 - 6).
Choose the appropriate value based on your req.
Regards,
Udayasankar Rajagopalan
Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

Overall Purchase requisition Release strategy : Changed after Rejected

Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.

Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev

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

PR status as Active - after implementing Release Strategy

Similar Messages

Maybe you are looking for