Release Strategies in Purchase Order - possible values of caracteristics

Hello,
I have the following situation at hand.
We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
I can not change the caracteristics in the Release strateg because this would affect the already working strategies and SAP does not allow to asign another Class to the PO release groups.
Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
Can I use something generic in the caracteristics field of the strategy?
Thanks for any help. It would save me a lot of time!
Aart

Note 493900 - FAQ: Release Strategy
1. Question :
Why is the release strategy not determined?
Answer :
Please check the following points :
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
If you use version management, the determination of the release strategy starts when the version is completed.
You complete a version by setting the "version completed" indicator in the version tab.
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

Similar Messages

Wrong Release strategy in purchase order

Hi,
I have a specific purchase order with wrong release strategy.
I had been creating others documents with the same total value and the release strategy work correctly.
The release strategy configuration are right.
How I can correct the release strategy in a specific document?
Thanks.
Best Regards.

Hi,
The release strtegy is basically conssitss of Different type of characters.
What characters you are highlighting plays in release strategy.
First you comapre the characters you mentioned in two purchase orders,
eg: p.org, Pur Grp, Value,------
o to bith release strategies and compre the things or characters you mentioned Release strategy and found wher you missed to get the required Strategy.
SPRO>>MM>>Purchase order>>Release Procedure for Purchase Orders>>Define Release Procedure for Purchase Orders>>Click on release strategies
Select your release strategy and go to Classification , here you chck the parameters in both release strategies and compare with your purchase orders.
Regards,
Andra.

Release Procudure for Purchase Order

Hi Experts,
I am new Release Procudure.My client wants release procedure for two users.
End user wants create Purchase Order then other user wants release that purchase order and then another user wants final release. Please tell how can map this process in sap.
Thanks in advance,
Chandhu
Edited by: chnadu9 on Jan 5, 2011 5:48 AM

