PR Release strategy to be assigned to user

Hi Friends,
I have created the release procedure for releasing PR. Now I want that to assing to the user id. Can someone please tell me which paramter or role that i need to assign in the user profile.
Regards,
Wasim.

Did you created a char with the table is CEBAN and the field is BSART for document type.
What all char did you use along with doc type?
If you use only document type then it will be blocked, try to define one more char for value based and define diff value ranges in strategy so that it will work fine.
Check you have ticked Overall Rel for PR req in SPRO against your class..
Check you have ticked Overall Rel for PR req for your document type in SPRO.

Similar Messages

PR Release Strategy for Account assignment cat "U"

Is it possible to set up release strategy for Acct assignment Cat "U" - if yes, How would it be configured? additionally we are also setting up Rel str for acct assign cat K and A - specific question is relative to "U" in addition to K and A.
Other parameters being used are
pur Org
Doc type
cost center
Total value
Thanks for the help in advance
Raj

Dear Raj,
When you creating PR with acct assignment U, the acct. assignment tab will not appear, thus
you not able to enter cost center. You may try this workaround via customizing.
a) You may define a <BLANK> value for the cost center in customizing and assign it to your release strategy.
Characteristic:
Cost Center:
Value    Desc:
1000     1000
2000      2000
                <BLANK>
b) You may use user exit EXIT_SAPLEBND_001 and pass the dummy cost center to get the release strategy
determine.
Regards,
ian Wong Loke Foong

Release strategy -multiple account assignment

Hi,
I have PO release strategy based on account assignment(one of the criteria). AAC used is P,Q, and N . Couple of questions -
1) I do not want to allow multiple account assignment in PO.
2) KNTTP is not available in CEKKO communication structure. I had to bring it through a user exit. Because of this looks like multiple account assignment still triggers release.

Hi
The thing you need to get considered is does the PO release at header level or at item level .You can create a class for account assignment category and assign the charecterestic properly created with the tab basic data properly filled for value assignment and assign the values for the AAC .
Regards,

PR overall release strategy with acc. assignment category characteristics

Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
Isabelle

What is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer

PO release strategy user exit

Hi Experts,
This is regarding the PO Release strategy.
I have implemented user exit u2018EXIT_SAPLEBND_002u2019 for filling User defined field i_cekko-usrc1 based on PO line item net values for PO release strategy.
Our function consultant defined characteristic on this field and created at the release strategy.
My code in the user exit:
i_cekko-usrc1 = 'X'.
e_cekko = i_cekko.
It is triggering the user exit and setting the USRC1 to u2018Xu2019. But it is not triggering the release strategy.
Do I need fill any additional fields?
Thank you for your help in advance.
Regards,
Soujanya

Gentlemen,
Any Ideas....!!!

User exit for workflow for release strategy

HI,
I got the user exit M06E0005 for workflow for release strategy. Is there any user exit during PO saving time, so that depending upon the PO no and the release code, the mail will go to respective person for the release of PO.
Regards,

Hi,
Refer the below Link for PO workflow set up, for more information you can co-ordinate with your workflow team.
http://help.sap.com/erp2005_ehp_05/helpdata/en/4c/16443c4a089537e10000000a114084/frameset.htm

Release strategy

Hi all,
We have two document types for PO. In one of the document type if user wants to change the PO once the it is released then system asks user to get the release indicator in Block state & then allows user to change the PO.
In another document type if user wants to chnage the PO after it is released then system doesn't ask the user to change the release indicator to Block state.
Now problem is while migrating the data from one sap landscape to another our consultants have selected prior document type which is asking user to set the PO in Block state for change.
Now we want to change the POs & we know that we cann't change the document type of existing POs, pl. suggest how we can change the configuration so that system should not ask us to change the status of PO.
thanks in advance.
vinay

Hi,
I suppose that you are using the exit ME_REL_STRATEGIE_EKKO -> EXIT_SAPLEBND_002 in order to get that information
message which tells you to change the release status for blocking the PO again. Please switch off this exit for a while.
I would also recommend you to check the changeability indicator in the customizing of your release strategy - it was assigned to the concerned release indicator (which has the released status).
Regards,
Edit

Purchase Requisition with wrong purchasing group - release strategy

