In ME38 can we add Version Management , Release Strategy

Hi,
Is there any way to add Version Management and Release strategy in ME38.
Thanks & Regards
Sudhansu

Hello ,
Please check the settings
Here Activate (Tick) for LPA .
please check and revert back.

Similar Messages

Can we implement workflow for release strategy in 4.7

can we implement workflow for release strategy in 4.7 for PO's please provide some documents.

HI,
Check the links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30c81e21-cd00-2c10-bbba-edb8ce4961be?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70fef212-b6cb-2c10-e085-c84b80d7068e?quicklink=index&overridelayout=true
Regards
KK
Edited by: Kishore Kumar Galla on Mar 19, 2010 3:40 PM

Relation between Version and Release Strategy at Purchase Order level

Our requirement is as follows:-
Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
Price-A can be equal to Price- B, Less than or greated than.
I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
and when i delete the version condition, we can see the release strategy tab in the PO.
Thanks in advance,
Vikas Rander.

Our requirement is as follows:-
Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
Price-A can be equal to Price- B, Less than or greated than.
I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
and when i delete the version condition, we can see the release strategy tab in the PO.
Thanks in advance,
Vikas Rander.

Can't add account manager

I've recently returned to Verizon after a disastrous and short lived relationship with Sprint. My wife and I had to terminate our contract with them because of several issues and because she was the one that cracked first, she was the one that got to call and scream at them. Since I was the account owner and she was halfway across the state at the time there was a great deal of confusion over trying to get her access to the account so she could even discuss the problems we were having, let alone try to make changes to the account (which ended in our leaving their service). I am again the account owner for Verizon and I was quite thrilled to see that I could designate account managers on My Verizon, which would prevent such difficulties in the future. A couple days after getting the account started went to do just that online.
I changed the billing password with no problems, but when I try to complete the process of designating her as a manager I get an error message saying that I cannot do that online and I should call customer service. Not 'You cannot do that online at this time' or 'That service is currently unavailable online' but a straight up 'You just cannot do that online.' I get as far as putting in her name, number, and address, and when I hit continue - error message. I've tried three times in the last two days, with the same result each time. Sure, I could call customer service or go to a store, but isn't enabling it as a function within My Verizon supposed to make it easier? I've even gotten a welcome email promoting it as one of the things I should do to set up my new account, along with things like setting up alerts for data usage and paperless billing.
I don't like calling customer service for cell service providers because I have never had a good experience with any company in doing so, and going to the Verizon store is always at least an hour visit while I wait for the two people ahead of me to finish their business. I love the convenience of managing my account online, but if you're going to promote that I do so, maybe you should actually make it so I can, rather than have me chase my tail trying.

That's great that you need to be with Verizon for 30 days before it becomes available. I have been with Verizon for several years. I am trying to setup account managers in my Verizon, I have a request pending from an account member to the account owner to become an account manager. Every time I, as the account owner, click accept on the request, I get the same error message. "Assign Account Managers
This option is temporarily unavailable in My Verizon. Please contact Customer Service at (800) 922-0204 if you'd like to add, change or remove Account Managers.
We apologize for the inconvenience."
This same error message has been showing for months. The last rep I spoke with de registered all of my my Verizon login accounts so that they can be re registered. How do I get my lines setup as an account manager?

Version management for POs

Dear friends,
Iam implimenting Version management for purchase orders.I have got doubts like;
1)---In IMG side ,under setup change displays node, we need to enter all the field names of purchase order document type wise, ..i.e.
we have got three doc.types of POs,NB,ZCP,ZCO,then Header and item details fields of PO shall be entered against each doc.type in this node.
like -NB-EKPO---MATNR
NB-EKKO-field
We need to enter tables as EKKO and EKPO and
all the fileds are to be entered for all the doc.types.
we need to enter all the fields including header fields and item fields ,
2)----For header fields,if i change the data,version is not creating,
3)--At item details ,after release of the PO,if i change the data,if i save the document,it is saving without automatically closing the version.We need to manually close the version.
I have given error category E for application MEDCM for 14,19,22,eventhough system is not giving error.
Atleast provision should be there to give error if user doesnot close the version manually.
Please suggest for my doubts.
Regards,
Magana

Hi
For a combination of purchasing organization, document category, and document type, you can:
<b>Activate version management</b>
If version management is active, changes to a purchasing document are managed in versions.
<b>Define field selection for versions</b>
You can specify the attributes certain fields of the version are to have: mandatory entry, optional entry, display only, field suppressed.
Set the message ststus as follows
MEDCM     014     Purchasing document &, version & in process     W
MEDCM     019     Purchasing document &, version 0, still in process     E
MEDCM     021     Not all version-relevant changes were cancelled (&1)     W
MEDCM     023     No unprocessed message exists                         W
System will allow to manually close the version .Version 0 will be set automatically .After that system will allow to manually close the version.
I dont think you will face probelm.
Regards
Sunny

