Hack release strategy customizing on production system?

Hello Gurus,
I have a problem - I made a mistake in release strategy customizing for purchase requisitions and now I need to repair it (the change is possible only on development system, but our development system is now under upgrade process and no development customizing is possible for one month).
So I need change the release strategy customizing directly on production system. Please, is there some possibility (some hack or whatever) to change it on production system ?
Thank you,
Ondrej
Edited by: Ondrej Hladek on Jul 11, 2008 2:37 PM
Edited by: Ondrej Hladek on Jul 11, 2008 2:38 PM

In SPRO Materials Management / Purchasing / Purchase Requisition / Release Procedure / Set Up Procedure Without Classification / Assign Release Indicators
For one strategy there is entered 4th level, which is redundant. I need to edit line which sets in 3rd level blocked state (it should be set for Purchase Order) and then I need to delete the line in 4th level which mistakenly sets Purchase order (actually there shloud be no 4th level entered for this strategy).
Edited by: Ondrej Hladek on Jul 11, 2008 3:01 PM
Edited by: Ondrej Hladek on Jul 11, 2008 3:01 PM

Similar Messages

Release strategy & EBAN for project systems, purchasing

Hi
We have 2 different scenarios for which we use same account assignment category "Z".
1) Purchase Requisitions for capital expenses (Account assignment category "Z") - this is part of project systems requisition attached to WBS elements
2) Purchase Requisitions for expensed items (Account assignment category "Z")
I have configured release strategy with classification with following characteristics
1) plant
2) cost centers
3) total amount in PR
4) account assignment category
all 4 characteristics are same in both areas (capital and expensed)of purchase requisitions, account assignment category Z decides whether it is capital purchase or expense related purchases. Z uses order number that is internally tied to WBS element.
my question is - if some one has similar scenario then what is the best solution to handle invocation of release strategy.
how release strategy can be determine, do I need to use user exit and if yes what best user exit is available.
EBAN fields, I have researched and I cant use fields like "requisitioner" for determining release strategy.
I would like to invoke different release strategy for capital projects and different release strategy for expensed items in PR. there is a workflow attached to this later.
Please reply
Thanks and regards
Umesh

Umesh,
Well, there needs to be some way to differentiate the 2 types of purchase requisitions for you to use 2 different release strategies.
I am not sure if you have the option of using a different document type to differentiate the 2 requisitions. I would definitely look at this possibility and include the document type (CEBAN-BSART) as a characteristic in the release strategy.
Other options would be to look at using the purchasing group (CEBAN-EKGRP) or the requirements tracking number (CEBAN-BEDNR) as characteristics in your release strategy.
Hope this helps.
H Narayan

PR release strategy - customer individual scenario.- user exit required.

Hi,
WE have customer individual scenario wherein PR is created from sales order (just like) third party scenario. we have sepatare document types for both these SO (ZCUS)and PR (ZCS).
Now our requirement is to have release strategy for all such ZCS PRS for which customer group of the customer master in SO has the value 02.
We set up the standard release strategy for PR based on document type (with value ZCS) at header level. Now we want to add the above condition.
ANy idea how to achieve this?
Appreciate your quick help.

Hi Pat,
I understand that you have already setup the release strategy for Purchase requisition ZCS, But now you want a check to happen, that the release strategy should only be triggered if the Customer group of the customer master in the Sales Order is 02.
I think this is possible by using a user exit at header level as provided by Arminda.
Thanks and do let us know.
Regards
Shailesh

Transferr clasification of release strategy

Dear all,
I want to transfer the clasification of my Release strategy to the productive system.
Is it possible? only the release codes are transferred through requests.
How can i transfer it, as i do not have permission at my client's productive system to maintain it.
Thanx in advance

Aldais
SAP Note 86900 explains that you cannot transfer classification. IF you dont have access to service sap give me you email ID i can forward that note.
Summary
Symptom
The transport of Customizing data in the release procedure area 'Release strategies' can only be used in a restricted manner. The 'Transport' function displayed in Customizing under 'Table view' only takes the release strategies into account but not the dependent data of the release prerequisites, the release statuses and classification data.
Thanks
Reeves

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
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 most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

Release strategy determination for PO item level characteristic value

Hi Experts
I have user material group as release characterstic for PO.
I have created two line items with two different material groups.
How the release strategy determination occurs when the two different material groups are linked to two different strategies?
regards
ramSiva

Hi,
in this case system is NOT able to find the release startegy.
Please take care of the following explanation (see note 365604)
o For OVERALL RELEASE (purchase order and purchase requisition) the
   item fields such as Plant and Material Group will be aggregated
   to header level.
   For example you use Plant/material group
