Release strategy(urgent)

hi,
i have doubt regarding PO creation.
Purchase Order has to be approved after modidfication, but,
release strategy is not getting updated when i am modifying my PO......so i can't approve it..........
and i am chaning quantity,delivery date, price and condition type, actually i want to know wht is the problem......... and why this is happening......
and "on wht factors will the release startegy depend ?????????"

Hi,
Please can you clarify the following.
You are saying that it should be approved ONLY after modifying it.
But was it caught by the release strategy BEFORE it was modified?
Or are you saying that when a released PO is modified you want the strategy to be reapplied?
Steve B

Similar Messages

Release strategy-- very very urgent

hi,
i have created the release strategy & its working properly in devolopment client. The entire thing is transported to quality client. But the characteristics values are not coming in the classification tab of release strategy. I have saved even the view in transport request but still the values are not coming. Can anyone suggest something. Its very urgent
thanks

Hi,
The transport of release procedure customizing data can only be done in
a 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.
The classification data must be sent over using ALE. It does not
get transported directly. Notes 45951, 86900 and note 365604 should
help. Please follow the instructions in note 45951.
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 agin 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.
There is another possibility that you could take into consideration for
the classification is to import them via batch input:
RCCTBI01 for creating characteristics
RCCLBi01 for creating classes
RCCLBI03 for classification
Regards,
Sunitha.

Release Strategy for PR--------Help is required urgently.

Hello all,
I have one severe problem in PR release strategy. Whenever we create a PR the Release is triggering but the name of the processer who will release this PR is not triggering. I have done the PO13, where the HR positions are maintained as per the release levels and PA30 where the SAP user ids of these processers is given. But still the processor name is not triggering. Is there any other transaction where we have to maintain certain data?? Kindly help me as this is an urgent issue.
I will be very glad and give points to all of u.
Thanks and Regards,
Umakanth.

Hi,
Please check whether the relevant HR authorizations are given or not, especially relating to Org. management.
This is not only for the approver but also for the person viewing the requisition.
Hope this helps..

Purchase Requisition Release Strategy ---- help required urgently.

Hello all,
I have one severe problem in PR release strategy. Whenever we create a PR the Release is triggering but the name of the processer who will release this PR is not triggering. I have done the PO13, where the HR positions are maintained as per the release levels and PA30 where the SAP user ids of these processers is given. But still the processor name is not triggering. Is there any other transaction where we have to maintain certain data?? Kindly help me as this is an urgent issue.
I will be very glad and give points to all of u.
Thanks and Regards,
Umakanth.

hi,
Check your release codes and its assignments in the release strategy..
Also do check whether the PR is liable to trigger for the given characteristics as compared to your PR which you are making...
Regards
Priyanka.P

User exit ML81N.....Name of user exit to trigger 'Release Strategy'..urgent

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy when the amount is less than $2500.
Can anyone please tell me the name of the user exit that controls the 'Release strategy'.
Points will be awarded...
Thanks
Rahul

Hi
Your settlement rule says "Settle to Cost Center" only.... I dont think any user exit can help in this case, if you want to settle occasioanlly to 2 cost objects
Try with these options
Option A
1. Remove the 100% validation tick in the settlement profile...
2. Maintain 2 settlement rules... i.e. One with Cost center and another with PSG... If any warning comes, ignore it
3. Execute settlement now
Option B
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, Menu GO TO > DETAILS and maintain Cost Center also....
3. Now execute settlement...
Option C
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, populate Cost Center also as a Valid Characteristic
3. Now execute settlement...
BR,Ajay M

ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release Strategy'.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
Please tell me how to select the lowest Release strategy using the CESSR structure ?
Points will be awarded...
Thanks
Rahul

Use this exit.
MM06E005

To avoid deleted item of P.O in release Strategy

Dear all
We are facing a problem. our user deleting the line item of a P.O and this is routed through release strategy. Is there any configuration that , any deleted item in P.O can by pass release strategy. Shall be grateful, if you could kindly urgently help me,
Kind Regards - P.L.dey

Thanks ....I have seen the structure for the PO release.I have gone thouogh the parameters of the function module of the user exit...But to me it is not clear how to incorporate the Deletion indicator of the PO item in the code...
Hope to hear from you.......
Regards

Error message if no release strategy is applied for PO

Dear All,
In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
Is there any way to encounter this
Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
OR
While making GRN against this PO, System will give message Like say ... no release strategy is applied for the PO..
Please reply ...URGENT
Regards,
Rakesh Shelar

Dear Thanx.
my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
In this, case system is allowing to take GRN against such POs without release strategies

Release Strategy for Sales Order-IMP

Hi Gurus,
I want to know regarding <b>Release Strategy for sales orders</b>. I want to know the detailed step-wise procedure for SO and not for PO. My understanding is that standard SAP does not support Release Strategy for SO in SD Module. Please l want the following queries to be answered
1) Is my understanding on Release Strategy for SO correct as mentioned above?
2) What are the other alternatives and the steps of configuration step-wise.?
Kindly help me post this information as it is required urgently. Suitable full Reward Points will be given to all answers.
Many Thanks,
Pankaj Mishra
E-Mail : [email protected]

Pankaj,
There is no release strategy for sales order.
You can try it doing Authorisation /Status profile with your BASIS person...
REWARD IF U FINDS THIS AS USEFUL...
Regds
MM

Multiple currency release strategy

Hi,
Currently all our release strategies are set up in ZAR (South African Rand). We are however implementing a new company situated in the UK. We thus require this companys release strategy be set up in GBP (Great Britain Pounds). How do we go about doing this?
We have already tried to make a copy of our "Total order value" characteristic and changed the currency to GBP. We then created a new class and included this characteristic in our class. We then run into a problem when we try assigning the new class to a new release group. It appears that you not allowed assigning more than one class to the same purchasing document type (in our case purchase orders).
Urgent assistance required please.
Regards

Hi Shiyam Khatieb and Raju
please update me ,I tried the way you told me but still my PO not pulling release properly. I have created four characteristics ,compony code,po document type and PO order value with USD and one with AUD.but still release is not affecting.If I take only one characterstics value with USD then PO pulling the release ok in US company codes but in australia it is affecting by exhange rate. I set range 0 to 1000 and next is from 1000 to 5000.In australia PO if amount is 1001 it is not going for next strategy of 1000 to 5000.
Please can send me screenshot of seletion of charactristics in classification while setting the release.
Please reply me. my email- [email protected]

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Hello everyone,
I've run into an interesting problem:
We have defined several PO release strategies. Most of these work in the traditional manner, requiring manual approval by a given user. One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
What would cause this discrepancy? The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
Thank you ahead of time for your help.
-Jarrod

Configuration issue/user error.

PO Release strategy

Hi,
I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
Any suggestions are highly appreciated to fix this issue.
Regards
Sudhakar

Hello,
After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
regards
anand

Release strategy(urgent)

Similar Messages

Maybe you are looking for