P Req. Release Strategy not Transported

Hi,
For Configuring the Purchase Requsition Release Strategy, We have Created Characteristics and Class in the Configuration Development Client. Created Release Groups, Assigned Release Codes with the Release Group, and Assigned Release Group with Release Strategy with Classification. Tested PR Release Strategy for the given Classification Values the Release Strategy triggered.
We have Created same Charateristics and Class in the Testing Development Client (Since the Characteristics and Class are not Transportable). Transported Release Groups, Release Codes and Release Strategy from Configuration Development Client to Testing Development Client. When we check the Release Strategy Classification in the Testing Developmemnt Client, system showing Classification Error.
Please let us know whether the Release Strategy Classification Requests are Transportable or not.
Ravi

Dear Ravi,
The Release Strategy Configurations can be transported, in respect to the requests transported.
But the assignment of the Characteristic Values to the respective classes needs to be done in respective destination clients. Since teh assignment will get transported.
To Do the same, please use transaction CL24N, Enter the classes Used in your release strategy and assign the respective Characteristics Values.
Hope this will serve the need.
Njoy SAP
- Regards,
Saravanaganesh

Similar Messages

Release strategy for Transport requests

Hi,
Can anybody give me the detail steps to configure release strategy for transporting requests?
we are having Dev and Prd systems.
Regards,
Vinnu.

Hello,
I hope you have configured TMS for two system landscape.
Just make the transport routes also, make DEV system as a Domain Controler.
Then transport requests will automatically come in to the request queue.
Using tx stms_import , import those request sequentially !!
Note: Points always encourage me to reply !!

PO Release Strategy not changed after deletion of few line items with less

Subject : PO Release Strategy not changed after deletion of few line items with less Total PO
Dear Friends
We have issue with PO Release strategy. We have created the PO. with release strategy with multiple approvers. After approval of first approval manager , one of the PO line item got deleted and Total PO value is reduced . The new PO value should have changed the PO release strategy. But it is not changed. Old release strategy only showing in the PO which is wrong.
Details of the PO
PO no 4500000123 with 5 line items Total PO value : 100,000 USD Release strategy : AB
PO line item 5 deleted. Now total PO value changed to 50,000 USD and the PO release strategy should have been changed to AA but not changed. Still showing PO release strategy AB only.
Are there any OSS notes available to correct his bug.
Please let me know if you need more details
Thanks in Advance
Thanks
MVS

Hi,
release indicators change it to 4.It may works. Please explore to all 6 indicators..........
i.e,
1-cannot be changed
2-changable,no new determination of strategy
3-changable,new release in case of strategy
4-changable,new release in case of strategy or value change
5-changable,new release if new strategy/outputted
6-changable,new release if new strategy or value changed/ outputted......
And check Characteristic description and value in Classification of Release strategies ........
I hope this will help you. Thanking you.
Regards,
Venkat.

Release Strategy not triggered in PO

Release Strategy not triggered in PO and also in PR. Release Strategy stimulation is working fine but release tab is not coming in Po and also Pr.
What step I have to do after release strategy stimulation.
Regards
cns

Hi,
Unless you provides details, difficult to suggest an answer.
What are release criteria's you selected for PO and PR release strategy?
What are the release characteristics you have for PO and PR release procedure?
If you configure perfectly the PO and PR release strategy, did you transfers the "Vital Release Values" with your release strategy with release group and release class.
Refer few threads , may help full to you!
http://scn.sap.com/thread/1973324
http://scn.sap.com/thread/3212400
Also refer SCN wikiblog
https://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards,
Biju K

Release strategy not trigerred if PR changed after Approval

Dear Gurus,
I have a requirement kindly help.   We have a PR generated from PS module, This PR is released by the approver. After the Approval, PS user change the PR qty and value has been increased. Now my client wants that this PR should be again sent for approval and release strategy should be trigerred. After the approval my release indicator is 2 RFQ/Purchase Order. I have set the Changeability indicator to 4 and define the tolerance to 0.1 %.
But PR release not trigerred even after this. Kidnly help.
Thanks.
Johi