as one of your characteristics. If all
items do not belong to the same plant/material group
then
*******the relase strategy will not be found***********
unless you have maintained a blank value as one
of your allowed values for the characteristic Plant/material group
. If all items
belong to the same plant7material group
then that plant is aggregated to the
header; if one or more is different then a blank is aggregated to
the header.
If you use an overall release strategy all
characteristics which you have defined in the customizing (CEKKO-MATKL
must have the same value. If one item has material class x and the
other y the system does not know with which material class it should
look for a release strategy. Now the system sets the material class
to 'blank' and tries to find a release strategy. If you do not have
defined a blank entry in the customizing (Transaction: OMGS
: OLME >release procedure for PO > rel. strategy ) the
system won't find a release strategy.
you need
to add a blank value to your allowed characteristic values in your
release strategy. To do this you can define a blank value in your
characteristic (CT04). On the values screen leave the char.value
blank and add a description and save. Now in OMGS you can select
this value as an allowed value for the characteristic.
(Example:
To avoid this you can do the following:
- go into transaction CT04
- enter the characteristic 'CEKKO-MATKL'
- click on the tab 'values'
- set a flag in 'additional values'
- in the column 'Char. value' do not enter anything
- in the column 'Description' enter a text like 'no material class'
- save this setting
Now
- go into transaction OMGS -> button 'release strategy'
-> button 'classification'
- double click on CEKKO-MATKL' and set a flag in 'no material class' )
Please also have a look into the attached note 365604 point 2d).
BR
Nadia Orlandi

Release Strategy - Purchase requistion go back to unreleased

Hi Friends,
I am facing two problem in release strategy in our client system.
Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
Current System Settings;-
Release Procedure:- Procedure with classification ( Also setting available for setup procedure without classification maintained )
Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
Value maintained in CL24N for plant , Creation indicator.
Release Indicator:- 1 Stage:- X. Blocked
2 Nd Stage:- 4.RFQ/PO no changes
Scenario :- When PR is created and released , If any one changes the Purchase Group in any line item which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
I checked all the system setting and it seems to be correct except when i use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
Checks re requisns. with item-wise release 3
-> Checks re release group and release class 2
-> No release group exists 1
Problem. 2:- Purchase Requisition not triggering when PR is created from other source linked to SAP.
Please suggest the solution for the above problem.

Hello Kunal,
A few thoughts and questions on your problem:
You generally can't have both release procedure without classification and release procedure with classification working at the same time.
To get the system with classification working, you have to have several things in place and consistent: You need a release group. It should have a class. That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release). You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
You have to choose item-based or overall release for each requisition document type. You mark this on the document type. You must also choose the same option for the release groups that the document type will be assigned to. Example: document type NB is item-based. Document type ZB is overall. Document type will be a characteristic. CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ. Release group NN will be marked as item-based. Release group ZB will be marked as overall-based. Usually, I think, you will just use one or the other, and it will be less complicated, but the release group must match the document type.
The indicators themselves have some configuration, including a field for changeability. Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
If you are using workflow, there might be custom events related to the business objects involved that can change things, as well.
Are you using workflow?
Are you using overall or item-based release?
Good luck,
- Jeff

PRs not finding a release strategy

Hi All,
I am having a issue with creating PRs, when i create PR with one line item, it is finding the release strategy but when i create PR for more than one line item SAP can't find the release strategy.
The only common factor for the problem would appear to be that they are multi-line PRs.
Please help what should i do.
Thanks in advance.

Hi Madhur,
Kindly check below
1.If for each line item the material group is different
2.Using Header level release strategy
Thus this material group is aggregated at header level and " " value
used as document in the below note
47089 Release procedure for purching docs - Aggregation
The release procedure for purchasing documents is carried out on header
level. For this, the following values are aggregated from the items on
header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items coThe same fun
same plant. If only one alternative plant exists, ' ' is aggregated on
header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was
maintained for the characteristic 'Value' as an object value.
The same functionality applies to the material group as for the plant.
If one item has material class x and the
other y the system does not know with which material class it should
look for a release strategy. Now the system sets the material class
to 'blank' and tries to find a release strategy. If you do not have
defined a blank entry in the customizing.
(: OLME >release procedure for PO > rel. strategy)
system won't find a release strategy.
Add a blank value to your allowed characteristic values in your
release strategy. To do this you can define a blank value in your
characteristic (CT04). On the values screen leave the char.value
blank and add a description and save.
THIS PART YOU HAVE ALREADY DONE
CT04 > PO_MATERIAL_GRP has blank entry
SO JUST maintain it in customising of Release strategy.
Please also have a look into the attached note 365604 point 2d)
regards,
Lalita

Release Strategy for Preq

