Release Strategy for PR doesn't work

Hi experts!
I'm a begginer with the release strategy.
From customizing I've created the characterisitcs, class, group, indicators and strategy for Purchase Requisition.
I've created a purchase requisition to prove it works,... but nothing has happened.
The characteristics are GWFRT >0 and WERKS = 1001.
And after the purchase requisition have been created I don't see anything in the PR. With the ME54N transaction , the message
' the PR can't be released' appears.
Could anybody help me please?
any help would be appreciate....
thanks in advanced.

Hi,
Check out this :-
http://www.sap-img.com/workflow/workflow-of-purchase-requisition-release-strategy.htm
http://sapdocs.info/sap/materials-management-2/step-by-step-sap-pr-configuration/
pherasath

Similar Messages

PR Cost Center Release Strategy for Item Level not Working

Hi All,
I have a class with 2 Characterictics, CEBAN-ESTKZ (Creation indicator) and CEBAN-KOSTL (cost Center) and I have 2 release strategies the first one should trigger when MRP creates a PR ( ESTKZ=B and KOSTL=No input) this strategy is working fine, but the second strategy should trigger is if manually I create a PR and it is relevant to a cost center (ESTKZ=R and KOSTL=XXXX) This is not working, I dont know why sistem is not triggering the release strategy if everything seems to be ok.
I know ceban structure has kostl field, but I checked and this field is not in the EBAN table, maybe this is the reason but then how will this work and as far as I know, this is standard field.
I checked in CL24N and all the objects are assigned to the class, all hace status released (1) and and the "OK" check mark
I checked in CL30N and if I enter in the ESTKZ characteristic=R and KOSTL=XXXX Then it finds the correct and only strategy, so I don´t know why this is not working, the only strange thing is that in CL30N if I only enter value R and leave empty the cost center, the system finds and shows me the 2 release strategies, this is strange.
Is it mandatory to include the acc assignment field in the release strategy?
Please give some guidance.
Thanks
Edited by: Julio on Nov 14, 2011 12:14 PM

Hi, thanks for your reply,
I have entered with leading zeros to complete 10 characters and is not working, I really don´t understand what is going on here, It should work even if I just have 1 characteristic assigned to the class right? this characteristic is CEBAN-KOSTL but this is not working.
Any more ideas?
Regards

Download Oracle 10g Release 2 for Solaris doesn't work

Hi,
I think the file to download Oracle 10g Release 2 for Solaris Sparc 64 has incorrect format.
After download I try to do as you suggest:
guzip file
But the result is:
gunzip: 10gr2_db_sol.cpio.gz: invalid compressed data--format violated
Could you check this
Cheers
Angle

But I can download it.Its space is 623M.

Download Oracle 10g Client Release 2 for Solaris doesn't work

Hello,
When I try to download 10gr2_client_sol.cpio.gz at this url :
http://download.oracle.com/otn/solaris/oracle10g/10201/sol64/10gr2_client_sol.cpio.gz
I get 0KB file .
How can I do ?

But I can download it.Its space is 623M.

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
subbu

Hi,
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 PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

Work flow for release strategy for PO & PR

Hi Gurus
Can anybody explain workflow for release strategy for PO and PR
Thanks in advance.
Atul Kulkarni

Hi,
First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
For Work flow settings,You have to do follwoing configuration:
MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
Creation of work flow object,activation of workflow and other related settings will be done by Techinical work flow consulant.
Thanks,
AMIT

Redetermine release strategy for purchasing requisitions

Hi Guys,
How can I redetermine the release strategy for purchasing requisions when changes on the costcenter (EBKN-KOSTL) are done -
I know that it will be redermined when I add the costcenter as charateristics in customizing for release strategy but thats not an option
I also tried to add coding in userexit for changing the communication strategy (Include ZXM06U13) but this exit doesn't provide information of the document number and position (EBAN, EBKN ..) so I can't find out if changes have been made
I spend several hours trying to find solutions for this issue but no working results so far ..
I hope you can help me on that
TIA
Manuel

Hi,
Note that EBKN will have entries corresponding to a PR only when it is
saved or checked, so KOSTL will not have any values for a PR which is under
creation. You should always use fields from structure CEBAN while
creating characteristics for Requisition release procedure as it
contains most of the relevant data about a PR under creation/change.
I would advice you to check the note 365604.
Please also check the changeability indicator in the customizing:
transaction OLME -> Purchase Requisitions -> Release Procedure -> Procedure with Classification -> Set Up Procedure with Classification -> Release indicator -> check the detail screen for settings.
Please check additionally the possible values for your characteristic cost centre (transaction CT04).
Regards,
Edit

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

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

Reg.Release strategy for particular vendor

Dear Friends
We have 500 vendors, the release strategy is aplies to all but the Release strategy should not be applied for particular one vendor.
that is w/o release strategy that vendor has to work(if we raise PO the release strategy should not be applied)
Pls help me
Thanks
Rajakumar.K

Vendor master is dynamic and if you define it as a character value, then you need to keep on adding the vendor numbers.
as and when the new vendor is created.
if you use the purchasing group as a character, then what happens if another user creates PO with different purchase group.
you need to think about the below options.
1. Define release process based on purchase group XX as suggested by many , but use BADI ME_PROCESS_PO_CUST
and write the logic in such a way that, do not allow to save PO if the purchase group is not equal to XX.
2. Use BADI ME_PROCESS_PO_CUST and write your logic in such a way that for that vendor it should not refer table CEKKO

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.

Release Strategy for contracts.

Hi gurus,
Good day,.
Please help on this.
We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
Example.
Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
Thank you.

Dear Acel,
The example you given was working just fine and correct.
a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
-> The release strategy will only be reset if the total net value for the contract was higher the previous
value but not lower.
As your example, quantity was updated to 1200, then it will reset when changing from 1000
to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
In system, it always assume if you had approved for the total value of the higher 1 before, then
it should be fine for the lower total net value for your management and therefore not need to re-approve
again for redundancy job. This was very logic in common business scenario in many companies.
However, like in your example , if you had define a different release strategy for a value that met the
the 1100 quantity, it will redermine the different release strategy. For example:
USD 1 for every quantity = 1
Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
USD 1200 for quantity = 1200.
Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
Release strategy C for 1200 , characteristics from USD 1200 onwards
Then if you change the quantity from 1200 to 1100, it will redetermine the release
strategy B which means from Release strategy C to Release strategy B. If you
only had Release strategy C that had a characteristics from 1000-1200, then
it will keep the Release strategy C as released and it won't be reset unless
if you had change it and the condition of the total net value was higher than any value
before.
Hope this will explain the logic.
Ian Wong

Release Strategy for PR doesn't work

Similar Messages

Maybe you are looking for