Po release strategy - if value decreased

Dears,
If the Po value is decreased, I need the release strategy to be re triggered. As I know in standard its not possible. But can you help Is there any BADI or user exits can be used to accomplish this task.
Regards
Kamesh

Hi,
Use release indicator '4' or '6" during designing of release strategy.
And
If you want PO release strategy should trigger for reduced value ,then you can for User exit EXIT_SAPLEBND_002 or check to modify standard function module ME_REL_STRATEGIE_EKKO which help to reset existing release strategy for reduced/increased and/or values.
For more check the SAP note:493900
Regards,
Biju K

Similar Messages

PR release strategy-characteristic values

Hi All
Is there any data base table in which Release strategy characteristic values are stored.
Gobinathan G

Hi Gobinathan,
Go through the following link for complete procedure for PR Release.
http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
Check table CAWN.
Regards,
Nani.

PO Release Strategy on Value Based

Dear All My Friends,
i want to define the following Release Strategy, please advice how it will be done
Person A will Release PO value <=50,000/-
Person B will Release PO Value >50000 and <=100000
Person C will Release PO Value >100000
please help me
Thanks and Regards,
Rajesh G

Hi,
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 total value. So you can create characteristic for Total net value. Take reference of CEKKO structure and GNETW field for Total net value in additional data of characteristic. E.g :- Total net value u2013 GNETWu2026Click on intervals allowed check box ..
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 u2013 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 u2013 Purchase Head,
Release group: -01, release code: - 02 u2013 Auditor.
3) Release indicator: - In this step you have to define release indicator.
Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
4) Release Strategy: - This is the final step for release strategy.
Assign release code 01, 02.
Click on release prerequisites, select 02 u2013 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 Total net value for which you want to created release strategy.
Person A will Release PO value <=50,000/-
Person B will Release PO Value >50000 and <=100000
Person C will Release PO Value >100000
Utsav

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

Release strategy values

Dear All,
Is there any table to find the change documents for release strategy characteristics values. Or how to find who has changed the CL20N values
Regards
Kamesh

Check in Table AUSP.

PR Release Strategy for MRP & Manually created PR

There is a scenario in which it's required when,
PR is generated automaticaly through MRP then Release strategt should be applicable and when
PR is created manually then release strategy won't be applicale.
Please suggest about this..........
Thanks in advance.

Hi,
You should have two document types ( as required by you here), MRP PR document type & Manual PR document type.Link plant, MRP group and the default order types as MRP PR document type in OMDT t.code.
You should create release characteristics (CT04) with the table & field and add all release characteristics in release class. For document type release characteristics with CEBAN & BSART and do not keep value ZNB which you do not want, just keep value ZMNB. During design of release strategy keep value only for document type ZMNB with other character values.
Regards,
Biju K

Release strategy H8 Update

Hi Experts,
We wanted to know who changed the release strategy H8 value in our SAP system.
Found that PRD System release strategy GT value has been updated somehow with in six months.
please let us know how to check find out who updated value?.
Thanks
Malai

Hello Malai,
I think that for "Release Strategy" questions you should opan a thread under category SAP Community Network Forums » SAP Solutions » ERP - Logistics Materials Management (MM).
Please, go to and formulate your question.
Best regards,
Rafa

PO Multilevel Release - Value Decreased

Dear Gurus,
I'm not familiar with PO release procedure.
We have a scenario:
Release is based on the price
$5000 - $20000 release by FI
>$20000 release by FI, then release by MG
How to set it?
Currently we create 2 strategy:
FI consist of FI
MG consist of FI & MG
For value $5000 - $20000, we assign FI strategy
For value >$20000, we assign MG strategy
The case is....
1. PO created with value $25000 -> will triger release strategy MG, need FI & MG to release
2. FI release, then MG release
3. PO quantity is reduced, so that the PO value also reduce become $15000
What happening in my system is, the PO release status is reset (block), and now it use strategy FI and required FI to release it again.
By common sense, it doesn't seem right that FI had release/approve this PO earlier and now FI need to release it again.
Is there a walk around (or is the current configuration incorrect?) so that in this scenario FI no need to release it for the second time.
Thank you.

Hi,
The behaviour you are seeing is the standard behaviour and is correct.
See Note 662993 for an explanation:
When quantities or values are decreased, the system resets the release
only if a different release strategy is determined for the lower
quantity or the lower value.
If no different release strategy is determined due to the quantity or
the value decreasing, the system retains the releases that already
exist.
This is the desired standard system behavior.
As the note also says: "This function can be changed only by a customer-specific modification.", there is no standard way
to achieve any behaviour otherwise.
Regards,
Purnima.

PO Release Strategy not triggerred for particular Total Net Order Value

