Transport characteristics+classes of clasification system: release strategy

Hello,
Someone know how I can transport the characteristics+classes of classification system for the MM release strategy.
I think that the values must be assigned manual in each client but I do not have to recreate manually the characteristics+classes.
Cheers,
Marta

Hello,
The OSS solution to transport the clasification is via ALE.
I will create a LSMW batch to load the clasification system.
Thank you very much for your comments.
Marta
The classification data need to be transported by ALE as described in
notes 86900 and 45951. The only other solution is to enter the data
manually.
You can obtain information about how to set-up ALE in the Online
Documentation CD (R/3 Library -> CA - Cross Aplication Components ->
Business Framework Architecture -> ALE Integration Technology ->
ALE Quick start).
However, if you can't set-up ALE, you can re-create the classification
data again in your target system.
For that you have to:
1. assign new values to the characteristic master data (trx. CT02)
2. assign the new data to the classification system (trx. CL30)
3. verify the consistency with trx. CL24. Please see note #186809.
For more information, please see note #365604.
Please check the answer from development regarding this issue:
"The transport of release procedure customizing data can only be done ina restricted manner. Please take a look at attached Note 86900 and
follow the procedure described in this note, in order to correctly
transport your release strategies.
Classification data can only be transported via ALE as per note 45951.
Note 45951 explains what class data for the release strategy will
be distributed from one system to another.
It does not describe how to implement as this involves a lot of
explanation and is truely a consulting issue. Customer may consider
remote consulting to do the set up."

Similar Messages

Transferr clasification of release strategy

Dear all,
I want to transfer the clasification of my Release strategy to the productive system.
Is it possible? only the release codes are transferred through requests.
How can i transfer it, as i do not have permission at my client's productive system to maintain it.
Thanx in advance

Aldais
SAP Note 86900 explains that you cannot transfer classification. IF you dont have access to service sap give me you email ID i can forward that note.
Summary
Symptom
The transport of Customizing data in the release procedure area 'Release strategies' can only be used in a restricted manner. The 'Transport' function displayed in Customizing under 'Table view' only takes the release strategies into account but not the dependent data of the release prerequisites, the release statuses and classification data.
Thanks
Reeves

P Req. Release Strategy not Transported

Hi,
For Configuring the Purchase Requsition Release Strategy, We have Created Characteristics and Class in the Configuration Development Client. Created Release Groups, Assigned Release Codes with the Release Group, and Assigned Release Group with Release Strategy with Classification. Tested PR Release Strategy for the given Classification Values the Release Strategy triggered.
We have Created same Charateristics and Class in the Testing Development Client (Since the Characteristics and Class are not Transportable). Transported Release Groups, Release Codes and Release Strategy from Configuration Development Client to Testing Development Client. When we check the Release Strategy Classification in the Testing Developmemnt Client, system showing Classification Error.
Please let us know whether the Release Strategy Classification Requests are Transportable or not.
Ravi

Dear Ravi,
The Release Strategy Configurations can be transported, in respect to the requests transported.
But the assignment of the Characteristic Values to the respective classes needs to be done in respective destination clients. Since teh assignment will get transported.
To Do the same, please use transaction CL24N, Enter the classes Used in your release strategy and assign the respective Characteristics Values.
Hope this will serve the need.
Njoy SAP
- Regards,
Saravanaganesh

Release strategy characteristics

Hello Experts,
I am looking to have a report / query where I can see the characteristics values for a specific Release strategy combination .
It should show Release Strategy , Group , Release code & their respective Chararcteristics .
I have tried table AUSP, CAWN , T16FS but this does make up the required report .
Regards,
Lawrei

Hi Lawrei,
It's not a problem to find a report combining the release group, the strategy and the corresponding values, since all reside in the classification system. CL6BN is one way; another report with the characteristics as columns is CL30N - search without assigning any values in the class that you use for release strategies. The resulting list is presented as an ALV report which gives you the options to add columns - here you can add all the characteristics in separate columns. Don't forget to click the pushbutton "Expand multiple values" if you have such characteristics.
Release codes assigned to strategies are stored in another table, T16FS. You can list it using SE16N, then download both to Excel and make a simple lookup using the release group/strategy combination.
BR
Raf

Release strategy class

Hi,
Can we assign the two release class for the po release strategy.?

