Migration form W/O Classification to With Classification Release Strategy

Hi MM Experts,
Our client is currently having purchasing requisition release strategy based on without classification. There are almost hunderds of release codes for multiple sites.
Now he wishes to migrate to release strategy with classification. So, Can anyone guide me on what all the cut-over tasks that has to be considered before going live ???
Thanks in advance.
Best Regards,
Devendra Gaware

hi,
first for doing the settings
follow this link
http://www.sap123.com/showthread.php?t=59
all these settings should be done in development server and test it
if it working good
migrate the data to production server
if useful Reward me
Thanks & Regards
Swathi

Similar Messages

Issue with PO Release strategy

Hi experts,
I have problem with Po release strategy in 5 to 10 purchase orders, i have created few purchase orders(2000 Po's) with same document type and company code ..etc and saved, then release strategy has been triggered.
For few purhcase orders release strategy has not been triggered.
If i take 1 po from that few purchase orders(Release strategy has not triggered) as reference and again if i create PO,new purchase order have getting created with release strategy.
Can some body tel how this ican be possible, hope this might be standard syatem behaviour.
Hope i should delete thos e purchase orders and i should create new PO's instead of of old PO's (Without release strategy).
Some experts can share their experiance in this regard.
And how i should proceed further with this issue.??
Thanks

Hi,
You issue in your system has 2000Nou2019s purchase orders with release strategy has been triggered but 5 to 10 purchase orders do have release strategy.
& when you are creating a new PO with reference to old purchase orders (which release strategy has not triggered) and on saving NEW PO created with triggering release strategy.
Cause for above:
PO which release strategy does not trigger because the purchase orders are created before setting release strategy for PO. Those PO triggered release strategy and all are created after setting release strategy for PO.
Action:
Its completely business call for business users to go for options:
Option-- >1# You can use same old PO which release strategy does not triggered, do GR and all other process
Option-- >2# You can create new PO with reference old PO which release strategy does not triggered and upon saving you will have new PO number with release strategy triggered, then release PO & do GR and other related process.
Regards,
Biju K

Shifting the PR without classification to classification release strategy

Hi Sap Guru,
I have deleted the PR release strategy without classification and configured PR release with classification in dev server.
Now before putting to production server I have to delete the old one and transport the new one. I have done the same procedure in Quality server but while tranporting the request the old one is not deleted and new strategy is also not mapped in Quality server.
Let me know which sequence I should delete the without classification in the system and incorporate the new release strategy with classification in live server.
Thnx
AC

When you deeleted "Without classification". the chnages were supposed to be transported to Production all the way.. first
This should be followed by your configuration through Classification.
The order is :
Characteristics first- BD91
Class- BD92
Your configuration and any other custom changes
and Classification data- BD93 in the very end
If you have messed up,
delete your strategies first, and then your classes and then your charcateristics .. transport them and restart the cycle

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

Problem with my release strategy (PR), Please help

Folks,
I have designed a release strategy with three characteristics:
This is what I entered in characteristic
1.PRQuantity with table name MEREQ3211GRID and Field :MENGE
2.PRmaterial # with table name RMMG1 and Field :MATNR
3.PRPlant with table name RMMG1 and Field :werks
the value for PRQuantity is >= 10000,000.
Also, I have set the indicator for (allow interval) in characteristics
Classes, procedure with classification, Release startegies are all proper.
I am getting the Release startegy tab in PR, but the problem is when I adopt a PR to create a PO with PO quantity >=10000, the release starategy gets picked up, which is perfect but it is also getting picked up with PO Quantity <=10000.
I dont understand why is it getting picked up for <=10000..Please suggest!!
Thanks in advance!!
Megha

Megha,
In your original post you said,
"1.PRQuantity with table name MEREQ3211GRID and Field :MENGE
2.PRmaterial # with table name RMMG1 and Field :MATNR
3.PRPlant with table name RMMG1 and Field :werks"
Per documentation I have seen, the table you should use for your characteristics for PRs should be CEBAN and CEKKO for POs. Here are some links to SAP notes you may find useful.
[365604 - Release strategies in purchasing|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=365604]
[493900 - Release Strategy|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=493900]
[672719 - Release strategies in the service|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=672719]
Note 365604 may be by far the most descriptive of how to set up the entire process. Hope this helps if you are still having problems.
Regards,
Paul

How to block PR creation with no release strategy

Hi,
We have this PR release strategy implemented. Currrently, user are able to create the PR even there's no release strategy determined. Thus, PO can be created as the processing state is "02 Active".
Would like to block user from creating the PR if there's no release strategy determined. How should we do in order to achieve this?
Many thanks in advance.
Sue

Hi Sue
Assuming that you are using release with classification.
Create a new characteristic for PR document type (CT04)
Attach this characteristic to your Class (CL02)
Create new release strategy and in Characteristic data you will have to assign all your PR document type. This will ensure that all the PRs need to be released.
Regards
Rajesh
-Do reward if this is useful.

Verison Management with PO release strategy - CEKKO-REVNO

Hello,
I'm a bit stuck... I'm trying to do a PO release strategy using version management, were the PO goes through a release strategy if the PO gets changed (not the intial PO creation).. So once the field RENVO is greater then 0, it should go through R.S.
I've read to create a characterstic CEKKO-REVNO and then assign it as a valuet <0... I intital;y created it with a NUM Data type, but the ABAP dictonary overides it with a CHAR instead... So I read to mark the value as a default value (<0)
However, after I add it to my class, I go to the define release strategy - classifcation section (to add the value <0) I'm getting a value inconsistency check.
How do i setup this characterstic so I can use it in release strategy?

Based on adding 00000000 the release strategy will work when its version 0 (intial). However, I'm trying to have it so it goes through a release strategy when the version is 1 or greater...
It seems like I cant get the strategy to work for more then one version... I can get it to work for version 0 but no others, or version 1 and no others etc...
I need to have it some it works for anything greater then zero, in which i tried <0000000 and even >000000
I also tried adding 000001, 000002, 0000003, 0000004 etc.. An although the release strategy tab is still applying, it will NOT result to a blocked status...
I cant get this to work... How should the characterstic value look to get this requirement?
Edited by: farmerj3 on Feb 20, 2012 3:16 PM
Edited by: farmerj3 on Feb 20, 2012 3:43 PM

HR organisation Structuer Link with PR release Strategy

Dear Gurus,
As per our organisation, once the PR is created, it has go to the Cost Center Owner and it has to follow the HR organization structure. we have 200 Cost centers in different departments.
Please help me how to configure this with HR organization structure
Your help is most appreciated and Full point will be rewarded.
Thanks
RS

Neetu,
Hi Neetu,
My Release strategy working fine and nothing wrong with it. My question is, why only NB type is falling for Rel Strategy. I think I found answer from Rosa's Answer. If you check overall release at Document Type, then that document type falls for Release Strategy.
Thanks all. I am closing this with Answered and points goes to Rosa...

Multiple release of Service Entry sheet in ML85 with a release Strategy

Hello Techies,
We have requirement where in we need to each release service entry sheet created in each month.
We have created a release strategy and now using ML85 for releasing SES instead of ML81N.
Is there any process so that all the SES are released at once(Mass release) .
Thanks
Jayashree

Hi Dear,
you select the SES as per your Release code and Code Grp, henceofrth the no of service entry sheets will be display you can choose the multiple Entry sheets and select the green flag w/o coming to the same T-Code again and again.
Hope it will help you.
Regards,
Yawar Khan

PO Release Strategy not changed after deletion of few line items with less

Subject : PO Release Strategy not changed after deletion of few line items with less Total PO
Dear Friends
We have issue with PO Release strategy. We have created the PO. with release strategy with multiple approvers. After approval of first approval manager , one of the PO line item got deleted and Total PO value is reduced . The new PO value should have changed the PO release strategy. But it is not changed. Old release strategy only showing in the PO which is wrong.
Details of the PO
PO no 4500000123 with 5 line items Total PO value : 100,000 USD Release strategy : AB
PO line item 5 deleted. Now total PO value changed to 50,000 USD and the PO release strategy should have been changed to AA but not changed. Still showing PO release strategy AB only.
Are there any OSS notes available to correct his bug.
Please let me know if you need more details
Thanks in Advance
Thanks
MVS

Hi,
release indicators change it to 4.It may works. Please explore to all 6 indicators..........
i.e,
1-cannot be changed
2-changable,no new determination of strategy
3-changable,new release in case of strategy
4-changable,new release in case of strategy or value change
5-changable,new release if new strategy/outputted
6-changable,new release if new strategy or value changed/ outputted......
And check Characteristic description and value in Classification of Release strategies ........
I hope this will help you. Thanking you.
Regards,
Venkat.

Why PO is automatically assigned with release strategy?

I created a PO with PO document type NB and NB is not assigned with any release strategy.
But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO. Why?
And only when the PO is in held status, there is no release strategy assigned to NB PO.
Is the normal ERP behavior?
I only assigned a release strategy to PO document type DB, which means dummy document type.

Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

Purchase Order E-mailing with Release Strategy

Hello,
We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
Print Programs:
/SMB11/FM06P
/SMB40/FM06P
SAPFM06P (Sapscript Only)
Forms:
/SMB11/BL_MMPO_L
/SMB11/MMPO_L
/SMB40/MMPO_L

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

Chek budget in PO with release strategy

Hi
When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
Thank's
serge

Normally checks like those happen once the PO is released ( example - output is not allowed etc)...
You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
Name of the Enhancement: - M06E0004
Name of the function module: - EXIT_SAPLEBND_002
Hope this helps

PR release strategy with classification

As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.

Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

With classification release procedure for PO

Dear Experts ,
here one issue is with classification release procedure for PO
when I create characteristics
in Additional data
table name :-- Cekko field name :-- match code
enter
click all sec charars then which block I select to go next screen
and fill name is right or ?
please help me

hi,
in additional data field you have to give the field name of characteristic you are maintaining. like if you want to maintain characteristic as document type of the PO then we have to give the field name for document type mentioned in table CEKKO i.e. BSART.
then you have to do the value assignment. here you have to tick the check box for "NOT READY FOR INPUT".
JASH

Migration form W/O Classification to With Classification Release Strategy

Similar Messages

Maybe you are looking for