Reject a Collectivly PR' S from Release strategy

Dear All,
How to reject a Collectivly PR' S from Release strategy.
Regards
Aamir

The line items may be approved collectively as a whole or individually, but, each line item must be rejected individually.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/75/ee14d755c811d189900000e8322d00/frameset.htm

Similar Messages

Reject a po from release strategy in workflow

Hi all,
For Purchasing document Release strategy, if a purchase order is rejected by the approver then it should go back to the originator of the document.
I am trying for this scenario for that my configuration is
     Business object is Bus2012
     Workflow template is WS 20000075
In this configuration, I used the originator name in activity (Release of purchase order cancelled )& under this activity I am using the task is TS20000167
But after configure this all thing I am not able to get mail inside the originator mail box
I want to know following thing
     How approver can reject the po
     What setting we can do for getting the mail inside the originator mail box
Regards
Giridhar

Hi Rick,
Thanks for the comments. Below is our actual scenario:
When we did the setup, we did the following:
1. Create a release code
2. Create a position
3. Attach the release code to the position
4. Create a role
5. Attach the position to the role
6. Attach the role to users A and B
When user A resigned, we did the following:
1. Deactivate user A and put "Valid Up to" date.
   We even removed his email address from his account
2. Detach the role from user A
After which, notifications are still being sent to this deactivated users. The said notifications are actually those that happened before he left and this is what Im trying to solve. This is creating too much records in SOST and the system is sending the same notifications over and over.
Do you have any suggestions how to solve this?
Thanks

Release Strategy for contracts.

Hi gurus,
Good day,.
Please help on this.
We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
Example.
Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
Thank you.

Dear Acel,
The example you given was working just fine and correct.
a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
-> The release strategy will only be reset if the total net value for the contract was higher the previous
value but not lower.
As your example, quantity was updated to 1200, then it will reset when changing from 1000
to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
In system, it always assume if you had approved for the total value of the higher 1 before, then
it should be fine for the lower total net value for your management and therefore not need to re-approve
again for redundancy job. This was very logic in common business scenario in many companies.
However, like in your example , if you had define a different release strategy for a value that met the
the 1100 quantity, it will redermine the different release strategy. For example:
USD 1 for every quantity = 1
Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
USD 1200 for quantity = 1200.
Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
Release strategy C for 1200 , characteristics from USD 1200 onwards
Then if you change the quantity from 1200 to 1100, it will redetermine the release
strategy B which means from Release strategy C to Release strategy B. If you
only had Release strategy C that had a characteristics from 1000-1200, then
it will keep the Release strategy C as released and it won't be reset unless
if you had change it and the condition of the total net value was higher than any value
before.
Hope this will explain the logic.
Ian Wong

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

Re-set release strategy of rejected PO,after doing respective changes to po

Hi friends,
I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...
Here PO printout is possible only after the final approval...
Pls give some inputs in fixing this issue..
Thanks in advance....
Regards
Shashidhar...

Hi
What are the characteristics of your strategy?
Try to change one of them save and then rechange it to the original
eg.
If the strategy depends for example on the Purchasing Group (PG)
i mean according to different PG's different strategies working
then with ME22N change the PG save and rechange it again to the original.
or
for example If the strategy depends on Materail Groups (MG)
then do the change with MG
With ME22N change the MG save and rechange it again to the original.
I guess this will trigger the strategy again.
Hope it helps
Best Regards

SES Release Strategy not invoked in Backend from SRM confirmation posting

Hi,
I have configured a SES release strategy based on vendor number in R/3. When a SES is created in R/3 via ML81N the release strategy is invoked as expected. However, when a confirmation is entered in SRM for that vendor, the SES that is created in the backend system is created in accepted status and the release strategy is not invoked.
Can anyone advise how to get this to work the same way as ML81N?
I would expect that the SES would be created in the backend from the confirmation without acceptance and the release procedure to be the same as ML81N.
thanks,
Michelle.

Hi,
The SRM confirmation in EBP is the goods receipt(MIGO) and not the service entry sheet entry (ML81N) as we do in Materials management.
As per my understanding there is no provision of service entry sheet entry in SRM 5.0 as of now and SRM 7.0 has this option coming up :
In SRM 7.0 ,
"Supplier-maintained confirmation (service entry sheet) for services performed based on the service items within a purchase order
Confirmation supporting hierarchical structure of service items"
are added.
Look for this information in the thread which speaks about SRM 7.0
Re: Benefits of upgrading to SAP SRM 2007
which gives the info in slide 11, Delta SRM 7.0, Service procurement -2
Best regards,
Sridhar.

Release strategy for PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

In release strategy unrelease should happen from higher level

