PR Release Strategies on purchasing group basis

Dear All,
I want to define PR Release Strategies on purchasing group basis. please suggest process.
Regards,
Mukesh Chejara
SAP

you can use Table name CEBAN and Field name EKGRP define in the characteristics and then maintain the master data in CL20N.
Regards,
qsm sap

Similar Messages

Release Strategies in Purchase Order - possible values of caracteristics

Hello,
I have the following situation at hand.
We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
I can not change the caracteristics in the Release strateg because this would affect the already working strategies and SAP does not allow to asign another Class to the PO release groups.
Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
Can I use something generic in the caracteristics field of the strategy?
Thanks for any help. It would save me a lot of time!
Aart

Note 493900 - FAQ: Release Strategy
1. Question :
Why is the release strategy not determined?
Answer :
Please check the following points :
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
If you use version management, the determination of the release strategy starts when the version is completed.
You complete a version by setting the "version completed" indicator in the version tab.
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

Release strategies for purchase requisitions

Hello,
I'm having trouble with profiles and roles for release strategies, this is the scenario:
-for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
Many thanks
Daniel

HI,
Not necessarily, you just need a different strategy for each different combination of release codes involved.
So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
Or however many different variations you have.
Steve B

Workflow for PR release for multiple purchasing groups

Hi Guru,
We have multiple purchasing groups and want to send emails to the responsible person for PR release for their own purchasing groups. In the standard SAP pr release work flow configure, there is no place to specify purchasing groups. Do you have any recommendation? If we need ABAP development, do you know the user exit that we need to modify?
Thanks a lot!

Hi
Define the release codes for each person heading a department (purchasing group) and assign the work flow for concerned person. When ever you create PR, depending on purchasing group work flow will be triggered. Assign the release code and release group authorization to particular person's profile in PFCG. Then he can be able to release PR.
Thanks

PR RELEASE STRATEGIES-Details Unseen it SPRO

Friends,
Over the time period there are several RELEASE Gropus & associated RELEASE Strategies also for PR in our scenario.
PR is also picking right RELEASE Strategies on item level basis.
However isse is that there are few RELEASE STRATEGIES picked up by RELEASE CRETERIA which I cannot see in SPRO config screen where we define / see release strategies...
However release strategy / rel Grp details are there in TABLES...
Then why system is NOT showing details of All RELEASE GROUPS / Rel codes / Rel indicators & Rel strategies which are so far configured till today in a client.
What can be possible de-link in system?

We can see release startegy customizing in the following path
SPRO -> Materials Management -> Purchasing -> Purchase Requisition
-> Release Procedure
under this Release Procedure -> Procedure with Classification ->
Check Release Strategies we can check whether the basic settings
for our release strategy are complete and correct
Please review the SAP note 365604 'FAQ: Release strategies in
purchasing' which describes all the prerequisites for a release strategy
to be determined correctly.
If on the other hand, the release strategy you have defined for
purchase requisitions is not being determined by the system please check
the following:
1- Go into transaction CL30(N) and enter the values of the document and
click on the button 'find in initial class'. If you do not get a result,
check the customizing if there is a release strategy which matches the
values of the document.
2- If you get exactly one result, it is an indicator that the
   customizing was defined correctly. Then check:
2.1 Is there a userexit activated (see note 365604 for the user
         exit name)? If yes, check if it contains the magic line (for
         purchase requisition: E_CEBAN = I_CEBAN)
2.2- For purchase requisition, the overall release flag has to match
    the one defined in transaction OMEB for the document type.
3- If there is no release strategy determined after the implementation
of a support package and you use a userexit, check note 435150.
4- Check in the customizing if the characteristics were entered in the
internal format (e.g. the cost center must have 10 characters with
leading zeros), see also note 365604, point 2b).
5- In case the item category is used as a characteristic, check that you
use the internal format defined in OMH4.

Release strategies to PO

Dear friends !
we will use release strategies to Purchase orders with standard workflow only to send a message to user (into tcode SBWP).
I have configured release strategies and put it on field " Workflow" the value " 1"Role resolution with group, code, and plant (T16FW) and also put at the " Workflow " specific , the Object Type = US and the userid = BRAZILA(logon to SAP).
But after we save the PO no message has been sent to Users.
does anyone knows if are necessary others customizing settings ?
Which settings and tcodes are theses ?
I´m looking for more details inside SDN but no specific transactions were available and easy to understand until now.
Best regards,
Ale

Dear friend Thx for your answer
Do you have any BPP to config this ?
Any documentation general about this configuration!
best regards
ale

Block creation of PO if the release strategies is not applicable

HI SAP,
Can we block creation of PO if the release strategies is no applicable ?
My release strategies is on the PO header. It's only work if the PO have one Plant only. If the user put more then one plant
my release strategies will not work. how to solve this problem ?

Hi,
Check on it:-
http://www.sapfans.com/forums/viewtopic.php?f=6&t=205684&start=0&st=0&sk=t&sd=a
Re: Release Strategies in Purchase Order - possible values of caracteristics
PO Release strategy question
pherasath

Create new characteristics for existing release strategies