Can we add extra row in colorpicker?

Hi all,
I want to add one extra row below all colors in color picker. If you have seen word color picker, it shows you recently used colors.
Is it possible to add extra row in color picker?
Thanks,
-Chandu

Hi,
SAP has given user defined fileds in CEKKO communication structure which you can use by using user exits to fill in CEKKO.
These fileds you can use as characteristics for release strategy.
Details of user exit:
M06E0004 Changes to communication structure for release purch. doc.
EXIT_SAPLEBND_002, Changes to Communication Structure for Release of Purchasing Documents
Description: User exit that control the values in CEKKO for the Release Strategy.
Regards,
Shailesh Mackwan

PO release strategy ONLY for change

I have a requirement to only have a release strategy for a purchase order only when it is changed
The problem is that even if I can disable the event to be triggered when created, the release strategy is written down to the EKKO-table when the PO is created meaning that the purchase order still needs to be released before being used for example in MIRO.
How can I avoid having the release strategy written to the EKKO-table when the PO is created?
How can I have it written to the EKKO-table when it is changed?
Good answers will ofcourse be rewarded with points!
Edited by: Snowroller on Feb 11, 2012 4:00 PM

Dear,
Check this and try. Not tested.
Set up Version management for Purchase order and keep all relevant fields of PO relevant for version change.
Add charaecteristics PO_Version value as 00000001. So, When you create PO the version will be 0 so no release strategy. Whenever relevant fields changes the version changes to 0 to 1 and release strategy triggers.
Try this option.
Regards,
Syed Hussain.
Forget to mention please search with 'PO release strategy based on Version Management in SAP' you will get many SDN posts.
Edited by: Syed Hussain on Feb 11, 2012 7:27 PM

Release Strategy not working for MRP generated PR

