Regarding:PR Release strategy

Dear SAP Gurus.
I created below charecterstics.
PR_RELEASE_TOTAL_PR_VALUE
PR_RELEASE_PURORGANISATION
PR_RELEASE_PURCHASING_GROUP
PR_RELEASE_PLANT
PR_RELEASE_ITEMCATEGORY
PR_RELEASE_DOCUMENTTYPE
PR_RELEASE_CREATIONINDICATOR
and linked that all as characterstic in Class PR_RELEASE_TOTAL.
but while doing Set Up Procedure with Classification for Release Groups
Below information message came
Please check release classes (see long text)
Message no. ME492
Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
Procedure
Assign the release groups that were created for overall release to one release class only. Assign the release groups that were not created for overall release to a different release class.
Example:
Rel. group Rel. obj. Overall rel.    Class       Description
01 1 _   FRG_EBAN      Group 01
02 1 _   FRG_EBAN      Group 02
S1 1 X   FRG_GF_EBAN Group S1
S2 1 X   FRG_GF_EBAN Group S2
Please help me out to correct this.
With Regards
MK

Hi Mukul,
What this means is, that for a particular Group, that you have, you can have only one class for the release groups( Its is a technical Limitation), for P.R which have item wise release as well as overall release, we can have two different groups.
Kindly check in the configuration of groups, what is the class used, you would then need to add all the characteristics that you have created, to that class, then it will work fine.
Please let me know if you come across any issues.
Would be glad to help
Regards
Shailesh
Edited by: Shailesh Rajan on Jul 8, 2011 3:01 PM

Similar Messages

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.

Release strategy modification

Hi all,
I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document & 2. Purchasing Group .
Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
Please help! How can I achieve this...
Thanks,
Rajan U

Hi,
As needed, you created one more charterictics CEBAN - CFWRT and included it in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
1. <= 5000 INR
2. > 5000 INR
Craete release group as PO and create two release codes C1 & C2.
Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
Regards,
Biju K

Purchase Order Release strategy revoke when Delivery Comp indicator Ticked

Dear Experts,
There is PO for 100.Release strategy is activated for PO.PO is released.
Inbound Delivery for 100 was done .after which for 70 Goods reciept was done.
Then User wanted to Short close as no more quantiy is going to come.
So user went to ME22n and Done Delivey completed indicator was ticked which can be done Without Re-Release.
But When i am seeing the Log of PO (Both Header and Item Changes) The Release strategy is again Getting Revoked,
And going to Release again.
What should i do for not revoking Release strategy.And Also Price is getting Changed.
with regards,
GMP

hi,
Release strategy is revoked via release indicator settings done via settings up the release strategy...
If you don't want any revoke even if any field is changed then used the changebility as '1'...
Also as per std sap settings, once you make changes to com. indicator in PO, system will revoke the release again...
so, decide and make settings as you need...
Regards
Priyanka.P

Contract Release Strategy - Adding New Line

I have a question regarding Contract Release Strategy - How can i force a release reset if a new line is added to the contract. I dont see a field in CEKKO - Any suggestions?

Hi
Version mangement is activated with Version Zero only. When you select Version 0 Ok
If you have selected this indicator, version '0', which is generated automatically when a purchase requisition or external purchasing document is created, is automatically flagged by the system as Completed.
If version '0' is completed automatically, the system does not check whether the version data includes any mandatory fields.
If you have not selected the indicator, version '0' must be manually flagged as Completed.
Only if this indicator has been selected for the current version:
Can a requisition be converted into a PO (for example)
Does the release procedure commence
Thanks & Regards
Kishore

Release Strategy for Sales Order-IMP

Hi Gurus,
I want to know regarding <b>Release Strategy for sales orders</b>. I want to know the detailed step-wise procedure for SO and not for PO. My understanding is that standard SAP does not support Release Strategy for SO in SD Module. Please l want the following queries to be answered
1) Is my understanding on Release Strategy for SO correct as mentioned above?
2) What are the other alternatives and the steps of configuration step-wise.?
Kindly help me post this information as it is required urgently. Suitable full Reward Points will be given to all answers.
Many Thanks,
Pankaj Mishra
E-Mail : [email protected]

