Can a release strategy be based on a formula?

Hi,
A retail client i'm working on wants the release strategy PO to be based on a formula, i.e. the release strategy should have OTB check.
Is this possible?
Thanks in advance for your help

Hi,
Thanks, I didn't know what OTB means.
I do not know how this OTB is maintained in the system (is it development?) but I assume it should be stored in a data table (data tables). If it is so, I think you should be able to extract it (this data) via the ABAP code in the mentioned user exit - but this is just my opinion, it's better you ask your ABAPer to check it in a sandbox system.
Regards,
Csaba
Edited by: Csaba Szommer on Jun 23, 2010 9:23 PM

Similar Messages

PO release strategy workflow based on plant

Hi Gurus,
I am setting up PO release strategy workflow. We have purchasing at plant level. Fg. plant 1234's PO should be sent to the plant 1234's purchasing dept. Plant 5678's PO should be sent to the plant 5678's purchasing dept. In PR release strategy workflow config. screen, there is a plant field. However, plant field is not showing in the PO release strategy workflow screen. they are both in the table T16FW, and plant field is define in the table. Pls help and explain how we can get plant field in the PO release strategy workflow config. Or if this is what SAP design, then is there any other way to accomplish what we want? Thanks a lot!

We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Hi,
You can try doing it with a WorkFlow as you identified communication structures differ.
Regards
Shiva

PO Release Strategy trigger based on PR value

Hello All,
We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Pls advise.
Rgds,
AC

We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Hi,
You can try doing it with a WorkFlow as you identified communication structures differ.
Regards
Shiva

PO release strategy based on Material Group (CEKKO - MAKTL)

Hi Experts,
I have configure the Rel strategy based CEKKO-MATKL (material group) for purchase order, but when i raise the PO Rel strategy is not affecting, Can any body tell me why.
Regards,
Kumar

You can set Release strategy based on Material group & other Line item specific fields..
You better follow a suitable and hinder less process..
For PR use Material group & Account Assignment based Release process..
then for PO use a Release Process based on Header level fields like Doc type, Amount, pur Group etc..
So that the approved PR line can be converted into PR and then the PO also subjected to Release before sending it to External Vendor..
Even if you want you can make that the PO can not be created without referencing PR for SOme users or All users..
based on your business requirement..

Release Strategy based on Attached PO scanned Image

Hi experts,
Can u please let me know if i can configure Release Strategy for PO based on the attachement. If possible i would insist on configuring the same using characteristics instead of Customization.
When I have tried to do so I beleive there are two custom feilds allowed for Characteristics configuration but unfortunately both the custom classification parameters are already utilized. namely USRC1, USRC2.
Please suggest.
Thanks

Hi Singh,
Your requirement is not possible in standard settings.
But how do you plan to configure release strategy on what is attached in PO? Do you use DMS for this purpose or use GOS?
Regards

PO Release Strategy on Value Based

Dear All My Friends,
i want to define the following Release Strategy, please advice how it will be done
Person A will Release PO value <=50,000/-
Person B will Release PO Value >50000 and <=100000
Person C will Release PO Value >100000
please help me
Thanks and Regards,
Rajesh G

Hi,
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 total value. So you can create characteristic for Total net value. Take reference of CEKKO structure and GNETW field for Total net value in additional data of characteristic. E.g :- Total net value u2013 GNETWu2026Click on intervals allowed check box ..
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 Total net value for which you want to created release strategy.
Person A will Release PO value <=50,000/-
Person B will Release PO Value >50000 and <=100000
Person C will Release PO Value >100000
Utsav

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

Release strategy for PO and Service Entry Sheet

Hi
I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
should I maintain the same characteristics for service entry sheet ?
the approval will be the same for both

Hi,
The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
Note: The release strategy must be based on the structure CESSR.
The PO release strategy is based on the structure CEKKO.
For the SEs release strategy you must create a different class.
Regards,
Edit

Release Strategy @ Company Code Level

Hi Guys:
We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
with Characteristics as Company Code ,PO Document Type and PO Value?
Thanks
Sweth

Hi
For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
The characteristics for release strategy for external purchasing documents are
Plant                - WERKS
Pur.group        - EKGRP
Pur.org            -EKORG
Acc.assignment category-KNTTP
Document value-GNETW
Document type-BSART
The table is CEKKO
Thanks