HI,
No,we can assign only one class.but we can assign multiple characteristics to this class.
Characteristics are used to define the criteria on which you wish your purchasing documents are to be released. For example it can be plant , value, Document type, Material Group etc.
The selection is based on the fields available in the tables for release, Like CEBAN for Requisitions and CEKKO for Purchasing documents.
If you want that Value shall be a criteria for release then you will make a characteristic for value, and define the value or value ranges, you have the option of going foe single value or multiple values. Like wise you can make diff Characteristics as per the Client Requirement.
Now all these characteristics can be grouped under a class.
Now this class is assigned to a release group.
Then when you create a release strategy, you can make many strategies under one group, where in you shall get the option of selecting value of Characteristic to be used in release stategy,
For eg. say I have a characteristic Z_Value. with values 1- 10000, 10001 - 20000. and other characteeristic as Z_Plant, with values 1000 and 2000.
Now you add this to a Class say Z_rel.
Assign it to a Group say 01
then while creating a release strategy say s1 unde group 01 you can choose plant value as 1000 and value as 1-10000.
so whenever there is a PO of value b/w 1-10000 and plant 1000 it will go as per the release strategy s1.
hope its useful for u
Venkat.

PR Release strategy

Dear All,
We want that if any user change account assignment(Cost center,G/L.Order etc..) in PR the release should reset and need reapprovals.
Please let me know how we can achieve this.
Thanks.

Hi ,
           In standard design system only considers characteristics from
CEKKO structure for release strategy consideration. But it will not
stop us in selecting the other characteristics.
Please go through the IMG help of release strategy, will give good
information.
I think you have already read the note:
The characteristics of the class used must all be linked to the
       corresponding fields of structure CEBAN or CEKKO (for purchase
       orders)...."
Characteristics which are created for the release strategy with
classification MUST access communication structures CEBAN or CEKKO since
during the strategy determination, the system cannot access any other
tables or structures.
If the characteristics refer to fields which are not contained in
structures CEBAN or CEKKO, the corresponding fields can be added to
communication structure CEKKOZZ or CEBANZZ, or an append structure can
be created for CEKKO or CEBAN in which new fields can be included.
If you want to use new defined fields as part of the
release strategy clasification, you should use enhancement M06E0004
(User exit "exit_saplebnd_002").This user exit allows you to use the
user fields in strucure CEKKO to include additional data.
Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and
control them through user exit "EXIT_SAPLEBND_002. Otherwise new field
will not work.
As you very well know SAP has provided the following customer exits
which allow us to change the communication structure for determining
the release strategy
Purchase requisition
                       M06E0002 - for item wise release
                       M06E0005 - for overall release
External purchasing document
                       M06E0004
I hope this helps!
Regards
Vijayesh V V

PO release strategy - release code

Hi Experts,
I have completed the release strategy and transported to production.
However noticed that the release codes that has been configured earlier wasn't in the production.
Is there a way to update the release codes in the production besides using SPRO (no authorisation for maintaining - only display) like using CL24N to update the characteristics?
Thanks and regards

Hi,
Please first check the attached notes that refer to transport issues.
365604   FAQ: Release strategies in purchasing
186809   OMGQ/CL24: Inconsistency for release strategy class
   86900   Transport of Release strategies (OMGQ,OMGS)
   45951   Transporting class data: system / client
   10745   Copying classification data to another client
The classification data must be sent over using ALE. It does not get
transported directly. Notes 45951, 86900 and note 365604 should help.
Please follow the instructions in note 45951.
You can obtain more information about how to set-up ALE in the Online
Documentation CD (R/3 Library > CA - Cross Aplication Components >
Business Framework Architecture > ALE Integration Technology > ALE Quick
start).
However, if you can't set-up ALE, you can re-create the classification
data agin in your target system. For that you have to:
1- assign new values to the characteristic master data (t-code CT02)
2- assign the new data to the classification system (t-code CL30)
3- verify the consistency with t-code CL24. Please see note 186809.
For more information, please see note 365604.
The transport of release procedure customizing data can only be done
in a restricted manner. Please take a look at attached Note 86900 and
follow the procedure described in this note, in order to correctly
transport your release strategies.
Classification data can only be transported via ALE as per note 45951.
Note 45951 explains what class data for the release strategy will be
distributed from one system to another. It does not describe how to
implement as this involves a lot of explanation and is truely a
consulting issue.
There is another possibility that you could take into consideration for
the classification is to import them via batch input:
RCCTBI01 for creating characteristics
RCCLBi01 for creating classes
RCCLBI03 for classification
Best Regards,
Arminda Jack

Escape Release strategy based on purchasing group

Dear Experts,
In our system, PO release strategy is set up,
But, some of the POs are not subjected to release strategy because they belong to a perticular Purhasing Group (P01).
Where this set up is done?
Regards,
Shashidhar

