PO release strategies

Hi all,
A requirement arose in my company, to get all the details of PO release strategies exist now.
That is, when you consider a single department we identify that department in SAP by purchase group code allocate for that particular depaartment. At the same time there are few level in a particular purchase group like 0 to im value category , 1 m to 5 m value category, 5 m to 10 m value category, etc, etc.
now it is a company need to collect all the data relating to release groups, that is who are the responsible people that are having the authority to approve each and every value categoryfor all purchase groups.
there is no other way that i can see rather than collecting these information manually which will take atleast 3 weeks time if i do only this job,
but if i can find the tables where the data is stored i will be able to write a small programme and collect the required informaion
what are the tables related to SPRO PO release strategies
Your assistance in this regard is highly appreciated
Regards
Sasika

Hi ,
Customizing Tables
Release strategy without classification
u2022 T161I as described above.
u2022 T161E Release code and Description
u2022 T161S Release indicator
u2022 T161G Assignment to release indicator
u2022 T161F Prerequisites
AUSF Characteristics Value
Release strategy with classification
u2022 T16FG, T16FS as described above.
u2022 T16FH description of the release group
u2022 T16FT description of the release strategy
u2022 T16FC Release code
u2022 T16FD Description of the release code
u2022 T16FV Prerequisites and actions
u2022 T16FK Assignment to release indicator
u2022 T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
u2022 T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
Regards,
Anupam

Similar Messages

PO release strategies with Contract

Hi,
implementing a PO release strategy (SAP-MM module)I need to consider the case in which a PO is assigned to a Contract.
If so, different release strategies should be selected according to the PO value.
Possible cases:
S0-strategy 0: Contract does not exist, PO value>=0eur
S1-strategy 1: Contract exists, PO value>=100eur
S2-strategy 2: Contract exists, PO value>=200eur
Is someone aware if it is possible to activate such release strategy without defining manually in the characteristic for CEKKO-KONNR field all possible contract single values (entire range)?
Thanks a lot for helping!
Regards,
Elisabetta Rizza
Please contact me at following mail addresses:
[email protected]
[email protected]
Hi Elisabetta,
I've moved this here because it is a more appropriate thread. BPX is the place for discussing the role of the buisness process expert. This is a MM question
Message was edited by: Marilyn Pratt

Dear Amit,
Requirement: If GR posting date exceeded 45 days than delivery date set in PO, then delivery date in PO has to be changed to current system date and at the same time New Release Strategy (B1) has to be triggered with one release code (02) automatically.
So in that case the values in Release Strategy (A1) and (B1) would remain same,,, as you suggested we will assign the value 01 u2013 USRC1 to Rel Strategy (A1) and 02 u2013 USRC1 to Rel Strategy (B1) and the same we will try to incorporate in the coding of Exit u2018'M06E0004'
We will check the process and confirm the same.
Thanks for your suggestion.
regards,
Urendra Kumar

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

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.

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.

Are these requisition release strategies common?

All,
I’m designing new requisition release strategies for indirect requisitions at a chemical industry client. I’d like to know how often you have seen the following sorts of design before:
Existing design: Item-based release with workflow, with three dollar levels. At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic). Characteristics assign several cost centers to each approver. Strategies and codes are named for users, so we change configuration whenever someone changes jobs. The codes are linked to positions, which are attached to user IDs. Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic. A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase. I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
Thanks for your help!

Hi,
No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
For more refer a discussion:
PR release: place holder for Cost center and Material grp
NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
You can also go for other concept designing of your Requisition release strategies
Regards,
Biju K

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.

Tables for Release strategies

Hi ...
I was referring to MM table doc , in that it is mentioned table EBELN & EBELP are for Purchase Order header / Line and BANFN & BNFPO are for PR header/ Line.
But for release strategy ...people told me to refer CEKKO for PO and CEBAN for PR.
does it mean that release strategy refers to different tables for execution ( and I believe these tables are used for release strategy purpose only and if Yes then at what point PO / PR data gets updated in these tables)
Regards
Suresh

Hi,
Please find release tables used in MM.
EKAB       Release Documentation
EKEH        Scheduling Agreement Release Documentation
EKEK        Header Data for Scheduling Agreement Releases
T161E       Release Codes
T161F       Release Point Assignment for Purchase Requisition
T161G       Release Prerequisite, Purchase Requisition
T161H       Fields for Release Procedure, Purchase Requisitio
T161I        Determination of Release Strategy
T161S       Release Indicator, Purchase Requisition
T161U      Texts for Release Indicator
T163P        Release Creation Profile
T163S        Description for Release Creation Profile
T16FB        Release Indicators: Purchasing Document
T16FC        Release Codes
T16FD        Description of Release Codes
T16FE        Descriptions of Release Indicators: Purchasing Do
T16FG        Release Groups
T16FH        Descriptions of Release Groups
T16FK        Release Statuses
T16FS        Release Strategies
I think, it will help u.
Ishu

