Release strategy for Poduction order

To All
We are mapped client bussiness with MTO scenario, but deactivate automatic Sales order costing as the material BOM is changable as per production line. We planned to cost after Bom is fixed for particular production.Now as Sales Order planned fot manual costing we want a check, that no one can RELEASE the production Order before SALES ORDER Costing is done.
I tried it by stasus setting but through it checking is not possible.
Please tell me if any Exit or other method that I can apply to restrict the Production Order release before Sales order coting.

Hi
No std setting is available in STD SAP .
we are working on same seneriao "Production orders will not be released unless a standard cost estimate or marked sale order cost estimate is available for the material.Standard cost estimate . Sale order costing to be done by authorized persons whenever required."
For that setting you can make a "Z" programe (means validation ) with the help of apaber and co consutant

Similar Messages

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

Is it possible to have release strategy for sales order?

Is it possible to have release strategy for sales order?

hi
as per SAP standard there can not be any release strategy for sales order but if u want to control u can use authorization profile for this purpose.
povide authoriztion to the required persons only..
regards
CMM

Release Strategy for Sales Order-IMP

Hi Gurus,
I want to know regarding <b>Release Strategy for sales orders</b>. I want to know the detailed step-wise procedure for SO and not for PO. My understanding is that standard SAP does not support Release Strategy for SO in SD Module. Please l want the following queries to be answered
1) Is my understanding on Release Strategy for SO correct as mentioned above?
2) What are the other alternatives and the steps of configuration step-wise.?
Kindly help me post this information as it is required urgently. Suitable full Reward Points will be given to all answers.
Many Thanks,
Pankaj Mishra
E-Mail : [email protected]

Pankaj,
There is no release strategy for sales order.
You can try it doing Authorisation /Status profile with your BASIS person...
REWARD IF U FINDS THIS AS USEFUL...
Regds
MM

Release strategy for maintenance order

Hi experts,
Can we have release strategy of maintenance order based on the components cost in the miantenance order

hi
i think you cannot achevie this with Standard SAP, you can make use of customer exit to enhance the releasing of order,other way is by indirectly ,ie create permits with classification as Planned cost specify the amount which will reject the relase of order saying permits are to be issued,and also you can assign the roles for the user for displaying the permits ,forbidding the issue of permits
regards
thyagarajan

Release strategy for Sales Order

Hi all,
Is it possible to assign release strategy to Sales Order document in SAP?
Thanks
SAP-MM.

Please check this answered link:
Re: Release strategy for a Sales order
what is release strtegy for sales order
Edited by: Afshad Irani on Jun 30, 2010 12:27 PM

Release strategy for sales orders

Hello Gurus,
My customer has got a requirement of approval of sales order before it actually goes for dispatch, (it is inline with the purchase release strategy).
Hope, SAP does not have a standard solution for this but I understand this can be done through the "status profiles". I dont have any idea how exactly this can be configured, can someone help on this? Please guide with the stepwise configuration.
Thanks in advance.
Ajit Patro

Hi,
User statuses are always defined in a status profile.
Procedure
First, you create a status profile.
Assign the corresponding object types to the status profile.
Define the required user statuses in the status profile.
Assign the user statuses to the corresponding business transactions.
If necessary, translate the status profile and the user statuses.
To be able to work with a status profile, you first need to assign it to the order type in Customizing (Customizing for Shop Floor Control by choosing Master Data - Order - Define Order Types).
For information on how to create a status profile, see Customizing for Shop Floor Control by choosing Master Data - Order - Define Status Profile.
You have to activate the customized status profile.
Regards,
Siddharth.

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

External mail for workflow of release strategy for PO

Dear All,
I have configured the workflow of two step release strategy for purchase order and the internal mail is getting generated in the sap business workplace with the error message SWF_RUN 594 this i have taken care with SWE2 with changing the settings of "Behaviour upon error feedback" from "default" to "do not change linkage"
Now the requiremnt is that the message has to be send to first level releaser through external mail and once first level release the PO external mail should be send to second level releaser.
Please help me with the configuration step that is to be done
Thanks in advance
Naveen Singh

Schedule the report Rswuwfml2. this will send workitem from sap inbox to respective user external mail id maintain in user master.

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.

What is release strtegy for sales order

hi gurus
what is release strategy for sales order
can any one throw some light
points awarded.
kishore

Dear Rama,
There is nothing like release strategy for sales order. There is a release strategy for purchase order. A bit of search on sdn forum in MM section will help you a lot on this area.
For your reference, 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   0
                        1
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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

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,
2tea

Please 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

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.

Reset Release Strategy for any change in the Purchase Order

Hi,
Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
If so, where do we need to make the configurations.
I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
Thanks in Advance.
S.Raghavan

hi sandesh,
sorry, i know it's too late.
i tried your suggestion, it works blocking the purchase order after release strategies are setted.
sandesh, raghavan:
i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
regards
f

MM:Release Strategy for Release Order again Approved Contract

Hi,
Release strategy for Release Order is required or not against approved contrat??
As fas as I know once the contract is approved, release order is not required to approve again.
This is the standard setting from SAP or We need to do some setting for this??
In my support project I have studied the release procedure and found that, same release strategy and release Group has been used for Purchase Order and Contract.
Please let me know if anyone have faced this rquirement or I have to go for Z development for this requirement.
Thanks you.

Hi Lalita,
Thank you for your quick suggestion.
yes definitely the release stratergy and release group should be set up separately but here both are same
that is the reason this is picking of the same release procedure again evenif the contract is approved.
we have following release characterstic for the release procedure.
1) Purchasing Group
2)Total Net Order Value
3)Order Type
4)Purchase Organisation
5)Material Group.
I think for the above characterstic we must a separater value for PO and Contract but Currently all are merge
in this only
But Can you tell me "Release Order should be subjected to release procedure" this is correct or not .
If yes then what is the base for this, I mean is it working on the concept that " If do relevent
release characterstic value is found then no release procedure and this is treated as autorelease in sap"
Thanks you.

Release strategy for Poduction order

Similar Messages

Maybe you are looking for