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

Similar Messages

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

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

Release strategy problem in RFQ

Dear cons
In release strategy of P.O we are using three characterstics. I.e- net order value, purchase group & plant. Wehave not made any Release strategy setting for RFQ..while we are creating RFQ the system ask to release the RFQ. wHY.wHAT IS THE REMEDY FOR THAT. BECAUSE WE DONOT WANT TO RELEASE THE RFQ. I saw which data I have entered for P.O release strategy The same data is available In RFQ path.The path is img-material mang- purchasing- P.o- rel. PROCEDURE for P.O- DEFINE REL. PROCEDURE FOR p.o. you can check same data is avaiable in RFQ PATH.
PL. GIVE ME SOME HINTS.

Hi,
Please use document category or document type or both as chanracteristics for the release class.

Release strategy for PO, RFQ & Contract

Hi,
We have created release strategy for PO, RFQ & Contract.
Characterisitc is created for Target Value for Header Area (CEKKO-KTWRT)
for RFQ & Contract it working fine but for PO not triggering.
what can be the cause.
Pls guide.

Hi,
Melih is right, for POs you can not use the target value.
What you might do is to include the document type and CEKKO-GNETW as additional characteristics and then set for contract document types the GNETW blank, and for PO documet type the target value blank. Blank means any value should fit.
I hope this hint helps!
Best Regards,
Arminda Jack

How to turn off Release strategy

Hi,
We need to upload purchase orders via LSMW. While doing so, we do not wan the release strategy to be active to avoid the need for approving each order. How can I turn off the release strategy.
Thanks in Advance.
Regards,
Pavan

