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

Similar Messages

Release Code and Strategy

Hi,
We have created a new release code and its corresponding release strategy. But when we are trying to release the PO, the PO goes to a release code not maintained in the system. What could possibly be lacking in my config?
Scenario : I created release code T1 but the PO goes to release code F2 (which is not configured in the system). Please help.

Hi,
It happens some time , it is taking default values.
I will suggest you to delete all the release codes and release strategy maintained in the system.
After deleting pl Save it.
Now you create your release codes and maintain release strategy again.
Def now it will work.
Uts
Award if helpfull

Report on Manual and Automatic release of Invoices - MRBR

Hi Gurus,
What is the difference between Manual Release and Automatic Release of Invoice in MRBR?
How can i get the report of invoices release automatically and invoices released manually?
Please revert asap.
Thank You

Hi,
Rlease Manually
The system creates the list of blocked invoices as soon as you choose Execute. On this list, you can release invoices or delete individual blocking reasons!
Release Automatically
If you select this field and choose Execute, the system deletes all blocking reasons that satisfy the criteria entered in the group box Selection of blocked invoices and that are no longer relevant. A list of the released invoices appears.
That's it!
Good day
Tao

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

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.

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

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

MIR7 doesn't get PO and PO release strategy

I can see PO item 10, 10000 MYR in ME23N, and it is already released.
In MIR7, PO reference tab, I put PO number and item number, but mesages says no item number. and it didn't populate item from PO.
what's the reason?
also I create PR and released PR, but when I run ME59N and input PR number, it says No suitable purchase requisitions found
Message no. ME261? I can't generate PO automatically. I have to use ME21N, what's the wrong with my system?
I tried one purchase group and PO can't be released, but when I change purchase group, it is ok, may i know the SPRO configuration to define certain purchase group for release strategy?
also how can we set certain PO document type with release strategy and some PO document type without release strategy ?

Hello
For first question, Please check in the PO line item level Invoice tab, whether GR based invoice verification is checked. If yes, then system will allow you perform MIR7 after Goods receipt.
Second question:
ME59N should display the open PRs for PO creation. Please cross check once agian the input selection parameters.
Third Question
Yes, you can configure the Release procedure based on Purchasing document type/Pur group. You need to define the paramter as Charactetristic and assign to the Release class.
warm regards
Ramakrishna

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.

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

Creation of release order possible during release strategy

Hi folks,
we have currently contract and purchase order release strategy parallel in place. Both are working fine.
We are using quantity and value contracts.
Quantity contracts are changed frequentely by the business; with every change (adding new items, changing prices of existing items), the release strategy is pulled again.
Our release indicator is set to 6 and has value change 0,00%.
The business requirement is now to release a contract with status X (e.g. 10 items and a total item value of 10.000EUR). After release, call offs can be created for all the released line items.
If a new line item 11 is added, it should still be possible to create call offs for item 1-10 but not for item 11.
Item 11 should undergo a new release.
Has anyone ever come across such requirement?
I have tried version management. However, version management will only force a new release whenever the version is completed.
Even then, the complete contract is subject to release strategy and it is not possible to create call offs.
We dont want to set error message ME347 "Release orders against contract xxxx not possible (contract not released)" to warning, as this will allow to always create call offs regardless of the contract being released or not.
Any ideas greately appreciated.
Thanks!!

I suppose program checks in EKKO whether contract is released,, irrespective of version exist it or not. IF you are able to direct it to EREV, then may be version 0 or ( current - 1 ) released can be returned.
Isn't it a special case that your version 0 data is intact in version 1; Even if someone change lines 1 to 10 , with or without adding line 11, it still triggers version 1. How do you ensure that lines up to 10 are not changed. you may have to look in CDPOS CDHDR with object Revision..
This is just an idea which you may discuss with your developer to see whether a copy of the program can be modified..

Release strategy: User should release only with his highest release code

Hello,
Because of personel absences we want to configure the release strategy so that:
User A or user B releases in the normal case the first level of a PO (with release code 01).
User C (Manager) releases after release code 01 with release code 02.
User A is deputy of user C. In this case user B will release with code 01 and user A will release with code 02.
Because user A can use depending of the case release code 01 or 02 (C deputy) it must be avoided that user B sets release code 01 and 02 for the same purchase order.
Do you know about a solution for this issue
Br
Manuel

Dear W1N,
But the systems knows that A released with code 01 and when A tries to release with code 02 the system knows that the same person of release code 01 is trying with release code 02.
<b>The aim is to avoid the second release from the same person and not to automate the release strategy.</b>
In such a case A has to cancel the release for code 01 (ME28) and wait until B is reachable to do the release of code 01.
When C is absent A knows that his task is to release code 02.
Is this check really not possible?
Best regards
Manuel

Overall release of PR in Release Strategy

I have created item-wise release of PR using with Classification of Rel Str.
But when I am creating overall release of PR I am not getting the tab.
I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
Pl guide
regards
VS

Hi VS
Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
Best regards
Ramki

Create a purchase order strategy with four release steps.

Hi all,
how can I create a purchase order release strategy with 4 release steps?
The steps have to be the following:
AC (Buyer);
CO (Controller);
FI (Finance);
AD (CEO).
I couldn't configure and add entries in "Release prerequisites" (trx.OMGS).
Best regards

Hi ,
The implemantation steps as follows ;
Materials Management -- Purchasing -- Purchase Order --Release Procedure for Purchase Orders
1 . Edit Characteristic ; You must create characteristics that related your strategy first . IN additonal data screen use "CEKKO " as table and appropriate field as field name .
2. Edit Class ; Create your class with class type - 032 . And enter your characteristics that created first step .
3. Define Release Procedure for Purchase Orders
                a.Create Release Groups and enter your class
                b.Create release codes related with Buyer , controller etc.
                c.Create Release indicator
                d. Create Release Strategies ; Enter your release codes and in classificaiton area , you must enter your values that related with characteristics that created step 1.

Dynamic release strategy and static release strategy

Similar Messages

Maybe you are looking for