Contract without release strategy

Hi Gurus!!!
I have an issue with contracts that withour release strategy. it happens because in the contract there are more than one item and those items must have the same material group. If it's not equal the release strategy is not added to the contract but if they are equal the release strategy is added.
Message error: Purchasing document XXXXXXXXXX not subject to release strategy.
Is there any way to put more than one material group in a contract?

Dear,
For OVERALL RELEASE (purchase order, Contract) the item fields such as Plant and Material Group will be aggregated to header level.For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header.
So please maintain a Blank value in CL20N if you have multiple material group
For more please refer SAP note 47089
Edited by: redriver on Dec 8, 2011 1:45 PM

Similar Messages

Requisition without release strategy

Hello everybody
Is it possible to block create purchase orders with reference to requisition without release strategy?
Example:
1. Purchase Requisition 100887 with release strategy R1 <> Purchase Order 300 created with reference to PR 100
2. Purchase Requisition 100888 without release strategy <> Purchase Order cannot be created.
Thank you for help in advance
Arek

Hi,
If you have seperate document type for PR's for release strategy
You can remove the link of PR document types to purchase order document types
other than release startegy in
Purchase order document type customizing spro>mm>purchasing>PO>define doc types>link to PR
this will not allow PO's to be created without Pr's having release strategy
BR
Diwakar
reward if useful

UserExit required - Do not Create PO without Release Strategy

Hi
My requirement is Do not Create PO without Release Strategy.
When user try to save PO, it should not allow to save, if it does not have Release Strategy.
For this scenario, we require which UserExit.
If UserExit, can you guide me which userexit and the following steps.
For this scenario, which is the best way to control.
If you got anyother options other than userexit can also be advised.
Pls advise me.
With Regards
Kamesh

Hi Shailaja
Very thanks for your reply.
Some more doubts,
I think Release strategy data will be populated in I_EKKO table.
I can use fields from I_EKKO-FRGSX & FRGKE.
If these fields are initial (ie) PO without release strategy, I want to exit PO without saving - Creation.
So here can i put Error message if the fields are initial.
IF i put Error message then the PO screen will be block ? in that Error message.
Just want to confirm before testing something with the Exit code.
Is this the way to proceed.
Thanks in advance,
With Regards,
Kamesh

Contract & PO Release Strategy

Hi All,
We are in the process of designing the release strategy for contract and PO. I would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
The release conditions for Contract required are
1)Porg
2)Pgroup
3) Value
Also, for quantity contract how can we make the release strategy trigger based on value.
The release conditions for PO required are
1)Porg
2)Pgroup
3)Material Group
4)Value
The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
Request your help.
Regards,
Kannan

Hi Kannan
Yes your requirement is possible...
While creating Charectristics in CT04 for External Purchase Documents...Create one more Value for your Document Category...ie) Table as :CEKKO and Field as BSTYP and choose the Purchase Doc. Category values K and F.
Then create Charecteris for CEKKO - EKORG, CEKKO - EKGRP and CEKKO - GNETW, CEKKO- MATKL... and assign these all 4 Chareteristices in your release class.
And Configure your release statergy according to your requirement...
Reward if useful
Regards
S.Baskaran

Release strategy of PO creation under contract

Hi,
if PO creation without any contract, release strategy is required. However, if PO is created from contract, no release strategy should be used. Pls advice how to configure it. thanks

The best option is you differentiate the PO document type i.e. create a seperate document type (ZNB) for those PO which are created wrt contract...Now while creating PO release strategy use PO document type (BSART) as one of the characteristic and there don't use this new PO document type (ZNB)
Regards,
Indranil

Release Strategy in Contract

Hello Guru
I have Created a Contract and when ever i want to change the Contract my release Strategy has to be re triggered and my version management is Active.
I tried to change the Value in Contract and when i do change the Value and if i ticked the Version on the Header of the Contract then my new release Strategy has to be re triggered but its not happening. when i checked the tick box in version in Contract it is saving but when i come out of the Contract it is showing unticked again.
I am unable to re trigger the Contract and if i tick the Version in the header of the Contract when i close it untick the verison it is not saving, how can i do this, please let me know
Sreedhar

Release strategy will trigger again when the version will be completed.
You have to tick the flag as version complete for contract, only the release strategy will be reset.
Be sure you release indicator has the Changeable as 6.
Then make the version complete for release strategy as below :
Once you will click the version complete flag, then version complete tick will also displayed.
Have a look into the similar discussion Re: Release changeable indicator 6 not working

ME31K release strategy