Release Purchase Requisition - "Release strategy"

Hi there,
I am trying to release a purchase requisition. I looked in the table "EBAN" and i can see the entry or in other words, the requisition i created. In the Release indicator, Release status and Release strategy fields, these are empty. How do i add information to these fields which appear to have missing data?
Speedy repsponse would be very much appreciated.
Thanks
Motolani Fatuga

Hi Motolani
spro>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release strategy
Select release strategy> Go to details>classification
here check what are the charactaristic and what are the values maintained for it
Check this for all release strategy
Mostly PR release strategy is based on Document type and PR Value
Check whether UR PR fits in release strategy criteria
Suppose Total value of requisition is maintained as 1000-2000
If UR PR value is less than 1000 Then PR will not subject to release
Vishal...

Verison Management with PO release strategy - CEKKO-REVNO

Hello,
I'm a bit stuck... I'm trying to do a PO release strategy using version management, were the PO goes through a release strategy if the PO gets changed (not the intial PO creation).. So once the field RENVO is greater then 0, it should go through R.S.
I've read to create a characterstic CEKKO-REVNO and then assign it as a valuet <0... I intital;y created it with a NUM Data type, but the ABAP dictonary overides it with a CHAR instead... So I read to mark the value as a default value (<0)
However, after I add it to my class, I go to the define release strategy - classifcation section (to add the value <0) I'm getting a value inconsistency check.
How do i setup this characterstic so I can use it in release strategy?

Based on adding 00000000 the release strategy will work when its version 0 (intial). However, I'm trying to have it so it goes through a release strategy when the version is 1 or greater...
It seems like I cant get the strategy to work for more then one version... I can get it to work for version 0 but no others, or version 1 and no others etc...
I need to have it some it works for anything greater then zero, in which i tried <0000000 and even >000000
I also tried adding 000001, 000002, 0000003, 0000004 etc.. An although the release strategy tab is still applying, it will NOT result to a blocked status...
I cant get this to work... How should the characterstic value look to get this requirement?
Edited by: farmerj3 on Feb 20, 2012 3:16 PM
Edited by: farmerj3 on Feb 20, 2012 3:43 PM

Error while creating new release groups in PO release strategy

Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
Illan

Dear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**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**
**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 - REL_PO**
*Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh

Transportation of release strategy

Hi guys,
We heard that in ECC 6.0, we can transport release strategy for PRs and POs along with characteristics and classes. I have the following doubts on this
1) Can we transport the values assigned in the strategies also with this functionality ?
2) From MM side can we configure the strategies in the normal way i.e. creating characteristics, creating classes, creating release groups, creating release indicators, configuring release strategies (or) we need to follow any other procedure for transporting the strategies
Any suggestions on this

Hi
I dont think this functionality exits of transporting the charcterisitcs & classes.
In ECC 6.0 also this functionality does not exist as per my knowledge.
Jurgen Thank you for the SAP note
Thanks & Regards
Kishore

Release Strategy in PO for direct materials not driven by MRP

We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
Request you to let me know how I can make this work.
I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
Thanks and Regards
Murali

Hi Murali,
Standard SAP provides PO release strategy at header level only and not at item level.
So you can create a new PO document type and allow use of only this document type for manual PO creation.
Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
Hope this will fulfill your requirements.
-Ravi

Issue with Purchase Requisition Release strategy

Hi Gurus,
We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group
3.     Value of the PR
As a result of PM module implementation, there is requirement of additional 30 release strategies.
We configured them but one more field of doc type was added in the characteristics fields.
Now the release strategy was based upon following fields:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group-(Configured against new purchasing groups )
3.     Value of the PR
4.     Document type of purchase requisitions.
Classification data was accordingly maintained that is for older release strategies,
Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
We are in testing phase. Many of the test scripts failed due to this issue.
Quick response will be appreciated!!!
Thanks & Regards,
Niti

Dear Niti,
Please check if your "overall release" indicator is consistent for document type and release group:
a)SPRO:MM-PUR-PR-Define Document Type
"overall release" indicator
b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
->Release group
"overall release" indicator
Regards,
ian,Wong Loke Foong

Can a release strategy be based on a formula?

Similar Messages

Maybe you are looking for