Error : create release strategy

define release procedure for po-> release strategies->classification->purchase organization i gave value 7,it changes to red colour error is inconsitent.
any one answer for this error .

hi,
check whethar you have 7 as purchase organisation or not.
Go to table T024E and check EKORG is 4 chacater field
it might be 0007 .
also in ct04, for chacaterstics for pur org, go to additional data
CEKKO - EKORG is manained for not.
regards,
pardeep malik

Similar Messages

Create Release Strategy in T-code f-48 and Va01

Dear Friends , I want to create release strategy on vendor down payment because my client wants that every down payment to vendor must be approved by senior management .Can f-48 entries be hold or parked .
Also My client wants that every sale order must be approved in sap before release .
Kindly provide solution .
Rajan

Hi
You need to implement Workflow which is out of functional consultants premises.
Thanks
Srinivas

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

Error in Release strategy : Inconsistent Characteristic Value assignment

Hello Gurus ,
Good Day ...
Need your help in release strategy in purchase order .
Thanks in advance .......
Characteristics characteristics value
R2R_PURCH_ORD_TYPE NB
R2R_PURCH_GRP1 001
R2R_PURCH_ORD_VALUE 0,00 - 1000,00 USD
1001,00 - 2000,00 USD
2001,00 - 10000,00 USD
Class assigned char
Z_CLASS R2R_PURCH_ORD_TYPE
R2R_PURCH_GRP1
R2R_PURCH_ORD_VALUE
Rel grp assigned class
PH Z_CLASS
rel grp rel codes
PH 1 -director/VP
PH 2 - manager
PH 3 - buyer
rel grp rel strategy
PH A1
PH A2
PH A3
Now in SPRO -
> define Release Procedures for Purchase ORder -
> Release Strategies
PH A1 Release Strategy 1 (rel. prereq , rel statuses, classification , rel simulation ) working fine
PH A2 Release Strategy 2 (rel. prereq , rel statuses, classification , rel simulation )
ERROR MSG: INCONSISTENT CHARACTERISTIC VALUE ASSIGNMENT
DETAILS :
You want to change the value assigned to a characteristic. However, the change causes inconsistency, so the new value is not allowed.
The inconsistency may be for the following reasons:
A precondition or selection condition is violated.
The characteristic is a single-value characteristic, and different values have been set by constraints, actions, or procedures.
In classification, inconsistencies occur when you change the value set of a characteristic if objects or classes have already been classified with values from the previous value set.
Procedure
Choose Inconsistencies to see what triggered the inconsistency. You can also use the explanation facility for more information.
Delete the values that triggered the inconsistency.
You can only change or delete a value or value set that has already been used to classify objects if you delete the existing allocations.
PH A3 Release Strategy 3 -
> SAME AS ABOVE
regards,
ajay

Hi,
Inconsistency due to different "VALUE" in the Release Strategy & "VALUE" present in the Release Characteristics . Check details with value assignment with designed Strategies.
Also keep following VALUE Release Characteristics for value
<=1000,00.00 USD
1000,00.01 USD- 2000,00 .00USD
2000,00 .01- 10000,00.00 USD
instead of (0,00 - 1000,00 USD,1001,00 - 2000,00 USD,2001,00 - 10000,00 USD )
Regards,
Biju K

Error in Release strategy

Hi,
If I assign the following in a Class, the release strategy is trigger in the PRS with out any enty of the given objects in the Class.
Purchase Requisitioner
Plant
Value
Pl help me out

Hi
Check on it:-
http://www.sap-basis-abap.com/sapmo017.htm
http://www.sap.com/services/pdf/BWP_WP_Release_Strategy.pdf
http://sapdocs.info/wp-content/uploads/2009/07/PR-Release-Strategy-Guide-a-case-study-Free.pdf
http://www.google.co.in/url?sa=t&source=web&cd=13&ved=0CB8QFjACOAo&url=http%3A%2F%2Fwww.sdm-c.com%2Ffiles%2FBarcelona_Mazliach_Automate_Your_Purchasing.ppt&rct=j&q=sap-Release+strategy&ei=6IAYTJ2DHJi80gTx7JS_Cw&usg=AFQjCNGi6UQkRdPdIeVmt7mqSiwZr04-Sw&sig2=rJsnJKRW-_8CQebhDq66Tw
pherasath