Hi Johi,
Check note 493900 point 3:
3. Question :
Why is the release strategy not reset?
Answer :
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 total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
I hope this helps.
Regards,
Ashwini.

Release strategy not working - no multiple releases

Hi All,
Thanks for your help.
I have resolved that issue.
Now I am facing another problem.I am having release strategy with release codes R1,R2,R3,R4.
For certain amount say 1-99 I need only R1 approval.
and 100-199 the Po should go to R2 approval only and for 200-299 it should go to R3 level approver.But for amount >300 PO need both R3 and R4 approval.The PO should go for R4 Release after R3 Release.
R1,R2,R3 levels are working fine as the PO goes only at one level.But for R4 it not working.
The users are selected based on the roles assigned.
I am using a Ztable to get the roles where release code,group and roles are populate.
For each Release code are assigned Say for R1 it is ZR1 and R2 it is ZR2 etc...for each level the users selected based on roles say for R1 ---users will have roles ZR1.
But at R4 level I need to select the users for both ZR3 and ZR4.
When I am triggering the WF using Purchase order as Po number and Release code as R4 it is not selecting R3 roles.
I am using the user exit for the user determination based on roles.
Can anyone please help me on how to resolve this.
Thanks and Regards
Raju
<MODERATOR NOTE: Original post in [this thread|Release strategy not working; moved to new question>
Edited by: Mike Pokraka on Jun 20, 2008 10:47 AM

Hi Sujoy!
Thanks for the resolution.
My question is: Currently, plant is set as one of the characteristic in the release strategy. Hence, this problem!!
Now, we need to remove this "plant" and maybe consider including Company code or Purchase organization as the characteristic.
1. Pl tell me how to implement this?
Regards..

Purchase Req release strategy help

PR's generated from MRP are being blocked, however when I convert a planned order from MRP into a PR it is automatically released. I want MRP generated Reqs to be also released. I tried creating a new class, characteristic and strategy group but ran into problems when assigning the class to the group. Basically we just want all reqs created from MRP to be released and not go through workflow. Any ideas? My inital thought was to use the creation indicator EBAN-ESTKZ with the value of B (MRP) and U (converted planned orders)

hi Ryan
U can use only one release class in PR release strategy
error is because ur trying to use another class add the charactaristics ib existing class and configure release strategy
Vishal...

P Req Release Strategy

Hi,
We have scenario in which there are lot of strategies based on P Req's created for Cost centres, Assets, Orders and P Req created via MRP etc. In each of them depending on the Total Item value, Creation Indicator, Plant and Account Assignment Release Strategies varies. So Characteristics of each of the above were created and assigned to Class.
The problem occured when one of the Release Group required Material Group in their Strategy. So the Characteristic for Material Group (CEBAN-MATKL) was created and asssigned to the Class. But now this Material group gets reflected in other Strategies and appears as blank and the other Release Strategy which worked well before does not work as the Material Group is Blank. We cannot define the Material Group in each of them because there would be enough Material Group and its rather cumbersome to define for each and eveyone.
How can i overcome this situation?
Sonu

Hi,
this will happen like this only. There is a sap Note 47089 - Release procedure for purching docs - Aggregation that explains this for material group if used as one of the charateristics.
Summary
*Symptom
Release procedure for purchasing documents
No strategy is found if the plant and material group were defined as characteristics and no blank entry was maintained.
Additional key words
OMGS, ME21, ME22, ME23
Cause and prerequisites
Solution
The release procedure for purchasing documents is carried out on header level. For this, the following values are aggregated from the items on header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items contain the same plant. If only one alternative plant exists, ' ' is aggregated on header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was maintained for the haracteristic 'Value' as an object value.
The same functionality applies to the material group as for the plant.
this will info will resolve your issue.
if still have doubts let me know.
Thanks and Regards
Rajesh

PO release strategy not effected

Hi Experts,
I did all the standard settings for PO release strategy based on net value, doc type , purchasing group but it is working fine in my development server and same is not working in my quality server where as i configured the same settings.Kindly guide me .
Regards,
Sri..........

Hi,
Go to CL20N and check wether all chacterstics Values are maintained or not.
these values are sometime not transported and you have to maintain in each client.
also go to cl24N
HOPE HELP U !
Regards,
Pardeep Malik

Purchae requisition Release strategy not Invoked

Hi,
I have Purchase requisition Release startegy.
Criteria is
1. Account assignment category -K
2. Material Group suppose -001
3. Plant - 4001
4. Valuation Price - 1000 USD.
Then Release staregy got Invoked. Presently it is working fine.
I have Created another Release strategy for with same criteria but I have added another criteria with user name- ernam.
Same thing I have created characterstic and assigned to Class.
CL24N and CL20N also Maintained.
But this New Release stragey Not Invoked and Old one only invoked at the time of requsition created.
Please guide me is there any configuration to Invoke this new Strategy?
Regards,
Sridhar.

Hi Indranil,
Thanks for your response.
I thought user name will differentiate the new release strategy with old one.
I am using same parameters in both strategies.
Plants, Material groups, Cost center same with old one. New release strategy very few members are going to use.
Business is few users will create Pur Req. Users are not having release codes. Tracking number also used in another release strategy.
Regards,
Sridhar.

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.

PO release strategy not triggered after PO printout

Hi Experts,
I have configured PO release strategy and have given 10% tolerance to PO value.
When I change PO value (more than 10%) after releasing the PO, but before taking Print out of PO, the system triggers new release strategy.
But when I change the PO value (More than 10%) after taking PO print out, system do not trigger the new release strategy.
I want the system to trigger new release strategy after PO print out (if its going beyond the tolerance).
Please help.
regards,
Anand

Hi Anand,
you cannot reset the release once the PO is printed.
When the purchase order is printed/faxed the vendor will deliver the goods. Therefore it would make no sense if the system resets the strategy.
Please ensure that changeability of the release indicator should be 5 or 6.
Sanjeev

Release strategy not getting triggered.

Hello,
As per the client request, new Purchase group had to be added to the existing release strategy.
I had added the purchase group in the edit characteristics and in the release strategies: classification.
But now the the release strategy is not getting triggerred.
In CL20n I see that the, status is marked 3 i.e incomplete. The reason to this is not known as customizing done is correct.
In OMGSCK i see that no errors are found with the release strategy.
Please suggest.
Regards,
Neetha

hi,
Sometimes the strategies are taken after restarting the sap system...there has been one same situation before also..at that time the same strategy started working after restarting the sap system...
pls check it may be the same issue with you also..
Regards
Priyanka.P

Creating Roles for Purchase Req. release strategy with classification

Hi friends,
Since I have created Purchase req rel strategy where I have four release strategy
1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
Now the manager will have 2 release code,if officer is absent he could release the requisition.
Same has to be done for plant 2
The release Group and code needs to be assigned to the Roles , could anybody tell me where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
1. For Plant 1 lower value of requisition 1 codeL1(Officer)
2 For higher value of requisition 2 code say Li and L2(Manager)
Manager should have 2 codes if officer is absent he could release
Same has to be done for Plant 2
Thanks N Regards
Siddhartha

Hii,
Steps:
1) Create a Role
2) Add the authorization Object M_EINK_FRG by taking the manual option
3) Assign Release Code and Release Grp
4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
Regards,
Kumar

Purchase Req Release strategy - Requestor /Approver

We want to skip the Approver to release his own purchase requisition without workflow set up.Is it possible in ECC6.0 ?. Any help will be highly appreciated
Thanks
Nick

Hi Nick
While configurating add P group as one of charactaristic.Then maintain values of all P. Group in this charactaristic
While defining Release strategy Do not tick against Approvers P group which means release strategy will be skiped for him
( Release strategy--classification here u difine value for P Group skip P group here)
Cheers!!!
Vishal...

P Req. Release Strategy not Transported

Similar Messages

Maybe you are looking for