Release strategy related

Hi Experts
We were using release strategy w/o classification. Now we want to change to with classification.
I have done all the settings with overall po value taking CEBAN- GFWRT & assigning the same in the class. In the simulation it is working fine. When i go to actual pr it is not working.
Do I have to remove all entries in W/O classification
Regards

hi
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
For requisitions, you can use either the release procedure WITHOUT
classification (procedure 1) or the one WITH classification (procedure
2). Procedure 2 gives you considerably more flexibility in determining
the strategy.
If you have previously worked with procedure 1, for example, but now
wish to switch to procedure 2, you must at least define the release
group for procedure 2. As soon as you have saved this, procedure 2 is
active. If you wish to work with procedure 1 again, it is enough to
delete the release group.
hope it help
regards
kunal

Similar Messages

Error relate to PO Release Strategy

Hi expert,
I have a problem relate to PO release strategy. I try some of suggestions but nothing work. I hope you guy can help me to fix it.
I have finished configuring PO Release Strategy and Release Group is ZT with 2 release code (01, 02).
After that i created some of other release groups and delete the first release group ZT (include release strategy). But whenever when i go to ME29N, ZT always appear in release group with it's release strategy even i already deleted it.
Thanks for your help

Hi,
What procedure did you follow while deleting the release group ? The process for release group deletion should be as mentioned below.
1. First delete the classification data for the release strategies you want to delete
2. Delete release strategies ( from detail view in SPRO )
3. Then delete release codes ( including description in different languages - translation )
5. Lastly delete release groups ( including description in different languages - translation )
If you dont follow the above process inconsistency might be there.
After deletion if you want to create new release groups follow the steps in reverse reverse order.
1. Create Release group ( including description in different languages - translation ) Check table - T16FG
2. Create Release Codes ( including description in different languages - translation ) - Check table - T16FC/T16FD
3. Create Release Strategies ( ( including description in different languages - translation ) - Check table - T16FS/T16FT
- Assign codes to Release Strategies
4. Maintain classification values - Tocode CL20N
Please let me know ifyou need any further help.
Regards
Sayan
Edited by: Sayan Pal on Dec 8, 2011 3:28 AM

Relation between Version and Release Strategy at Purchase Order level

Our requirement is as follows:-
Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
Price-A can be equal to Price- B, Less than or greated than.
I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
and when i delete the version condition, we can see the release strategy tab in the PO.
Thanks in advance,
Vikas Rander.

Our requirement is as follows:-
Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
Price-A can be equal to Price- B, Less than or greated than.
I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
and when i delete the version condition, we can see the release strategy tab in the PO.
Thanks in advance,
Vikas Rander.

Purchase Order release strategy -- Workflow related

Hi All,
We have a scenario where in the PO's are subject to Release Strategy with 4 levels based on the Value of the PO.
My requirement is to .........
1) Trigger a workflow once the PO is fully released. (Final approver has released), send a copy of the PO spool to the ID of the person who has created the PO.
2) Normally the spool is saved in the ID of the person who has done the final release.
Please suggest if this is possible thru workflow and how is this to be configured ?

Hi
Contact ur abaper.
Vijay

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

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.

Purchase order -- release strategy

Dear Friends,
I have a requirement for Purchase order Release.
The problem area is in purchase order ... there will be 2 Relase approvals
01 Mr. Abcd
02 Mr. Xyz
After level 1 approval and before level 2 approval ... i want to do some actions.. these actions are related to another product named savvion .
My question is can i stop the document to be edited by 02 ( Mr.Xyz ) untill i complete my process after 01( Mr.Abcd ) has finished his work.
This is to be done on top priority.
Please help me.
Cheers
Jitesh.

Hi,
Yes, We can stop the document to be edited by 02 until 01 has finished his work.
After 01 approved the document need to be correct, go to PO header menu release strategy TAB and 01 approved to be revoked (means double click on the tick mark, it will revoked).
Hope it is useful for you.
Regards,
K.Rajendran

PR Release Strategy- transport of charact/class/ values using ALE

Does anyone have the information relative to ALE set up for release strategy-
I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
This will be a great help.
Thanks
Raj

Hi Raj,
Please check the below notes for more inrofmation:
86900 - Transport of Release strategies (OMGQ,OMGS)
799345    Transport of release strategy disabled
10745     Copying classification data to another client
45951     Transporting class data: system / client. - has details of what you are looking for.
Hope this helps.
Regards,
Ashwini.

Release strategy affecting old POs

Hi Experts,
When we tried to cancel the material document by tcode MBST , we got the error message u201C Purchasing document not yet releasedu201D
This PO and related GRs were created before we implemented PO release functionality. Even then, the system looks for PO release while reversing the old GR documents.
If we release this PO now, it will go to top management level for further approval.
Please advice whether we can process OLD POs without effecting releasing procedure
Many thanks,

thankyou for the replies.
finally we got minor price change done manually in all the POs to get the new rel strategy on them
Open POs , no change done - Did not pick release strategy (then it was no problem at the first place)
Open POs , change done in price - picked the new release strategy
Open POs , no change done but click on 'check' button in change mode - Could not test this one bcoz all POs are now converted. But I put break point in save user exit (which also plays part in determining the new release strategy) it did not stop at the break point and I gave message 'No data changed' so I think this action will not redetermine release strategy. It was very useful if it did though.
thank you.

