Re-set release strategy of rejected PO,after doing respective changes to po

Hi friends,
I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...
Here PO printout is possible only after the final approval...
Pls give some inputs in fixing this issue..
Thanks in advance....
Regards
Shashidhar...

Hi
What are the characteristics of your strategy?
Try to change one of them save and then rechange it to the original
eg.
If the strategy depends for example on the Purchasing Group (PG)
i mean according to different PG's different strategies working
then with ME22N change the PG save and rechange it again to the original.
or
for example If the strategy depends on Materail Groups (MG)
then do the change with MG
With ME22N change the MG save and rechange it again to the original.
I guess this will trigger the strategy again.
Hope it helps
Best Regards

Similar Messages

Release strategy of contract disappeared after using of MEMASSCONTRACT

Hi All,
May be some one can help me?
I have next problem it tr. MEMASSCONTRACT(ECC6)
Release strategy of contract disappeared after using of tr. MEMASSCONTRACT. I know why it happened, but I don't know how to correct it. Some time ago IN ECC5 we added a field to a table EKKO and used this field as one of characteristics in the release strategy of contracts. In order to transfer value of this field to field CEKKO-USRC1 we used User Exit EXIT_SAPLEBND_002. This User Exit is suitable only for online transactions (ME31K, ME32K). How can I feel field CEKKO-USRC1 in transaction MEMASSCONTRACT?
Regards, Liza

Thank you. Probably I didn't explain my problem clearly. It's section of code from User Exit EXIT_SAPLEBND_002:
ATA: reference(20) TYPE c VALUE '(SAPMM06E)EKKO'.
DATA: it_ekko TYPE ekko.
FIELD-SYMBOLS: <ymm_icl> TYPE ANY.
e_cekko = i_cekko.
*THE "ICL Contract" FIELD IS ONLY RELEVENT IN THESE TRANSACTIONS
IF sy-tcode EQ 'ME31K' OR sy-tcode EQ 'ME32K'
OR sy-tcode EQ 'ME33K' .
ASSIGN (reference) TO <ymm_icl>.
it_ekko = <ymm_icl>.
e_cekko-usrc1 = it_ekko-ymm_icl.
ENDIF.
Program SAPMM06E can only be reffered while using online transactions. Mass transactions does not use these program and it is completely class based. So, may be someone know how can i do the same , but for tr. MASS in ECC6.

Setting release strategy for PR for mixed requirement

Dear SAP gurus,
I have a mixed requirement for PR release strategy. For instance, there will be 2 types of PR created in my company. One is created manually, the other one created from MRP. The requirement is that for PR created manually the release strategy will kicked based requisitioner data. While for PR created from MRP, the release strategy will be based on MRP controller.
At first I thought that it is possible to have 2 class set for PR (both should be released at header level), but apparently it is not. So I'm forced to create ONE class that supposedly able to cater both condition.
So at first I create one class with 2 chars: MRP controller and requistioner
For PR which is created manually: I put requistioner eq 'FINANCE' and MRP controller blank (with the hope that ALL value doesnt matter),
For PR which is created from MRP: I put MRP controler eq '001' and requsitioner blank (with the hope that it means that ALL value doesnt matter).
However it seems that SAP consider that blank means blank. I tried with * it also not working. How can I configure this kind of scenario?
Please help.
Best regards,
John

The solution that we implement is to have an exit to determine the requisitioner in the PR based on the MRP controller. Thus we have a common solution for both PR

Setting Release Strategy

HI GUrus,
I wanted to set my PO to Release Strategy:
01 for raw materials
02 PO with Total net order value less than 100
03 PO with Total net order value more than 100
I've set it, but its not working. Is there other ways?
Thank you.

Hi,
Please down load the Configuration guide from the below link..
it will show you the standard MM config including Release Process for PO
http://help.sap.com/bp_bblibrary/600/html/J05_EN_IN.htm
Thx
Raju

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
   Create the release codes.     For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
   Define release indicators and branch to the detail screen. Here you
   define whether fixed purchase requisitions may be changed by Materials
   Planning, for example, and whether an RFQ or a purchase order may be
   created from the requisition.
   You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
   specify whether a requisition may be changed after the release
   procedure has begun. You specify whether the strategy has to be
   redetermined after changes, or whether the release procedure has to
   start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
   example, previous releases are not cancelled if the value of the
   requisition item after the change does not exceed plus 10% of its
   original value.
Attention:
   Be sure to create a release indicator (e.g. B for "blocked") that
   serves as the starting point for subsequent indicators. Do not set the
   indicators for release for the issue of RFQs and PO on the detail
   screen for this indicator.
   Also create a release indicator characterizing the released status.
   Set the indicators for release for the issue of RFQs and PO on the
   detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
   Assign a release indicator in dependence on the status of the release.
