Release startegy for PO

Suppose i want to define release strategy for my POS on the basis of PO value...
Can i get in detail....what characterstick?
We have only one characterstic ZPO_EKGRP.
How to define new characterstic for value release.?
Regards,
Satyendra

thru ct04 create a new characteristic for ur PO value.use:
Data Type                       CURR
Number of Chars              15
Decimal Places                2
Currency                          INR
Template                        _____________.__
tick Multiple values and Inverval valuesallowed.
table CEKKO,field GNETW
give the values in the value tab
save it and assign it with ur class.
regards,
indranil

Similar Messages

Release startegy for service PO

Hi,
Can you people help me out with release startegy for Service PO and service entry sheet?
Regards,
Satyendra

Hi,
Please refer below mention format.
SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
Three steps involved in release process of purchase order.
1) Edit Characteristic: -
Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
2) Edit Class: -
After creation of characteristic, create class for release purchase order. In which you can take reference of
Class Type: - 032,
Status: - Release,
Class group: - Release strategy class,
And put reference of your characteristic, which are created by you in first step.
E.g: - Class u2013 REL_PO
3)Define Release Procedure of purchase order: -
In this step four processes involved.
1) Release Groups
2) Release Codes
3) Release indicator
4) Release Strategies
1) Release Group: - In which you can define release strategy group
For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
2) Release code: - In which you can define release code. Enter value as
Release group: - 01,release code: -01 u2013 Purchase Head,
Release group: -01, release code: - 02 u2013 Auditor.
3) Release indicator: - In this step you have to define release indicator.
Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
4) Release Strategy: - This is the final step for release strategy.
Assign release code 01, 02.
Click on release prerequisites, select 02 u2013 check box and click on continue.
Click on release status button, enter release indicator X, I, S and click continue
Click on classification button, Enter values of purchasing group for which you want to created release strategy.
Note: - Create characteristics for service order document type in CT04.
Regards,
Mahesh Wagh

Release Startegy for Item Category

Hi ,
Can we have a release startegy for PO for Charcetrstic Item category.
It do not have any reference in in Table CEKKO for any field.
Can you tell me how can I activate the item category as a charcetrstic value in PO release startegy.
Thanks,
Lekhram

PO release strategy always work at the header level but if oyu want to add the item level field as a char (in your case Item category) than you need use the user exit to insert the field in CEKKOZZ include of the CEKKO structure.
Use the user exit M06E0004 to insert your field in CEKKOZZ include.
once you get the field in this include then create the Char and use in classification.
But make sure one thing is that
Suppose you create the first line item of PO with Item category D and than you insert the second line with item category L and your release stratey doesn't have the both the item category than you are in problem
Or suppose your first line has blank item category and second one has item category than also you will have issue.
so make sure you create the PO for same item category without any othe combination to work with release.

Purchase order release startegy

Dear Experts,
We have got release startegy for five release codes i.e L1,L2,L3,L4 and L5 for purchase orders
Release startegy is based on Pur order category,doctype, Net order value and Pur group.
For L1-L5 authorisation(all authorisations) is given for General managers.
Currently when emergency is there general Manager has to release L1 to L5 all release codes.
Requirement is that instead of releasing all can it be possible to release only L5 so that all can be released.( This authorisation is for only for L5)
Once the authorisation is there for all any customisation possible for releasing code L5 so that remaining all release codes can be released.
Please suggest.
Regards,
Dayanand

Hi Mr.Shawn,
I have removed ticks for L1,L2,L3,L4 in Release prerequisites then release startegy L1 L2 L3 L4 kept as Released.
Then Even if release one all releasing.
But Requirement is that when only L5 is released only All shall be removed, other wise remaining Releases shall be based on the old procedure only. L1 to L4 shall be L1 is released then only L2 can be released principle. But in case of L5 releases all shall be released.
Is it possible, what needs to be done ,please suggest.
Regards,
Dayanand

Release strategy for PR

Hi All,
I ahve configured a release startegy for PR with 3 characteristics for Plant,Purchasing Org and Purchasing Grp.These i have assigned to a class and created a release code. But now when I create a PR with these 3 characteristics with values as maintained in classification the PR is not getting blocked.
Am I missing something?
Regards,
V S

Hi ,
Check your release indicators .
IMG > Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification->Set Up Procedure with Classification>Release indicator
goto to details of the release indicator --- theke you uncheck the check box for which you need the PR to be blocked .
Regards,
Anupam

PR Release Strategy for DOCUMENT TYPE

Hi Gurus,
I have created a Document Type in PR & I want to set a Release Startegy for ONLY that Document Type.
Can anybody explain me step by setp procedure for this ?, I have gone thru one link :
http://www.sap123.com/showthread.php?t=59
but I could not set the relase startegy. May be I am missing something ??
Thanks & Regards,
Vikas

If you want to define the release strategy only for doc type
then
create the class using CL02
create the chra for Doc type using CT04 - the table is CEBAN and the field is BSART
then assign the doc type value in char (after you create the char then go back and assign the value)
now assign your char to your class
now go to SPRO and goto PR release strategy config - procedure with classification
go to Set Up Procedure with Classification
create your release group by assigning the calss you have created (make sure this config should have only one class)
create release code
release indicator is already exist in sap so you don;t need to create
create your release strategy and assign the value in classification tab of release strategy
this will work
but make sure that - if you are creating only for doc type means all the reqs created for this doc type will be blocked by the system. so if you have reqs like if this doc type and the amount >5000 then only block then you have to have amount is also you char in your class
hope this will give you a cleat idea

