Apply release strategy to STO PO same as normal PO

Hi Expert,
my user requested to have release strategy for STO (stock transport order) as the same practise as normal PO. So if they want to use the same release strategy as in normal PO, is it means that only need to add PO document type (for STO) to the release strategy? That's it?
Thanks.

Hi,
It depends upon the characteristics you presently have for existing release strategy. If you have total PO value as one of the criteriion, then you may have to go for new release strategy because generally conditions tab will not come for line items with item cateogry U.
If the above situation is not relevant for your case, then you need to add the STO PO document type in the characteristics and assign the value for the particular release strategy using CL20N.
Regards,

Similar Messages

Release strategy to STO - Order type UB

How to apply release strategy for STO for order type UB ? Except UB order type I'm able to apply release strategy. Is there any Config for exclusition ?
What is the userexit for STO Creation i.e. ME27 / ME21 ?
Regards,

http://www.sap123.com/showthread.php?t=59
check UB is existing or not in the existing characteristics or any combination characteristics stops you.
you need to create a characteristic with CEKKO--BSART and assign the same in your class and further use this characteristic in your release strategy.
br
muthu

Release Strategy for STO

Hello Experts,
We have a requirement to configure release procedure for STO scenario. Release procedure needs to be captured in STO PO's.
We have 6 plants - A,B,C,D,E,F, and each plant is having different approving authority individually.
When STO PO is created, it has to be approved by Issuing plant authority & receiving plant authority as well. The major concern here is for eg., approval authority for plant A can be a issuing authority at one instance & receiving authority at another instance.
How to configure release strategy for this.
We believe ,creating those many release strategies for all the combinations of plants will be a hectic task & still it'll multiply with the introduction of more number of plants.
Hence looking for a more simpler & feasible workaround/solution.
Regards
Mahesh.C.R

Hi,
you can use Supplying plant ( RESWK) and issuing plant (werks) both as characteristic and with these combination you can configue release strategy.
Or you can use User field format character for release strategy (USRC1)as per your requirement.
YB

Release Strategy for inter Storage Loc Material transfer within same Plant

Hi Guru's
I hope all are doing good. I gota small concern to share with you. Is it possible to apply Release Strategy between two Storage Locations within same Plant for Material Movement?
Many Thanks
SONAL

Release Strategy cannot be assigned in material document.
However you can restrict this at authorisation level for T code MIGO_TR.
Regards
Bhavesh Mistry

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
   case of a purchase requisition and '4' or '6' in case of
   another purchasing document (purchase order, request for
   quotation, contract, scheduling agreement),
- the document is still subject to the previous release
   strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

Po Release Strategy Change

Hi Gurus
I am changing the release strategy for po.
Same characterstics and value also same.
only change is release codes. so that, what i can do. if i add new release codes in same old strategies ?
Otherwise i can create new release strategies ?
if i create new what i have to take steps ?
if i use same old release strategy and in that i can chage release codes what about previous documents ?
client side cl24n here we can block old stratiges what about the documents created on old ?
If any body answer right rewarded full.
Thanks in advance
Regards
Laxman

Hi
we have also did some changes to relase codes after once in use & we had encountered some problems in the PO.
For E.g. If you have the previous repease codes as L1 & L2 , & if you are removeing the L2 form the release codes then All the PO's whcih are approved by L1 & awaiting tobe approed by L2 will be in hanging status. You need to go into each PO 7 click on revoke acceptance & Click on check then The new relase codes will appear.
If you can clearly explain what you are planning to do on the relase codes , then we can advise you in the right manner.
Thanks & Regards
Kishore

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.

Appluing release strategy for scheduling agreement

Dear Sapguru,
Can anybody explain.How to apply release strategy to scheduling agreement.I'm working on MRP implementation project.
Here already release strategy using for PO.
Pls explain steps of release strategy to scheduling agreement.