Hi,
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.
An example of configuring a Purchase Order Release Strategy
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.
Steps for configuring the PO release strategy
Create the PO Characteristic
Transaction code : CT04 - Create Characteristic e.g. NETVALUE
Click Additional data tabstrips
Table name CEKKO Field name GNETW and press enter and you will see this information message :-
Format data taken from Data Dictionary (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 tabsritps (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >=10000 (equal or greater than 10000) and press enter
Save your data
Create the Class of the PO Release Strategy
Transaction code : CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create button
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tabstrips, type NETVALUE to assign your characteristics to the class
Save your data and this message will appear :-
Class type 032: Class REL_PUR created
Define the Release Procedure
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
Save your entries.
Release codes - New entries
Grp Code
02 01
Save your entries.
Release indicators - New entries
Release indicators Release Description
0 Blocked
1 X Release
Save your entries
Release Strategy - New entries
Release group 02
Rel.strategy 01 - Release
Release codes 01
Release status 0 - Blocked
1 - Release
Click the Release prerequisities button
Click the Relase statuses button the click the Continue button
Click the Classification button
Choose your check values
Click the Back button
Save your entries
Check your PO release configuration
Finally, check your PO Release Strategy configuration to make sure that there are no errors.
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,
Mohar

Release Strategy in Purchase Order

Hi,
Can any explain the usage of Release Strategy in Purchase Order.
ganesh

Hi Ganesh,
Release strategy works the same way in purchasing documents (i.e. PR and PO). It is a form of control that company use to control the purchases made.
In your scenario, a PO release strategy is used to control the PO release status for Good Receipt process. Once the PR is released by the relevant releaser, you will see that the PR is now unblocked for issuance of PO.
Once the PO is issued with reference to the PR, it is now blocked again by a release strategy for user to perform Goods Issue. The releaser will evaluate the PO issued and determine if it is necessary to be released for GR / Service Acceptance process. At this stage, the releaser can still reject the PO although issued, and hence GR / Service Acceptance is not able to be performed. Different value will trigger different set of release strategy with different level of approvals, depending on how the PO release strategy is configured by the MM functional consultant. Usually, the PO release strategy has a flatter approving level as compared to PR release strategy, reason being that once the PR has been fully released by all releaser and the PO issued, usually the purchase is deemed necessary and PO releaser would usually consider to release the PO for GR or Service Acceptance process, unless there is discrepancy or sudden change in decision of Management.
Hence, all in all, the PO release strategy act as another form of control to the company to restrict the release of PO for GR or Service Acceptance.
Hope this will give u a better understanding on the function of a PO release strategy.
Rgds.

Restrict Purchase Order Minimum Value

Hi,
We want that the SAP System should not allow the user to create a Purchase Order of Value less than Rs. 5000.
Is there any SAP Standard Functionality available for the same or we need to use the User Exit?
Regards,
PK

Thanks Shital for the reply.
We are not using Release Strategy, hence we want to out the check at the PO Creation level only.
Pls. advise.
Regards,
PK

Release procedure for Purchase orders

Hello SAP Gurus,
Can anyone explain in steps the release procedure for purchase orders and also can any one explain how it differs from Puchase requisition release procedure.
Thanks
NDS

Hi
Release procedure for Purchase orders here is process flow.
Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
1. Create characterstics -Intially you will create characterstics based on which you would like to release a purchase order.
Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
3. Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
4. under classfication define value limits for release of purchase order.
5. define release indicators
6. simulate the release
7. assign if there is any workflow.
hope it helps.

Define Release Procedure for Purchase Orders

Hi Friends,
We are changing Release procedure for purchase orders for one department from > $ 5000 to > $ 10000.
We defined three characteristics for the class namely Purchasing Order Document, Purchasing Order Type and Ner Order Value which is Currency data type. I Defined Release Procedure for Purchase Orders in configuration master. It's working fine, I mean the Net order Value field is updated in Configuration Client.
After transporting the above change to the Testing Client, the Net Order Value field did not update in testing Client even though I created Characteristics in Testing Client (as characters are not transportable, I created them seperately in Testing Client). I can't update the Net Order Value manually in Testing Client as it says "Client 010 (test) has status 'not modifiable' "
Please tell me how to update that field, as the net order value didn't change even after transport. I can't change manually in testing Client as the status is "not modifiable"

Hi,
Yes I have already done that.
In SPRO,
After hitting the following:-
MM --> Purchasing --> Purchase Order --> Release Procedure for Purchase Orders --> Define Release procedre for Purchase Orders
I have to process the objects in the following sequence,
Release Group, Release Code, Release Indicator, Release Strategy & Workflow.
Upto Release Indicator it is fine. After hitting Release Strategy, I should select the release strategy (which I just created) and display. Then 4 buttons will be displayed namely,
Release Prerequisites, Release statuses, Classification, Release simulation.
Upto Release statuses it's fine. Afeter hitting Classification,
the values of Purchase document & Order type are populated, but the Total Net Order Value is Blank. It is supposed to populate the amount & 10,000. But it is not.
Actually that amount will be stored in the field GNETW of table CEKKO. But CEKKO is a Structure not a table. So I can't update the field.
Please advice me...
Thank You,
Nag

Release strategy of Purchase order

Dear all,
   I configured Release strategy for purchase order in which i create characteristic,Class.
   I also define release procedure for PO like release group,release code,release indicator & release strategy.
   But it is not reflecting in Purchase order.
Regards,
Nitin Patil.

Hi Nitin,.
check had you missed any step while creating the release procedure...
Follow the link it may be useful to you, this is for PR.... this is same for PO also onle differnce is in coummunicaitton structure CEKKO you neet put...
http://www.sap123.com/showthread.php?t=59&highlight=SettingsimpleReleaseProcedurePurchase+Requisitions
regards
anand

How to Retrieve Purchase order TAX value price

Hi,
I want to retrieve Purchase order TAX value price from the purchase order is there any function module to retrieve this value. Or from which table we can retrieve this value using purchase order no.
Thanks in advance

Hi Pradeep,
Have you looked BAPI BAPI_PRICES_CONDITIONS?
Hope this will help.
Regards,
Ferry Lianto

PR Release Strategies on purchasing group basis

Dear All,
I want to define PR Release Strategies on purchasing group basis. please suggest process.
Regards,
Mukesh Chejara
SAP

you can use Table name CEBAN and Field name EKGRP define in the characteristics and then maintain the master data in CL20N.
Regards,
qsm sap

Release strategy for Purchase order

Hi Friends,
My client was using Release strategy for purchase order. Now we want to know the T-code for showing list of Rejected Purchase orders, T-code for for showing list of approved purchase orders, T-code for showing list of blocked purchase order.
Thanks and regards
Krishna

HI,
You can go to SE16N view table name EKKO
FRGKE Release ind. = B
FRGZU Release status = <blank>
mean, this PO yet to approve/ rejected.
FRGKE Release ind. = R
FRGZU Release status = X
means, this PO has been approved.
Hope this helps

T.Code for Release Procedure for Purchase Order Type

Hi Frd
im working in ECC 6.0.
OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
Thanks
By
Pari

Hi Rajasekharan,
Go to tcode ME22 and enter the Purchase order number.
inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
Click on a item and press the Green Button.
U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
Actually the tcode for releasing purchase order is ME28
Reward points if useful.
Cheers,
Swamy Kunche

Release stratedires for Purchase Order

Hi
Dear All
I need a clarification that my needs cost centre based release strategy for Po, but t is not in Cekko table.i have to use customer exit M06E0004 or any other way to use cost centre as char in release st.
i appreciare if anybody can help/ give the suggestion in this regard
MVRAo

Hi,
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement,request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item)and in total. The latter approach is also termed overall release.
 Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor
of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
Procedure Without Classification (Requisition Items Only)
The conditions can be based on one of the following item characteristics or a combination of
these:
 Account assignment category
Material group
Plant
Total value
Hope this will answer your question
Thanks
Arun agrawal.

Release Tab in purchase order disappear after release using ME29n

Hi there,
We are busy testing support stacks (upgrading from ECC6 SAP_APPL SAPKH60305 to SAPKH60307)and we've come accross a strange problem. When we create a normal purchase order (ME21n) the purchase order does pick up a release strategy. Using the older ME28 transaction to release this purchase order, everything is fine. We can use ME28 to release the purchase order, as well as unreleasing the purchase order, as often as we want (the same purchase order). When we use transaction ME29n the release tab in the purchase order just simply disappears after saving. In the purchase order header changes, the release change is visible, but the release tab is missing. This purchase order is now not subject for release, and a goods receipt is possible without release. I checked in table EKKO as well and the release fields in this table for this purchase order is empty.
Has anybody had a similar experience? Any advise would be greatly appreciated.
Regards
Christo Vermeulen

Hi Christo Vermeulen,
I have detected the same problem as reported by you. Did you solve it? Do you know how can I procedure to solve it?
Thanks in advanced,
Eder Nicoleti

Finding releasing agent of purchase order

Hi experts!
I am trying to find out the releasing agent of a purchase order, following release using transaction ME29n. How can I find this data? I've tried using the object and the related tables, but to no avail.
Thanks in advance!
Sincerely,
Christian

Thanks for your replies!
Nazrin: We're using the release strategy concept only partially. In the WF rule, and the exit, approvers are attached based on accounting information, since this is common practice in this case. This is based on an extensive approval register table, which can not contain release codes. Therefore, we use only one such code in order to take advantage of the standard workflow, and "simulate" the process. When the release has taken place, I need to update the view with the user id of the approver, so I have to find this agent by other means.
Regarding Antony's reply, I'm trying that right now
By the way, does anyone know if it is possible to get the system to display multiple approvers in the grid in ME29n?
Thanks!

Release Strategies in Purchase Order - possible values of caracteristics

Similar Messages

Maybe you are looking for