Error create release record

When trying to access
the SCSM
console to create the
record release
appears the error below:
Version: System Center Service Manager 2012 R2
System.MissingMethodException: Method not found: 'Void Microsoft.EnterpriseManagement.ServiceManager.Application.Common.RelatedItemsPane.set_IsReadOnly(Boolean)'.
at Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Forms.ReleaseRecordForm.UpdateRelatedItemsPaneSettings()
at Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Forms.ReleaseRecordForm.ReleaseRecordDataContextChanged(Object sender, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyPropertyChangedEventHandler.Invoke(Object sender, DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.RaiseDependencyPropertyChanged(EventPrivateKey key, DependencyPropertyChangedEventArgs args)
at System.Windows.FrameworkElement.OnDataContextChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, OperationType operationType)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, OperationType operationType, Boolean isInternal)
at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
at System.Windows.FrameworkElement.set_DataContext(Object value)
at Microsoft.EnterpriseManagement.UI.FormsInfra.FormViewController.<OnReadHelperPropertyChanged>b__16()
at Microsoft.EnterpriseManagement.UI.FormsInfra.FormViewController.OnReadHelperPropertyChanged(Object sender, PropertyChangedEventArgs e)
at Microsoft.EnterpriseManagement.UI.ViewFramework.SupportClassBase.OnPropertyChanged(Object sender, PropertyChangedEventArgs e)
at Microsoft.EnterpriseManagement.UI.ViewFramework.SingleItemSupportClass.NewDataAvailable(Object sender, DataEventArgs e)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Window.Show()
at System.Windows.Window.ShowDialog()
at Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager.GenericWpfWindowConstructor.BeginShow(ShowViewContext showViewContext, Object parent, Object view, AsyncCallback callback, Object state)
at Microsoft.EnterpriseManagement.ConsoleFramework.ViewConstructor.BeginShow(ShowViewContext showViewContext, AsyncCallback callback, Object state)
at Microsoft.EnterpriseManagement.ConsoleFramework.WindowManager.WpfWindowRecord.ShowWindow()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

I haven't seen that particular error before, but if i had to take a guess, i'd wager your console wasn't properly upgraded to 2012, or possibly wasn't installed fully. MissingMethodException against a form display function in what appears to be a common
library makes me suspect this is a problem local to that execution context.
can you replicate this issue on another console?

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

PO Release strategy, error: class POCLASS class type 032

All SAP Gurus,
We are configuring new PO release strategy.
When we go to Release strategy - classification
(Release procedure for PO - Define release procedure for PO - Release Strategies - classification)
It gives following error: Error in classification (class POCLASS class type 032).
Where we can maintain the classification?
Regards,

Dear,
Please follow bellow detail.
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 - 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 - Purchase Head,
Release group: -01, release code: - 02 - Auditor.
3)     Release indicator: - In this step you have to define release indicator.
Like X - Blocked, I - Under process, S - Release.
4)     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 continue
Click on classification button, Enter values of purchasing group for which you want to created release strategy.
Regards,
Mahesh Wagh

Mass Create PO release strategy

Hi gurus,
We are undergoing a major re-org. Due to the changes, we are taking the opportunities to delete the current strategies and re-create everything from scratch as part of the strategies clean up too.
But in doing this, we find ourselves facing a tremendious task as we have 1000+ buyers and each buyers, we need approx. 6 strategies to be created. Thus sizing is almost 14 weeks as OMGS do not allow parallel processing.
We attempt BDC recroding by it's not working. We go errors that pre-requisite not set even though our BDC program did go into that screen. Have any guru here tried or know any feasible mass uploading method to mass create release strategy in the system?
Thanks.