Hi,
Welcome you post on the forum.
Have you searched the forum already? Such as:
http://forums.sdn.sap.com/search.jspa?threadID=&q=%22applyreleasestrategy%22&objID=f245&dateRange=all&numResults=15&rankBy=10001
Thanks,
Gordon

Release strategy control fields

I am doing release strategy in my project for P.O. Please answer follow question
a) by what fields we can control release strategy, and how we know can use only those particular fields control by these field
b) What is the difference between EKKO and CEKKO? Why CEKKO should use? Is that should use always C before EKKO? If yes, why?

Hi,
a) by what fields we can control release strategy, and how we know can use only those particular fields control by these field
--> You can use the fields to configure release startegy which are available in communication structure CEKKO. All fields in communication structure can be used to control release strategy.
b) What is the difference between EKKO and CEKKO? Why CEKKO should use? Is that should use always C before EKKO? If yes, why?
---> As said by Indranil, it is a communication structure and it is copied from the table EKKO to enable the release strategy.
System follows the below described procedure to apply release strategy. This will understand you more clearly.
When you process a purchase order (PO), the system passes on the data from the PO document to the communication structure CEKKO.
After the data has been passed on to the communication structure, the system initiates an object search:
1. The system checks which class is defined in Customizing for the release procedure.
Note
There can be only one class for all purchasing documents (POs, contracts, scheduling agreements, etc.). This one class (032)then constitutes the basis for the release procedures for all purchasing documents.
2. The system assigns the values from the communication structure CEKKO to the characteristics of this class.
3. Via the object search function, the system then identifies a release strategy whose characteristics accord with the values from the communication structure or lie within the specified interval.
The following search results are possible:
Just one release strategy is found.
The system assigns this release strategy to the purchasing document.
Several release strategies are found.
The system assigns the first release strategy found to the purchasing document.
No release strategy is found.
The system does not assign a release strategy to the purchasing document.
Hope above explaination helps you.
Deepak.

Release Strategy Error

Hi All,
We are in Classic scenario and for the PO in backend we have applied Release Strategy. However, for the PO with approval we are getting error as per the below screenshot. Could you please let me know the possible reason?
Thanks,
Sunil

Hello Sunil,
click onto the hyper-link from step in error to get error details.
Regards.
Laurent.

Release strategy for PR generated through network activity (Project)

*Hi,
I am facing the problem that PR generated through network activity (Project) does not have release strategy attached. For same combination of characteristics value of PR document type , account assignment, release strategy strategy is attached for PR created manuelly.
Please suggest
Regards.*

What is the account assignment used in Network generated PR, Have included that in your characteristics? Is PR in Your defined document type?

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 not applied for some contracts..

Dear All,
At my client place,In some of the contracts release strategy is not applied.
I have tried evrything...in classification plant,purchasing group,net value and order type (MK and WK)everything is added.
but some of contracts release strategy is there and for some it is not applied...what could be the reason?
Please help.
Amit

Dear All,
Please reply....

Error message if no release strategy is applied for PO

Dear All,
In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
Is there any way to encounter this
Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
OR
While making GRN against this PO, System will give message Like say ... no release strategy is applied for the PO..
Please reply ...URGENT
Regards,
Rakesh Shelar

Dear Thanx.
my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
In this, case system is allowing to take GRN against such POs without release strategies

Release Strategy - Object "ZX NX" already classified with same characterist

Hi Gurus
While modifiying the exist release strategy the following error occurs.
Object "ZX NX" already classified with same characteristic values
Message no. C1818
Diagnosis
Object ZX NX was already classified with the same characteristic values. In class maintenance, you define whether a warning message or error message is displayed in these circumstances. This message draws your attention to the possibility of data redundancy.
Procedure
Change the assigned characteristic values, so that you do not have redundancy in your system.
Perhaps the object you are classifying is not necessary, because it can be replaced by the object found by the system.
Please advice on this.
Thanks in advance
ARAS

Hi
Thanks for your input. I will test this and come back.
Experts, any further inputs...
Regards
Aras

Apply release strategy to STO PO same as normal PO

Similar Messages

Maybe you are looking for