PO Release strategy on Overall Limit

HI All,
Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
For limit PO it triggered on Exepected value but we want to trigger it on Overall Limit value.
( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
Please help on this.
Thanks in advance
Vikas

Dear Vikas,
you can use enhancement M06E0004 , Exit EXIT_SAPLEBND_002.
This allows to change values in structure CEKKO based on specific conditions.
First after activating you have to put this line:
e_cekko = i_cekko.
This means that no change will be made to cekko structure. Then if you want to change gnetw value, do something like this:
e_cekko = i_cekko.
If xxxxxxxxxxxxxxx.
e_cekko-gnetw = xxxxxxxxx.
endif.
Maybe you can have multiple items so you will have probably to loop on IT_BEKPO table to get the total Overall Limit for all items in your document and then transfer the total value.
Good luck,
SL

Similar Messages

PO release strategy on Overall limit of the PO

HI All,
Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
For limit PO it triggered on Expected value but we want to trigger it on Overall Limit value.
( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
Please help on this.
we have used the enhancement used : M06E0004 , Exit EXIT_SAPLEBND_002.
But I do not find the table or field showing the overall limit of the PO so that I can put the same in my purchase order release stucture.
Thanks in advance, will appreciate any help on this regard,
Anurag Goel

Hi
The expected value is the value that the item is not likely to exeed. in std SAP the expected value serves as a creterian for a possible release procedure for limit p.o
Thanks

Additional PR release step in current release strategy

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the first release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise how to implement the additional release step. Thanks.

Hi Arghadip,
Thanks for your reply. My intention to create different doc type is for separate set of release strategy.
In current release strategy, for example, if doc type = NB, creation indicator = manual and the total value of PR is $1K, then the PR requires release code A1 for approval and the approval is align with the company finance policy. The manager (with release authority A1) of the PR creator then selected by the user exit and assigned with workflow task.
For the request for additional release step, if doc type = ZS, creation indicator = manual and the total value of PR is $1K, then the PR requires release codes AA and A1 (new release strategy). The user exit will assign a dedicated position/user (not necessary the manager of the PR creator) for release code AA, and then assign the manager of the PR creator for release code A1. Therefore, even the total value of PR is also $1K, but since the PR item contains material group 80501, then the PR require an additional approval on top of the $1K financial approval.
Your comment is welcome. Thanks again.

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

Overall release of PR in Release Strategy

I have created item-wise release of PR using with Classification of Rel Str.
But when I am creating overall release of PR I am not getting the tab.
I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
Pl guide
regards
VS

Hi VS
Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
Best regards
Ramki

PR Overall Release Strategy Problem

Hi Expert,
I have set the following
Characterisrtic Name:
1) ZPR_Release_Plant, Char : CEBAN-WERKS (Char format : 4)
2) ZPR_Release_DOC_Type , char : CEBAN-BSART (Char format : 4)
3) ZPR_Release_Pur_Grp, Char: CEBAN_EKGRP (Char format : 3)
4) ZPR_Release_Total_Value, Char: CEBAN-GFWRT (Curr format : 15 and EUR)
I assign the above to Class : ZPR_Overall_Rel
I created Release Grp R1 and assign the class and tick "Overall Release" checkbox. There is only one class, no others in the list
I created two Release codes, F1 - Senior Finance Manager, C2, CEO
I created two purchasing group, LLL and LYL
I used the standard indicators for S - block 2 - RFQ/PO and I created two release strategies A1 and A2 for Rel grp R1.
A1 - release Code: F1, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LLL
A2 - release Code: C2, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LYL
The problem is when I tried to created the PR, it doesn't work at all. No trigger whether I click the "check" button at the toolbar of the PR (i.e., the release strategy tab not appearing at the header). I also tried saved and display the PR and see if the Release strategy appears at the header but still not triggering.
Can you folks advise?
Thanks
Lo

Forgot to check the box "Overall Release" forthe Nb doc Type. The problem is now solved.

PR overall release strategy