Dear experts,
Whenever I have a roll-out, I have to create a new characteristic that is the purchase order value in local currency, that is to be assigned to the class used for the Release Strategies of purchase orders.
The problem is that whenever I do this, all the existing release strategies have an additional characteristic to be maintained. Since I have more than 1.500 release strategies, I have to go through each one of them and except for the new release strategies, put >= zero in this new characteristic.
Is there any way, that whenever I create this new characteristics, I can define a default value that will be assigned to every existing release strategies in the system?
I've tried to use the default value, but it only works when I'm introducing the characteristics values for the first time in the release strategies.
Any ideas?
Thanks.

Hi,
You can try LSMW (Direct method) for uploading class values.
Upload file can hae following structure:
OBJEK     |     ATINN     |     KLART     |     ATWRT
Release Grou+Release strategy |     Characteristic name     |     Class type     |     Class Value
e.g. rel grp is PO, rel strategy is 01, characteristic name is EBAN_EKORG, and class value is 1000 then
OBJEK     |     ATINN     |     KLART     |     ATWRT
PO01     |     EBAN_EKORG |     032     |     1000
multiple characterstics can be
OBJEK     |     ATINN     |     KLART     |     ATWRT
PO01     |     EBAN_EKORG |     032     |     1000
PO01     |     EBAN_EKGRP |     032     |     100
Regards,
Yogesh

To maintain the purchasing group to all release strategies

I want to maintain the purchasing group to all release strategies using cl24n transaction.
plz help me out.
I am trying to do that using 'BAPI_OBJCL_CHANGE' and passing the values as:
OBJECTKEY: A0T1
OBJECTTABL: ******
CLASSNUM: available
CLASSTYP: 032
Plz tell me the what table name need to pass in OBJECTTABL field.

There are few tables with T16F* , please try with suitable one...

Release Strategies not works - When multiple material group in a single P.O

Hai,
This related to Release Strategies in SAP- IS -Retail.
The Material group was one of the character in the Rel Strgy.
1) If i create a P.O for the item which is related to " X" material group , Rel Strgy been set to P.O
2) If i create a P.O for the item which is related to " Y" material group , Rel Strgy been set to P.O
If I combine material group "X' & "y" in a same Purchase order , then RELEASE STRATGY NOT BEEN SET TO P.O .
How to make this as possible in SAP -IS-Retail - Version 6.0
Thanks,
PS

Hi,
Generally it is not advisable to use item level characteristics for overall release . Please refer the sap note 493900
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.
you have to maintain blank value in CT04 for material group and the same thing must be maintained for all strategies.
The release procedure for purchasing documents is carried out on header level. For this, the following values are aggregated from the items on header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items contain the same plant. If only one alternative plant exists, ' ' is aggregated on header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was maintained for the characteristic 'Value' as an object value.
The same functionality applies to the plant

Purchase requisition : problem with check release Strategies

Hi all,
i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
Is there a special value to give the release indicator 'released' ?
Thanks for your help.
Edited by: ToraTora on Mar 31, 2011 5:46 PM

Hi,
Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
select release indicator
by default, you will be having the following release indicators in the system,
1     Request for quotation
2     RFQ/purchase order
3     RFQ/PO no change of date
4     RFQ/PO no changes
A     Fixed RFQ
B     Fixed RFQ/purchase order
X     Blocked
please check whether you have got these or else create and then assign them to the release strategies.

T code to get the detail of release strategies for all purchas groups?

Hi,
Is there any T ode that i can run a report and get the current details of release strategies for all purchase groups exist at the moment?
if so pls let me know
or else how can i get that information?
highly appreciate all of your assistance in this regard?
thanks in advance
Regards
Sasika

from T16FS you can only get which strategy are present.
Which strategy you have can already be seen in the PO or requisition.
But you are looking for the person. this is not really easy, as this can be more than one person.
A strategy has the information what release code is needed.
And this release code is in a role which is then assigned to an approver.
So the only way would be to execute SUIM and then roles by authorization values.
there you enter the authorization object M_EINK_FRG (hit enter) then you have to enter the release group and release code.
Execute. SAP will list all roles that grand the authority to release order with this combination.
in this list you can click another button to see the users that are assigned to this role.

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

Release Strategy in PR not triggered for different Purchase Groups.

Dear Experts,
For Purchase Requistion - Header Level Release Strategy has been defined with Purchase Group as one of the Characteristics(Characteristic Values are V1, V2, V3).
When PR is created for 30Line items with V1, V2 or V3 as Purchase groups independently- Release Strategy is triggered.
But when a combination of all 3 Purchase groups is used in the same PR for 30 Line items together. No Release Strategy is Triggered. All these 3 Purchase groups have been assigned for all strategies.
Thanks & Regards
Chandan H N

You are using characteristic P. Group for different RS. That means that if only one value exists, the system will be able to understand which RS to implement. If you are using more than one values for this characteristic, the system simply does not know which RS to choose and takes nothing.
More simply you are using a header data (p. Goup) for RS and you are using it in line items. This is wrong. You have to make PR's only for the respective P. Group

Purchase Order Release Strategies for Changed Amount

Hi Gurus,
We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
Example: Configuration is PO total amount <$5K requires only L1 approval. PO total amount >$5K requires L1 and L2 approval. PO was created for $8K and was release using L1 and L2 approvals. Receipts were posted to PO in the amount of $7K. Now the buyer has added an additional line item for $1K. The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item). Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
Has anyone done this before? Any ideas??
Thanks,
Gabe

from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
The following user fields are available:
USRC1
USRC2
USRN1
USRN2
In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

PR Release Strategies on purchasing group basis

Similar Messages

Maybe you are looking for