Hi all,
thanks for your respond.
I have found out with the help of my developers that this can be done.
In fact, the original problem that that after we post the release code and go into the set pre-requisite screen, once we come back to the main screen, the recorder put back the release code again and thus SAP detect this a s a new entry and require you to setup the pre-requisite again.
To resolve the above, just make sure in the coding, when you come back from the pre-requisite screen, the coding to set the release code in the screen is not there any more. The 1st entry of the release code (before going into pre-requisite screen or another other screen) will be sufficient in this BDC program.
This speed up RS setup alot. I can upload 494 release strategies in 82 sec. Normal human hand will only be able to post 1 in approx. 5min per strategy (Excluding classification).
Hope you guys find this useful
Edited by: Cynefrid Pua on Oct 5, 2009 11:25 AM
Edited by: Cynefrid Pua on Oct 5, 2009 11:27 AM

Release strategy with classfication & w/o classfication problem

Hello guys
I am facing problem in setting up the release strategy . ECC 6,0 came up default without classification. we need with classification. i set up w/o classification, then delete it and then did with classification.. it works fine for me in the Sand Box , but in dev server it didn't work for me. It is working only w/o classification , When i am trying to set up with classification , it didn't work for me , i am getting the error message in the check release strategy as follows . How i can find which release group need to create ?
Any help will be highly appreciated
Thanks
N
Release code for release group is inconsistent
Message no. ME_RELCHK057
Diagnosis
The release code is not allowed because the associated release group no longer exists.
Procedure
1. Recreate release group .
Note
The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group in order to delete the release codes and release strategies.
2. If necessary, delete the release strategies and the release codes for release group .
3. Then delete release group .

Hi,
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
To set up a release procedure with classification, you please delete all entries in the Release codes and Release Groups for Purchasing Requisitions and start a fresh creation of new Release Codes and Release Groups.
Hope you have followed the following procedure:
1. Create characteristics and classes
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
2. Define organizational plan
3. Assign standard tasks and activate event-receiver linkage.
4. Set up release procedure with classification
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a release point
5. Check release strategies
Hope, this time you will be able to perform the PR Release with Clasiification.
Regards,
Narayana.

No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

No Release Strategy determined - Message no. Z_MESSAGES032

Hi All,
I am trying to creat PO without reference to PR and facing error:
No Release Strategy determined
Message no. Z_MESSAGES032
This is for newly created PO type and new cost center.
We don't have any PR, we are creating PO directly
please advice

Hi Vishal,
As you mentioned you have created new PO type so I think release strategy is not created for this document type. You can go to the IMG ==> MM ==> Purchasing ==> Purchase Order ==> Rlease Procedure for Purchase order ==> Define Release Procedure for Purchase Order.
Select Release Strategies option and create new Strategy. Selecte the newly created strategy and go to details and click on Classification and then Add your document type and other information. If you have any existing release strategy you can select that and add another document type in the classification.
I hope this will help.
regards,
Ajay Mishra

Release Strategy for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

Issue: Purchase order release strategy with storage loaction.

Hi Friends,
I have created release strategy for purchase order considering following characteristics.
1. Plant
2. Purchase organization
3. Purchase group
4. Document type
Hence the release strategy is working fine.
Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
Can any one tell me how to maintain this LGORT filed in structure CEKKO.
Thanks in advance
Shashidhar

HI Shashi ,
Thanks for your quick response,
I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
Also we written the code :move: i_cekko = e_cekko, in user User-Exit M06E0004 function exit
FUNCTION EXIT_SAPLEBND_002.
However, the release strategy is not triggering when PO is saved,
also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
in it.
Kindly reply.
Thanks ,
Shashidhar

Re-set release strategy of rejected PO,after doing respective changes to po

Hi friends,
I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...
Here PO printout is possible only after the final approval...
Pls give some inputs in fixing this issue..
Thanks in advance....
Regards
Shashidhar...

Hi
What are the characteristics of your strategy?
Try to change one of them save and then rechange it to the original
eg.
If the strategy depends for example on the Purchasing Group (PG)
i mean according to different PG's different strategies working
then with ME22N change the PG save and rechange it again to the original.
or
for example If the strategy depends on Materail Groups (MG)
then do the change with MG
With ME22N change the MG save and rechange it again to the original.
I guess this will trigger the strategy again.
Hope it helps
Best Regards

Error : create release strategy

Similar Messages

Maybe you are looking for