Release strategy & EBAN for project systems, purchasing

Hi
We have 2 different scenarios for which we use same account assignment category "Z".
1) Purchase Requisitions for capital expenses (Account assignment category "Z") - this is part of project systems requisition attached to WBS elements
2) Purchase Requisitions for expensed items (Account assignment category "Z")
I have configured release strategy with classification with following characteristics
1) plant
2) cost centers
3) total amount in PR
4) account assignment category
all 4 characteristics are same in both areas (capital and expensed)of purchase requisitions, account assignment category Z decides whether it is capital purchase or expense related purchases. Z uses order number that is internally tied to WBS element.
my question is - if some one has similar scenario then what is the best solution to handle invocation of release strategy.
how release strategy can be determine, do I need to use user exit and if yes what best user exit is available.
EBAN fields, I have researched and I cant use fields like "requisitioner" for determining release strategy.
I would like to invoke different release strategy for capital projects and different release strategy for expensed items in PR. there is a workflow attached to this later.
Please reply
Thanks and regards
Umesh

Umesh,
Well, there needs to be some way to differentiate the 2 types of purchase requisitions for you to use 2 different release strategies.
I am not sure if you have the option of using a different document type to differentiate the 2 requisitions. I would definitely look at this possibility and include the document type (CEBAN-BSART) as a characteristic in the release strategy.
Other options would be to look at using the purchasing group (CEBAN-EKGRP) or the requirements tracking number (CEBAN-BEDNR) as characteristics in your release strategy.
Hope this helps.
H Narayan

PO Release Strategy Determination

Hi,
Is there a user exit/badi where we can skip calling the FM ME_REL_STRATEGIE_EKKO (I believe this FM is responsible for re determining the release strategy of a PO) if this change is not related to any item price change ? What we want to have is for the PO to use the same release strategy if the header text is the only one changed.
Thanks.

Hi,
I dont think there is any EXIT/BADI to avoid FM 'ME_REL_STRATEGIE_EKKO'.
You can actually create an enhancement point at the start of this FM and check for the conditions when you want this FM to skip and EXIT from this FM.
But this is not the wise way of doing.
If you can elaborate your requirement in detail, may be some one can help you with other alternatives..
Regards,
Gautham Paspala

Item category control the release strategy?

Hi,
Currently the purchase of a material needs to be released.
My issue is that as soon as I change the item category in the sales order,
the material does not need to be released.
How does item category control the release strategy?
Sincerely,
Ketan

Hi Ketan,
You can set item category in the characteristic of a release strategy.
In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
Thanks & regards,
JT

Service PR release strategy

Dear all,
We need to configure release strategy for Only Service PR which consist Account Assignment Category 'K' and Item Category 'D'.
How can we configure it?
We have release strategy in general.That means no service specific release triggered.Release effected for both Service and Material PR.
Thanks & Regards
Dipayan Bose

Hi,
As per your post, you require separate release strategy for Material PR and Serivce PR.
now as per my pervious post, you can assign two more charcaterstic to your calss used in release of PR.
Now for Service PR, you can put value as given above.
Now for material PR, these field should be blank not you need to assign blank values to these chaacterstics in CT04 and other valuse applicable.
First of all, you should go to Transaction CT04 and add this 'blank' value to your related 'account assignment category' release characteristics & Item Category. This addition is done by not entering any particular value into the 'Char. value' column but with related description (you can name it as 'Blank Account Assignment Category'). Then go back to CL20N Transaction where you can manually select it for your respective characteristic value of your release strategy.
Regards,
Pardeep Malik

Release Strategy for PR--------Help is required urgently.

Hello all,
I have one severe problem in PR release strategy. Whenever we create a PR the Release is triggering but the name of the processer who will release this PR is not triggering. I have done the PO13, where the HR positions are maintained as per the release levels and PA30 where the SAP user ids of these processers is given. But still the processor name is not triggering. Is there any other transaction where we have to maintain certain data?? Kindly help me as this is an urgent issue.
I will be very glad and give points to all of u.
Thanks and Regards,
Umakanth.

Hi,
Please check whether the relevant HR authorizations are given or not, especially relating to Org. management.
This is not only for the approver but also for the person viewing the requisition.
Hope this helps..

Release strategy against material type

Hi
Our customer requires a separate to group of people to release Raw Material POs and a person to release Spare Parts related POs. How can I set release strategy according to material type?

Hi,
These 2 purchases (Raw Mat & Spare Parts), are they being purchased by the same Purchasing Group?
If different, you can use Purchasing group as a classification in your release strategy.
Or Material Groups as a classification?
Currently, i dont know if there is a way to differentiate between material types in PO for your release classification.
Maybe you can use Exit to control CEBAN-USRC1 where, It includes the first few characters of your material number range.
Im assuming that you have:
1) SP001001 for Spare parts
2) RM001001 for Raw Materials
So you can use SP, for Spare parts release strategy and RM for Raw Materials Release Strategy.
Im not sure if this works, just an idea.

Release strategy related

Similar Messages

Maybe you are looking for