Release Strategy different plant in one PO

Hi.,
Can u clarify, I want to set release strategy in PO .
In PO two line item entered for each line item is different plant 1000, 2000.
IS there Possible to do release strategy in this scenario .
If possible please guide me how to proceed this.
Best Regards
K

yes you can do.you have to create a characteristics for Plant(field WERKS)and table CEKKO select multiple values in the characetristics.you add this with your class and in the classification of release strategy enter both plants 1000,1100(within same company code) along with your other characters.try it will work.
note: you cannot do it for 2 company codes.because company code at header level and it is unique.
hope this helps
reward if useful.
regards
venkadesh

Similar Messages

Assign multiple internal parts (materials of different plants) to one MPN

HI
I have a requirement to assign multiple internal parts (materials of different plants) to one manufacture part number.
but in HERS material type it allows to assign to only one .
can any body suggest how can I do this.
Sreeram

You can do that.
1:Assign the new plant to the sales org / distribution channel - Enterprise structure
2:DO the shipping point determination for the new plant.
3:Extend the materials to the new plant.
4:If there is intercompnay process, please check "Assignmnet of organizational units to plants" in navigation SD - Billing - Intercompany billing.
5: Check if there are any pricing records, output records....et cwhich has Plant as parameters. if yes maintain the entries for the new plant.
These are the things I could think of.
Before deleting the existing plants, make sure there are no open documents existing for these plants, else system will not allow to delete.
Regards
Sai
Edited by: Sai on Jun 1, 2010 4:19 PM

Release Strategy for Plants

Dearest Friends,
we have Plant A & Plant B
for Plant A     PR and PO <50K will be released by R1   and value >50K   by R1 and R2, R3.
*for Plant B   PR and PO >50K will be released by R1, S1 and >50K R1, S1, R2, R3.
how can we define the above release strategy.
hope you guys will help me.
Thanks and Best Regards,
Rajesh G

Hi,
for Release streagty either for PR or PO.
Steps :-
1. Create a Class T code CL01....Put Class type "32".
2. Crate Charateristics CT04 for ur case
Suppose for Plant ....in Addidtional data Put Table Name CEKKO and Field Name - WERKS
For Value ......... maintain CEKKO - GNETW
For PR .....
Table Name CEBAN --- WERKS for Plant
                      CEBAN -- GSWRT for Value
either go to se11, give the table name....u will get all the field there for which u want ur charterstics will work.
3. Assign Charcatristic to Class either in CL01 or cl24n.
3. Now go to Spro --> MM --> Purchase ---> release streatgy
first define Release code as R1, S1, R2, R3
Define GRp and Streatgy....
for Plant A PR and PO <50K will be released by R1
Suppose Grp is XY and Release Ste R1....click on details ....fill release Code R1 and in classification maintain Values <=50 and plant A.
Similarly Mainatin other....
Also u can document from
http://sapdocs.info/wp-content/uploads/2009/07/Step-by-step-guide-of-SAP-PR-Release-Strategy-configuration-a-case-study.pdf
http://sapdocs.info/sap/materials-management-2/automating-purchasing-approval-sap-release-strategy-tips/
Hope Help U !
Regards,
Pardeep malik
Edited by: Pardeep Malik on Sep 19, 2009 11:53 AM

PO release strategy, ref: plant and activity

Hi,
for PO release M_EINK_FRG is the object.
but along with this we need to give M_BEST_BSA & M_BEST_WRK, the activity is 02(change).
my concern is, if we give him the same objects authorization, he will be in a position to change the PO also, along with releasing the PO.
do we have any control for the same?

Hi,
In that case create seperate Z roles according to
Combination of Rel Code,Pur Grp,and plant combination
You can have that role with combination of all these objects with limited
authority specific to plant and or doc type
And assign these seperate roles to each user id
Try this and confirm
BR
Diwakar

Problem in release strategy in a plant PO. Strategy does not appear

Hi:
I have a problem with release strategy in plant PO. When we create a PO in this plant, we have no tab for release strategy, if I change the plant in PO for a different one I get this tab with all data.
I have checked OMGS, CL20N and everything seems to be in order. I think this is a problem in plant definition, but I really donu2019t know where I can look for. This plant is a copy of an existing one, and in this plant there is no problem.
Please, any idea?
Thank you very much in advance.

you can test if one or more strategies can be found. (you should one find one, otherwise SAP is not able to determine which one should be used)
go to CL30N.
Enter your class and class type 032, hit enter
Enter values for the characteristics. and click button for a search in initial class.
I dont think it has something todo with plant customizing. Classification just takes the values that are in your PO and searches for a strategy which has to be in table T16FS.

Removal of plant from P/R release strategy of another plant

Dear Friends,
In our office there are two plants P068 & P281 both belongs to two separate co codes. In its P/r release strategy in characteristics plants are mentioned so for each plant their should be separate p/r as they are located differently. But unfortunately plant P281 is added in the release strategy of plant P068 though there is a separate release strategy configured for plant P281. So while making P/r of plant P281 release strategy of plant P068 is getting called & the user is not able to release the same because of the restricted authorizations. We have tried to remove the plant P281for which we created the request on DEV server & transported to PRD server but this is not removed. It is still reflecting in P068 P/r release strategy. Kindly advise how we can remove this ? Is their any other alternative way?
Rgds
Prashant B

You need to remove the plant from classification of release strategy. If system is modifiable, go into release strategy and classification and uncheck the plant, which is not required and save.
OR
If backend is unmodifiable, use this t-code CL20n/CL24n, put in the release code strategy combination and in the classification remove the plant of it and then save and your problem will be solved.
Follow the above steps for adding the plant to new release strategy as well.
Edited by: Afshad Irani on Apr 28, 2010 4:45 PM

