Reg PO Release Strategy

Firstly Release strategy for PO is configured.
Now they are asking for new release codes to be added to the old ones.
The issue is when i am configuring this
old PO's no probelm as they are released.
new PO's no problem.
The issue is with OPEN PO'S .The new release code is going and sitting there but no PEN MARK will be there.(It is simply GRAYED OUT).so this creating problem for OPEN PO's.
How to overcome this.
with regards,
Patil Mallik

You didnot understand my problem.the problem is suppose there are 3 release codes previously.now only 2 release codes has released the PO.Still one release code yet to release.
now if i configure the new release strategy with one more New Release code.That New release code will come and sit in this Open PO(whose two release has happened and waiting for 3rd release) without having Pen symbol to release it is infact grayed out.
This should not happen i think.
for this there is any solution.this wont effect my procurement process.but the job of 4th new release code is done by 3rd release code which is not correct at the time of audit etc etc.
Any work around for this.welcome your suggestions and answers.
with regards,
Patil Mallik

Similar Messages

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 Get cancelled - Reg

Hai,
We are in SAP R/3 -ECC 6.O
Release stratgey has been set for the Purchase order and its works well for so many years.
The issue is , Some of the P.O alone , when the Header Terms & condition changed , Like adding one text line, or Some space or some dot, comma, The Release Strategy gets Re - Triggered ( Plz mind that , i have not changed any P.O Qty / Value/ Organisation entities/ Material Group/ Material/Tax code)
Kindly update , The reason - Why Release strategy gets re triggred for the , already Released P.O.
Regards,
PS

Release strategy gets retriggered only in case you have changed the amount or qty thereby increasing the amount of the PO
but as you say that you have not changed any thing which will impact the amount of the PO but the RS still gets re-triggered then we are left with only one option that some user exit has been active for this or some BADI please take help of abaper to find out the exit for this

Reg: P.O Release Strategy Changes

Hi All,
Release strategy is configured for a P.O.The changes in terms of releasing the P.O can be viewed in P.O Screen---Environment -
Changes.
Do we have any table for checking the changes made to a P.O in terms of Release strategy?
Have a Nice Day.
Regards,
RaviKumar.S

Hi,
You can check this in CDHDR table.
If version management is active for your PO then you can check the changes in EREV table.
Regards,
Bharat

Travel request release strategy reg

Hi,
How to create Travel Request Release strategy.

Hi,
If its TR for Release strategy,then follow this process
In golden client , its automatically cretaed/ saved in TR.
You have to create characterstic/class in all clients
Regards

Reg: Release strategy

Hi Experts,
I am now doing rollout project.
We copied the earlier configuration & dumped it.
Now we r in testing phase.
I configured released strategy for PO.
First I created charecterstics & then assign all to my class with class type 032.
Then inT code OMGS i configured every thing but when I am creating PO release strategy is not triggering. Same time also system is not throughing any error.
Please can anybody guide me in this regard.
Thanks in advance
Regards
Nayak

Hi dibyajyoti nayak ,
Check this
Go to SPRO > Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Check Release Strategies
Also checkcharacteristic CT04 for additional data.
Hope thsi will solve your problem
Thanks and regards
Gitesh

How to check the PR release Strategy change date?

hi,
how to check when the PR Release Strategy chagned by someone ...?
Regs,
S J Solanki

Hi
You can directly go into the Purcahse order & check for the Heder changes which will give the Changed Date
If you need to use two table to find out the date when the Strategy was changed.
Use Table CDHDR & CDPOS. Object key is the POurcahse order number
Thanks & regards
Kishore

How to turn off Release strategy

Hi,
We need to upload purchase orders via LSMW. While doing so, we do not wan the release strategy to be active to avoid the need for approving each order. How can I turn off the release strategy.
Thanks in Advance.
Regards,
Pavan

Hi
Not sure if this requirement is to handle the cutover POs/ POs which were already approved in legacy system, I have handled this by two ways in the past ( as due to last minute changes we were not sure abiut frequency and need of turning release strategy to on / off
1. We have use a charactertistc (corressponding to PO date ) in Rel strategy and setup in such a way that REL strategy is active for PO with PO date > Go-live date ( all legacy POs were loaded with s date earlier than Go -live date)- this ensure that we need not to do on/off several time
2. another case we created a seperate PO doc type and excluded from rel strategy, no uses was given authorization for creation of this except the cutover / data migration team which was responsible for cutover
Hope these suggestion helps
Reg
Dheeraj

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

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.

PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Hello everyone,
I've run into an interesting problem:
We have defined several PO release strategies. Most of these work in the traditional manner, requiring manual approval by a given user. One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
What would cause this discrepancy? The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
Thank you ahead of time for your help.
-Jarrod

Configuration issue/user error.

PO Release strategy

Hi,
I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
Any suggestions are highly appreciated to fix this issue.
Regards
Sudhakar

Hello,
After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
regards
anand

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

Contract & PO Release Strategy

Hi All,
We are in the process of designing the release strategy for contract and PO. I would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
The release conditions for Contract required are
1)Porg
2)Pgroup
3) Value
Also, for quantity contract how can we make the release strategy trigger based on value.
The release conditions for PO required are
1)Porg
2)Pgroup
3)Material Group
4)Value
The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
Request your help.
Regards,
Kannan

Hi Kannan
Yes your requirement is possible...
While creating Charectristics in CT04 for External Purchase Documents...Create one more Value for your Document Category...ie) Table as :CEKKO and Field as BSTYP and choose the Purchase Doc. Category values K and F.
Then create Charecteris for CEKKO - EKORG, CEKKO - EKGRP and CEKKO - GNETW, CEKKO- MATKL... and assign these all 4 Chareteristices in your release class.
And Configure your release statergy according to your requirement...
Reward if useful
Regards
S.Baskaran

Reg PO Release Strategy

Similar Messages

Maybe you are looking for