Rel strategy for PR

I want to create Release Strategy for PR as follows:
For Standard PR (NB) one level of release is always required.
(eg HOD will have to release all the PRs of a department)
How shall I proceed pleae guide in detail.
regards
VS

Hi,
Release Process for PR is as below
1 Create the Characteristics for your release strategy based on fields of table CEBAN.
2 Create a class of class type 032. You have a free choice of names for the new class
3. Assign your characteristics to the class on the tab page Characteristics.
4. Create Release Groups
5. Create Release Code -HOD in your case
6. Create Release indicator -all type of PR or selective
7. Define Release prerequisites
Hope you will explore after this overview on RS.
Regards,
Ashish

Similar Messages

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

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

What is your strategy for form validation when using MVC pattern?

This is more of a general discussion topic and will not necessarily have a correct answer. I'm using some of the Flex validator components in order to do form validation, but it seems I'm always coming back to the same issue, which is that in the world of Flex, validation needs to be put in the view components since in order to show error messages you need to set the source property of the validator to an instance of a view component. This again in my case seems to lead to me duplicating the code for setting up my Validators into several views. But, in terms of the MVC pattern, I always thought that data validation should happen in the model, since whether or not a piece of data is valid might be depending on business rules, which again should be stored in the model. Also, this way you'd only need to write the validation rules once for all fields that contain the same type of information in your application.
So my question is, what strategies do you use when validating data and using an MVC framework? Do you create all the validators in the views and just duplicate the validator if the exact same rules are needed in some other view, or do you store the validators in the model and somehow reference them from the views, changing the source properties as needed? Or do you use some completely different strategy for validating forms and showing error messages to the user?

Thanks for your answer, JoshBeall. Just to clarify, you would basically create a subclass of e.g. TextInput and add the validation rules to that? Then you'd use your subclass when you need a textinput with validation?
Anyway, I ended up building sort of my own validation framework. Because the other issue I had with the standard validation was that it relies on inheritance instead of composition. Say I needed a TextInput to both check that it doesn't contain an empty string or just space characters, is between 4 and 100 characters long, and follows a certain pattern (e.g. allows only alphanumerical characters). With the Flex built in validators I would have to create a subclass or my own validator in order to meet all the requirements and if at some point I need another configuration (say just a length and pattern restriction) I would have to create another subclass which duplicates most of the rules, or I would have to build a lot of flags and conditional statements into that one subclass. With the framework I created I can just string together different rules using composition, and the filter classes themselves can be kept very simple since they only need to handle a single condition (check the string length for instance). E.g. below is the rule for my username:
library["user_name"] = new EmptyStringFilter( new StringLengthFilter(4,255, new RegExpFilter(/^[a-z0-9\-@\._]+$/i) ) );
<code>library</code> is a Dictionary that contains all my validation rules, and which resides in the model in a ValidationManager class. The framework calls a method <code>validate</code> on the stored filter references which goes through all the filters, the first filter to fail returns an error message and the validation fails:
(library["user_name"] as IValidationFilter).validate("testuser");
I only need to setup the rule once for each property I want to validate, regardless where in the app the validation needs to happen. The biggest plus of course that I can be sure the same rules are applied every time I need to validate e.g. a username.
The second part of the framework basically relies on Chris Callendar's great ErrorTipManager class and a custom subclass of spark.components.Panel (in my case it seemed like the reasonable place to put the code needed, although perhaps extending Form would be even better). ErrorTipManager allows you to force open a error tooltip on a target component easily. The subclass I've created basically allows me to just extend the class whenever I need a form and pass in an array of inputs that I want to validate in the creationComplete handler:
validatableInputs = [{source:productName, validateAs:"product_name"},
                     {source:unitWeight, validateAs:"unit_weight", dataField:"value"},
               {source:unitsPerBox, validateAs:"units_per_box", dataField:"value"},
                    {source:producer, validateAs:"producer"}];
