Release strategy and code authorizations

Hi,
We need to create a new release strategy for PO. After setting strategy, we are assigning existing release codes A1 and A2 to strategy. The same release code is also used in existing release strategy.
Now, will this create any authorization issue if we assign same release codes to different strategies, and different users in user roles.
Thanks
Alex

Hi,
I am confused with your requirement. When you have a business requirement to control the release, may be a new department created or new character value requires for adding to release process.
Option-1:--- >When you decided to create new release strategy, you should have gone for creating new release codes & design your release process with new release strategy with new release codes. Do not use same release codes, use different release codes for new release strategy which will be easy to control for authorization based on respective users.
Option-2:--- > When you added a new release characteristic to release class based on requirement, then check assignment of release group to release class ( just make change & TR need to be transported),release strategy design which trigger on how release is to be affected & which manner with a logic. Also check the new value you are entering with your release class, release group & release strategy in Cl20N/CL24N t.codes. Also check during creation of new release characteristic, you have values with correct field name.
Regards,
Biju K

Similar Messages

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 Strategy @ Company Code Level

Hi Guys:
We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
with Characteristics as Company Code ,PO Document Type and PO Value?
Thanks
Sweth

Hi
For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
The characteristics for release strategy for external purchasing documents are
Plant                - WERKS
Pur.group        - EKGRP
Pur.org            -EKORG
Acc.assignment category-KNTTP
Document value-GNETW
Document type-BSART
The table is CEKKO
Thanks

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

PR release strategy and Standard Workflow suddenly doesn't work

Good day,
I have PR release strategy and Workflow activated. My workflow is copied from standard PR release workflow in SAP. The only changes I made in the WF is Agent Assignment. It worked like a wonder.
However this week when I was creating PR, Release Strat still works but WF doesn't kick in. No change was done to both PR release strat and WF.
Any help/suggestion for this? Is there a period of activation in WF?
Regards,
Si

Hi Diwakar,
I was able to activate it already yesterday. What I did was to test the workflow in SWDD. After the test, all workflow items were created. Am still wondering though why WF would suddenly stop (not generate workflow items) even with no changes made.
Thanks for the info and link. Points awarded.
Regards,
Si

Query on Release strategy and WFL?

Hi Friends
what is the diff bet Release Strategy and WFL
Regards
Emil

By WFL if you are referring to Workflow, then these two are not something you should look for differentiating. Worflow is tool provided by SAP to automate a series of business process activities based on business rules. In case release strategy it helps in automating the whole approval process.
Workflow is used to trigger e-mails to approvers once a purchasing document is subjected to release strategy. It can used to write the approval rules and in what scenario who is the approver, are there multiple approvers etc.

Dynamic release strategy and static release strategy

Hi,
What is the difference between dynamic release strategy and static release strategy.
What the customization setting required to activate dymanic and static release strategy.
Thank you
REgards,
Yshu

Dear Yshu,
What do you mean by dynamic and static release strategy. In SAP, we don'y have this term.
Please kindly give more explanation so we can help you.
We only have with classification and without classification.
Normally, release strategy without classification is used in R/2, and out of support in
R/3. However the functionality still available in case you want to use it.
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT), only release with
classification can be used.
If you are in R/3, then forget the release strategy without classification but just
use the release strategy with classification as it had more flexibility than the old
system design.
Thanks
Ian

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.

Purchase Order Release Strategy and SAP user RelationShip

Hi,
We are currently developing a work flow to streamline PO release in our company . What we want to achieve is that
E.g
A purchase order 100001 is creates and a release strategy s1 is applied to it which is a 3 level relase statrgy having release code c1,c2,c3 which are uniquely assigned to user/employee of the company and no 2 users'employee can have the same release code.
Now when c1 release the purchase order a work item should be created to for the user/employee who is assigned the c2 code.
Currently this workflow is not implemented in our company adn the relase stategy is handeled by authorization oobjects and when ever a po user relase the po he calls up the other persona next in relase strategy to notify him about the work he has to do .
I am need to know can we develop a relationship b/w the release code and sap user or employee
Regards
Kamran ellahi

Hi,
We are currently developing a work flow to streamline PO release in our company . What we want to achieve is that
E.g
A purchase order 100001 is creates and a release strategy s1 is applied to it which is a 3 level relase statrgy having release code c1,c2,c3 which are uniquely assigned to user/employee of the company and no 2 users'employee can have the same release code.
Now when c1 release the purchase order a work item should be created to for the user/employee who is assigned the c2 code.
Currently this workflow is not implemented in our company adn the relase stategy is handeled by authorization oobjects and when ever a po user relase the po he calls up the other persona next in relase strategy to notify him about the work he has to do .
I am need to know can we develop a relationship b/w the release code and sap user or employee
Regards
Kamran ellahi

Release Groups and code - PR and PO??

Hii
Some body explain me about the significance of release code and groups in PR and PO release strategy.??
Thanks

HI,
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users
Check the link for more details
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM
Regards
KK

Release strategy and ME54N.

Hi,
I can't perform the release with trx ME54N for a purchase requisition.
In the screen layout I don't see the release button in "Release strategy" view,
it seems not enabled.
Best regards

Hi,
Actually to criteria to meet release of any document is defined via class and characterstics so you first check the purchase requisition you are raising come under that release criteris.
For example any PR above rs 100000 is subjected to release.So you check in release startegy what threshold value or other characterstics are given in relative class.
This you can check in this link
http://www.sap123.com/showthread.php?t=59
I Hope this will work for you
Regards
VS
-- Reward if helpful

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

Purchase Order Release Strategy Approval

HI All,
I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
Level one will have 1 approver
Level two must have two approvers.
The scene is:
Level one will approve all purchase orders betwee 400 to 5000 euros. 1 approver only
Level two will approve all purchase orders above 5000 euros. 2 approvers.
The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
Pur. group G70, Release Group GC and release strategy DF.
I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
CL20N is completed for both levels and works correctly for level one approval but not for level two
Can any please help
Leslie

Hi,
May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
1. PO Order Type (ZPO_BSART),
2. Company Code (ZPO_ BUKRS),
3. Purchasing Organization (ZPO_EKORG),
4.Plant (ZPO_WERKS)
5. Purchasing Group (ZPO_ EKGRP) and
6. Total net PO Value (ZPO_GNETW)
Create one release class ZPO_CLASS & then add all above release characteristics
And then design your release strategies as required.
AND under release characteristic for PO Value (ZPO_GNETW) keep following values
A. <= 400 EUR
B. 400.01- 5000 EUR
C. >5000 EUR
As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
Regards,
Bijju K

RELEASE CODES IN SERVICE RELEASE STRATEGY

Dear All,
I have created a Service Group and assigned three release codes.But when I am trying to simulate the release in release strategy the release codes are not displayed.
Where have I gone wrong????.
Someone please help.
REgards

Did you maintain the combination of 'release group', 'release strategy' and 'release codes' under 'release strategies? You need to maintain this combination before simulating the release. Also, ensure after entering the said combination verifying 'relase preqreuisites, release statuses, assignment of class and then simulating the release.

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

Release strategy and code authorizations

Similar Messages

Maybe you are looking for