Hello
There is a lot questions about release strategies but I cannot find answer.
I have release strategy based on:
- Plant
- Purchasing Group
If I create Purchase Requisition with right purchasing group release strategy is assigned to PR item.
When use wrong purchasing group - release strategy is not assigned.
How to easy set control if user use wrong purchasing group system automatically set one strategy which not allow to create purchase order.
There is too many plants (150) and purchasing groups (60) to create all combinations in strategy. So I cannot do that.
Maybe there is some useful user-exit?
I use SAP ECC 6.0
My problem occurred because SAP allow to create PO with reference to PR which have no assigned strategy.
Thanks in advance for help
Arek

Yes it is solution
But as I wrote before there is too many incorrect combination.
Example
PG A1, A2, A3, A4. A50
Pl 2200, PG A1 OK
Pl 2200, PG A2 OK
Pl 2200, PG A3..50 NOK
For this example I have to set 48 combinations (strategy with S).
I noticed that I would have to set about 200 strategies. Client dont want accept it.
You wrote set up one unique strategy. How? As I know I need 200 strategies (or there is something I dont know
Kind regards
Arek

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

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
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.
regards
ravikant dewangan

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 purchase order workflow

hi,
after release strategy defined ,
i configured role on relesae codes in img.
1. If I (functional people and me) define release strategy, I have assigned the roles, then if purchase is created , the work item goes to particular agent inbox or not ?.
Because there is any further configuration is there after release strategy is defined,
Now, I configure workflow only for to send mails to particular release code persons.
I want this clarification.
2. For rejecting POs is there any EVENT.
I found RESET event for rejecting POs, is it correct.
please reply ASAP.
thanks & regards
suresh

Hey,
You need to use business object BUS2012. Do a where used list from transaction SWO1 and you will find the standard workflows delivered by SAP. You can either use these or create a new workflow.
Event ReleaseStepCreated can be used as an triggering event to send emails when a PO is created. If you want to trigger an email only for specific release codes you need to evaluate the release code in your workflow.
Event Rejection_start for evaluating Rejections.
-Kiran
*Please reward useful answers

PO Release Strategy Issue

HI,
We have created a PO release strategy workflow.All scenarios are working fine except 1 scenario.
That is,when a PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.
If the release strategy is for a different user,its triggering the workflow.
I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Can anyone tell the solution for why the workflow is not triggering for only this scenario?
Thanks,
Aparna.

Feddie wrote:>
> Kjetil, I am not clear still, could you explain me a bit clear. I have not seen any tool tip in my release tab.
Don't you see any buttons in the subscreen? The tooltip is not for the tab (title) it is for the button. I am quite sure there is a button there for cancelling the rejection, but without access to a system where this has been set up I can't check it. I just had the same issue before Christmas, where the users said the solution didn't work for the same reason mentioned here - no workflow was sent after changes where made. In fact the solution did work flawlessly as soon as they cancelled the rejection.
See also [documentation at help.sap.com|http://help.sap.com/erp2005_ehp_02/helpdata/en/4c/16443c4a089537e10000000a114084/frameset.htm|ERP release ECC 6.0] for the workflow for rejected purchase orders.

Stop release strategy when pgrp changed triggering different release group/

Currently when our buyers change the purchasing group field on the purchase requisition it is triggering a new release strategy because the release group and code is different than the original creator.
It has been indicated that we should request from SAP that these two fields be made available to the structure for the release strategy.
Is there a user exit that we can use to stop a new release strategy?

Hi,
Do you have different rel. stgy for diff. plants? if yes, than which rel. stgy should be picked in case if both plants entered have different rel. stgy? what is your expectations/requirements?
If your PO is to go through diff. approvals for different plants than you should have different PO for each plant (even diff authorizations and rel. codes), or else you should not have plant as the criteria. Technically, whether it is fesible or not is different question, but whether practically your organization is ready that if a common material is to be procured it will have approvals of only one plant or may be a different approvals all together?
Regards,
Dakshesh

Where to assign User Id to agent id in PO release strategy work flow

Hi Guys
I have on requirement
Where to assign User Id to agent id in PO release strategy work flow
Thanks in advance
SAP MM

Hi,
Check & follow the path:
SPRO-- > MM ---> Purchasing -> Purchase Order- > Release Procedure for Purchase Orders -
> Define Release Procedure for Purchase Orders -
> Workflow
Here against each release code assign respective User ID's for Release Code
Regards,
Biju K

PR Release strategy to be assigned to user

Similar Messages

Maybe you are looking for