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

Similar Messages

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.

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

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

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.

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

PR rel strategy

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
I have created a release procedure for PR by maintaining 4 levels. Have made all the necessary conf. in SPRO & then trying to release the PR in ME54N. But iam unable to release it as iam getting an error
Pr No1 can't be released & Msg # MEPO822.
pls. i neeed a solution for this.
shouldn't i select 4 levels to approve a standard PR
Vineeth

Issue while configuring PO Rel Strategy with more than 17 rel conditions

Hi all,
I am trying to change a PO Rel startegy which has 8 release codes and about 25+ different release conditions already defined. When I am trying change the release status configuration tab I can only see upto 17 conditions. I don't see any work flow activation and I am not sure how intially they maintained all these conditions. Please let me know how to over come this issue.
Thank you for your time,
Srav

Hi all,
I am trying to change a PO Rel startegy which has 8 release codes and about 25+ different release conditions already defined. When I am trying change the release status configuration tab I can only see upto 17 conditions. I don't see any work flow activation and I am not sure how intially they maintained all these conditions. Please let me know how to over come this issue.
Thank you for your time,
Srav

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

ME38 resets Release strategy of Scheduling agreement

Hello,
It seems when the users change the delivery date in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
I cannot understand why this happens.
Has anyone encountered such a problem before.
Thanks
Sunil

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

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

Rel.strategy

Similar Messages

Maybe you are looking for