The final step is to add a focusOut handler on the inputs that I want to validate if I want the validation to happen right away. The handler just calls a validateForm method, which in turn iterates through each of the inputs in the validatableInputs array, passing a reference of the input to a suitable validation rule in the model (a reference to the model has been injected into the view for this).
Having written this down I could probably improve the View side of things a bit, remove the dependency on the Panel component and make the API easier (have the framework wire up more of the boilerplate like adding listeners etc). But for now the code does what it needs to.

PO Release Strategy for 3 company codes

Hi
I am working on PO release procedure for 3 company codes in a client.I have created a one charecteristics called Order Type & assigned to class -POVALUE_NEW .I am using the same charecteristics & class in 3 company codes. I have created a different Rel Group & release Codes & assign as shown below
Group                       Class
AA     2     POVALUE_NEW
AB     2     POVALUE_NEW
F1     2     POVALUE_NEW
F2     2     POVALUE_NEW
V1     2     POVALUE_NEW
V2     2     POVALUE_NEW
Group     Rel Code
AA     L1
AA     L2
AB     L1
AB     L2
F1     F1
F2     F2
V1     A1
V1     A2
V2     A1
V2     A2
Created a Rel strategy as below
Group       Strategy
AA     P1------Vendor PO
AB     P2-------STO PO
F1     F1------Vendor PO
F2     F2-------STO PO
V1     V1------Vendor PO
V2     V2-------STO PO
I have maintained all the Doc type in value coloum of the cherecteristics .For vendor PO combination of Group & strategy , I have selected the respective Doc types in clasification .*When I raise the PO I am not getting the Release Strategy Tab in PO header* & when I remove the value in clasification any strategy , I will get the Rel Strategy Tab but this will appear in all company code POs .I want to give different lease codes for each company codes I am unable to find a solution to this issue . I am looking for a valuable suggesion from you all .
Thanks
Venkat

Hi,
1.in addition to existing Characteristic, create one more characteristic for Co. Code. Table CEKKO Field: BUKRS
2. Assign this new char. to your PO Release Class
3. Define your Release Codes for each Co. Code.
4. Define Strategies with characteristic values Co. code and Doc. Type.with co. code relevantRelease codes.
Ex: Co. Code1   Rel Grp-1 G1; Codes: A1, A2, A3
      Co. Code2   Rel Grp-2 G2; Codes: B1, B2, B3
      Co. Code3   Rel Grp-3 G3; Codes: C1, C2, C3
Strategy-1:
              G1   S1     A1 A2 A3;   values: CCd-1, Doc. type1
Strategy-2:
              G1   S2     A1 A2    ;   values: CCd-1, Doc. type2
Strategy-3:
              G1   S3     B1 B2 B3;   values: CCd-2, Doc. type1/Doc Type2
Strategy-4:
              G1   S4     B1 B2 ;   values: CCd-2, Doc. type2/Doc Type3
Like this you can make as many strategies to meet your requirement.

Work flow for release strategy for PO & PR

Hi Gurus
Can anybody explain workflow for release strategy for PO and PR
Thanks in advance.
Atul Kulkarni

Hi,
First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
For Work flow settings,You have to do follwoing configuration:
MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
Creation of work flow object,activation of workflow and other related settings will be done by Techinical work flow consulant.
Thanks,
AMIT

PR Release Strategy for Assets

Dears,
We have PR Rel Strategy with characteristics Cost Center and total value, it is working fine. But now the requirement is that PR for Assets to be included. For this we have included characteristic 'A/C assignment category", but it is not working. We have maintained in cl20n. How to activate the release for 'Assets'?
Thanks,

Hi,
Steps - if already done then please recheck it
1. Maintain values for new characteristic - Account assignment
2. Assign new characteristic - A/C assignment to CLASS.
3.In CL24N check the status of all release strategies - Green check - symbol should appear against each strategy.If its green then release strategy tab gets triggered if all pre requisites are satisfied.
Regards,
Uzair

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

