PO release strategy , classification tab

Dear Friends ,
I am designing the release strategy for PO.
Characterstic designed as- Value / Plant/ Document type.
But while doing the -define release procedure for PO->Release strategy - where in classification TAB , given characteristic are not getting for selection.
Regards,
Mahesh.

HI
Please close the thread,when its solved....

Similar Messages

Transport of Release Strategy Classification

Hi Experts,
Is there any way to transport Release Strategy Classifications.
Regards,
AKS

You cannot transport them (Class and characteristics) . But There is a way to send them accross systems by ALE . ref SAP link http://help.sap.com/erp2005_ehp_04/helpdata/EN/24/903b39878f4205e10000000a114084/frameset.htm . You will need help of an Abaper who has worked on ALE .
If the data isnt large, its safest to manually create class and chars and assign in CL24N .

New purchasing group release strategy classification

Hi all,
I am creating a new purchasing group and need to do the release strategy classification. Please would you outline the process involved including the transaction codes?
Thanks in advance.
JJ

Hi,
Please go through this link, it has all the required information,
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM
In case you encounter any issues, please let me know all details, would he happy to help.
Regards
Shailesh

PO release strategy Classification

Dear all,
I have a question about PO release strategy would like to ask, hope you can give me some advice.
I have about ten release strategies which is used for different requirements.
For each release strateg, there are several Classification.
I am going to set a new release strategy, which only concern some of the Classifications, for the non-used Classifications, I have set a '*' to be the value, but the release strategy does work.
I would like to know is it all Classification should be provided a value?
Many Thanks
Sunny

Hello Biju,
Firstly, many thanks of your idea.
Let me make an example.
I have a clasification (GROUP 1) which has predefined values ('A', 'B', 'C', 'D', 'E', ' ' ), and this clasification was already used in many release strategys.
A release strategy is defined to trigger the release when the value of the clasification (GROUP 1) is value 'A' and a release strategy is defined to trigger the release when the value of the clasification (GROUP 1) is value 'B' ..etc.
For this new release strategy, it does not concern the values of the clasification (GROUP 1). In my setting, if I set a value '*' in the release classification, the release never triggers. What should I set if I would like to ignore this classification for this release strategy?
Thanks your advice again
sunny

RELEASE STRATEGY - CLASSIFICATION

Hi:
The classification part on our release strategy do not appear any more when displayed in config, therefor we cannot release any PO's....
Can anyone tell me how do I set it up again....
Thanks.

Hi Wynand,
Please confirm following process.
1.Create Characteristics( Ex :CEKKO- GNETW)
2. Create Class( Ex: FRG_EKKo)
3. Asign characteristics to Class
4. Define release procedure in which there should be only one REL GP & ONE CLASS attached to it : for Ex : REL Group is PO & then assigh REL CLASS ( FRG_ EKKO ) to it
Then follow rest process for release procedure.
Vivek

P.R - Release Strategy

Hi All,
I am trying to create release stragies for the following.
Charestics : Totalvalue of the P.R
>10,000 - PP(buyer) should release.
<=10,000 - PP(buyer) and QQ(manager) should release.
I tried in 2 different ways.
1)I defined 1 release group, In the release strategy classification tab-- I give both the >10,000 and <= 10,000 value. It did not work.
and
2) I tried creating 2 different strategies for this 2 conditions, but when i create a P.R, for value (less than 10,000) the system picks both PP and QQ. It should actually pick only PP.
Where am i making the err?
Any suggestions.
GP

Hi N
Links are provided by CHARLIE in one of the post today, i am telling you the same..
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/04/926f8546f311d189470000e829fbbd/frameset.htm
CHARLIE: I hope u dun mind for this...
regrds
Yogesh

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.

Purchase Req Release strategy - Requestor /Approver

We want to skip the Approver to release his own purchase requisition without workflow set up.Is it possible in ECC6.0 ?. Any help will be highly appreciated
Thanks
Nick

Hi Nick
While configurating add P group as one of charactaristic.Then maintain values of all P. Group in this charactaristic
While defining Release strategy Do not tick against Approvers P group which means release strategy will be skiped for him
( Release strategy--classification here u difine value for P Group skip P group here)
Cheers!!!
Vishal...

Release Strategy and workflow in Purchase Requisition

Hello All,
My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
Thanks in advance for your help!!

You will need to activate the user exit. This will keep the PO release strategy simple.
Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
Just a couple of points:
1) What will you do if one item in PO is created with reference to PR and the another item is not?
2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
Hope this helps
Lakshman

PO Release strategy, error: class POCLASS class type 032