Hi Shashidhar,
In your system it seems there is a characteristic created for Purchasing Group, if you want it activated for a particular Purch Group, then please do the following
Determine the strategy that you want to be called ( You can see any existing PO to find it out), once done, you need to identify the characteristics and class
SPRO-MM-Purchasing-Purchase order-release strategy, define release strategy, select your strategy and go to details and click on classification, in case you get an error and not able to, click on release pre requisites, come back and then try again, in classification you will get to see the various characteristics maintained and also the class name at the top.
Once you have done that, please go back to the node Edit Class, please put the class that you obtained earlier and get the characteristics for Purchasing Group.
Then go to the node Edit Characteristic, put your characteristic name say PO_RELEASE_EKGRP, Click on the tab values, and add your Purchasing group here and save it.
Then go to transaction CL24N, provide the class, and select the release strategy you are interested in, and select change, and detail, there for the characteristic for Purchasing group, you can add the previously added Group, and you are good to go.
Please let me know if this helps.
Regards
Shailesh

Release strategy modification

Hi all,
I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document & 2. Purchasing Group .
Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
Please help! How can I achieve this...
Thanks,
Rajan U

Hi,
As needed, you created one more charterictics CEBAN - CFWRT and included it in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
1. <= 5000 INR
2. > 5000 INR
Craete release group as PO and create two release codes C1 & C2.
Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
Regards,
Biju K

PR Release Strategy Characteristic Changes

I created several characteristics for a purchase req. release strategy. I added an incorrect value and then deleted it on one of the characteristics. Is there anything else that needs to be done to ensure that value is really deleted?
I'm receiveing an error when I ALE that I have documents that won't post for the error:
REQ_PURCH_ORG : Value "Structure Exists " not found
Structure exists is not a value associated with this characteristic.

Thanks for the solution that helped me to understand PR Release much better.
Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
In my PR Release strategy with 2 levels I have these below things:
Rel Groups : 1 Group with name AA
Rel Codes: For AA is A1, For another AA is A2.
Rel Indicator: nothing is selected, am not sure what to do in this step.
Rel Strategy : For AA is S1, For another AA is S2.
I created class Z_GFWRT but am not sure which group I should assign it AA or I have to create another new group for Overall release.
After I checked the release strategy the system is giving me this below message.
No release group exists
Message no. ME_RELCHK014
Please can you walkme through in this process. This is first time I am creating a PR Release.
Thank you Very Much
Imraan

Scheduling Agreement Release Strategy Issue

Hi,
We have a typical problem in Scheduling Agreement Release Strategy.
Once the SA is released for the first time it should restart the release strategy again if there is a change in Quantity or Value or Purchasing group. The release strategy is getting restart for some of the release strategies and not for others. I compared the characteristics, class for both the release strategies and I am not seeing any difference.
Can anyone please help me in this regard.
Thanks in advance.
Regards
Ram

release strategy can be rerigger in case where qty or price change and the changes is over the percentage you defined for Release indicator
goto release indicator config and in SPRO for release strategy and check the Value change %
maintian 0.1 here
so any change above 0.1 will retrigger
and maintian value 4 in chgable field.

Release strategy for PO and Service Entry Sheet

Hi
I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
should I maintain the same characteristics for service entry sheet ?
the approval will be the same for both

Hi,
The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
Note: The release strategy must be based on the structure CESSR.
The PO release strategy is based on the structure CEKKO.
For the SEs release strategy you must create a different class.
Regards,
Edit

Issue with Purchase Requisition Release strategy

Hi Gurus,
We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group
3.     Value of the PR
As a result of PM module implementation, there is requirement of additional 30 release strategies.
We configured them but one more field of doc type was added in the characteristics fields.
Now the release strategy was based upon following fields:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group-(Configured against new purchasing groups )
3.     Value of the PR
4.     Document type of purchase requisitions.
Classification data was accordingly maintained that is for older release strategies,
Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
We are in testing phase. Many of the test scripts failed due to this issue.
Quick response will be appreciated!!!
Thanks & Regards,
Niti

Dear Niti,
Please check if your "overall release" indicator is consistent for document type and release group:
a)SPRO:MM-PUR-PR-Define Document Type
"overall release" indicator
b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
->Release group
"overall release" indicator
Regards,
ian,Wong Loke Foong

Create Release strategy for PR

Dear experts,
We have one class FRG_EBAN for PR release strategy and there are 5 characteristics in that class. Now i need to create a rel. strategy with 4 characteristics . Can i create a new class for PR release strategy?
Please help.
Thank you
King regards,
Zusen

Thank you SAM for your reply.
In the existing class FRG_EBAN one of characteristics is Account Assignment Category. If i am not wrong which cannt be blank. and i have seen that all characteristics included in the class needs to be maintained in the release strategy.
I need to create a release strategy of PR in which no a/c assignment category will be maintained. but in existing scenario i cannt create release strategy without giving value in a/c assignment category characteristic in the characteristic tab of release strategy.
Please suggest how to resolve this problem
Kind regards,
Zusen

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

Transport characteristics+classes of clasification system: release strategy

Similar Messages

Maybe you are looking for