Dear Users,
In our release strategy we want to make changes like whenever user want to unrelease it should happen from higher hierarchy to bottom level as vice versa of release process. If there is any solution for this process please provide your suggestions.
Thanks,
Manoj

Hi,
For restriction from higher hierarchy to bottom level, refer similar blog
Release Strategy: Restrict lower users to revoke PO after the complete release by superior
Regards,
Biju K

Need to activate release strategy for PR from PS(a/c assignment N)

Dear experts,
I need to establish release strategy in PR raised from Project System. PR account assignment in 'N'= network. PR will be differentiated PR value wise . Please help in this regards,
Thank you.
Kind regards,
Zusen

Hi
You already have account assignment category (KNTTP) in communication structure CEBAN. You can use it to define your release strategy. If you wan to use field which is not there in CEBAN then you need to append CEBAN with the help of apaper.
Use this link as an example for release procedure and create your own with KNTTP.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Release Strategy for reservation created from PM and PS

Dear All,
How to configure the release strategy for reservation generated from PM and PS.
Regards,
Atanu

do you talk about release strategie for requisitions, or really reservations?

Removal of plant from P/R release strategy of another plant

Dear Friends,
In our office there are two plants P068 & P281 both belongs to two separate co codes. In its P/r release strategy in characteristics plants are mentioned so for each plant their should be separate p/r as they are located differently. But unfortunately plant P281 is added in the release strategy of plant P068 though there is a separate release strategy configured for plant P281. So while making P/r of plant P281 release strategy of plant P068 is getting called & the user is not able to release the same because of the restricted authorizations. We have tried to remove the plant P281for which we created the request on DEV server & transported to PRD server but this is not removed. It is still reflecting in P068 P/r release strategy. Kindly advise how we can remove this ? Is their any other alternative way?
Rgds
Prashant B

You need to remove the plant from classification of release strategy. If system is modifiable, go into release strategy and classification and uncheck the plant, which is not required and save.
OR
If backend is unmodifiable, use this t-code CL20n/CL24n, put in the release code strategy combination and in the classification remove the plant of it and then save and your problem will be solved.
Follow the above steps for adding the plant to new release strategy as well.
Edited by: Afshad Irani on Apr 28, 2010 4:45 PM

Release Strategy ME53N - Approver rejection

Dear all,
I would like to generate a change history report based on approvers choice on Release Strategy in ME53N. The thing is I can't find any table where rejections are stored when a approver doen't release a PR.
I know that in CDPOS I can find wich ones were released, but what about when it is rejected?
I would appreciate any help.
Thanks in advance,
Alm.

Thanks again, Eddy.
Not yet what I'm looking for, here is an example:
Consider a PR XXXX with the Release Strategy flow - CG-F3-FM.
In ME53N we can see:
CG - Green Check Icon (approver released)
F3 - Green Check Icon (approver released)
FM - Yellow Icon (Waiting Approval) However I know this approver has rejected the PR in the past, but the System only shows that this approval is pending - the system does not inform the existing rejection.
Where to find that behind this yellow icon there is already one rejection?
Thanks in advance.

Release Strategy Rejection with Note

Hi friends.
Is it possibel to reject Release strategy for PO adn PR with Remarks for rejection. If so please explaing me.
Thanks and regrds
Madhavan

Hello,
It possibel to reject PO and PR with Remarks for rejection with the help of workflow.
If you are not using work flow then you can use the Header text in PO and Pr for the same so that Creator knows the reason for the same.
Regards,
Shailesh Mackwan

Accessing Release Strategy defintion from outside SAP

Hi !
I'm trying to integrate SAP MM with other 3rd party application. We want to access and read SAP's release strategy definitions and also document classes, to avoid having to maintain that information from the 3rd party too.
Is there any standard approach to access this info ? a BAPI maybe ? or do we have to access the data tables from a custom made RFC that reads specific tables ?
Thanks.
Regards,
Matias

Hi Rajoo,
As per I know, in standard sap, you can achieve this requirement.
Just make sure you have the characteristic for Total net value (CEKKO-GNETW) , and maintain the currency to USD. As long as you have USD to INR conversion in OB08, the system will able to fetch the correct release strategy for the PO based on the amount you set in the Release strategy.
Regards,
w1n

How to Reject RFQ (Release Strategy)

Hi,
In ME29N , we have facility to Reject / Approve a Purchase order in Release staretgy tab .... but how to reject a RFQ .
There is no option available in ME45 to Reject a RFQ, only we can release it.
Need your help
REGARDS
SHREY

hi
rejection of rfq is not possible
ru talking of calcelling or reversing the release
if yes
then in me45 select therel code then belowt that tick on cancel release
execute ,select ur po and click on cancel release
regards
kunal

Reject a Collectivly PR' S from Release strategy

Similar Messages

Maybe you are looking for