PR Release startegy

PR release startegy should be flexible so that if we add any of the parameters, the program should follow the rules. The parameters that can be changed are:
1. Document Types
2. Project Types (We will need a custom table)
3. Plants Groups
4. Threshold Amounts
The routing of the Purchase requisition approval is primarily based on the amount on the requisition, the Plant, and the department the requisitioner belongs to.
In standard sap we have static parameters for release staregy, but here requiremnet is dynamic, when ever you chnage any of the parameters the syatem should adapt those chnages and the existing rules must apply for new one.

Why would you change Doc. Type?
If your requirements are not firmed than you should not raise requisition.
No matter how dynamic your business is, requisition raised for a particular requirement should not vanish or change in a day or so.
Practically speaking, it seems your supply chain is not process driven.
For such scenarios you should allow to create POs directly once the requirements are firmed and aprovals covered for POs only.
Regards,
Dakshesh

Release Strategy for PO and RFQ

Hello
iI have configured following Release Stategy for PO.
0-1500 INR-Officer
1500-50000-Manager
>50000-General Manager.
The same release startegy has got coped fr RFQ also which is fine.However after I for release in ME45 it is selecting Release Strtagey 0-1500 only.
Even though I raise RFQ for more quantity I get the same Release Strategy applied.
I am not sure why this is happening,can anybody explain the reason for the same.
Regards

Dear All
Thanks,issue got resolved.

Release strategy for RFQ

Hi,
Please let me know,how to set release strategy for rfq.. i'VE ACTIVATED MY RELEASE STRATEGY FOR po USING TABLE cekko... iF I WANT TO ACTIVATE RELEASE STRATEGY FOR rfq... WHICH TABLE AND FIELD NAME I WANT TO USE... PLS EXPLAIN..

For RFQ also we can use the same communication structure CEKKO, but for differentiation between release startegy of Contrcats Purchase orders & RFQ's better to use the Charcteristic Document category i.e CEKKO - BSTYP - Purchasing Document Category

Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO

Hi All,
I have the following requirement/scenario
1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
This is what I hoped for would work after doing the necessary config,
For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
The problem
Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan. I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
Is their any other identifier I can use to address the requirement above? Let me know.
Thanks
Ashvin

Thanks Charlie for your response.
The conditions in the PO is not equal.
On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
Let me know your thoughts.
Thanks for your feedback.

Release Strategy for a new material type in PR

Dear Friends,
One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
Regards,
Ask

Hi,
Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
Then follow all the cusmozation path for your PR release startegy .
For Config part refer the below wiki link it may help you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808

Reg Release startegy, Class n characeristics

Hi
This is regarding PO release strartegy
I setup Release strategy for PO's in Development system, for each release startegy allowed characteristic values are mentioned during config as expected
I released transport to quality [we have 2 systems
1. In One quality system i forgot to maintain classes, i maintained class, but still i am getting error 'Error in classification (class 032 class type 032)'
2. in another quality system class and characteristics are maintained before releasing transport. when i see SPRO, system hasnt assigned allowed characteristics values for each release startegy? why?
Do i need to perform any thing else other than creating characteristics and classes?
What task should i b doing in target system
Thanks in advance

Thank you
i understood exept 'donot open the client in quality and assign the values' what does this mean ?
I am doing CL20N in quality only ?
i understood in Qulity[target sytem]i must perform below
--> create characteristics
--> create class and assign characteristics
--->CL20N assign allowed characteristic values for each release startegy

Difrence between work flow n release startegy

hii frnds
can anybody tell me wats the difrence between work flow n release startegy ..
thnks
rohit

Workflow could be generic and can be configured for any process you want.
When you want to control the releases of the documents depending on the parameters that you want to configure, you use the release strategies. While configuring release strategies, you can develop some workflows.
Release strategies is more of a functional concept and workflow is the technical implementation.
Regards,
Ravi

Release Startegy

Hi,
We have configured PO release strategy by taking characters as Plant, Document Type, Value & Material Group.
To be clear release is working fine when we consider a single material in line item of PO.
We have 60 material groups and the release startegy is common for the material groups from 1 to 50 and the remaining 10 material groups 51 to 60 have different release strategy.
If I create a PO with the material group from 1 - 50 i.e. two or theree materials which belong different material groups the release is not applied for that PO.
For the same materials if I create PO for individual material i.e. only single material group the release is applied.
The release for PO isconfigured at header level. but the material groups are at item level.
Thanks & Regards
Sachin

Hi Sachin,
PO release strategy is only in header level not item level. So u should not consider Plant & Material Group as both the fields are in Item level.
Our release strategy willl work if the palnt & material groups are same for all the line items.
If there are multiple combination of plant & material group then release strategy won't affect.
Reward points if its helpful to you.
Sangram

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 startegy for PO

Similar Messages

Maybe you are looking for