Hi SAPgurus...
I have release strategy implemented in my system with 7 level approvals for the Pur. Req . Now i need to Change the release strategy to 4 levels approval based on one of the Characterstics that is the Preq Net Price. Which cud be the best process to ahcieve it , since if i am going to keep the old one and create a new one then wheneve similar characterstics appear the system cant recognize which strategy to apply.......
Please can any one advice me how can i approach ...
Regards
Balaji

Hi Lakshman, Srini & Venki
From ur statements i understand to modify the existing ones , okie as u said i will delete the extra release codes and modify it . Now fine..
What happens when i moved to prodcution these changes then, say if i have Preq
with older version of release strategy how it impacts.....How i can handle this in
effective manner...To my knowledge i think whenever if i go for a change in preq the new release strategy will be affected....( In this case its fine) what abt the ones which doesnt need a change and has to be released....
Thanks for the time ...
Regards
Balaji

Release strategy for PR & PO

Hi Sap gurus
I have created release strategy for PR & PO in development server.
How do i create the same release strategy in quality & production .whether i have to create transport request from dev. or i have to create in quality & production?If i try to create a new strategy it will be in non editable mode.& shows client is not modifiable.
plz help

Hi,
If you are talking about release strategy and release group it is transportable.
Release class and Release characterstics are not transportable.
You have to configure release class and characterstics in the target server individually.
One thing more you have to give the characterstics value in each server after all the above steps.
Regards
Ankur

PR Old Release Strategy - triggering NEW Release strategy any change OLD PR

Dear Gurus,
We have implement item level PR release strategy,
characteristic used: 1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
Please advice
REgards
RS

HI,
If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
Is this is standard behaviour? pleae advice
Regards
RS

PO Release strategy release procedure

Hi
Any body can suggest
what is the procedure for release strategy transport to anther system means D to Q

Hi,
Release strtagy Configuration can be transported from one client to various client[Like creation Class,characterstic,Release code,release strtagy definations etc]
Where as assignments of Objects / class and various parameter for release strategy has to be done in individual clients in -T-code: CL24N.
Example : For Class -PO Release we need to assign -Values for Class -characteristic values has to assign in CL24N
with regards
Shrinivas Gangoor
Edited by: Shrinivas Gangoor on May 22, 2009 3:06 PM

Transport characteristics+classes of clasification system: release strategy

Hello,
Someone know how I can transport the characteristics+classes of classification system for the MM release strategy.
I think that the values must be assigned manual in each client but I do not have to recreate manually the characteristics+classes.
Cheers,
Marta

Hello,
The OSS solution to transport the clasification is via ALE.
I will create a LSMW batch to load the clasification system.
Thank you very much for your comments.
Marta
The classification data need to be transported by ALE as described in
notes 86900 and 45951. The only other solution is to enter the data
manually.
You can obtain 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 again in your target system.
For that you have to:
1. assign new values to the characteristic master data (trx. CT02)
2. assign the new data to the classification system (trx. CL30)
3. verify the consistency with trx. CL24. Please see note #186809.
For more information, please see note #365604.
Please check the answer from development regarding this issue:
"The transport of release procedure customizing data can only be done ina 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. Customer may consider
remote consulting to do the set up."

Customizing open in production system for tcode KOT2

Hi gurus!
I have a problems with tcode KOt2
The problem is that the modifications are aviable also in production system, and you can change it in production system.
How can i put it again just with the seeing mode? I want to modify it just in test system.
Thanks

Hello Nereab
Transaction KOT2/_OPA is a so-called 'current setting' in SOBJ, the settings in
SCC4 do not influence this. This is the reason why the transaction can
be called in 'change' mode in your system; the philosophy concerning
this has changed since release 4.0B (where it was not a 'current
setting').
If you want to prevent changes for this transaction, you have to follow
the information given in note 420909 accordingly.
br, Guido

Release strategy complex customer specific checks

Hi MM guys,
does anybody knows whether there are UserExits for the release strategy functionality in 46C? We´re already using this strategy functionality via classification. But now we´ve got further request concerning the checks which have to be processed to determine wether a PO will be released or locked. These checks cannot be implemented over the classification system cause they´re more complex.
Thx, for any tips.
Andy

Hi,
The Enhancement for this purpose is M06E0004 and the user exit is EXIT_SAPLEBND_002.
You can use this user exit to pass values in user defined fields (e.g. USRC1, USRC2 etc) in structure CEKKO. If the user fields given in the structure not enough then this structure can be expanded and new fields can be added.
While using this user exit, please keep in mind that the user exit gets called while you start the transaction (e.g. ME29N) and you check or save the document. So when you want to pass values, you will do so only at the time of saving the document.
Regards.

Hack release strategy customizing on production system?

Similar Messages

Maybe you are looking for