Release strategy , changing class

Once you do release strategy using particular class, is it possible to adjust the release strategies by changing the existing class?
eg; class CL contains one characteristic total order value and done release strategy
I want to change the class CL adding one characteristic say doc type, is there any effectby this

Hi,
I think it is possible.
Add the characterstic in class and in classification of release strategy.
regards
suresh

Similar Messages

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

Po Release Strategy Change

Hi Gurus
I am changing the release strategy for po.
Same characterstics and value also same.
only change is release codes. so that, what i can do. if i add new release codes in same old strategies ?
Otherwise i can create new release strategies ?
if i create new what i have to take steps ?
if i use same old release strategy and in that i can chage release codes what about previous documents ?
client side cl24n here we can block old stratiges what about the documents created on old ?
If any body answer right rewarded full.
Thanks in advance
Regards
Laxman

Hi
we have also did some changes to relase codes after once in use & we had encountered some problems in the PO.
For E.g. If you have the previous repease codes as L1 & L2 , & if you are removeing the L2 form the release codes then All the PO's whcih are approved by L1 & awaiting tobe approed by L2 will be in hanging status. You need to go into each PO 7 click on revoke acceptance & Click on check then The new relase codes will appear.
If you can clearly explain what you are planning to do on the relase codes , then we can advise you in the right manner.
Thanks & Regards
Kishore

Old POs affected by release strategy change

Hello,
Recently major changes were made to a group of release strategies for our business. The new release strategies are being applied correctly to all new POs. However, even POs created before the change of release strategies are showing the new strategies. Even the old POs which have already been released and goods received are showing the new strategies. How can this be corrected? POs created before the change should be showing the old strategies. Thanks in advance.
Regards

Hi,
First of all, I don't suggest to bring back the old release strategies as it will mess up the entire system and to me it does not make sense at all as the efforts to solve these issues with old POs are significant and believe me, you will encounter a lot of pains and frustration. What I suggest hereunder is as simple and effective as I thought given your current situation -
1) In regard to those old POs (I hope the number is small up to now) to which the new release strategies are applied, you will have to use ME28 for mass release. Of course, you can develop the simple ABAP program which can allow mass approval (if you wish to).
2a) If you did not eradicate your old release strategies through configuration (i.e. you used only "2" to block your old release strategies in CL20N Transaction), then you can select the proper value in the "Changeability" field of your "released" release indicator that was used in your old release strategies. This selection will allow the fact that no new release strategy will be applied for your old POs in case of change.
2b) If it turns out that your old release strategies were deleted from the current system (which I don't really know why), then the only solution you should do is to inform your end users of not making any change in the old POs.
Cheers,
HT

Overall Purchase requisition Release strategy : Changed after Rejected

Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.

Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev

Reg: P.O Release Strategy Changes

Hi All,
Release strategy is configured for a P.O.The changes in terms of releasing the P.O can be viewed in P.O Screen---Environment -
Changes.
Do we have any table for checking the changes made to a P.O in terms of Release strategy?
Have a Nice Day.
Regards,
RaviKumar.S

Hi,
You can check this in CDHDR table.
If version management is active for your PO then you can check the changes in EREV table.
Regards,
Bharat

How to check the PR release Strategy change date?

hi,
how to check when the PR Release Strategy chagned by someone ...?
Regs,
S J Solanki

Hi
You can directly go into the Purcahse order & check for the Heder changes which will give the Changed Date
If you need to use two table to find out the date when the Strategy was changed.
Use Table CDHDR & CDPOS. Object key is the POurcahse order number
Thanks & regards
Kishore

PO Release strategy, error: class POCLASS class type 032

All SAP Gurus,
We are configuring new PO release strategy.
When we go to Release strategy - classification
(Release procedure for PO - Define release procedure for PO - Release Strategies - classification)
It gives following error: Error in classification (class POCLASS class type 032).
Where we can maintain the classification?
Regards,

Dear,
Please follow bellow detail.
SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
Three steps involved in release process of purchase order.
1)     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
2)     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
3)     Define Release Procedure of purchase order: -
In this step four processes involved.
1)     Release Groups
2)     Release Codes
3)     Release indicator
4)     Release Strategies
1)     Release Group: - In which you can define release strategy group
For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
2)     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.
3)     Release indicator: - In this step you have to define release indicator.
Like X - Blocked, I - Under process, S - Release.
4)     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 continue
Click on classification button, Enter values of purchasing group for which you want to created release strategy.
Regards,
Mahesh Wagh