Create Release strategy for PR

Dear experts,
We have one class FRG_EBAN for PR release strategy and there are 5 characteristics in that class. Now i need to create a rel. strategy with 4 characteristics . Can i create a new class for PR release strategy?
Please help.
Thank you
King regards,
Zusen

Thank you SAM for your reply.
In the existing class FRG_EBAN one of characteristics is Account Assignment Category. If i am not wrong which cannt be blank. and i have seen that all characteristics included in the class needs to be maintained in the release strategy.
I need to create a release strategy of PR in which no a/c assignment category will be maintained. but in existing scenario i cannt create release strategy without giving value in a/c assignment category characteristic in the characteristic tab of release strategy.
Please suggest how to resolve this problem
Kind regards,
Zusen

Po rel. strategy

Hi,
In p.o rel. strategy we have the three stage release status. First A( say) will rel. then B then C. we have released lot of p.o in the same manner. Now we want to change the rel.status to two step. That means A will release then B will rel.the document as the final rel. authority. But in the previous P.O created which was subject to three stage rel. status has been already reduced to two stage. Where is the setting so that it will not effect the old p.o rel. strategy procedure.

Hi,
For this you have to create two release strategies as given below:
1. For old PO's
Add a new characterstic (Say DOCUMENT_DATE) to the old 3 level release strategy having value as before today's date (i.e. <13.06.2011 ).
2. For new PO's
Add a new characterstic (Say DOCUMENT_DATE) to the new 2 level release strategy having value as on & after today's date (i.e. >= 13.06.2011). Rest all the characteristics will be same as the old 3 level release rstrategy.
The characterstic DOCUMENT_DATE will have Table name as CEKKO & Field name as BEDAT (i.e. PO creation date).
So, For Example if you will go for making any changes to PO created before today's date will pick the same old 3 level strategy however for creation or changes to PO's having creation date today onwards will pick the new 2 level release strategy.

Rel.strategy

Dear cons
We have created one user I.D (procurement) for creation of purchase requisition. One person is only able to approve the document. We have created another I.D for finance deptt. For thr Pur. Doc.we want both person can approve the document. i.e- first fi ance deptt. Will approve then procurement deptt. Will approve. Because at the time of creation P.R the purchase deptt. Enters a wrong G/L account. To avoid this first it will come to finance deptt. So how can you make settings in the release strategy. If I create two release code & enter in the rel. strategy of procurement I.d Then How it will come to finance i.d. pl.look into the matter. Without workflow it is possible or not.. Basis people has restricted the user i.d.pl. give some hints.

Hi Nirupama,
Create the 2 release codes for that Release strategy.First release code should be for Finance dept 2nd should be pur dept user.
Give the authorization to 2 user ids with release codes one for Finance dept and another for Pur dept with the help of Basis Consultant.
Once the Pur dept user creates the Pur requisition.In the PR release tab the 2 release codes will appear . Then the first release code should be Finance dept user. Then final release can be Pur dept user.
So that before releasing the PR the finance dept user will correct the G/L account and then release the PR. Then the Pur dept user will finally release the PR for procurement.
Hope you understand
rgds
Chidanand

PR Rel Strategy scenario

Hello
I have 2 requirements in PR Rel Strategy scenario.
1.No changes should be allowed in the PR once the PO is created.Can we fulfill this requirement by assigning changeability Indicator 1.
2.Once the PR is released and PO created it should not allow to revoke the release.
Any ideas on this?
Regards
Vaibhav Mahajan

Hello Afshad and Swaminathan
Users are revoking the release after the PO is created.With changeability indicator no changes are possible via ME52N but revoke is possible in ME54N.
Bases on the links given by Afshad I am checking if we can use the User Exit but not sure which user exit will work.
Regards
Thanks for the suggestions.

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Release strategy for quantity contract

Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbu

Hi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

Rel strategy for PR

Similar Messages

Maybe you are looking for