Dear,
I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
Please suggest for solution.
Thank you.
Warm Regards.

Dear All,
While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
May I know how the value for this field gets calculated.
Thank you.
Warm Regards.

Purchase order release strategy with a characteristic value as a variable

Hi all,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
a few other custom fields
We would like to add a characteristic based on the creator of the PO. In the purchasing department there are two person which have the authorization to create an release POs. The goal is now to check if the actual user, who release the PO, is different from the PO creator. The value of this characteristic may not be a fix value, it must be contain the name of the actual user name.
Is there are a possibility to insert the characteristic value as a variable such as SY-UNAME instead a fix value?
Thanks,
Charles

this is verymuch possible. You can use unsed fields user1, user2 etc in CEKKO or (ii) insert a new field in CEKKOZZ and use the new field. You need to build up logic in user-exit such that this field will take the value of person who had logged in. This can be done by ABAPer.
Hope this resolves ur problem

NUMBER OF CHARACTERISTICS AND VALUES IN RELEASE STRATEGY

Hi there, how R U.
Please, can any body help my with this one ?
How many characteristics may I have in a release estrategy for purchase order an contracts ?, how many values could a characteristic have ?, if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
I hope you can help me.
Have a nice day.

How many characteristics may I have in a release estrategy for purchase order an contracts ?,
You can have as many number of characteristics you want for release strategy, no restirction
how many values could a characteristic have ?
You can have as many as you want, no restiction
if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
Release code you can define only 8 and if oyu want more release code than create new release group and assign more release code
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
the release strategy can hold only 8 release code but every release strategy you can have more than 8 charcteristics and each char can have n number of values and that can be decied at char creation level

PO Release strategy User Exit if value is Reduced

Hi,
I need to write a user exit to trigger the release strategy in Purchase order even if the value is "Reduced".
As you may be knowing releases will only be triggered if the value is increased according to standard SAP functionality.
So to trigger the release stratgey even if the value of PO is reduced some one suggested me user exit "M06E0004" Program :ZXM06U22.I guess we need to define a new characteristic called "URSC1".But cannot make out how really i can achieve this.
Can any one please guide,if you have worked on it earlier.
Thanks.

Gentlemen,
Any Ideas....!!!

PR Release Strategy- transport of charact/class/ values using ALE

Does anyone have the information relative to ALE set up for release strategy-
I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
This will be a great help.
Thanks
Raj

Hi Raj,
Please check the below notes for more inrofmation:
86900 - Transport of Release strategies (OMGQ,OMGS)
799345    Transport of release strategy disabled
10745     Copying classification data to another client
45951     Transporting class data: system / client. - has details of what you are looking for.
Hope this helps.
Regards,
Ashwini.

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 on doc. level isn't working because different values for B

Hi,
At my company we just created a new release strategy (3rd) for PR's. The old strategies were on item level, the new one is on document level. This is the third strategy in the system and with every new PR the strategy is decided based on the creation date (table EBAN field BADAT). For example:
Strategy 1 - BADAT < 2009.01.01
Strategy 2 - BADAT >- 2010.01.01 AND BADAT < 2011.01.01
Strategy 3 - BADAT >2011.01.01
These selection criteria are stored in the class.
This used to work fine between the 1st and 2nd strategy but now it doesn't. Whenever a new line item is added on a different day than the other line(s) the value's for BADAT will be different within the PR and the system isn't able to select a strategy. It's like no value is used for BADAT because there are more than 1 available. As a result the release tab will disappear and the PR will be ready to create a PO from it.
For example:
Line 1 BADAT 15.09.2011
Line 2 BADAT 15.09.2011
No problem releasing the PR
Line 3 BADAT 17.09.2011 added (release strategy reset)
Release tab disappears so no release can be done. However, this PR line 3 can now be converted into an PO without being ever released.
One solution we thought about is using the PR number BANFN. But no ranges are allowed in the class so it doesn't seem to work. Another option is to delete al the old strategies but what will be the consequences for all the old PR's?
We are not sure what to use. Maybe someone else worked out this issue before or has an idea?

Hi,
First of all why you want to release a PR based on Creation date ?
Anyhow, as I understand from the above explanation, since you have created your 3rd strategy @ header/document level. You are facing this issue.
If you have a strategy @ document level then why you want 2 separate strategies @ item level.
Following are the possible solutions as per my understanding
1. You can make the 3rd strategy as item level itself so that the different creation date for different items wont be a problem.
2. You don't have to delete the Old release strategies instead you can remove the characteristics assignment so that release strategy wont be determined @ item level & you can keep the new release @ document level. But in this case you cannot have creation date as a characteristic since it will result in the same issue..
Thanks & Regards,

Po release strategy - if value decreased

Similar Messages

Maybe you are looking for