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

Similar Messages

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

Problem in creating Release group for Release Procedure for PR

Hi Experts,
I could not able to create Release Group ( 01 & 02 ) for Release Procedure and assigning it with a Class
( Z_CLASS_PR ) in Set up Procedure with Classification.
The following error is getting displayed.
Please check release classes (see long text)..
How to over come this problem.
Thanks in advance.
Regards,
Nani

Release group:
You are only allowed to use one class for each release object (1=PReq, 2=Purchase order). When you use the overall release (as of Release 4.0A), you are only allowed to use one class for the overall release or individual release. If you use the overall release for purchase requisitions, you must mark this for the document type (transaction OMEB, flag for V_T161-GSFRG) and the release group (transaction OMGQ, flag for V_T16FG-FRGFG). In the overall release, the system only takes into account characteristics that are identical for all items. If, for example, item 10 of a purchase requisition contains material group 001 and item 20 contains material group 002, the material group is set to BLANK for the strategy determination.

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

Release Group for PR Release Strategy

Hi ,
When i am trying to define new "Release Group" AA , with Class "Z_PR" (it has Plant and Item Value as charcteristics ) , I am receiving message "Please Check Release Classes" , Message no. ME492.It doesn't allow me to save this new release group.
Please also note that other two release Groups are already available.
Do u know what I am missing and how can I save my Release group ?
ALSO as per the LONG text of this prompted message
"Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used."
What does it mean ?
Sandeep

Hi,
The message has explained the problem.
You cannot have two classes for the same document release and you are tryng to break this rule by adding another entry (the fact that you have give it a different release group does not make any difference this is still another class for the same document.)
You should be able to do what you want without the need for a new release group or additional class, after all everyone else that uses SAP is using one class per document.
Why diod you think that you needed another release group / class?
Steve B

Release Procudure - Problem while creating Release Group:Reg-

in release procedure char. were created and class also created and the char. were assigned to the class too.
But when i am creating release group the below error was coming..
Please check release classes (see long text)
and if i am see long text the below is the error
Please check release classes (see long text)
Message no. ME492
Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
Procedure
Assign the release groups that were created for overall release to one release class only. Assign the release groups that were not created for overall release to a different release class.
Example:
Rel. group Rel. obj. Overall rel.    Class       Description
01 1 _   FRG_EBAN      Group 01
02 1 _   FRG_EBAN      Group 02
S1 1 X   FRG_GF_EBAN Group S1
S2 1 X   FRG_GF_EBAN Group S2
please see what can i do to solve the issue.
Thanks and Regards,
Rajesh.

HI,
It is not possible to have more than one class define in the release
strategy but it is possible to define difference characterics within
the same class.
Please verify the following:
1) As the long text of the message says, first check that one release
class only is used within the release groups for overall release and
   the release groups without overall release in each case. However, in
   this instance several release classes have been used.
   This means you have to have one release class only for all the
   release groups for overall release.
   Assign the release groups that were not created for overall release
   to a different release class.
Example:
Rel. group,   Rel. obj.,   Overall rel., Class ,     Description
01,,1,,_,    FRG_EBAN,      Group 01
02,,1,,_,    FRG_EBAN,      Group 02
S1,,1,,X,    FRG_GF_EBAN,   Group S1
S2,,1,,X,    FRG_GF_EBAN,   Group S2
2) If you have followed all the indications of the long text of the
   message and the error is still displayed, please try to create the
   new release group via the 'New Entries' button.
3) If you tried to create the release group via this button and the
   error is still been displayed, please verify the implementation of
   note 125316 in you system.
Best Regards,
Arminda Jack

Deletion of Release Group and Code in PO

Dear Consultant,
In Purchase order, we have created some release group and code, Unfortunately we deleted some groups Without deleting in Order wise.
In table level the Release Group is there but in SPRO Release Strategy settings its not there..My consultant advised again you have to create same release group in Release strategy...
If I create same Release Group which are lying in my T16FC Table..But system throwing this err "An entry already exists with the same key"
Could you suggest me.
Regards,
PRIYA.

Hi,
Please go with below mention path: -
SPRO >> Materials Management >> Purchase Order >> Release Procedure for Purchase Orders >> Define Release Procedure for Purchase Orders >> Release Groups.
Here check release group is existing, if yes then remove them and click on save button.
Then try to create new service group.
Some times we delete release group and create new release group with same description without saving changes.Due to this this type of error is occur.
Regards,