Pankaj,
There is no release strategy for sales order.
You can try it doing Authorisation /Status profile with your BASIS person...
REWARD IF U FINDS THIS AS USEFUL...
Regds
MM

Regarding Purchase Order Release Strategy

Dear SDNers,
I want to create a worfklow for PO release strategy.
For this to take events for BO, I swich on the evnet trace at swels.
After creation of PO, BUS2012 - RELEASESTEPCREATED even triggered.
For release the PO, BUS2012- RELEASESTEPCREATED,RELEASED two events were triggered.
But when I change PO, BUS2011 - CREATED_VIA_SPEC2000_MESSAGE event triggered.
No change event for BUS2012. I checked at SWEC. Radio button On change is selected for BUS2012-CHAGE event
Even though its not triggered. What might be the problem?
Thanks in advance,
Regards,
Amarnath S

Hello Venkat,
Did you checked SWE2 entry. If not, please check if for BUS2012 SIGNIFICANtLYCHANGED event is maintained for your WF template and is active or not.
Also check in SWE3, for event SIGNIFICANtLYCHANGED and object type BUS2012, please check if receiver type is WORKITEM.
Note - Whenevr you changed any PO there will be event related to chnaged document maintained in swec and SWE3.
Rewards will be appreciated.

Regarding overall purchase requisition release strategy

Hi,
For following combination PR release strategy is not working.
1.Total value of requisition
2.Purchasing Organization
3.Name of Requisitioner/Requeste
But when we take any one of them it is working. But when I tried to put together, these field system is not picking any release strategy.
What would be the reason? is there any inter connection between these fields?
Regards,

Dear Aj,
Chek is theare any other release strategy in the syestem wth mentioned chraterstic,
also chek all chraterstic are ticked in the release strategy?
Some time syestem is not able to find the unique release strategy,
Please let me know

Regarding Release strategy - Approver on vacation

Hi ..
This is regarding Release Strategy ..
We don't have work flow configured now. can you please suggest for below
1. If a Person responsible for a role [release code] is on vacation, how we pass this authorization to alternative person
2. i believe without work flow there will be no way that we can notify approver
Thanks

You can assign the Role/Profile containing the authorisation on a time limited basis to the person who covers for the person on holiday.
It's not particularly efficient to have to continue doing this though so I'd suggest doing it on a permanent basis.
Regards,
Nick

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

PO Release strategy

Hi,
I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
Any suggestions are highly appreciated to fix this issue.
Regards
Sudhakar

Hello,
After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
regards
anand

Release strategy for quantity contract

Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbu

Hi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT

Contract & PO Release Strategy

Hi All,
We are in the process of designing the release strategy for contract and PO. I would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
The release conditions for Contract required are
1)Porg
2)Pgroup
3) Value
Also, for quantity contract how can we make the release strategy trigger based on value.
The release conditions for PO required are
1)Porg
2)Pgroup
3)Material Group
4)Value
The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
Request your help.
Regards,
Kannan

Hi Kannan
Yes your requirement is possible...
While creating Charectristics in CT04 for External Purchase Documents...Create one more Value for your Document Category...ie) Table as :CEKKO and Field as BSTYP and choose the Purchase Doc. Category values K and F.
Then create Charecteris for CEKKO - EKORG, CEKKO - EKGRP and CEKKO - GNETW, CEKKO- MATKL... and assign these all 4 Chareteristices in your release class.
And Configure your release statergy according to your requirement...
Reward if useful
Regards
S.Baskaran

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

Release strategy reversal for the purchase requisition.

Hi all,
I have a scenario were we have three release levels to release the PR through ME54N tcode.
After all the levels are released,If at the first level the PR release is cancelled all other levels are automatically cancelled.
Now my concern is until the 3rd release cancellation is done, 2nd and 1st level should not be allowed to cancel the release of PR. and until 3rd & 2nd release cancelltion is done, 1st level should not be allowed to cancell the release of PR.
Please Let me know if any BADI or any enhancement is available to acheive this back release strategy for PR.
Regards,
Kumar
Edited by: kumar g on Jul 16, 2009 6:21 AM

-

Regarding:PR Release strategy

Similar Messages

Maybe you are looking for