PO Release Strategy for a single Plant
Dear Friends,
I have created a new release strategy to trigger multiple plants
Release Strategy is triggering in case of PO is having more than one single Plants but not in case of a single plant in one item or multiple items for the same plants.
I know that PO release strategy is at header level so I have not entered plant in CL24N.My purpose is solved in case of aPO is having more thatnn one plant but still i need to get the Release Strategy to trigger in case of any single plant or more than one time by using a single plant in PO.
Has anybody done this? Could you please suggest any logic to be developed if available
Thanks
Ranjith'
Hi Ranjit,
Do you have PLANT as the Characteristics in the Release procedure?
If not there, add PLANT as Characteristic and enter plant code in CL24N & also make the plant value as blank and check.
eg. suppose You Have two plants codes 1000 & 2000
So enter both plant codes(1000 & 2000) in plant value & also enter one blank value in Plant field.
In characteristic value
Plant-1000
2000
No Plant
Thanks
Madhurendra Sharma
Similar Messages
-
Release Strategy for New Plant
Dear All,
I have a Release strategy in my 3 Plants and it is working fine.
Now I want to add one more plant under the same release strategy.
I tried to add the new Plant in CL24N. System allows me to add the same in this but the RS is not working in this new Plant.
waiting for replyhi,
you follow the following steps to insert new characteristics value in your release procedure.
1. define the new characteristics value plant4 in your characteristics.
2. assign the same characteristics value plant4 in classification of release strategy.
3. run the release simulation and comes out.
4. now create PO for your requirment and save it.
5. u can use me22n/23n to view your release status of po.
hope it helps....
manoj singh -
How to setup a release strategy for store generated purchase order
Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2teaPlease go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok -
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 adviceFirst 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. -
Release Strategy for SA/Contract/PO
Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
PrabhuHi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards -
How to Maintain Two Countries for a Single Plant in OX10
Hi Experts
I need the solution for the below settings for OX10 ( Plant Overview ) .
For a single Plant i have to maintain two countries .
1) One country in details screen of Plant ( Country Key )
2) Second country in Address details of the same plants ( In the Street Address - Country )
while i am doing that the country in main screen is getting copied as same as address country after saving .
Pls Help .
Regards
Sameer
Edited by: Saxena Sameer on Oct 20, 2011 7:46 AMIt is not possible and not logical to have one plant in 2 countries.
And the 2 screens you talk about should actually have the same values, otherwise it is just inconsistent data.
The first screen was all what SAP had for a plant address before central address management was implemented with 4.0 release.
Since central address management is in use, you only need to define you address behind the envelope button and the necessary information is adopted to the first screen automatically.
Knowing this background should make you aware that these 2 address screens are not designed to be maintianed for different purposes. -
Release strategy for PO and RO
Hi All
My release strategy for Purchase order and Release Order is same.My release strategy has material group and PO/RO value as characteristics. What I want is that my releaase strategy for PO should be based on value whereas for RO it should be based on material group. Is this possible since we cannot have different release group for PO and RO.
Pl suggest how to go about?HI Satish,
In the characteristic value screen we not only can give single values ,but also multiple values
and also range of values.
Since the Data type for this Feild is character ,that is the reason it is not taking Ranges
So the same is not working for PO,I too Checked the same.
So it is that you have to have material group ,then there is no other go but entering all the values for the same.
As we cant add a new Release Class also
Becoz the release class cant be different ,so as the characteristic values would be same.
if i could find something else will post you soon.
but as of know we cant do nothing in this case but create all the material group as charecterics values and add to that strategy.
Thanks
Anjanna. -
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,
ShailendraKeep the release strategy at Plant level only....All the purchasing docs will get blocked
-
Hello Experts,
We have a requirement to configure release procedure for STO scenario. Release procedure needs to be captured in STO PO's.
We have 6 plants - A,B,C,D,E,F, and each plant is having different approving authority individually.
When STO PO is created, it has to be approved by Issuing plant authority & receiving plant authority as well. The major concern here is for eg., approval authority for plant A can be a issuing authority at one instance & receiving authority at another instance.
How to configure release strategy for this.
We believe ,creating those many release strategies for all the combinations of plants will be a hectic task & still it'll multiply with the introduction of more number of plants.
Hence looking for a more simpler & feasible workaround/solution.
Regards
Mahesh.C.RHi,
you can use Supplying plant ( RESWK) and issuing plant (werks) both as characteristic and with these combination you can configue release strategy.
Or you can use User field format character for release strategy (USRC1)as per your requirement.
YB -
Release strategy for quantity contract
Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbuHi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT -
Release Strategy for Contract is not getting picked whereas it is ok for PO
Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
SatishS0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you -
Release strategy for Schedule lines in SD
Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias -
Release strategy for Scheduling Agreement(SA)
Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM in response to: sathish.kumar Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...?? -
Purchase Order not subject to release strategy for contract rel. strategy
Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract. -
Release strategy for Release POs
Hi Every one,
We have a requirement.
A contract is created and approved as per the regular strategy.
The releases (POs) are created against it and sent directly to the vendor.
As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
But the business wants the PO releases too to follow the release strategy.
Can you please look in to this and let me what changes we need to make this happen.
Regards
PavanAs the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
So that the Release Process is applicable to PO's created w.r.to Contract also..
For ex: if you use the field purchase Doc category as a Character in the Release , it differentiates whether it is PO or Contract..
So that you can define different Release Strategy for PO & Contract
Or if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
then the release strategy applies to PO also..
Maybe you are looking for
-
In moving from one page to another on a website, I get this error message:
ices</a> and perform a title search for the words <b>HTTP</b> and <b>404</b>.</li> <li>Open <b>IIS Help</b>, which is accessible in IIS Manager (inetmgr), and search for topics titled <b>Web Site Setup</b>, <b>Common Administrative Tasks</b>, and <b>
-
Creating chart leads in XML Parsing Error: mismatched tag. Expected: /svg
Hello ALL, I searched this forum but unfortunately I find not a solution for the following use case: described in steps 1.) create a region with chart (typ = line) -> o.k. 2.) create a sql statement to have data in the chart -> o.k. 3.) running repor
-
Select statement fails under Express, but works under Fortewhen using
Express sometimes (e.g. with nested windows) generates SQL with a select subquery, e.g. select x1, x2 from t1 where (x1,x2) in (select x1,x2 from t2.....) This fails on DB2 with a message that the comma in the where clause (x1,x2) is not allowed. Thi
-
Changing the bounding box size
When I go to print an image in Photoshop CC, a dialogue box appears and on the left-hand side is the image to be printed. Bordering the image are small diagonal lines which I'm assuming are the bounding box. The distance between the edge of the page
-
How to join MTL_MATERIAL_TRANSACTIONS and MTL_SERIAL_NUMBERS
Hello, I was browsing a lot to find a solution for this, but I did not find any useful information. What I would like to do is to create a SELECT query that downloads all material transactions of a particular serialized item. However I did not find a