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

Similar Messages

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

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

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

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

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 of contract disappeared after using of MEMASSCONTRACT

Hi All,
May be some one can help me?
I have next problem it tr. MEMASSCONTRACT(ECC6)
Release strategy of contract disappeared after using of tr. MEMASSCONTRACT. I know why it happened, but I don't know how to correct it. Some time ago IN ECC5 we added a field to a table EKKO and used this field as one of characteristics in the release strategy of contracts. In order to transfer value of this field to field CEKKO-USRC1 we used User Exit EXIT_SAPLEBND_002. This User Exit is suitable only for online transactions (ME31K, ME32K). How can I feel field CEKKO-USRC1 in transaction MEMASSCONTRACT?
Regards, Liza

Thank you. Probably I didn't explain my problem clearly. It's section of code from User Exit EXIT_SAPLEBND_002:
ATA: reference(20) TYPE c VALUE '(SAPMM06E)EKKO'.
DATA: it_ekko TYPE ekko.
FIELD-SYMBOLS: <ymm_icl> TYPE ANY.
e_cekko = i_cekko.
*THE "ICL Contract" FIELD IS ONLY RELEVENT IN THESE TRANSACTIONS
IF sy-tcode EQ 'ME31K' OR sy-tcode EQ 'ME32K'
OR sy-tcode EQ 'ME33K' .
ASSIGN (reference) TO <ymm_icl>.
it_ekko = <ymm_icl>.
e_cekko-usrc1 = it_ekko-ymm_icl.
ENDIF.
Program SAPMM06E can only be reffered while using online transactions. Mass transactions does not use these program and it is completely class based. So, may be someone know how can i do the same , but for tr. MASS in ECC6.

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.

Contract Release strategy

Dear Guru,
We have three types of contracts like A type, B type, C type......with these three types of contracts we have release strategy with different conditions.
               For A type of contract : Release Strategy should trigger on cost center and value base.
               For B Type of Contract : Same conditons like above.
               For C type of contract : it should trigger on duration base like.....if contract create for one year itshould trigger manager........if one year to two years it should trigger to director........if above two years it should trigger to CEO.
          This is my requirement.....how to configure this pls explain me.
Best Regards,
Bhaskar.

Hi,
You can only have one class and so you will have to use all of the characteristics from each type of check that you want.
So you would need a characteristic of Cost centre, one for Value and one for start and end date. (in addition to whatever characteristic you are using to determine if the contract is type A, B or C.)
With the release strategies you need to ensure that for type A and B contracts the date range characteristic is not checked and so you need to specify that all date ranges are included (so if the difference between the two dates is one day to 999 years).
then on the release strategy for the type C contract, make sure that the cost centre and value characteristics are set to include all too (so cost centre 0000 to ZZZZ and value from 0.01 to 9999999, if you don't want either to be checked).
this should work, the basic idea is that you ahev to have ALL characteristics included in every strategy but you use the values to make sure that you ignore certain characteristics in certain situations.
Steve B

Contract Release Strategy - error

Hi Guys
I have one problem in Defining Release Strategy for Contract.
scenario : i want to create RS for PR,Contract and PO for all the three.
Well i am able to create RS for PR and PO but when i try to make RS for contract , it doesnt work.
it give information message : - Purchasing document XXXXXXXXX not subject to RS. and "Message no. ME298"
I am using the Same Table CEKKO for making the RS of contract.
Characteristic
1) GNETW - >=000*
2) BSTYP - A CHECK BUTTON COMES FOR SELECTION:
K Contract
*F Purchase Order
3) BSART - A CHECK BUTTON COMES FOR SELECTION:
MK/ WK - Contract
NB Purchase Order
I have make the RS like this :
Class : Est_lib_CEKKO
Release Group : CO - for Contract/ PA and PB - for PO
Release Code : CA/ AA/AB
WHERE : CO -> CA, PA and PB --> AA/AB
Release Indicator : 0 - RELEASE
1 - BLOCKED
in classification for CO
1) GNETW : >=00,1
2) BSTYP : K
3) BSART : MK/WK
If someone knows how to fix it, please i thank you.
Regards
Antonio Oliveira

Hi,
PO release strategy working fine, then you should not have any problem now for contract also as you have separate release group for contract CO, have own release indicators( PO & Contract) and have following in RS of contract in classification
1) GNETW : >=00,1
2) BSTYP : K
3) BSART : MK/WK
Just change <=000 in GNETW and save, now try creating contract to have difference.
Generally value are to be in GNETW others follow as per business (it may differs company to company) are as like example <=100000, 100000.01-1000000.00 & 1000000.01-20000000.00, > 20000000.00
Regards,
Biju K

Release Strategy for contracts.

Hi gurus,
Good day,.
Please help on this.
We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
Example.
Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
Thank you.

Dear Acel,
The example you given was working just fine and correct.
a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
-> The release strategy will only be reset if the total net value for the contract was higher the previous
value but not lower.
As your example, quantity was updated to 1200, then it will reset when changing from 1000
to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
In system, it always assume if you had approved for the total value of the higher 1 before, then
it should be fine for the lower total net value for your management and therefore not need to re-approve
again for redundancy job. This was very logic in common business scenario in many companies.
However, like in your example , if you had define a different release strategy for a value that met the
the 1100 quantity, it will redermine the different release strategy. For example:
USD 1 for every quantity = 1
Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
USD 1200 for quantity = 1200.
Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
Release strategy C for 1200 , characteristics from USD 1200 onwards
Then if you change the quantity from 1200 to 1100, it will redetermine the release
strategy B which means from Release strategy C to Release strategy B. If you
only had Release strategy C that had a characteristics from 1000-1200, then
it will keep the Release strategy C as released and it won't be reset unless
if you had change it and the condition of the total net value was higher than any value
before.
Hope this will explain the logic.
Ian Wong

Contract & PO Release Strategy

Similar Messages

Maybe you are looking for