Release Groups at "Release strategy

Hi,
At "Release strategy with Classification " there are Release Groups.
But at "Release strategy without Classification " are not Groups availbale.
What is the reason for and for what are Release Groups existing ?
Regards
sas

hi,
The release group is the only element which makes a pool/connection/linkage between the class and the release strategy....This is specially applicable for the release strategy with classification...
And then further this group is assigned release codes based on which you release the documents...
You can see and check the above explaination here:
SPRO >> MM >> Purchasing >> PR >> release strategy >> Rel startegy with classification >> check for the "set up procedure with classification"
Hope it answers your query
Regards
Priyanka.P

Similar Messages

Error while creating new release groups in PO release strategy

Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
Illan

Dear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**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**
**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**
*Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
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
Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*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 continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

PO release strategy based on Material Group (CEKKO - MAKTL)

Hi Experts,
I have configure the Rel strategy based CEKKO-MATKL (material group) for purchase order, but when i raise the PO Rel strategy is not affecting, Can any body tell me why.
Regards,
Kumar

You can set Release strategy based on Material group & other Line item specific fields..
You better follow a suitable and hinder less process..
For PR use Material group & Account Assignment based Release process..
then for PO use a Release Process based on Header level fields like Doc type, Amount, pur Group etc..
So that the approved PR line can be converted into PR and then the PO also subjected to Release before sending it to External Vendor..
Even if you want you can make that the PO can not be created without referencing PR for SOme users or All users..
based on your business requirement..

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 group in release strategy

HI gurus,
Can anyone tell the significance of release group in release strategy for purchase order with example.One use of it as i know is where a single person is responsible for multiple plants and in each plant he has different prerequisities.Please correct me if it is wrong.
Regards,
Sharma

Hi Rahul,
The Importance of Release group is it links the Classification functionality to the release procedure, So the characteristics which is included in the classes will appear in the release procedure if you mentioned the Class in the release group.
It also includes the release object which identifies which Purchasing document is active for Release group like 1 for PR , 2 for others.
rgds
Chidanand

PR release strategy for material group

Hi,
I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

Hello
In PR you can set up this release strategy without classification release strategy.
w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
Laxman

Inclusion of Purchase group in service entrey sheet release strategy

Hi
We are trying to include the purchase group in service entry sheet release strategy but system is not considering it.
Pl. let us know which table you have considered for purchase group character. We had considered EKKO table and Field EKGRP.
Regards
Kandre

Thanks Solved. The same field is done in development server, but after the request is moved to 201 and we manually changed to EKKO and EKGRP, that why the release strategy is not picking.
Thanks for fast response.
B.Kandre

Purchase Requisition with wrong purchasing group - release strategy

Hello
There is a lot questions about release strategies but I cannot find answer.
I have release strategy based on:
- Plant
- Purchasing Group
If I create Purchase Requisition with right purchasing group release strategy is assigned to PR item.
When use wrong purchasing group - release strategy is not assigned.
How to easy set control if user use wrong purchasing group system automatically set one strategy which not allow to create purchase order.
There is too many plants (150) and purchasing groups (60) to create all combinations in strategy. So I cannot do that.
Maybe there is some useful user-exit?
I use SAP ECC 6.0
My problem occurred because SAP allow to create PO with reference to PR which have no assigned strategy.
Thanks in advance for help
Arek

Yes it is solution
But as I wrote before there is too many incorrect combination.
Example
PG A1, A2, A3, A4. A50
Pl 2200, PG A1 OK
Pl 2200, PG A2 OK
Pl 2200, PG A3..50 NOK
For this example I have to set 48 combinations (strategy with S).
I noticed that I would have to set about 200 strategies. Client dont want accept it.
You wrote set up one unique strategy. How? As I know I need 200 strategies (or there is something I dont know
Kind regards
Arek

Release Strategy in PR not triggered for different Purchase Groups.

Dear Experts,
For Purchase Requistion - Header Level Release Strategy has been defined with Purchase Group as one of the Characteristics(Characteristic Values are V1, V2, V3).
When PR is created for 30Line items with V1, V2 or V3 as Purchase groups independently- Release Strategy is triggered.
But when a combination of all 3 Purchase groups is used in the same PR for 30 Line items together. No Release Strategy is Triggered. All these 3 Purchase groups have been assigned for all strategies.
Thanks & Regards
Chandan H N

You are using characteristic P. Group for different RS. That means that if only one value exists, the system will be able to understand which RS to implement. If you are using more than one values for this characteristic, the system simply does not know which RS to choose and takes nothing.
More simply you are using a header data (p. Goup) for RS and you are using it in line items. This is wrong. You have to make PR's only for the respective P. Group

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

Stop release strategy when pgrp changed triggering different release group/

Currently when our buyers change the purchasing group field on the purchase requisition it is triggering a new release strategy because the release group and code is different than the original creator.
It has been indicated that we should request from SAP that these two fields be made available to the structure for the release strategy.
Is there a user exit that we can use to stop a new release strategy?

Hi,
Do you have different rel. stgy for diff. plants? if yes, than which rel. stgy should be picked in case if both plants entered have different rel. stgy? what is your expectations/requirements?
If your PO is to go through diff. approvals for different plants than you should have different PO for each plant (even diff authorizations and rel. codes), or else you should not have plant as the criteria. Technically, whether it is fesible or not is different question, but whether practically your organization is ready that if a common material is to be procured it will have approvals of only one plant or may be a different approvals all together?
Regards,
Dakshesh

PR release strategy with material group

Hi Experts,
Release strategy for Purchase requisition already configured with characteristics Document type and Total net order Value.
For fulfill new requirement we have created New character with Material group.Our requirement is for Two material groups separate release strategy has to be trigger and remaing other material groups old release strategy has to be trigger.For exple if X and Y are two material groups ,which require seperate release strategy.Other than X and Y material groups requir old release strategy.
all the material groups assigned to character.Blank material group also assigned to the character.In release strategy level in classification view we have assigned two material groups( X and Y ) for separate release strategy and remaining material groups and Blank material group to old release strategy.
   At the time of creation of PR if i give two material groups ( X and Y)for different line items, seperate release strategy is not triggering, where as old release strategy is triggeringIf i create PR with single material group( X) for all line items it is triggering seperae release strategy properly.
   For other material groups (other then X and Y )with different line items it is triggering old release strategy properly.
      Kindly help me to resolve the problem.

Hi,
Please add Blank material group to the new release strategy also.
Maruthi

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.

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Release Groups at "Release strategy

Similar Messages

Maybe you are looking for