Release Procedure without Classification

Hi Experts,
i have create a release strategy for the release procedure without classification, which PR document type i use for this? NB?
Do i need to assign a PR document to this release procedure?
Thanks

Hi Chun,
You can not use one release strategy with classification and one more without classification at a time in the system. Only one will work.
For your case, already you have Overall release, and I suggest you go for second class with Itemwise release. With classification, it's possible to use two release strategies at a time based on the document type. ("Overall Release " check box for document type)
Umakanth

Similar Messages

PFTC, container tab, getting 'Release codes' without classifi !!!!

Hello,
I am settingup workflow for pur/req.
After making MMsettings in MM-config(MM > Purchasing > PR > Release Procedure > With Classification > Set Up Procedure, --Workflow.
Now I have made settings SWETYPV and SWDD and it automatically bring the task against WS20000077.
But do I need to activate it?
In PFTC, container tab, it is only getting 'Release codes' without classification (which we are not using).
In SWDD also (after pressing Test icon) I am getting 'Release codes without classification.
I don't know why it is not picking 'Release codes with classification'. However it is picking correct release codes in Pur/req header.
Can you please put some light on it.
Many thanks.
JAT

Hello !
    Purchase requisition release procedures for "with classification" and "without classification" are mutually exclusive.
    I think,release procedures for "with classification" and "without classification" are configured in your system.
    So, deleting the configuration for release procedures for "without classification" will help you to accomplish the requirement.
Regards,
S.Suresh

Release procedure with classification not getting triggered

Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachin

Hi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
   Create the release codes.     For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
   Define release indicators and branch to the detail screen. Here you
   define whether fixed purchase requisitions may be changed by Materials
   Planning, for example, and whether an RFQ or a purchase order may be
   created from the requisition.
   You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
   specify whether a requisition may be changed after the release
   procedure has begun. You specify whether the strategy has to be
   redetermined after changes, or whether the release procedure has to
   start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
   example, previous releases are not cancelled if the value of the
   requisition item after the change does not exceed plus 10% of its
   original value.
Attention:
   Be sure to create a release indicator (e.g. B for "blocked") that
   serves as the starting point for subsequent indicators. Do not set the
   indicators for release for the issue of RFQs and PO on the detail
   screen for this indicator.
   Also create a release indicator characterizing the released status.
   Set the indicators for release for the issue of RFQs and PO on the
   detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
   Assign a release indicator in dependence on the status of the release.
Example:
   You create a release strategy S1 consisting of two release codes 01
   and 02. Release with 01 is a prerequisite for release with 02. If
   release has been effected with 01, the requisition has been given the
   "all clear" for the issue of RFQs.
   You have created the release indicators B (blocked), 1 (cleared for
   issue of RFQs) and 2 (cleared for RFQs and PO).
   Now enter the following as assignment:
Strategy   C1 C2 C3 ...
   S1                          B (blocked)
   S1         X                1 (RFQ)
   S1         X   X            2 (RFQ/PO)
4. Release prerequisites
   Define which release codes are involved in a release strategy. Specify
   whether a code is set for a release status following release, and
   whether one release status is a prerequisite for another (+).
   Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

Release Strategy without Classification VS with Classification

Can you have a strategy based on with classification and another one without classification in the same client.
Thank you.

Hi
You can have either of the One active in a system
If you have activated RS without Classification, all the PR's will be subject to Release Process..
If you now activated RS with Classification then this will Not work as the sytem has already found a RS wothut classification & not depebndent on any charcterisitics.
So you can use only one of the Combination.
This is applicable to only Purchase requsitions.
For Purchase orders & othe Documents you will have only with Classification.
Thanks & Regards
Kishore

Help to modify the Release procedure without disturbing the existing class

Hi All,
We have a requirement to modify the existing workflow approval procedure for PR and PO to include a case, where the PO amount is less than certain value (say 100 EUR) and the material group is equal to certain value, then we need to include the approval levels L2 (defined for PR) and X2 (defined for PO).
Taking the case for PO`s, please note the following information,
Existing release Strategies & release Levels for PO are
51          Level X4
52          Level X4 + X3
53          Level X4 + X3 + X2
54          Level X4 + X3 + X2 +X1
Characteristics used
Total Net order Value
Purchasing organization
Order Type
Purchasing Group
Example : If the PO triggering a Release strategy 51 and if the conditions PO Value and Material Group satisfied then in addition to X4 system should send the PO Approval to X2 also. Similarly if the Po triggering the Release strategy 52 then in addition to X4 + X3, approval from X2 also required (provided if the condition satisfies).
Solutions tried
1) We can achieve the requirement by adding a dummy variable in the Characteristics and defining the new release strategy 55 with Level X4 + X2 and using the User Exit EXIT_SAPLEBND_002 .But we donu2019t want to touch the Characteristics and class because this is used by other companies also.
2) Also we can add a characteristic Material group with value equal to the required value and define 2 new release strategies 55 with Level X4 + X2 and 56 with Level X4+ X3 +X2.For all the other release strategies we can maintain the material group value as blank. Since the characteristics used by many companies we donu2019t want this option also.
Request your valuable suggestion to meet the above requirement, without disturbing the existing characteristics and Classes, would be highly appreciable.

>
MadhanRaj S wrote:
But we cannot use those because these are used by other companies of the same organization.
>
> We need a solution other than these two options with out disturbing the existing charecteristics and class.
It looks to me like you need a new release strategy for the company that is different. This is a perfectly normal way to use release strategies and is exactly what they are designed for.
Cheers,
Mike

Regarding Release Procedure with classification

Hi All,
Please anybody tell me,is't possible to release at item level in external document like PO,RFQ.
Thanks & Regards
Suresh.

In principle you wouldn't send (/release) part of an external document.
The information at Header level applies to the whole of the document, in other words it can also be considered as applying to each item. For example the payment terms apply to the whole of a PO, not the individual items. The individual items can not be considered complete without the Header information. Consequently the release strategy is set at Header level.
In theory all POs may be created with reference to preceding documents and these may be released at item level e.g. Purchase Reqs. Therefore at the time of creating the PO the individual PR items have been approved from a business point of view, the PO typically represents the overall commercial approval for the items.

Release Procedure with classification

hai all,
I read a statement which say "Realese procedure with calssification PR can be relesed at header level"
I want to know what does this sentence mean actually. if possible please expalin me with a practical example
thanks in advance
with regards
Sreenivasa Chary
9848993644

Release procedure defined at the client level and it use only one class
now suppose you have assigned the 6 char to the class then your release strategy should contain the value in each characteristcs other wise your release will not work.
the bottom line is you have to define the value for each char.

Release Procedure Query

Hello All,
In our scenario we are using release procedure without classification.
Let say in a Startegy S1 created there are three level of approvals L1, L2 and L3.
It goes in a way that if L1 created PR it should be released from L2 level from ME55 then L3 from same ME55 transaction which is fine.
But problem comes when L2 or L3 Person raises requisition. Let say L3 level person has raised requisition then he himself can released that from L1 and L2 level from ME55 transaction as he is on last level and has authority to release the requisition.
Ideally this is should not be fair practice.
We need to know how we can control this so that person who raised requisition should not release himself/herself.
Is there any configuration setting or any other way to do. Or we need to change the strategy.
Regards
Himanshu Nijhawan

Hi,
Do not design release process of PR as you explained. PR releaser always a PR releaser only and he should not create any PR. Also PR creator always used to create PR and PR creator should not release PR.
You can easily restrict and control PR release process by having well designed user authorization matrix and release matrix. As per release u201CVALUESu201D, release matrix designed and based on authorization, control can be established for transaction codes.
Lets example: User 1 will create PR, user 2 will change PR and you have 3 release codes for releasing PR such as like L1, L2, L3 for three user respectively user 3,user4 and user5..Now you can allow (authorized to) user to do following transaction
Transaction Code----
> User
ME51N----
> user 1
ME52N----
> user 2
ME53N -
>(All users ie..user1.user2,user3,user4 & user5)
ME54N or ME55 with release codeL1----
> user3
ME54N or ME55 with release codeL2----
> user4
ME54N or ME55 with release codeL3----
> user5
If business needs, you can give authorization user3, user4 and user5 to change PR(ME52N) by eliminating user2.
NOTE: For more details contact basis team and control all these by authorization object.
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

Release Procedure in PR .....

Hi SAP Gurus,
We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
Thnks & Regards
SAP MM User

You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
sri

Which release procedure will pick?

Can any body help?
We have a requirement that ,for same material (ABC) but belongs to different plant,
we have two release strategies R1,R2
R1:-in this strategy two codes assigned
This release strategy will effect when net value=50000
& plant "X"
R2:-in this strategy three codes assigned
This release strategy will effect when net value=50000
& plant "y"
i will create PO with two line items,                                                                                in one line material is ABC & plant X
in other line item material is ABC, Plant Y
net value =50000
my question is which strategy&releases procedure will effect to this scenario
plz do needful

These are the communication structures
CEBAN
CEKKO
CESSR
Customizing Tables
Release strategy without classification
u2022     T161I as described above.
u2022     T161E Release code and Description
u2022     T161S Release indicator
u2022     T161G Assignment to release indicator
u2022     T161F Prerequisites
Release strategy with classification
u2022     T16FG, T16FS as described above.
u2022     T16FH description of the release group
u2022     T16FT description of the release strategy
u2022     T16FC Release code
u2022     T16FD Description of the release code
u2022     T16FV Prerequisites and actions
u2022     T16FK Assignment to release indicator
u2022     T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
u2022     T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator

Purchase Requisition Realease Strategy without classification

Hi,
Request for detail process and configurations for Purchase Requisition Release Strategy without classification.
We have 5 authorities like A1 (Lowest) and A5 (Highest authority) in the organisation to release the PR.
The PR should be released according to value slabs.
Thanks a Lot.
Sachin

Hi Sachin,
IMG> Materials Management>Purchasing> Purchase Requistion> Set up procedure without classification
This process is similar to process of with classification
Go through the link below:
for this no need of creating characteristics and classes
http://www.sap123.com/showthread.php?t=59
http://help.sap.com/erp2005_ehp_03/helpdata/EN/75/ee150b55c811d189900000e8322d00/frameset.htm
If useful, reward me
Thanks & Regards,
Swathi

Release procedure for Purchase Requsition and especially f. a document type

Dear Experts,
how can I establish a release procedure. I need to set up the procedure
without classification. But it depends on a document type.
I have been to the customizing section with spro
Materials Management/Purchasing/Purchase Requisition/Release Procedure
and have choosen "Set up Procedure without classification. ".
But can I assign a document type and how is the handling generally with.
Release Codes
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Thanks
Ilhan

Hi Ramesh,
You are saying:
"Click on the Release strategy button under item tabs". Where is this button.
All what I have is: Tab for "Material Data", "Quantities", "Valuation", "Account Assignment",
"Source of Supply", "Status", "Contact Person", "Texts","Delivery Adress", "Customer Data",
on calling of Tcode me54n I get immediatly a message
"Purchase Requisition 5000000131 can not be released" although I didn't enter any number in it
Why does it refer to a PR Nr. generally . I think it is pre-filled- How can I call this transaction without this message ? Or how can I call this transaction so that I can type in my own Purchase Rq-Nr.
Regards
Ilhan

Release Procedure for A/c Assigment PRs

Dear Experts,
As per user requirement,we need to create Release procedure with classification for Purchase Requisitions based on a/c assignment category(F internal order)for protects.But there is already existed release strategy had characteristics document type,purchase group,can i add new character for item category F (internal order ) for the release class,please tel me field and structure.
Thanks in advance.
Varun

Hi Varun,
the new characteristic is CEBAN-KNTTP.
Pls. read FAQ note 365604 carefully /the whole note/.
Part 2e) is addressing your issue:
If you make changes to the class (add or delete a
characteristic), the system cannot determine the release for this
class. Then you must adjust all release strategies
correspondingly. (If you added a new characteristic, you must
maintain the characteristic value).
Please check also if you are using overall release strategy or item wise release strategy in your PR. . In the overall release, the system only considers the characteristics that are IDENTICAL for all items (like in all PR items you have acc. ***. category F).
Please check also note 326102 to avoid performance issues with PRs without acc. ***. category.
Regards,
Edit

Release Procedure without Classification

Similar Messages

Maybe you are looking for