Release strategy not triggering for Specif plant

Hi Friends
I configured a release strategy with three charecteristics. P.org, Plant, Net value.
this stretegy is triggering for specific plants which are under a particular company code, and if I change to my plant and P.org. its not triggering.
I have deleted all the classifications and release strategies from, no other data in VV_T16FS_2 , AUSP,T16FV,and T16FS tables except this release strategies data.
do we have any settings at cocode level??????
please respond if answer known
Points would be awarded for for your valuable answer.

Thank you deepak for your quick respond
Actually There were already release strategies with same charecteristics, and with the values of other plants and other P.orgs which are under certain companycode.
these were triggering perfectly for PO
Now created new strategy for plant and P.org under different plant code of different cocde. this strategy not triggering for PO.
but if the release strtegy values replaced by the erlier plants and P.org again its triggering.
Now I created new chars, class, and stategies still same problem persists.
Release stategy working for the values of a prticular company code plants, Porgs.
and already tried your suggestion Cocode as char. but same its working for only that company code not for my companycode

Similar Messages

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.

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 working for MRP generated PR

I have one qurey. Currently we are release strategy for normal PR.Now client want to activate release strategy for MRP generated PR.
current Release Strategy for normal PR configured as following.
Purchase requisition document     RV
Purchase requisition document     ZADV
Purchase requisition document     ZIMP
Purchase requisition document     ZSER
Purchase requisition document     ZSTD
Purchase requisition document     ZSTR
Purchasing group     A01
Total value of requisition for     > 1.00 INR
Creation indicator (purchase r     Realtime (manual)
Overall release of purchase re     Yes
For MRP generated PR I add creation indicator B - Material requirements Planning.Even after add creation indicator release strategy is not triggering for PR.
To trigger PR any setting need to do other than add creation indicator.
Regards
Sathish

Hi
You don't have to include creation indicator as parameter. Check in what documnet type MRP PR is generated. You can see it in t.code OMDT. At document type level also you can manage it. You need to include creation indicator only if a seperate person approves MRP generated PR.
To know how to configure release procedure see the below link
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Overhead user exit (COOM0001) not being triggered for specific plant

Hello all,
I was wondering if anyone came across this situation before. I activated user exit COOM0001 for overhead calculation. This user exit is triggered when I create PCE for plant A but not plant B.
I can't figure out why it is not being triggered for plant B at all. I put a break point in function module EXIT_SAPLKASC_001, EXIT_SAPLKASC_002 and EXIT_SAPLKASC_003 and the system didn't stop in anyone of these function module.
Any help is greatly appreciated.
Regards,
Cassandra

Hi
It seems that you are a Functional Consultant.
Please follow the following simple step for any userexit to see where all its been called.
1. Go To T. Code SMOD
2. Enter the Exit name COOM0001
3. Click on the COMPONANTS RADIO BUTTON and DISPLAY
4. U get Function Modules
EXIT_SAPLKASC_001
EXIT_SAPLKASC_002
EXIT_SAPLKASC_003
5. Now individually double click on each FM and put a break point ther.
6. Open a new session and see wheather it stop at the break-points of the T. code you are looking for.
I havent used this user exit, so no comments on how it ll be use ful.
Reward points if useful
Thank-You
regards
vinsee

Release strategy not applied for some contracts..

Dear All,
At my client place,In some of the contracts release strategy is not applied.
I have tried evrything...in classification plant,purchasing group,net value and order type (MK and WK)everything is added.
but some of contracts release strategy is there and for some it is not applied...what could be the reason?
Please help.
Amit

Dear All,
Please reply....

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

RFQ release strategy not triggered

Hi,
We have configured as follows,
Communication structure:-Cekko-Bsart = AN (RFQ doc type)
Created char with the above comm structure.
Class with 032 and assigned char as below.
Release groups,rel codes and two level of release.
When i simulate release strategy, showing blocked and released.
But when i create a RFQ and no release is triggered and when i checked in release rfqs(ME45) no suitable purchasing documents.What might be the mistake.
Regards
Kris

Hi,
Check you release procedure prerequisities & stateus in rel. strategy.
check below link:
[Re: PR Release strategy Problem]
[With and w/o classification;
[Re: release code deletion]
SAM

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

Release Strategy with Workflow for PR & PO

Hi Experts,
I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
So User should get the information about the releases for PR & PO.
But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
Points will be awarded .
thanks & rgds
Swamy

Hi Swamy,
The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
How to configure?
Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
Maintain the details u already have in hand:
For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO. After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
Hope this will give you an idea how the workflow works and how to configure it.
Rgds.

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..

Sales Text for Specific Plants

Hello SD Gurus,
Is it possible to turn off Sales Text in Material Master for specific Plant? For example, we have 10 plants and we want sales text only for 2 plants & for rest of plants it must be turned off.
This text we require to send the customer as a sales order confirmation once order is created.
Please advice.
Thanks,
Pradeep

Hi,
Sales text is maintained at Sales Org and distributation level and not at plant level, so it is not possible to control the flow of the data at plant level
Text types in procedure will have access sequence number assigned to it. Each access sequence will have text object and requirment column in it. So Create a new requirment in VOFM and make use of TVARV logic or hard code in the program that only if this plant is determined in SO the text should be fetched from material master.
Check on this with technical consultant

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.

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

Restrict F4 search results for specific plants / sales org / purchasing org

Hello All,
We have a project where a particular plant / sales org / purchasing org needs to be restricted because of the top secret data for that business. We would like to be able to restrict the search results that are displayed based on sales org / plant / purchasing org in the F4 help. If a user does not have access to the data / documents related a plant / sales org / purchasing org, we do not want the user to be able to see doc numbers, ship-to's, material numbers etc... My question is where do we restrict F4 results for the Sales and Distribution, Finance, Materials Management, Production Planning, Logistics, etc... modules? Thanks in advance for the help.
Jordan

We can set authorization for specific plants and other organization levels,contact the basis team and discuss about the authorization

Release strategy not triggering for Specif plant

Similar Messages

Maybe you are looking for