Example:
   You create a release strategy S1 consisting of two release codes 01
   and 02. Release with 01 is a prerequisite for release with 02. If
   release has been effected with 01, the requisition has been given the
   "all clear" for the issue of RFQs.
   You have created the release indicators B (blocked), 1 (cleared for
   issue of RFQs) and 2 (cleared for RFQs and PO).
   Now enter the following as assignment:
Strategy   C1 C2 C3 ...
   S1                          B (blocked)
   S1         X                1 (RFQ)
   S1         X   X            2 (RFQ/PO)
4. Release prerequisites
   Define which release codes are involved in a release strategy. Specify
   whether a code is set for a release status following release, and
   whether one release status is a prerequisite for another (+).
   Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

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

Issue with PO Release strategy

Hi experts,
I have problem with Po release strategy in 5 to 10 purchase orders, i have created few purchase orders(2000 Po's) with same document type and company code ..etc and saved, then release strategy has been triggered.
For few purhcase orders release strategy has not been triggered.
If i take 1 po from that few purchase orders(Release strategy has not triggered) as reference and again if i create PO,new purchase order have getting created with release strategy.
Can some body tel how this ican be possible, hope this might be standard syatem behaviour.
Hope i should delete thos e purchase orders and i should create new PO's instead of of old PO's (Without release strategy).
Some experts can share their experiance in this regard.
And how i should proceed further with this issue.??
Thanks

Hi,
You issue in your system has 2000Nou2019s purchase orders with release strategy has been triggered but 5 to 10 purchase orders do have release strategy.
& when you are creating a new PO with reference to old purchase orders (which release strategy has not triggered) and on saving NEW PO created with triggering release strategy.
Cause for above:
PO which release strategy does not trigger because the purchase orders are created before setting release strategy for PO. Those PO triggered release strategy and all are created after setting release strategy for PO.
Action:
Its completely business call for business users to go for options:
Option-- >1# You can use same old PO which release strategy does not triggered, do GR and all other process
Option-- >2# You can create new PO with reference old PO which release strategy does not triggered and upon saving you will have new PO number with release strategy triggered, then release PO & do GR and other related process.
Regards,
Biju K

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

PR overall release strategy (with shared PR document types)

We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know, this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

Hi ,
The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
The Plant can be taken as one of the characteristic.
The view CEBAN gives all the related views.
check the below LInk for Futher information on the same.
http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
hope so it helps
Regards
Anjanna.

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

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

PO release strategy based on Material Group (CEKKO - MAKTL)

Hi Experts,
I have configure the Rel strategy based CEKKO-MATKL (material group) for purchase order, but when i raise the PO Rel strategy is not affecting, Can any body tell me why.
Regards,
Kumar

You can set Release strategy based on Material group & other Line item specific fields..
You better follow a suitable and hinder less process..
For PR use Material group & Account Assignment based Release process..
then for PO use a Release Process based on Header level fields like Doc type, Amount, pur Group etc..
So that the approved PR line can be converted into PR and then the PO also subjected to Release before sending it to External Vendor..
Even if you want you can make that the PO can not be created without referencing PR for SOme users or All users..
based on your business requirement..

Escape Release strategy based on purchasing group

Dear Experts,
In our system, PO release strategy is set up,
But, some of the POs are not subjected to release strategy because they belong to a perticular Purhasing Group (P01).
Where this set up is done?
Regards,
Shashidhar

Hi Shashidhar,
In your system it seems there is a characteristic created for Purchasing Group, if you want it activated for a particular Purch Group, then please do the following
Determine the strategy that you want to be called ( You can see any existing PO to find it out), once done, you need to identify the characteristics and class
SPRO-MM-Purchasing-Purchase order-release strategy, define release strategy, select your strategy and go to details and click on classification, in case you get an error and not able to, click on release pre requisites, come back and then try again, in classification you will get to see the various characteristics maintained and also the class name at the top.
Once you have done that, please go back to the node Edit Class, please put the class that you obtained earlier and get the characteristics for Purchasing Group.
Then go to the node Edit Characteristic, put your characteristic name say PO_RELEASE_EKGRP, Click on the tab values, and add your Purchasing group here and save it.
Then go to transaction CL24N, provide the class, and select the release strategy you are interested in, and select change, and detail, there for the characteristic for Purchasing group, you can add the previously added Group, and you are good to go.
Please let me know if this helps.
Regards
Shailesh

Release strategy for RFQ

Hi,
Please let me know,how to set release strategy for rfq.. i'VE ACTIVATED MY RELEASE STRATEGY FOR po USING TABLE cekko... iF I WANT TO ACTIVATE RELEASE STRATEGY FOR rfq... WHICH TABLE AND FIELD NAME I WANT TO USE... PLS EXPLAIN..

For RFQ also we can use the same communication structure CEKKO, but for differentiation between release startegy of Contrcats Purchase orders & RFQ's better to use the Charcteristic Document category i.e CEKKO - BSTYP - Purchasing Document Category

Re-set release strategy of rejected PO,after doing respective changes to po

Similar Messages

Maybe you are looking for