I've defined several release strategies for contract ageement. When I create a contract, if the system cannot determine a valid release strategy, I can crate a document without release strategy.
How can I make a control when saving the document (tcode ME31K, ME32K) to verify that a strategy release is always defined?
For purchase order (tcode ME21N, ME22N) i've found a badi that works correctly, but it doesn't control in ME31K.
thanks,
Marco

I've definied several release strategy (100) with many parameters (company code, value, plant, etc).
Even if only one of parameters is not satisfied, the document has none release strategy, and I don't have any message about this.
By standard system I must define a phantom release strategy, with all combination not covered by the real strategies.
thanks,
Marco

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

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

Release strategy for Future validity period- (Outline agreements)

Dear All,
I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
How to set up release strategy in the above case.
Thanks in Advance.
Regards
Amar

Hi Amar,
1) if you maintain a target value (EKKO-KTWRT) in the header of the
contract this value is the basis for the determination of the release
strategy. If the target value is 0, the system will cumulate the
values of the items and will use this value for the determination.
2) So if the target value is 0 and you change the price of a condition
with a validity period in the future the system will react in the
following way:
Example:
   the contract contains one item with quantity = 100 and a net price
of EUR 5,-.
   all contracts with a target value from EUR 0 - 1.000,- should be
subject of a release strategy
   the contract is created and released on October the 1st
   ME32K -> October the 2nd you define a new price of EUR 7,- with a
validity period from 03.10.09 - 30-10.09 -> you save the contract
-> the release strategy is not reset, as the start date is not
reached yet (system date < startdate of validity period)
   ME32K October the 3rd you change a field in the contract -> the
release strategy is reset
This is system design that a release strategy can only be reset through
an action by the user. The determination of the release strategy can't
be triggered automatically in the background.
If you create a document which is subject of an overall release strategy
(e.g. p.o., contract) the determination of the release strategy takes
place when the user hits the 'save' button or chooses the 'check'
function.
So there must be a kind of event that tells the system that something
has changed.
Regards,
Edit

MIR7 doesn't get PO and PO release strategy

I can see PO item 10, 10000 MYR in ME23N, and it is already released.
In MIR7, PO reference tab, I put PO number and item number, but mesages says no item number. and it didn't populate item from PO.
what's the reason?
also I create PR and released PR, but when I run ME59N and input PR number, it says No suitable purchase requisitions found
Message no. ME261? I can't generate PO automatically. I have to use ME21N, what's the wrong with my system?
I tried one purchase group and PO can't be released, but when I change purchase group, it is ok, may i know the SPRO configuration to define certain purchase group for release strategy?
also how can we set certain PO document type with release strategy and some PO document type without release strategy ?

Hello
For first question, Please check in the PO line item level Invoice tab, whether GR based invoice verification is checked. If yes, then system will allow you perform MIR7 after Goods receipt.
Second question:
ME59N should display the open PRs for PO creation. Please cross check once agian the input selection parameters.
Third Question
Yes, you can configure the Release procedure based on Purchasing document type/Pur group. You need to define the paramter as Charactetristic and assign to the Release class.
warm regards
Ramakrishna

Purchasing Release strategy in Shipment Cost

Hy collegues,
i need some information about Purchasing Release strategy in shipment cost.
1° question: Release strategy on Service entry sheet document
Is it possible set the Release strategy on Service entry sheet document?
I have just created a release strategy on Service entry sheet but when i transfered the costs with transfert field on Shipment Cost document in VI02 the system didn't feel the Release Strategy on service entry sheet and trasfered the cost in FI/CO.
2° question: Release strategy on Purchase document
Because of the point one I try to set a release strategy on Purchase Order (on purchase order type that i create when transfering the shipment costs).
When i transfered the costs with transfert field on Shipment Cost document in VI02 the system felt the Release Strategy. Infact the purchase order was create without service entry sheet document and good receipt but, in this case, i lost the link from Shipment Cost and the created purchase order.
This in correct, this is a standard behavior???....if this is correct, how will the user (that release the purchase document) release the document if he don'tknow the Shipment cost linked??
Thanks for your precious help.
Piera

Dear Piera,
Please refer note 844752.
This note removes former OSS note 611846. As a result, the automatic
processing of shipment costs should be used WITHOUT release strategy.
This will be STANDARD now for releases 46B, 46C, and 470!!
The release strategy will not be triggered if the KZABN = X,
this is the standard functionality.
I hope this note will clarify your doubt.
Regards,
Rakesh Ojha

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 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

Contract without release strategy

Similar Messages

Maybe you are looking for