I have one qurey. Currently we are release strategy for normal PR.Now client want to activate release strategy for MRP generated PR.
current Release Strategy for normal PR configured as following.
Purchase requisition document     RV
Purchase requisition document     ZADV
Purchase requisition document     ZIMP
Purchase requisition document     ZSER
Purchase requisition document     ZSTD
Purchase requisition document     ZSTR
Purchasing group     A01
Total value of requisition for     > 1.00 INR
Creation indicator (purchase r     Realtime (manual)
Overall release of purchase re     Yes
For MRP generated PR I add creation indicator B - Material requirements Planning.Even after add creation indicator release strategy is not triggering for PR.
To trigger PR any setting need to do other than add creation indicator.
Regards
Sathish

Hi
You don't have to include creation indicator as parameter. Check in what documnet type MRP PR is generated. You can see it in t.code OMDT. At document type level also you can manage it. You need to include creation indicator only if a seperate person approves MRP generated PR.
To know how to configure release procedure see the below link
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Trigger PO release strategy

How to retrigger PO release strategy after delete the items in ME22N?
It only be retrigger when we increase the price.
Any user exits dat retrigger the changes made?
Where is the user exits located?
Or any standard configuration need to be done.
I already set the Release indicator, changeable = 6, and % = 0.
I am using 470 version.
Please help to provide some solution.
Thanks.
Edited by: Elaine Tang on Jul 3, 2009 8:02 AM

Hi,
As for as I know, SAP has not provided the retrigger of PO release strategy if the Value of PO is decreased than the released PO price. It will only retrigger if PO price is increased than released one.
There is no User exit available for this, you can use the Version management usuage for any changes made in PO using the availble user exits.
There are lot of discussions done on this Retrigger of PO release strategy for any changes in PO -- but till now there is no positive result. Don't why SAP has not taken this issue very seriously.
If any others has found any solutions on this, let them share the information on this .
rgds
gsc

Release Strategy for Preq

Hi SAPgurus...
I have release strategy implemented in my system with 7 level approvals for the Pur. Req . Now i need to Change the release strategy to 4 levels approval based on one of the Characterstics that is the Preq Net Price. Which cud be the best process to ahcieve it , since if i am going to keep the old one and create a new one then wheneve similar characterstics appear the system cant recognize which strategy to apply.......
Please can any one advice me how can i approach ...
Regards
Balaji

Hi Lakshman, Srini & Venki
From ur statements i understand to modify the existing ones , okie as u said i will delete the extra release codes and modify it . Now fine..
What happens when i moved to prodcution these changes then, say if i have Preq
with older version of release strategy how it impacts.....How i can handle this in
effective manner...To my knowledge i think whenever if i go for a change in preq the new release strategy will be affected....( In this case its fine) what abt the ones which doesnt need a change and has to be released....
Thanks for the time ...
Regards
Balaji

Release Strategy for Plants

Dearest Friends,
we have Plant A & Plant B
for Plant A     PR and PO <50K will be released by R1   and value >50K   by R1 and R2, R3.
*for Plant B   PR and PO >50K will be released by R1, S1 and >50K R1, S1, R2, R3.
how can we define the above release strategy.
hope you guys will help me.
Thanks and Best Regards,
Rajesh G

Hi,
for Release streagty either for PR or PO.
Steps :-
1. Create a Class T code CL01....Put Class type "32".
2. Crate Charateristics CT04 for ur case
Suppose for Plant ....in Addidtional data Put Table Name CEKKO and Field Name - WERKS
For Value ......... maintain CEKKO - GNETW
For PR .....
Table Name CEBAN --- WERKS for Plant
                      CEBAN -- GSWRT for Value
either go to se11, give the table name....u will get all the field there for which u want ur charterstics will work.
3. Assign Charcatristic to Class either in CL01 or cl24n.
3. Now go to Spro --> MM --> Purchase ---> release streatgy
first define Release code as R1, S1, R2, R3
Define GRp and Streatgy....
for Plant A PR and PO <50K will be released by R1
Suppose Grp is XY and Release Ste R1....click on details ....fill release Code R1 and in classification maintain Values <=50 and plant A.
Similarly Mainatin other....
Also u can document from
http://sapdocs.info/wp-content/uploads/2009/07/Step-by-step-guide-of-SAP-PR-Release-Strategy-configuration-a-case-study.pdf
http://sapdocs.info/sap/materials-management-2/automating-purchasing-approval-sap-release-strategy-tips/
Hope Help U !
Regards,
Pardeep malik
Edited by: Pardeep Malik on Sep 19, 2009 11:53 AM

Correction to PO release strategy

Dear All,
We have PO release strategy configured and working fine.
Now there are ammendments happend in the PO release strategy i.e. the value limits are changed also new levels are introduced which will be effectivef fro a particular date.
I want to make changes in the system such that the old strategy will be effective till the specidied date and from the cut off date new strategy will be effective.
Thanks in advance.
Regards
Yogesh Chaudhari

Dear Afshad,
Thanks for your reply.
I have one query.
We have PO version management active. i.e. released PO is changed system should trigger a version and release strategy is re-triggered.
Now If I am changing anything in the PO which is of older date ( i.e. before the new release strategy is active) what will happen to the release strategy.
Regards
Yogesh

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

P.O release strategy

Hi,
With the following requirement,how can we configure p.o release strategy?
Client requirement is that he wants one release strategy with
parameters plant and p.o type are the characters.
And one more release strategy will be based on only purchase group only.
How can we achieve it?
System will not allow two seperate release groups with two seperate release class.
With only one class with above three characteristics,we can't achieve client requirement.
So how can we achieve client requirement?
Thanks in advance and rewarded for useful information...
Regards
Mohan

Hi,
As some of our friends told that maitain the 3 characterstics to the same class and assign the class to one release group,and create 2 release strategies one with plant,document type and all Pur grps except that are in strategy 2 and second strategy with required pur grps( that are left in strategy 1) and all plants,all document types.
you can't leave any of the charecterisitcs blank in a strategy.
here is a example i did
strategy 1:
Document type     NB
Purchasing group     026
Plant     1000
Plant     1100
strategy 2:
Document type     NB
Purchasing group     001
Purchasing group     002
Plant     1000
test 1:
here i want to create a PO with strategy 1, then i created a PO with above combination NB-026-1000/1100 - it was success full
test 2:
here i want to create a PO with strategy 2, then i created a PO with above combination NB-001/002-1000 - it was success full
Please check and confirm the same.
Regards,
batchu

New po release strategy

hi,
i am having xxxxx class for po release strategy with 3 characteristics-(plant, po value and document type)
now i want to have only 2 characteristics with document type and PO value.
again i want to use new release codes for my new strategy, keeping the same class for release strategy.
can i define new release strategy using the new codes?, then what shall be the impact of the same on below
1. already released PO, now want to amend,(after new release strategy implimented)- what would be the effect on PO?? which release codes shall hit the same?
2. already release PO(i understand there wont be a problem in GR, as release ia already effected)
3. new PO shall catch the new strategy- no problem with the same.
for implimenting the new strategy using the same class, can i delete the old release strategy with codes or i just need to remove the value mentioned in the classification view of the release proceedure.

thank u.
my point is while re-defining the release proceedure.
earlier i had 150 release strategies and arround 40-50 release codes. now only 12 release codes
i just need to get confirm, if i create a new release code and assign a new release strategy using the same class(only deleting the plant characteristics), what will happen to old po(released) for which now we are amending.
i assume i need to delete/remove all the data of old release strategy available in classification view, and keeping the release codes as it is in release pre-requisites fr old release strategy.
or just any body briefe me what are all the condition for changing the exsiting release strategy.if i need to create new release code,release strategy by using the same release class.

In ME38 can we add Version Management , Release Strategy

Similar Messages

Maybe you are looking for