Retrigger Workflow if PO Release Strategy changes

Hi All
I have configured workflow for PO release.Now through work item if I am deleting a line item of the PO such that PO is capturing new release strategy due to change in PO value then workflow does not gets re-triggered again as per new release strategy.How can I achieve this?
Edited by: satish kumar on Apr 18, 2009 9:13 AM

Hi,
For Creation it working fine right, i.e. Event triggering fine
1) After Changing the PO, save it
2) And tell functional consultant, whether they configure for the settings for PO change in SPRO
Regards,
Surjith

What is the name of the table where Release Strategy changes are maintained

Dear Friends,
Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

Hi Chintan,
I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
I hope it clarifies.
Regards
sachin

Inconsistency for Previous Release Strategy of PO

Dear colleagues,
Is there any standard program to come up with new values and criteriau2019s for new release strategy if pre defined release strategy, with class, is deleted for PO approval.
Best regards,

Hello Metin,
can you please elaborate your question, it is not very clear, as it is not showing the clear picture of your requirement.
regards,
Prashant Rathore.

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

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 does not reset after PO change - tried changeability 4 & 6

Hi,
After my PO is released, I change the item quantity/price such that the net PO value (increased) is changed MORE than the tolerance % set in the changeability. I expect that the PO release should be reset but it does not.
However if my PO value is changed (increase) such that my PO value is now in a different "release bracket/range" -- as it falls into a different release strategy, then the release is reset.
Could anyone advise me what is wrong? I tried everything - i tried changeability = 4 and 6. i deleted the whole release class, release strategies and recreated -- nothing.
According to OSS note 493900 below, it should reset when the tolerance % is breached.
I'm on SAP 4.7.
Anyone could advise?
thanks!
     3. Question :
     Why is the release strategy not reset ?
     Answer :
     A reset of the release strategy only takes place if
            - the changeability of the release indicator is set to '4' in
               case of a purchase requisition and '4' or '6' in case of
               another purchasing document (purchase order, request for
               quotation, contract, scheduling agreement),
            - the document is still subject to the previous release
               strategy,
            - the new TOTAL NET ORDER VALUE is higher than the old one.
     The total net order value is linked to CEKKO-GNETW for a purchase order,
     CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
     for a purchase requisition overall release.
     If you have maintained a Tolerance for value changes during release
     (V_161S-TLFAE), the release strategy is reset when the value of the
     document is higher than the percentage you have specified and if the
     document is still subject to the previous release strategy.

Hi,
Thanks.
The release strategies are able to be determined correctly when the PO is created so I guess that means its all setup correctly?
The issue is only with PO change - how to cause the reset when the PO value increases by more than the tolerance %.
cheers.

Purchasing document release strategy to be cancelled at all changes

I want the release strategy of PO/ Contract/ Sch. Aggr. to be cancelled at every change i make to the document and not only the value. I do not want to include any fields at the class, i just want any change (like addition of new material, change of account assignment etc) to cancell the release document.
Regards

The way to achieve this requirement is to create a custom field in the PO header that signifies that the PO has been changed.
It should be populated with a value say - X when a change is done and presence of this X should trigger release strategy. So you will need only this field in the characterisitcs and through user exit populate this field with X when PO was created and once released, make it blank. Then when changed repopulate with X
In this way you can ensure that any change to PO will trigger the release strategy

Release strategy , changing class

Similar Messages

Maybe you are looking for