Release Strategy for a new material type in PR

Dear Friends,
One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
Regards,
Ask

Hi,
Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
Then follow all the cusmozation path for your PR release startegy .
For Config part refer the below wiki link it may help you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808

Similar Messages

Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

Hi Friends,
I have a issue to fix. The issue is releated to PR.
There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
I have to retrigger the release strategy for all the affected PR's.
The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
Regards,
Manjunath K

Hi,
Refer the discussion to triggers release again on release code addition/change in release strategy.
release code is changed on PR release strategy - old PR can´t be approved
Regards,
Biju K

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

S0004830404 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

Add release strategy in the PO document type

Dear all,
I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type.
Thanks
Pauline

Pauline,
I would suggest you to please post this query in ERP MM forum to get it answered asap.
Regards,
Faisal

Release strategy for purchase requization on basis of document type

Hi All
can somebody can explain me the procedure for creating releasing strategy on basis of doc type
Nabil

Hi,
The below link will help you to understand the process.
Please open the below link and u will get the complete process to have the Release stretegy on the basis of Doc. Type.
http://www.sap-img.com/materials/release-procedure-for-purchase-requisitions.htm

PR Release Strategy for DOCUMENT TYPE

Hi Gurus,
I have created a Document Type in PR & I want to set a Release Startegy for ONLY that Document Type.
Can anybody explain me step by setp procedure for this ?, I have gone thru one link :
http://www.sap123.com/showthread.php?t=59
but I could not set the relase startegy. May be I am missing something ??
Thanks & Regards,
Vikas

If you want to define the release strategy only for doc type
then
create the class using CL02
create the chra for Doc type using CT04 - the table is CEBAN and the field is BSART
then assign the doc type value in char (after you create the char then go back and assign the value)
now assign your char to your class
now go to SPRO and goto PR release strategy config - procedure with classification
go to Set Up Procedure with Classification
create your release group by assigning the calss you have created (make sure this config should have only one class)
create release code
release indicator is already exist in sap so you don;t need to create
create your release strategy and assign the value in classification tab of release strategy
this will work
but make sure that - if you are creating only for doc type means all the reqs created for this doc type will be blocked by the system. so if you have reqs like if this doc type and the amount >5000 then only block then you have to have amount is also you char in your class
hope this will give you a cleat idea

PR release strategy for material group

Hi,
I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

Hello
In PR you can set up this release strategy without classification release strategy.
w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
Laxman

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.

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

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Release strategy for Future validity period- (Outline agreements)

Dear All,
I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
How to set up release strategy in the above case.
Thanks in Advance.
Regards
Amar

Hi Amar,
1) if you maintain a target value (EKKO-KTWRT) in the header of the
contract this value is the basis for the determination of the release
strategy. If the target value is 0, the system will cumulate the
values of the items and will use this value for the determination.
2) So if the target value is 0 and you change the price of a condition
with a validity period in the future the system will react in the
following way:
Example:
   the contract contains one item with quantity = 100 and a net price
of EUR 5,-.
   all contracts with a target value from EUR 0 - 1.000,- should be
subject of a release strategy
   the contract is created and released on October the 1st
   ME32K -> October the 2nd you define a new price of EUR 7,- with a
validity period from 03.10.09 - 30-10.09 -> you save the contract
-> the release strategy is not reset, as the start date is not
reached yet (system date < startdate of validity period)
   ME32K October the 3rd you change a field in the contract -> the
release strategy is reset
This is system design that a release strategy can only be reset through
an action by the user. The determination of the release strategy can't
be triggered automatically in the background.
If you create a document which is subject of an overall release strategy
(e.g. p.o., contract) the determination of the release strategy takes
place when the user hits the 'save' button or chooses the 'check'
function.
So there must be a kind of event that tells the system that something
has changed.
Regards,
Edit

Release strategy for auto created PO's

Hi Guys,
I have a requirement to implement release strategy for automatically created PO's.
PR's are created automatically and we have a program which create PO's automatically.
we would want to release them before generating output to vendor.
could anyone please have any inputs here.
regards
mittu

Hi!
You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
Hope this helps! =)

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 GR?

Hi,
My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
Any help will be appreciated.
Best regard

Hi Yosea,
Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
Note: Controll always suggested at the time of making agreement (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
Hence there is no logic is going for that option
Hope it clarifies,
Regards,
Sapsrin

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 advice

First 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 a new material type in PR

Similar Messages

Maybe you are looking for