Hi
Greetings!
Overall all release strategy had already been set up in our system and it is working fine. But When i try to create a new strategy, it is not working.
We have a class for over all PR release with the following characteristics.
1) Purchasing Document type
2) Plant
3) PR total value
4) Cost center
5) Purchasing group
I have made the following settings which are relevant for overall release
1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
2. Materials Management --> Purchasing > Purchase Requisition> Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
Is ther any other settings which i am missing? Please help me in resolving the issue.
Gobinathan G

Hi Gobinathan G,
I am aware that you already did the following procedure:
1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
2. Materials Management --> Purchasing > Purchase Requisition> Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
However, since you are moving towards Overall release, what you must complete in order to achieve
the desired result, is to create a new Characteristic, and use it within the class parameter that
you already created to control the values in your release strategy. Then you have to associate the
new characteristic to the field name GFWRT in table CEBAN. It may be done in the Additional Data
Tabulator of the characteristic.
It worked for me.
Hope it helps.
Alfonso Chakarji

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.

PR overall release strategy with acc. assignment category characteristics

Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
Isabelle

What is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer

Overall Release Strategy

Hi Experts
I am trying to set up an overall release strategy with the following characteristics: total value and account assignment K.
In order to get the overall release strategy to work I had to set the overall strategy at the document type level (NB).
Now material PR and consumable PR are subject to an overall release. What can I do to set the strategy for only PR with account assignment K.
Thanks
Belle

Please let us know what have you maintained in CL20N
Regards,
Indranil

Regarding overall purchase requisition release strategy

Hi,
For following combination PR release strategy is not working.
1.Total value of requisition
2.Purchasing Organization
3.Name of Requisitioner/Requeste
But when we take any one of them it is working. But when I tried to put together, these field system is not picking any release strategy.
What would be the reason? is there any inter connection between these fields?
Regards,

Dear Aj,
Chek is theare any other release strategy in the syestem wth mentioned chraterstic,
also chek all chraterstic are ticked in the release strategy?
Some time syestem is not able to find the unique release strategy,
Please let me know

Free limit (overall limit vs free limit)

Hello,
I would have a question regarding item category D (service) in Purchase Order.
For such items, a tab "Limits" is displayed, In this tab, there is a field "Overall limit" but also a nested tab called "Other limit" with a field "Limit" (corresponds to free limit in the help)
Help gives me this message :
Overall limit --> Maximum value that the total of all unplanned services (or the value of the material) covered by this document item may not exceed.
Free limit --> Maximum value which an unplanned service may not exceed.
I don't understand the difference between those 2 fields. When I use ML81N, I can not create an item whose the value exceed one of this field.
Example given :
Overall limit = 5000u20AC
Free limit = 1000u20AC
In ML81N, if I create a SES with gross price = 1001u20AC, I get message No limit for unplanned services amounting to 2.501,00 exists
Other example :
Overall limit = 5000u20AC
Free limit = 10000u20AC
In ML81N, if I create a SES with gross price = 5001u20AC, I get message No overall limit of 5.001,00 for unplanned services exists
So I am blocked as soon as 1 of the limit in reached.
Does anyone could explain the difference between those 2 fields?
Thanks for your help,
Patrick

Please refer to the Online documentation: Material Management -> External Services Management -> Procurement of Services: Processes -> Accelerated and Simplified Processes -> Use of Value Limits (for Unplanned Services) Inside this documentation, it is stated that there is a variety of limits (combinations) to be used:- - Overall limit only - Overall limit and limit on services covered by contract item(s) - Overall limit, limit on services covered by contract item(s), - and other limit - Overall limit and other limit - Overall limit on services from model specifications or standard service catalog - Expected value The expected value is used in the update of the PO item value and this is the value used in the release strategy. Here is the f1 help: Expected value - ESUH-COMMITMENT Value that the unplanned services (or the materials) covered by this item are not expected to exceed. Use If you are working with the release (approval) procedure for purchasing documents, this value serves as the basis for a release strategy applied to this document. If you tick 'No limit',you don't need to enter 'Overall limit',but must enter 'Expected value'.Because 'Expected value' will affect the release strategy. Please read the note 440601 connected to this. Concerning the variability of actual cost of a purchase order, expected value means that the unplanned services (or materials) covered by this item are not EXPECTED to exceed. It is not mandatory that it has the same value like total limit value. Expected value can exceed, it is used for comparison with total limit value in cost control. Expected value can also be combined with unlimited total limit in a purchasing document

