Release strategy for RFQ

Hi,
Please let me know,how to set release strategy for rfq.. i'VE ACTIVATED MY RELEASE STRATEGY FOR po USING TABLE cekko... iF I WANT TO ACTIVATE RELEASE STRATEGY FOR rfq... WHICH TABLE AND FIELD NAME I WANT TO USE... PLS EXPLAIN..

For RFQ also we can use the same communication structure CEKKO, but for differentiation between release startegy of Contrcats Purchase orders & RFQ's better to use the Charcteristic Document category i.e CEKKO - BSTYP - Purchasing Document Category

Similar Messages

Cannot reset release strategy for RFQ

Dear SAP gurus,
I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
Best regards,
John.

Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
Lakshman

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

Release strategy in RFQ

Hello Gurus,
Is there any way I can implement a release strategy for RFQ?
Thanks,
Jeffrey

Hi Jeffrey,
yes you can set up release strategies to RFQ also in
trasaction SPRO->MM->purchasing->RFQ/Quotation->Release Procedure for RFQs->Define Release Procedure for RFQs.
RFQ's use the same structure as purchase orders for the release strategy classification (CEKKO). Nevertheless, there are some fields in this structure that are only relevant in POs. Field CEKKO-GNETW (Total net
order value) is not relevant to RFQ release strategies. You can enter a value for this characteristic in transaction OMGS, but the system won't consider it.
Since RFQ is just a Request for Quotation, it does not make sense to set the release strategy of RFQ according to value change.
By using the characteristic CEKKO-BSART you can exclude certain release strategies for certain document types. A release strategy with CEKKO-BSART = NB won't apply to documents with the document type AN (RFQs).
hope this will helps you.
Regards,
Sunitha

Release procedure for RFQ

Hello All,
I'm trying to configure release strategy for RFQ, but it's not working.
I have create characteristics for CEKKO-BSART,CEKKO-BSTYP,CEKKO-EKGRP,CEKKO-WERKS.
Have assigned objects to classes. Release indicators are assigned properly.
But in ME41 it is not getting activated. What could be the reason? I think I have made a mistake somewhere.
Thanks in advance,
Piyush

Hi,
Is it necessary to assign release code & release group to user id?
Because I have never done it for any release procedure uptill now.
Please explain the same.
Thanks in advance,
Piyush

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

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

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

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

Release strategy for Schedule lines in SD

Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

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

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Release strategy for Release POs

Hi Every one,
We have a requirement.
A contract is created and approved as per the regular strategy.
The releases (POs) are created against it and sent directly to the vendor.
As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
But the business wants the PO releases too to follow the release strategy.
Can you please look in to this and let me what changes we need to make this happen.
Regards
Pavan

As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
So that the Release Process is applicable to PO's created w.r.to Contract also..
For ex: if you use the field purchase Doc category as a Character in the Release , it differentiates whether it is PO or Contract..
So that you can define different Release Strategy for PO & Contract
Or if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
then the release strategy applies to PO also..

Release strategy for RFQ

Similar Messages

Maybe you are looking for