Release code and Release group

Hi All,
where we find PR release roles with release code and release group combination. Is there any table to identify with this combination?
Thanks in Advance
Suresh

Hi Suresh,
Here is the list of various tables in release procedure,
Tables in Release strategy:
T16FG - Release Groups
T16FC - Release Codes
T16FB - Release Indicator: Purchasing documents
T161S - Release Indicator, Purchase Requisition
T16FE - Description of Release Indicators: Purchasing Documents
T16FS - Release Strategies
T16FV - Release Prerequisites
T16FK - Release StatusesTable: V_161S
Vivek

Find sap user id from release code and release group

does anyone know any FM that can get sap user id from certain release code and release group?
ex: if i input rel code 40, rel group N1 , then it should be sap user id A
i would prefer FM rather than tables and tcode.

Hello,
Please find attached list of tables
T16FB                          Release Indicator: Purchasing Document
T16FC                          Release Codes
T16FD                          Description of Release Codes
T16FE                          Descriptions of Release Indicators: Purcha
T16FG                          Release Groups
T16FH                          Descriptions of Release Groups
T16FK                          Release Statuses
T16FL                          Release Indicators: Service Entry Sheet
T16FM                          Descriptions of Release Indicators for Ser
T16FS                          Release Strategies
T16FT                          Descriptions of Release Strategies
T16FV                          Release Prerequisites
T16FW                          Assignment of Role to Release Code
Thanks & Regards,
Mihir Popat

Delete Release Group and Code

Hi,
Is there any standard Program to delete all the release group and Release code.
Rgs,
Priya.

Hi Priya,
These are customization settings present in TCODE. SPRO. You can delete this from there. Any way these are entries in the Views
V_T16FC - Release Codes
V_T16FG - Release Groups
You can make changes here.
Regards

PO release change in release code

Hi Gurus,
Earlier a PO was being released by code A1. This employee has left the company so all the release of POs have been held up. So i want to change it & assign it to a different code B2 , please guide.
Regards,
Kumar

Hi,
Try to minimize headache. There may be so many factors/characters involves and you need to study the system 1st and then see the other implications too change or NOT.
Example:
You may have release groups, release codes and respective values to be released are following
Release Group A
Release Code: A5u2026 more then 2000K
Release Code: A4u2026.750K to 2000K
Release Code: A3u2026.250K to 750K
Release Code: A2u2026.50K to 250K
Release Code: A1u2026.0 to 50K
Release Group B
Release Code: B5u2026 more then 2000K
Release Code: B4u2026.750K to 2000K
Release Code: B3u2026.250K to 750K
Release Code: B2u2026.50K to 250K
Release Code: B1u2026.0 to 50K
u2026 see example A & B are may be different department. If user get B2 release code instead of A1 ,he can release greater value etcu2026u2026u2026
Regards,
Biju K

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.

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

PO Release Group Problem

Hi All
This problem regarding Purchase Order Release Strategy.
I have deleted the existing Release group : 02 and created New Release Group: 11 for Purchase Order Release Procedure.
I deleted Release Group 02 and Release strategy in sequence.
But still when I'm using ME29N transaction, system using release Group 02 not New group 11.
I verified all Release Group related tables.
T161E,S,G,F,
T16FG,FH,FT,FC,FD,FK,FB,FE
But there are no entires for Release group: 02.
when i look into EKKO table, purchase order linking automatically to release group 02.
from which table system pulling this?
How to solve this problem
Please suggest
Thanks
SUNIL KUMAR

If these all the POs were created before you delete the release group and created new than system will not take new release group
you have to put it the old one back and release all the POs which has old release group than you delete the release group
you can keep the new one so the new POs created based on the new release group
in sm30 check this both table
V_T16FG_2 and
v_T16FG
should be clear

Release group

Hi,
When is it needed to use more than one release group for purchase order release procedure.
Thanks
Aparna

Hey,
Is not necessary create a release group for each company/plant, is possíble to create just one characteristc that control plants under a strategy class.
Table: CEKKO
Field: WERKS
Creating a class with purchase order type, plant and a charac that control range values should be enough.
However, the plants sohuld work with different currencies, so, be careful about setting value range characteristics.

Release group in release strategy

Similar Messages

Maybe you are looking for