Expected Value and Overall limit value usage.

Hi Sap Gurus,
if the frame work order we have these 2 field Expected value and overall limit field value to be filled,
and the system allows Invoice (or GR) up to the maximum of the overall limit value. and only if the value entered crosses the overall limit value the system issues a Error Message ( which is agreeable)
but the logical requirement is that, if the value crosses the Expected value limit the system should display a warning message, indicating that the value has crossed the expected value.
is there any config or note to be applied to get this funtionality.
Thanks and regards
Priya S

Hi,
Please refer to the Online documentation:
         Material Management
         -> External Services Management
            -> Procurement of Services: Processes
               -> Accelerated and Simplified Processes
                  -> Use of Value Limits (for Unplanned Services)
Inside this documentation, it is stated that there is a variety of
limits (combinations) to be used:-
- Overall limit only
- Overall limit and limit on services covered by contract item(s)
- Overall limit, limit on services covered by contract item(s),
- and other limit
- Overall limit and other limit
- Overall limit on services from model specifications or standard
    service catalog
- Expected value
The expected value is used in the update of the
PO item value and this is the value used in the release strategy.
Here is the f1 help:
Expected value - ESUH-COMMITMENT
Value that the unplanned services (or the materials) covered by this
item are not expected to exceed.
Use
If you are working with the release (approval) procedure for purchasing
documents, this value serves as the basis for a release strategy applied
to this document.
If you tick 'No limit',you don't need to enter 'Overall limit',but must
enter 'Expected value'.Because 'Expected value' will affect the release
strategy. Please read the note 440601 connected to this.
Concerning the variability of actual cost of a purchase order,
expected value means that the unplanned services (or materials)
covered by this item are not EXPECTED to exceed.
It is not mandatory that it has the same value like total limit value.
Expected value can exceed, it is used for comparison with total limit
value in cost control.
Expected value can also be combined with unlimited total limit in a
purchasing document.
Regards,
Edit

Framework Orders - Overall Limit

Hi SAP Experts!
I have an issue with Framework Orders and more specific on the Fields
"Expected Value" and "Overall Limit".
Below is an example of the issue:
I have an FO where the Expected Value is R$200.000,00 and the Overall
Limit is 1.510.100,00.
When it was released, the approval were done using the Expected Value and
not the Overall Limit. If the approval was defined using Overall Limit it
should be set up a diferent release strategy.
I would like to know if there is any way to put an blockage on Overall
Limit that does not accept value different of Expected Value. Both
values must be the same.
Could you please help me with that?
Kind Regards,
Tâmara Oliveira.

Logically if both expected and overall limit need to be same, then we dont need to have two different fields. Both fields have different purpose and it doesn't a best practise to make the system to equal overall limit and expected limit.
Is it not a best way to change your release to pick the overall limit instead of expected value?

Grey out 'Overall Limit' field in ME23N/ME23

In ME23N (ME23), the 'Overall Limit' value of (Limit) Purchase Orders within the Limit tab can be amended even though the Purchase Order has been created and released. Once the Purchase Order has been released the 'Overall Limit' value needs to be locked unless the Purchase Order has been un-released.
Can someone tell me how this can be done?
John

Hi John,
please check also the note 672719 question 2 related to this issue. The system behavies the same in case of PO's. Unfortunately the field selection settings in transaction ML90 do not have an effect on this behaviour.
Additional information:
If you are working with the release (approval) procedure for purchasing
documents, the expected value serves as the basis for a release strategy applied
to this document, not the overall limit field.
Best regards,
Edit

PO Release strategy on Overall Limit

Similar Messages

Maybe you are looking for