Stop Re-triggering of PR release strategies for closed PR's.

Hi,
Scenario is like, PR raised and converted it into PO and material has been received.
After Receipt of material, system is allowing to change the quantities by un-releasing the release strategies.
Once material receipt is completed, system should not allow to change in / revoke the release strategies.
Please suggest.
Thanks in advance.
njs

hi
plz check ur release indicator in spro >mm>pur>pr>rel>
here select the rel indicator and check the changability option in bottom it has to be 6
hope it help
regards
kunal

Active release strategies

Dear SAP GURUS,
   Is there a transaction code where i can have a look at all the active release strategies.
Thanx,
Fayazuddin Syed.

Dear Syed fayazuddin ,
You can figure it out at CL24N or CL20N.
Example :
Transaction CL24N
Class        => Fill in class name
Class Type :     032
If it was active, then you will see
status field = 1     Released and with the "Green Tick" icon.
or else:
2     Locked
3     Incomplete
Sometimes, if you are having inconsistency/corrupted for your release strategy, you will also see some
message indicate that you had inconsistency in these transaction
Thanks
Loke Foong

Restrcuturing of PR and PO release strategies - corporate policies

Hello,
I´m in a proyect where a multinational company wants to restructure its PR and PO release strategies.
We are in the fase of defining corporate policies as guidelines for the new structure.
The multinational Holding contains Productive companies, distribution companies and other type of companies like investigation companies.
I would like to have some feedback about how to guide the company management in this process off defining corporate policies.
How does one or can one estandardize the release levels, release codes and amounts which separate the levels, in a diverse multinational.
Are there any paradigmas, methods to acomplish this.?
If anyone has experience with these kind of processes, please give me some feedback on how they tackled these issues.
Thanks,
Aart

Hi,
Normally when a company is coming into the sap , which have many business at various locations / countries , a structure will be defined in the SAP for the company as company code under which the plant and below the structure will be defined .
However when comes to purchasing and for PRs POs , SAP give a communication strusture called CBAN for PRs and CEKKO for POs which can be viewed at SE16 . Thease tables contains the fields upon which the release strategies can be made .
For example , say for one of your productive company , the company code created is XXXX and the plant under which is YYYY say , the policy can be for a groups of buyers which comes under the plant for a PO level , who can be the approver . Here for differrant PO/PR values differrant approvers can be added as strategies and based upon which the approval can be happened . and the approvers be the release codes .
There are no standard paradisms rather , prior come into purchasing the organization structure be made.
After that based upon the business/product , with in that company code defined , the levels can be defined in that perticular business .for purchases .
In purchasing , to fhe plant / purchase group / storage location etc plays important and normally for a set of buyers/p grps , in that plant or group of plants in that company code , the levels of the PO/PR values can be defined for differrant strategies .
Once at corporate level , the company code / plant is defined and under that the release strategy is easy to define .
Regards,

RCCLBI01 and Purchase Requisition Release Strategies

I'm trying to use RCCLBI01 to load Release Strategies. I've found a few threads on it but they don't tell you what you can and can't do with it. I know I can load the characteristic values for an already existing Release Strategy, but I have hundreds of Release Strategies that I need to create.
Will this load the strategies as well, or do I really have to go create them by hand in SPRO first then run it? Or is there another program that will load strategies and the codes and the characteristics?

Kris,
RCCLDI01 is now used. However Here's my view:
1. You will have to create chracteristics to begin with. I hope the number is not huge as it will narrow down the functionality otherwise.
2. The class-- How many would you create?? I don't believe you would need a Batch input program to create a class as I believe there could not be more than a handful, unless necessary
3.Now the classification.. the buggest task of all, where you could run in to hundreds.. Maintaining them is a nightmare and you'd have to have your strategies first.. I do not know of any input program to create Release strategies. So my answer is "a manual task"
4. RCCLBI02 is of no help here for release strategies.
5. I would rather use TCODE: CLMM to do the mass changes.. it makes life a lot easier.
6. The last option is for some one technical to help you create a script to load the data.

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.

Regarding the Release Strategies not getting picked up for PR

Hi Gurus,
1 ) I have configured a new Release strategy with Plant,Total Value,AAC and Doc.type as the Characteristics.I have assigned that to a release class and assigned values to the characteristics.
I have configured 6 release codes and 6 different Value Intervals for 6 release strategies and assigned it accordingly. But whenever i am trying to release the PR, it is picking the first strategy only. its not picking the other strategies even it is of differnet values. Please advice what needs to be done on this.
with Regards,
Saakithyan

1st of all check whether you defined release strategy for Item level or header level.
If you defined item level check the individual item has all the 6 characteristics you defined.If any characteristic is missing then it will not pick. Provided you defined all the characteristics for classification view or CL20N.
Thanks & Regards
Sudhansu

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

PO release strategies

Similar Messages

Maybe you are looking for