Hi
Not sure if this requirement is to handle the cutover POs/ POs which were already approved in legacy system, I have handled this by two ways in the past ( as due to last minute changes we were not sure abiut frequency and need of turning release strategy to on / off
1. We have use a charactertistc (corressponding to PO date ) in Rel strategy and setup in such a way that REL strategy is active for PO with PO date > Go-live date ( all legacy POs were loaded with s date earlier than Go -live date)- this ensure that we need not to do on/off several time
2. another case we created a seperate PO doc type and excluded from rel strategy, no uses was given authorization for creation of this except the cutover / data migration team which was responsible for cutover
Hope these suggestion helps
Reg
Dheeraj

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.

PR - How to use distinct release strategy

Hello SAP's gurus,
We use the procedure with classification for our release strategies.
I cannot undestrand why I cannot work with 2 disctinct class (it means different characteristics list) for my company.
Rel.Grp   /Rel.obj.   / OvRelPReq    /Class
ZY          /1              /NO                 /RELEASE_STRATEGY_1
ZZ          /1              /NO                  /RELEASE_STRATEGY_2
We would like to define specific characteristics depending on the currency used in the PR.
It means, if currency is USD (table CEBAN/WAERS) : characteristic "Total Value of Item in USD" (table CEBAN/GSWRT, currency USD) should be used and if the currency is EUR : characteristic "Total Value of Item in EUR" (table CEBAN/GSWRT, currency EUR) should be used in the release strategy.
How can I work to set up a list of characteristics for the release strategy different from a currency to another one?
Thank you so much in advance for your help.

I'll have a quick check but assuming GSWRT is purely a value figure, that won't provide the distinction you want. You need to use a characteristic that represents the currency i.e. use CEBAN / WAERS. That will allow you distinguish according to the cirrency.

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
   Create the release codes.     For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
   Define release indicators and branch to the detail screen. Here you
   define whether fixed purchase requisitions may be changed by Materials
   Planning, for example, and whether an RFQ or a purchase order may be
   created from the requisition.
   You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
   specify whether a requisition may be changed after the release
   procedure has begun. You specify whether the strategy has to be
   redetermined after changes, or whether the release procedure has to
   start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
   example, previous releases are not cancelled if the value of the
   requisition item after the change does not exceed plus 10% of its
   original value.
Attention:
   Be sure to create a release indicator (e.g. B for "blocked") that
   serves as the starting point for subsequent indicators. Do not set the
   indicators for release for the issue of RFQs and PO on the detail
   screen for this indicator.
   Also create a release indicator characterizing the released status.
   Set the indicators for release for the issue of RFQs and PO on the
   detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
   Assign a release indicator in dependence on the status of the release.
Example:
   You create a release strategy S1 consisting of two release codes 01
   and 02. Release with 01 is a prerequisite for release with 02. If
   release has been effected with 01, the requisition has been given the
   "all clear" for the issue of RFQs.
   You have created the release indicators B (blocked), 1 (cleared for
   issue of RFQs) and 2 (cleared for RFQs and PO).
   Now enter the following as assignment:
Strategy   C1 C2 C3 ...
   S1                          B (blocked)
   S1         X                1 (RFQ)
   S1         X   X            2 (RFQ/PO)
4. Release prerequisites
   Define which release codes are involved in a release strategy. Specify
   whether a code is set for a release status following release, and
   whether one release status is a prerequisite for another (+).
   Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

HOW TO BLOCK A RELEASE STRATEGY

Sir,
ply help me in blocking a release strategy as in i want to configure a new strategy
ply help
regards
amey

hi,
You can do the blocking of current release strategy via:
removing the connection of the release group to the release class and then deleting the release strategy parameters inside the release strategy tab under spro settings ...
Paul,
If we only remove the characteristics, system also determines internally,,, then will it be deactivated??
Regards
Priyanka.P
Edited by: Priyanka Paltanwale on Apr 27, 2009 4:52 PM

How to retrigger PO release strategy

Hi all,
We have configured PO release strategy. When creating PO, it is initially blocked. Then the manager have to release. When the PO price is increased, the PO will again be blocked. When the price is decreased, the PO is saved without any block. The requirement is to use the same logic when the price is increased and decreased. That is, to block the PO.
Kindly let me know if this is feasible.
Thank you.
Nene

Hi,
You should check first of all with your MM consultant see if through configuration is possible. If its not possible, you could use an user exit when saving, and check if price changed, and reset the release code using the bapi BAPI_PO_RESET_RELEASE.
Regards,
Gilberto Li

Release strategy error in RFQ

Dear MM gurus
I have maintained all the steps for release strategy for RFQ, while clicking on release flag in ME42 it is giving following error. please guide
Purchasing document 6000000015 not subject to
release strategy
Thanks in advance
kailash N. thakkar
9869171090

Hai,
Release strategy gets effected when all the characteristics mentioned for the release strategy are complied otherwise the strategy will not affect the RFQ.You might have given any value not relevant to the characteristic.For eg you might have given alower value than the value mentioned for the characteristic RFQ value.
Regards,
Gangadhar

How to avoid claim - release step in Human Workflow

Hi All,
I have a Human Workflow in which i need to assign a task to a group of people. However we want to skip the step of claim and release. Directly we need to have the approve or reject options in the task list for the user. Is there some way that can be accomplished?

In the corresponding .jsp files (TaskList.jsp,TaskDetails.jsp) in the $BPEL_HOME/samples/hw/worklistapp/public_html you need to change the following:
In the call to method HTMLFormatter.displayTaskActionsDropdown, change the last parameter to "HTMLFormatter.CUSTOM_ACTION_OPTIONS"
Then you need to deploy custom worklist application, once you have deployed the custom application you can access it through the URL -
http://localhost:port/integration/customapp/
In this custom application you will see "APPROVE"/"REJECT" options in corresponding pages.
Refer http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/worklist.htm#BHACDDFJ for more details.
Edited by: Krishnaraja Nelli on Dec 8, 2008 5:13 PM
Edited by: Krishnaraja Nelli on Dec 8, 2008 5:16 PM

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

How can Change PO Release Indicator to Released Status

Hi Gurus,
We are having an issue here, which user accidentally re-triggered customized program to re-trigger the release strategy of old PO documents.
This program basically reset the PO release startegy status and update the PO with the latest PO release strategy configuration. It's using FM ME_REL_STRATEGIE_EKKO.
So, currently some of the old PO which previously been fully released and closed PO (with GR & IR completed). So, we dont think that it's right for these old PO to be approved again, also the relevant approvers also refused to do so.
Is there any way that we can use the same FM to change the release indicator to R from S? Appreciate your help. Thanks!
Regards,
Michelle

may i suggest you accidently trigger the program to close the release strategy for all POs by modify class characteristics.
and then reopen the release strategy for necessary POs.
or maybe, you can trigger the program to close the release strategy for old POs.
please see below for details:
How to turn off Release strategy
Edited by: JiQing Zhao on Jun 14, 2011 1:19 PM

How to avoid po release strategy replicating in RFQ

Similar Messages

Maybe you are looking for