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

Similar Messages

Contract Release Strategy - field Requisitioner

Hello,
I will start to use the Contract release strategy and I need the field Requisitioner (EKPO-AFNAM), because this field is part of my PO release strategy.
This field isn't available in the transactions ME31K and ME32K.
Can you tell me, if it's possible to show it in these transactions?
In other case, where can I fill this field? How is the BAPI, BADI, etc?
Thank you,
Meire

Hi,
Please, be so kind to refer to note 373361. This field was only
available in purchase requisitions and due to requirements of
SRM (formerly BBP business tons business procurement ), it has
been added into the new enjoy transaction
ME21N/22N/23N for purchase orders.
It is not available for contracts.
The contract is not the last document in the procurement.In bussiness
process the requirement of requisitioner in contract is less important.
It is enough if you don't know the requisitioner at the time of contract but
you know it at the time of PO creation.
This is the standard SAP design.   Please do not use this field in the contract release strategy: create a new release group for the contract release strategy, delete the value entry for EKPO-AFNAM in the "Change view - release strategies - classificaion". The characteristic for EKPO-AFNAM should appear as black and not as blue on the screen. Save your strategy.
Regards,
Edit

Contract Release Strategy - Adding New Line

I have a question regarding Contract Release Strategy - How can i force a release reset if a new line is added to the contract. I dont see a field in CEKKO - Any suggestions?

Hi
Version mangement is activated with Version Zero only. When you select Version 0 Ok
If you have selected this indicator, version '0', which is generated automatically when a purchase requisition or external purchasing document is created, is automatically flagged by the system as Completed.
If version '0' is completed automatically, the system does not check whether the version data includes any mandatory fields.
If you have not selected the indicator, version '0' must be manually flagged as Completed.
Only if this indicator has been selected for the current version:
Can a requisition be converted into a PO (for example)
Does the release procedure commence
Thanks & Regards
Kishore

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

Reset contract release strategy ME32K

Hi Gurus,
I need to reset the release strategy of the contract everytime some value on the item screen EKPO got changed.
I've already implemented the EXIT -> EXIT_SAPLEBND_002, but it only changes the header EKKO with the structure CEKKO.
Please help me ASAP.
Thanks.

For PR's, there is no header level data. Because vendor number is optional since it is internal document .
If you are releasing all line items at a time, need header level release.
If you release line item by line item, need item level release.
But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
That's vendor number is at header level field and line item in the PO are related to the single vendor.
You can release all the items in the PO or u can reject entire PO, not a single line item.
That's why, only header level release is possible for the PO/Contract/SA.
Other than this information please for through this link
PO release at item level ? | SCN

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

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

Contract Release Stragery

Hi All,
My Contract Release Strategy is based on duration .. When i save the Contract the release stragery trigeers...
But if the Workflow is rejected at first level then the initiator should have the option to Re-trigger ( the option is available in ME22N AND ME52N ) But it is not available in ME32K ...
IS there any solution to trigger the Workflow for the contract so that workflow can start.
Appreciate your time.
Thanks and Regards
Mahesh

Hello,
You may use CEKKO-REVNO and set version as characteristic of release class. Then any changes to contracts will trigger release procedure.
Hope this helps.
JM

Contract Release Reset when decreasing the Value

Hi,
As per our client requirement we need to reset the contract Release Strategy when there is a change in Total Value of contract.
As per standard behaviour on decreasing the total value of the contract release is not reset.
How we can acheive this.
Regards,

As you already have the answers in your question..
That release strategy will never re-set if the value is decreased.
It always gets reset if the value is increased with earlier value.
Why you want to reset the release when the value is decreased, as the system value which was set earlier already had been released by your approver.
And contract is ready to proceed for further process.
The system behaves like even you decrease the value which was falling under the old value so it will not trigger the release again.
If you want to reset the release again then you need yo increase the value which has not been released earlier..

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

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

Contract Release strategy

Similar Messages

Maybe you are looking for