All SAP Gurus,
We are configuring new PO release strategy.
When we go to Release strategy - classification
(Release procedure for PO - Define release procedure for PO - Release Strategies - classification)
It gives following error: Error in classification (class POCLASS class type 032).
Where we can maintain the classification?
Regards,

Dear,
Please follow bellow detail.
SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
Three steps involved in release process of purchase order.
1)     Edit Characteristic: -
Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
2)     Edit Class: -
After creation of characteristic, create class for release purchase order. In which you can take reference of
Class Type: - 032,
Status: - Release,
Class group: - Release strategy class,
And put reference of your characteristic, which are created by you in first step.
E.g: - Class - REL_PO
3)     Define Release Procedure of purchase order: -
In this step four processes involved.
1)     Release Groups
2)     Release Codes
3)     Release indicator
4)     Release Strategies
1)     Release Group: - In which you can define release strategy group
For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
2)     Release code: - In which you can define release code. Enter value as
Release group: - 01,release code: -01 - Purchase Head,
Release group: -01, release code: - 02 - Auditor.
3)     Release indicator: - In this step you have to define release indicator.
Like X - Blocked, I - Under process, S - Release.
4)     Release Strategy: - This is the final step for release strategy.
Assign release code 01, 02.
Click on release prerequisites, select 02 - check box and click on continue.
Click on release status button, enter release indicator X, I, S and click continue
Click on classification button, Enter values of purchasing group for which you want to created release strategy.
Regards,
Mahesh Wagh

PO Release Strategy, include new field.

Hi,
What are the steps involved to include a new field ( for e.g Account Assignment Category ) which is not there in the standard structure CEKKO.
Shall I have to change the structure CEKKOZZ or from the user exit 'M06E0004'?
Thanks in advance,
Regards,
Madhu.

Hi Arif,
Thanks for your reply. My requirement is to exclude a material group from PO release strategy.
If I include the characteristic related to material group in PO rlease class, and subsequently change the PO release startegy below is the problem.
Suppose PO contains one item or multiple with same material group, then only it is picking release strategy ( let us say all materials belong to mat group: 101)
If PO contains multiple items with different mat groups ( for e.g: 101, 102 & 103 ), then it is not picking up the Release strategy.
classification data is perfect and release strategy is ok for all material groups ( if PO contains only one material group)
I have checked in the program : MM06EF0S_STRATEGIE_CEKKO , the logic written in the program is such a way that, if two values exist for a doc field, then blank is passed to CEEKO structure.
I will try with user exit, and please let me know if you have any other idea.
Many Thanks,
Madhu.

Release strategy in RFQ

Hello Gurus,
Is there any way I can implement a release strategy for RFQ?
Thanks,
Jeffrey

Hi Jeffrey,
yes you can set up release strategies to RFQ also in
trasaction SPRO->MM->purchasing->RFQ/Quotation->Release Procedure for RFQs->Define Release Procedure for RFQs.
RFQ's use the same structure as purchase orders for the release strategy classification (CEKKO). Nevertheless, there are some fields in this structure that are only relevant in POs. Field CEKKO-GNETW (Total net
order value) is not relevant to RFQ release strategies. You can enter a value for this characteristic in transaction OMGS, but the system won't consider it.
Since RFQ is just a Request for Quotation, it does not make sense to set the release strategy of RFQ according to value change.
By using the characteristic CEKKO-BSART you can exclude certain release strategies for certain document types. A release strategy with CEKKO-BSART = NB won't apply to documents with the document type AN (RFQs).
hope this will helps you.
Regards,
Sunitha

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

Workflow for release strategy

Dear All,
PLz let us know the step by step procedure for worflow for release strategy.
Regards,
Arati.

Hello Arati,
Please see that you have maintained the release strategy and the same is getting affected in the PO.
In PO -> Header Data -> Release Strategy (Last Tab) please check the Release Strategy and Release Grp.
Now go to T - Code /nPFAC .. and enter the ID as 90100005 (PO Approver) and click on display.
After this on the new screen there are different tabs.. in that click on last (fourth) tab: Responsibilities.
There you will find responsibilities IDs assigned to each release strategy and Release grp.. of you cant see the same please adjust the layout.
once you get the responsisbilities ID there for the referenced Release Strategy and Release Grp then go to T - Code /nPP01.
There you need to do the maping. in the first field it please enter Responsibility and second tab you can put the same responsibility ID whihc u obtained from /nPFAC.
Then select on applications and then click on new.. n there you can assign the user as a approver. Please check that proper authorization si also given to a user who is mapped for the release strategy...
Let me know if any confusion ...
Thanks And Regards,
Krupesh Kothari.

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

PO release strategy , classification tab

Similar Messages

Maybe you are looking for