Release strategy for PR in Third party case

Hi,
We have this third party scenario where Purchase reqs are created at the time of Sales Order creation. A release strategy is attached to these purchase req by defining a custom field in MMaster, whenever qty goes up or equal to tht field release strategy is applied.
The problem is, for the same material's PR, the release strategy is set in one case whereas for other PR (of different sales order) it is not set. Please help let me know what could have gone wrong.
Thx.
Amit

Per your information you say that based on a custom field qty in material master release strategy is triggered. Do you have any charecteristic maintained for the Release strategy anything other than this parameter- because there must be some difference between the 2 Reqs.
Or check the change history in Material master it may be possible that at the time of second sales order if the field value was changed so that release strategy was not triggered.
Please give more details
Thanks
Deepak

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 release strategy with classification

As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.

Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

PR - How to use distinct release strategy

Hello SAP's gurus,
We use the procedure with classification for our release strategies.
I cannot undestrand why I cannot work with 2 disctinct class (it means different characteristics list) for my company.
Rel.Grp   /Rel.obj.   / OvRelPReq    /Class
ZY          /1              /NO                 /RELEASE_STRATEGY_1
ZZ          /1              /NO                  /RELEASE_STRATEGY_2
We would like to define specific characteristics depending on the currency used in the PR.
It means, if currency is USD (table CEBAN/WAERS) : characteristic "Total Value of Item in USD" (table CEBAN/GSWRT, currency USD) should be used and if the currency is EUR : characteristic "Total Value of Item in EUR" (table CEBAN/GSWRT, currency EUR) should be used in the release strategy.
How can I work to set up a list of characteristics for the release strategy different from a currency to another one?
Thank you so much in advance for your help.

I'll have a quick check but assuming GSWRT is purely a value figure, that won't provide the distinction you want. You need to use a characteristic that represents the currency i.e. use CEBAN / WAERS. That will allow you distinguish according to the cirrency.

No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

PR Release Strategy-Characteristic Z_GSWRT must be linked with CEBAN-GFWRT

Dear Experts,
I did a simple config for PR Release strategy. using Plant(Z_WERKS) and Item values(Z_GSWRT )
chose overall PR Release. During simulate release
the second level release its not able to simulate and it says check Prerequistie for second level
Can somebody expain why the system is giving me this below message.
Characteristic Z_GSWRT must be linked with CEBAN-GFWRT
Message no. ME_RELCHK056
Thank you
Imraan

Thanks for the solution that helped me to understand PR Release much better.
Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
In my PR Release strategy with 2 levels I have these below things:
Rel Groups : 1 Group with name AA
Rel Codes: For AA is A1, For another AA is A2.
Rel Indicator: nothing is selected, am not sure what to do in this step.
Rel Strategy : For AA is S1, For another AA is S2.
I created class Z_GFWRT but am not sure which group I should assign it AA or I have to create another new group for Overall release.
After I checked the release strategy the system is giving me this below message.
No release group exists
Message no. ME_RELCHK014
Please can you walkme through in this process. This is first time I am creating a PR Release.
Thank you Very Much
Imraan

PO release strategy workflow based on plant

Hi Gurus,
I am setting up PO release strategy workflow. We have purchasing at plant level. Fg. plant 1234's PO should be sent to the plant 1234's purchasing dept. Plant 5678's PO should be sent to the plant 5678's purchasing dept. In PR release strategy workflow config. screen, there is a plant field. However, plant field is not showing in the PO release strategy workflow screen. they are both in the table T16FW, and plant field is define in the table. Pls help and explain how we can get plant field in the PO release strategy workflow config. Or if this is what SAP design, then is there any other way to accomplish what we want? Thanks a lot!

We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Hi,
You can try doing it with a WorkFlow as you identified communication structures differ.
Regards
Shiva

Stop release strategy when pgrp changed triggering different release group/

Currently when our buyers change the purchasing group field on the purchase requisition it is triggering a new release strategy because the release group and code is different than the original creator.
It has been indicated that we should request from SAP that these two fields be made available to the structure for the release strategy.
Is there a user exit that we can use to stop a new release strategy?

Hi,
Do you have different rel. stgy for diff. plants? if yes, than which rel. stgy should be picked in case if both plants entered have different rel. stgy? what is your expectations/requirements?
If your PO is to go through diff. approvals for different plants than you should have different PO for each plant (even diff authorizations and rel. codes), or else you should not have plant as the criteria. Technically, whether it is fesible or not is different question, but whether practically your organization is ready that if a common material is to be procured it will have approvals of only one plant or may be a different approvals all together?
Regards,
Dakshesh

Release strategy is not getting Trigerred for Multiple Plants in PO.

Dear gurus,
I have a Release strategy which is working Fine when I create a PO with Same Plant in line items.
But My release strategy is not getting trigerred when I have Different Plants in Line items.
I have Maintained all the Plants in the characteristic Values of Plant.
Why does the RS work for Single Plant & doesn't work for Multiple Plants in the same PO.
Is there any SAP Note applicable to this? Pl Suggest.
Thanks guys
SN

i got your point but i will again say the same thing that for item level field system is not able to block the po if there are multiple line item in RS and that too with different values against same char as system picks only 1 value and it sends that value in RS to cross check wheteher this po needs to be blocked or not .
now in your case system is getting multiple values against 1 field that is plant so now system is not able to send 1 in backend and hence it sends blank value in back end so system dosent blocks the po
even if you use material group or any other item level field system is going to behave that way only that is it will not be blocking the po

Release Strategy different plant in one PO

Similar Messages

Maybe you are looking for