Contract rel strategy

Gurus,
I have congfig Con rel stg.I rel it.Then i go & change the qty & value.The sys prompts a msg,rel liable to be rest.But when i go try to rel again,the sytem says no suitable documents found.

hi,
check for the release strategy set up options ie, under release indicator settings...
here set the changability option and for fine tuning changebility % value for your release ID....
You can use option 4 or 6 depending whether you want to see relevent changes with regards to output or not...
Regards
Priyanka.P

Similar Messages

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

Po rel. strategy

Hi,
In p.o rel. strategy we have the three stage release status. First A( say) will rel. then B then C. we have released lot of p.o in the same manner. Now we want to change the rel.status to two step. That means A will release then B will rel.the document as the final rel. authority. But in the previous P.O created which was subject to three stage rel. status has been already reduced to two stage. Where is the setting so that it will not effect the old p.o rel. strategy procedure.

Hi,
For this you have to create two release strategies as given below:
1. For old PO's
Add a new characterstic (Say DOCUMENT_DATE) to the old 3 level release strategy having value as before today's date (i.e. <13.06.2011 ).
2. For new PO's
Add a new characterstic (Say DOCUMENT_DATE) to the new 2 level release strategy having value as on & after today's date (i.e. >= 13.06.2011). Rest all the characteristics will be same as the old 3 level release rstrategy.
The characterstic DOCUMENT_DATE will have Table name as CEKKO & Field name as BEDAT (i.e. PO creation date).
So, For Example if you will go for making any changes to PO created before today's date will pick the same old 3 level strategy however for creation or changes to PO's having creation date today onwards will pick the new 2 level release strategy.

Rel.strategy

Dear cons
We have created one user I.D (procurement) for creation of purchase requisition. One person is only able to approve the document. We have created another I.D for finance deptt. For thr Pur. Doc.we want both person can approve the document. i.e- first fi ance deptt. Will approve then procurement deptt. Will approve. Because at the time of creation P.R the purchase deptt. Enters a wrong G/L account. To avoid this first it will come to finance deptt. So how can you make settings in the release strategy. If I create two release code & enter in the rel. strategy of procurement I.d Then How it will come to finance i.d. pl.look into the matter. Without workflow it is possible or not.. Basis people has restricted the user i.d.pl. give some hints.

Hi Nirupama,
Create the 2 release codes for that Release strategy.First release code should be for Finance dept 2nd should be pur dept user.
Give the authorization to 2 user ids with release codes one for Finance dept and another for Pur dept with the help of Basis Consultant.
Once the Pur dept user creates the Pur requisition.In the PR release tab the 2 release codes will appear . Then the first release code should be Finance dept user. Then final release can be Pur dept user.
So that before releasing the PR the finance dept user will correct the G/L account and then release the PR. Then the Pur dept user will finally release the PR for procurement.
Hope you understand
rgds
Chidanand

PR Rel Strategy scenario

Hello
I have 2 requirements in PR Rel Strategy scenario.
1.No changes should be allowed in the PR once the PO is created.Can we fulfill this requirement by assigning changeability Indicator 1.
2.Once the PR is released and PO created it should not allow to revoke the release.
Any ideas on this?
Regards
Vaibhav Mahajan

Hello Afshad and Swaminathan
Users are revoking the release after the PO is created.With changeability indicator no changes are possible via ME52N but revoke is possible in ME54N.
Bases on the links given by Afshad I am checking if we can use the User Exit but not sure which user exit will work.
Regards
Thanks for the suggestions.

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

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

Rel. strategy is not triggered while creation of PR with cost centr

Hi Gurus,
While creation of PR release strategy is not getting triggered with cost centre BCWSV870. But release strategy of PR triggered for cost centre BCWSV852 (In PR changed only cost centre as BCWSV852 instead of BCWSV870). Both cost centres are similar and the both cost centres are exist in characteristics value in CL20N for the same release strategy.
My question is why for one cost centre triggers release strategy triggers and for other cost centre release strategy is not triggered. Can you please tell how come this and rewarded for answer this.
With regards,
C. Sundar Rajan

Hi,
In regard to problematic PR with cost center BCWSV870, was your PR maintained with only one line item? or multiple line items?. In additions, when defining cost center as part of the release strategy structure, did you enter all cost centers with leading zeros? Tak a further look into OSS Note 365604 for your further investigation.
Cheers,
HT

Problem in rel.strategy

I created two doc. Type for P.R. i.e- zno1, zno2. I have one user i.d- MMCONS. For releasing P.R Document (ZNO1) we have rel code-01 & for releasing P.R Document (ZNO2) WE HAVE REL. CODE -02.WE HAVE CREATED CHARACTERSTICS FOR DOCUMENT TYPE, PLANT & USER I.D. Is it possible to give authorization in one user i.d. to release the different doc. type P.R in a single user I.D.waiting for your early response.
nrk

Hi
Try with assigning release code 01 and 02 to same user in authorization
Vishal...

Release strategy:ME53N : Older PR documents shows, modified PR rel.strategy

Hi Friends
We have updated the sequence of release codes for certain PR release strategies. But when we moved the changes production, i observe that all the older PR documents (Which were released last year and completed) also shows the updated release strategy in transaction ME52N/ME53N.
Can someone pls some explain? Is this normal?
SAP doesnt store the release strategy and its sequence of release codes, which were determined at the time of document creation?
Thanks for your help...Raj

Hi,
There is no change in the older documents.
The documents are older by few years.
I have checked few documents randomly, the tcode ME53N shows only the updated release strategy.
I did some investigation today on this.
i think system will not keep the release strategy pertaining to document creation.
It will just store Release Group and Release strategy in the Purchase Requisition tables (like EBAN).
And when ever we try to display the document it will go and read the release strategy sequence from relevant tables.
Hope someone helps to validate if my investigation is correct.
Good day..

Rel strategy for PR

I want to create Release Strategy for PR as follows:
For Standard PR (NB) one level of release is always required.
(eg HOD will have to release all the PRs of a department)
How shall I proceed pleae guide in detail.
regards
VS

Hi,
Release Process for PR is as below
1 Create the Characteristics for your release strategy based on fields of table CEBAN.
2 Create a class of class type 032. You have a free choice of names for the new class
3. Assign your characteristics to the class on the tab page Characteristics.
4. Create Release Groups
5. Create Release Code -HOD in your case
6. Create Release indicator -all type of PR or selective
7. Define Release prerequisites
Hope you will explore after this overview on RS.
Regards,
Ashish

Contract rel strategy

Similar Messages

Maybe you are looking for