Stop release strategy when pgrp changed triggering different release group/

Currently when our buyers change the purchasing group field on the purchase requisition it is triggering a new release strategy because the release group and code is different than the original creator.
It has been indicated that we should request from SAP that these two fields be made available to the structure for the release strategy.
Is there a user exit that we can use to stop a new release strategy?

Hi,
Do you have different rel. stgy for diff. plants? if yes, than which rel. stgy should be picked in case if both plants entered have different rel. stgy? what is your expectations/requirements?
If your PO is to go through diff. approvals for different plants than you should have different PO for each plant (even diff authorizations and rel. codes), or else you should not have plant as the criteria. Technically, whether it is fesible or not is different question, but whether practically your organization is ready that if a common material is to be procured it will have approvals of only one plant or may be a different approvals all together?
Regards,
Dakshesh

Similar Messages

Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO

Hi All,
I have the following requirement/scenario
1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
This is what I hoped for would work after doing the necessary config,
For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
The problem
Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan. I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
Is their any other identifier I can use to address the requirement above? Let me know.
Thanks
Ashvin

Thanks Charlie for your response.
The conditions in the PO is not equal.
On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
Let me know your thoughts.
Thanks for your feedback.

Release Strategy in PR not triggered for different Purchase Groups.

Dear Experts,
For Purchase Requistion - Header Level Release Strategy has been defined with Purchase Group as one of the Characteristics(Characteristic Values are V1, V2, V3).
When PR is created for 30Line items with V1, V2 or V3 as Purchase groups independently- Release Strategy is triggered.
But when a combination of all 3 Purchase groups is used in the same PR for 30 Line items together. No Release Strategy is Triggered. All these 3 Purchase groups have been assigned for all strategies.
Thanks & Regards
Chandan H N

You are using characteristic P. Group for different RS. That means that if only one value exists, the system will be able to understand which RS to implement. If you are using more than one values for this characteristic, the system simply does not know which RS to choose and takes nothing.
More simply you are using a header data (p. Goup) for RS and you are using it in line items. This is wrong. You have to make PR's only for the respective P. Group

PO release strategy ONLY for change

I have a requirement to only have a release strategy for a purchase order only when it is changed
The problem is that even if I can disable the event to be triggered when created, the release strategy is written down to the EKKO-table when the PO is created meaning that the purchase order still needs to be released before being used for example in MIRO.
How can I avoid having the release strategy written to the EKKO-table when the PO is created?
How can I have it written to the EKKO-table when it is changed?
Good answers will ofcourse be rewarded with points!
Edited by: Snowroller on Feb 11, 2012 4:00 PM

Dear,
Check this and try. Not tested.
Set up Version management for Purchase order and keep all relevant fields of PO relevant for version change.
Add charaecteristics PO_Version value as 00000001. So, When you create PO the version will be 0 so no release strategy. Whenever relevant fields changes the version changes to 0 to 1 and release strategy triggers.
Try this option.
Regards,
Syed Hussain.
Forget to mention please search with 'PO release strategy based on Version Management in SAP' you will get many SDN posts.
Edited by: Syed Hussain on Feb 11, 2012 7:27 PM

Reset Release Strategy for any change in the Purchase Order

Hi,
Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
If so, where do we need to make the configurations.
I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
Thanks in Advance.
S.Raghavan

hi sandesh,
sorry, i know it's too late.
i tried your suggestion, it works blocking the purchase order after release strategies are setted.
sandesh, raghavan:
i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
regards
f

How to know the database changes between different releases

Where can I get the information of database changes, like for example new columns new tables, etc, between different releases?
My goal to try to determine the current version, or is there a better way?
Thank you

For JD Edwards World or for JD Edwards EnterpriseOne - you can go to upgradejde.com Once this screen comes up, pick Resources. You will then have an option to take JD Edwards EnterpriseOne or JD Edwards World. On the next screen, you can select the tab Compare Releases. This will allow you to enter the release that you are currently on and enter the latest GA release of software. You will then see all the differences between your current release and the release you should upgrade to. You can also format this into a printed report.

WHEN-LIST-CHANGED Triggers Works Only Once ??

hi
i have a form with the 2 list ITEMS
And i have some trigger WHEN-LIST-CHANGED For the
first LIST item which Populates the Second List
Based on the Value selected in First List
Its Works Fine For the First time.
But for second time Onward , it Does change the Value of the items in List2.
Do i have to first clear and then repopulate, i tried this but then i get a total
Blank , please help.
jai

