How Release Strategy is picked up

Hi,
There are many release strategies configured in the system for various company code/P Grp/Plants combination.However for newly introduced territory and the respective company code/plants combination,the configuration has not yet been carried out.
Even though a configuration is not done, when a PO is manually created for one of the combination for this territory system does allow to successfully save the PO suggesting 'unable to determine Release Strategy'
My question is what is the driving parameter which is coming in to picture in this case which prevents me to create & save a PO for testing with this error.
Please suggest
BM

Hello Arjman,
The driving parameter here is the combination of Release Group, Release Class for External Purchasing Documents- indicator 2. Since you have configured a class for External Purchasing documents.. PO in this case, he message becomes relevant, however since none of your strategies or classification data exist, the system fails to derive a strategy

Similar Messages

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

How release of PR is affected in standard SAP

Dear experts,
Please help. How standard SAP PR release is affected. I want that if any change in PR , release will be affected. How this can be done. Please advise
Thank you
Kind regards,
Zusen

>
Badruddoza Zusen wrote:
> Hi
>
> Thank you for your reply.
>
> I checked that re-trigger is happened if i change value only when value exceed the certain level as specified in the release strategy. But, what i need to do if i want that any change in value will re-trigger release strategy.
>
> Please advise.
>
> Kind regards,
> Zusen
To pick up release strategy for all value your value characteristic should read:
>= 0
Meaning Greater than or = 0, even the release strategy will pick up PO's with 0 value in this case.
Edited by: Afshad Irani on Jun 21, 2010 9:53 AM

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

How to apply newly transported release strategy to existing POs ?

Hi,
We transported a new release strategy to production
The new POs created are catching the rel strat B if they meet criteria
But some of the existing POs also meet the criteria for B and they should also take up this new release strategy
We cannot change the POs in ME22N, busines refuses to make any change to POs
How can we apply our new rel strategy to these POs ? has the SAP provided any standard function module to report?
thank you
B

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 for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

How to Display PO Release Strategy in Enjoy Screen

Dear all,
I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
Thanks a lot.

Thanks 4 the reply Rahul.
I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
Thanks and appreciate if anyone could help.

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

Release Strategy is not picking up in the PO.

Hi All
I have defined a Release Strategy for the Purchase Order.
The Characteristics are
PO category
Pur Org
Total Net Order Value
All the lights are green which i check the release strategy.
But the Release Strategy is not picking when PO is created.
Kindly let me know what is the mistake i have dont or i need to make any corrections.
Thanks in advance
Renukaprasad.

Hi Renuka,
im using ECC6, my PO rel strategy dont have PO catergory,
but you can try this:
Maintained PO characteristics:
PO doc type
PO Plant
PO Pur Grp
PO total Value
Once your PO meet this, Rel Strategy triggres.
When you define the Rel Strategy, there is rel indicator Approved and Block, configure based on your requirement.
Hope this helps a little
Regards,
Maia

How to avoid po release strategy replicating in RFQ

Dear Sapiens,
I am aware as we are using same class for PO RFQ and Contract the release strategy will repliacte in rest,
but I dont want PO release strategy to get repliacted in RFQ,because I dont have realease for RFQ
how to avoid po release strategy replicating in RFQ?
Regards
Kantha

Hi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

How to have more than 8 release code for a release strategy

Hi,
In standard only 8 level of release is possible for a release strategy. Our client requires more than 8 levels i.e., more than 8 release codes for a release strategy. How can we achieve this?
Pls provide your views/ideas.
Reards,

Hello,
In case you require more than 8 levels in release strategy , write to SAP, maybe they could give a fitting reply.
By the way , 8 levels of release should be more than enough . Try to incorporate the client business process
within this.
Regards
Anis

How to do release strategy work flow in MM

how to do release strategy work flow in MM. for purchase order release how to do release strategy work flow. please give elaberate steps

1: Install SAP - your IT support team should be able to help you with this
2: Start the SAP Logon Pad (it is in the Start menu if you use Windows - look around)
3: Go to transaction SPRO
4: Navigate the structure, go to materials management, purchasing and then look around
5: Read the documentation for each activity
6: Perform the activities
Seriously, you will be amazed by how much you can learn by actually making an effort.
PS: I see you <b>expect</b> 10 points for your one-line replies, so this one should be worth at least 50.

How to assign Release strategy with new PO type

Hi experts,
I have created new PO type but the same is not mapped with release strategy at the time of raising purchase order.
I have done the following steps :
a ). Creation of new doc type via SPRO > MM > PURCHASING > PO > DEFINE PO TYPE
b). Edit characterstics in release strategy via path SPRO > MM > PURCHASING > PO > RELEASE PROECURE FOR PO > EDIT CHARACTERSTICS > VALUES ( MENTION NEW PO TYPE & DESC. HERE )
Still I am unable to find release strategy tab in purchase order. Please help.
Suggestions / Rewards will be highly appreciated.
Regards,
( Rajneesh Gulati )

Hi ,
I dont know how much customisation u have complited ,
But for release strategy
1 Following are the imp charecrticities ct04 you have to define
Order type (Purchasing)
Plant
Total net order value ( with table & field)
2.check or create relese group is assighned to appropriate class cl01 (with above charecricities )
3.define relese code ( in this u define release level --supervisor , manager etc)
4.release indicator (block ,release)
5.define the group with strategy in that specify prerequisites,release status,classification (specify to the document & plant you want to maintain)
6.create po me22. In me29 you can release it( unless u cant process)
Dev

How to configure release strategy in case of document parking ?

Hi experts,
I have a requirement wherein i have to create a workflow with four level approval when a document is parked before it can be posted.
The approval is by company code,reacon code and the amount .For example for a particular reason code for particular amount one person has to approve,if the amount is greater then 2 people have to approve, so on.
Is it possible to configure such a release strategy in SPRO ?
Kindly help,
thanks in advance,
regards
Ashwin

If it are FI Invoice you're talking about, it's possible.
Do you have access to the best practices of Public sector management ? There's an example on how to implement an FI workflow.
If not, check workflows on the object FIPP

How to control PO Release strategy using WorkFlow

please tell me how to control PO Release strategy using WorkFlow.
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on May 31, 2011 9:35 AM

Hi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

How Release Strategy is picked up

Similar Messages

Maybe you are looking for