From one of our support notes:
List Items populated from Record Groups are extremely useful when you need to
give your users a choice of items to choose from. This note will show you how
to create two list items that have a "master-detail" relationship, i.e., the
items appearing in the "detail" list item will depend on what is chosen in the
"master" list item.
CREATING THE LIST ITEMS
Create two list items called DEPT_LIST and ENAME_LIST. Allow them to remain
the default type of List Item, Poplists. For this situation we will not make
them base table items. Go to the property pallet of each list item, click on
the elements in list property and choose more. The cursor should be in the
very topmost item under List_Elements. Depress CTRL+SHIFT+< to remove this
default element and depress the OK button. Since you are going to populate the
list item with RG values at runtime you do not need this element. This will
avoid an "FRM-30351: No list elements defined for list item" error when
running the form.
CREATING THE RECORD GROUPS
For this example, we will use the dept and emp tables. We have a choice of
creating the Record Groups (RG) dynamically at runtime or at design
time. In this case, the easiest option is to create them at design time.
First create a RG called DEPT_GROUP with the following select statement:
SELECT TO_CHAR(DEPTNO) A,TO_CHAR(DEPTNO) B
FROM DEPT
If you are unfamiliar with the structure of the RG required when it will be
used to populate a list item please note the following:
1. A list item has both a label and a value. For this reason the select
statement brings back two fields, one which will be the label name and the other
the label value.
2. TO_CHAR is used to convert numeric values to character as the list item
contains character values.
Second, create a RG called ENAME_GROUP with the following select statement:
SELECT ENAME A, ENAME B FROM EMP ORDER BY ENAME
Note that depending upon your applications logic you may want to use the
distinct operator to prevent duplicate names. But you should be aware that
this will result in the overhead for sorting. Also, since ENAME is a VARCHAR2
data type, the to_char function is not needed.
POPULATING THE GROUPS AND LIST ITEMS
You can populate the RGs and list items from a number of triggers but the most
common is the WHEN-NEW-FORM-INSTANCE trigger. Place the following code in this
trigger:
DECLARE
V_DEPT_GROUP NUMBER;
V_ENAME_GROUP NUMBER;
BEGIN
V_DEPT_GROUP:=POPULATE_GROUP('DEPT_GROUP');
V_ENAME_GROUP:=POPULATE_GROUP('ENAME_GROUP');
POPULATE_LIST('DEPT_LIST','DEPT_GROUP');
POPULATE_LIST('ENAME_LIST','ENAME_GROUP');
END;
Note that this code is needed to initially populate both RGs and both List
Items.
If you run the form at this time you will see that DEPT_LIST contains all the
departments in Dept and ENAME_LIST contains ALL the enames in the emp table.
As our original goal was to populate ENAME_LIST depending upon what was chosen
from DEPT_LIST, we will now add the code to do this. In this situation we will
add the code to a WHEN-LIST-CHANGED trigger on DEPT_LIST. The code should
look as follows:
DECLARE
V_NUMBER NUMBER;
V_QUERY VARCHAR2(512);
BEGIN
V_QUERY:='SELECT ENAME A, ENAME B FROM EMP
WHERE DEPTNO = '||:DEPT_LIST||' ORDER BY ENAME';
V_NUMBER:=POPULATE_GROUP_WITH_QUERY('ENAME_GROUP',V_QUERY);
POPULATE_LIST('ENAME_LIST','ENAME_GROUP');
END;
First we will build a query that will contain the currently chosen department
in DEPT_LIST. This is basically the same query we created in RG ENAME_GROUP
but we are adding the where clause restriction. We then use the
populate_group_with_query built-in to repopulate the RG and then populate the
list again.
Run the form again and test. Choose department 10 from the DEPT_LIST list item
and then choose the ENAME_LIST item. You will note that the enames appearing
in ENAME_LIST will be those in department 10. This should work for any
department you choose.

Release strategy: problems after changing the price

HI Experts,
I have the follwing problem.
I´ve setup the release strategy for Purchase reqs.
The strategy includes 3 approval levels.
release indicator with changeability 4 and a value of 0,1% for the first two approval levels.
I´m able to release it, but if I release the first two appoval levels and change the Preq the release strategy goes back to the first level. Fine.
But the problem is now that I´m able to release the first level but if I try to release the second one I get a error message.
I guess the problem is the changeability - but how can I solve this issue?
The system have the cancel all approvals if someone changes the price.
Any ideas?
Thanks
Alex

HI RJ,
the exact message is "Release prerequisite not fulfilled".
The system should act in the following way:
Approval levels:
1. Supervisor
2. Manager
3. General Manager
1 and 2 is approved.
Then the requisitioner changes the price.
Release will be changeled (Releases already effected will be cancelled).
OK that work, now the release process starts with level 1.
1. Approved --> OK
2- try to approve and get the message "Release prerequisite not fulfilled".
1 and 2 have the same release indicator with 4 and 0,1%.
Thanks
Alex

PR release strategy reset after change in quantity/inclusion of line item

If a user adds a line item or increases the quantity of an existing line item to a fully released purcahse requisition, then the system does not render the PR for reapproval. Is there any way to configure SAP such that the release strategy resets if any of the above changes are made in a fully approved PR?

Hi,
the release strategy will ONLY be reset if one of the fields that are contained in your classification are changed.
For example
If you strategy is determined by Plant and value, if the plant or value doesn't change then the release strategy will not be affected.
So if you change qty and do not change value then the release strategy will not be reset. This is a basic limitation of the design.
But if you ARE changing one of the characteristic values of your strategy and you are saying that the release strategy is not being reset, then something else is wrong.
Steve B

Where can I found table or structure changes across different releases ?

Hi !
Just one question:
I would like to found where can I see tables or structures changes across differents releases of SAP R/3?, i tried to found a doc about this... but i couldn't found it.
For example, which table have been modify form version 4.x to 4.z, i mean fields added or modified, etc...
Thanks in advance,
Albio.-

Hi Albio,
You can do this. You can check the activation log of any table which you have to find for change history.
Just go to se11 and type the table name click on display and then go to utilities -> then activation log, it will show you all the changes made to table
Regards
Sumit Bhutani
<b>Ps reward pts if helpful</b>

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

Stop iTunes opening when I change a song with Remote, Stop iTunes opening when I change a song with Remote

Hey Guys,
I use the Remote app on my iTouch a lot. The problem is when I'm gaming, iTunes becomes the front window and block the view of my game.
Is there anyway to stop that happening?
Thanks,
cccc297

bump 10char

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

Assign right cost center to PR release strategy

in purchase requisition order type, how to assign cost center for release strategy? i.e. for different release strategy, i want to assign different cost center.

Create a new Charecterstic Using Table CEBAN and KOSTL. Here Select Multiple Entries and Maintain your Values (in Values Tab Maintain all the costcenters you are making use of).
Assign it to class and Continue with your Normal Release Procedure.
Revert any issues.
Thanks,
Shiva

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

Stop release strategy when pgrp changed triggering different release group/

Similar Messages

Maybe you are looking for