Release Strategy - Object "ZX NX" already classified with same characterist

Hi Gurus
While modifiying the exist release strategy the following error occurs.
Object "ZX NX" already classified with same characteristic values
Message no. C1818
Diagnosis
Object ZX NX was already classified with the same characteristic values. In class maintenance, you define whether a warning message or error message is displayed in these circumstances. This message draws your attention to the possibility of data redundancy.
Procedure
Change the assigned characteristic values, so that you do not have redundancy in your system.
Perhaps the object you are classifying is not necessary, because it can be replaced by the object found by the system.
Please advice on this.
Thanks in advance
ARAS

Hi
Thanks for your input. I will test this and come back.
Experts, any further inputs...
Regards
Aras

Similar Messages

PR release strategy with material group

Hi Experts,
Release strategy for Purchase requisition already configured with characteristics Document type and Total net order Value.
For fulfill new requirement we have created New character with Material group.Our requirement is for Two material groups separate release strategy has to be trigger and remaing other material groups old release strategy has to be trigger.For exple if X and Y are two material groups ,which require seperate release strategy.Other than X and Y material groups requir old release strategy.
all the material groups assigned to character.Blank material group also assigned to the character.In release strategy level in classification view we have assigned two material groups( X and Y ) for separate release strategy and remaining material groups and Blank material group to old release strategy.
   At the time of creation of PR if i give two material groups ( X and Y)for different line items, seperate release strategy is not triggering, where as old release strategy is triggeringIf i create PR with single material group( X) for all line items it is triggering seperae release strategy properly.
   For other material groups (other then X and Y )with different line items it is triggering old release strategy properly.
      Kindly help me to resolve the problem.

Hi,
Please add Blank material group to the new release strategy also.
Maruthi

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

PO release strategy LSMW with SM30_VV_T16FS_2

Dear Friends ,
Problem in Release strategy upload for PO release strategy.
We are making LSMW with SM30 for - VV_T16FS_2
Problem is that when we do recording actulat release codes come in , release prerequisites also come but as you know in that case we not prese ENTER , we need to click on Release prerequisite then only Release status comes.
There is some problem with OKCODE. Means as per my understanding system not takes full release startegy smoothly.
Regards,
MAhesh

Hi ,
It is with help of ABAPEr , i dont know exactly but while designed LSMW some lines was ger dublicated and we removed it. thats it.

HR organisation Structuer Link with PR release Strategy

Dear Gurus,
As per our organisation, once the PR is created, it has go to the Cost Center Owner and it has to follow the HR organization structure. we have 200 Cost centers in different departments.
Please help me how to configure this with HR organization structure
Your help is most appreciated and Full point will be rewarded.
Thanks
RS

Neetu,
Hi Neetu,
My Release strategy working fine and nothing wrong with it. My question is, why only NB type is falling for Rel Strategy. I think I found answer from Rosa's Answer. If you check overall release at Document Type, then that document type falls for Release Strategy.
Thanks all. I am closing this with Answered and points goes to Rosa...

Release Strategy with New Class and Char.

Dear All,
I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
when i going to add in Release group.. system giving the error.
Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
My existing Characteristic for india :
ZP0_GNETW     Total net order value     CURR     15     2     INR
ZPO_BSART     Order type (Purchasing)     CHAR     4     0
ZPO_EKORG     Purchasing Organization     CHAR     4     0
ZPO_EKGRP     Purchasing group     CHAR     3     0
New Characteristic for South africa :
ZPOSA_BSART     PO Order Type ATSA     CHAR     4     0
ZPOSA_EKGRP     Purchasing Group ATSA     CHAR     3     0
ZPOSA_EKORG     Purchasing Organization ATSA     CHAR     4     0
ZPOSA_GNETW     Total net PO value ATSA     CURR     15     2     ZAR
ZPOSA_WERKS     Plant     CHAR     4     0
Please help me how do configure 2 release strategy for 2 country.
I will be very thankfull to u.
Regards,
Vishal Garg

HI Biju K,
I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
Please explain..
And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
Please explain in details.
I will be highly thankfull to u.
Regards,
Vishal Garg
9810402156

Purchase Order not subject to release strategy

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
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   0
                        1
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
ravikant dewangan

Purchase Order Release Strategy Approval

HI All,
I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
Level one will have 1 approver
Level two must have two approvers.
The scene is:
Level one will approve all purchase orders betwee 400 to 5000 euros. 1 approver only
Level two will approve all purchase orders above 5000 euros. 2 approvers.
The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
Pur. group G70, Release Group GC and release strategy DF.
I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
CL20N is completed for both levels and works correctly for level one approval but not for level two
Can any please help
Leslie

Hi,
May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
1. PO Order Type (ZPO_BSART),
2. Company Code (ZPO_ BUKRS),
3. Purchasing Organization (ZPO_EKORG),
4.Plant (ZPO_WERKS)
5. Purchasing Group (ZPO_ EKGRP) and
6. Total net PO Value (ZPO_GNETW)
Create one release class ZPO_CLASS & then add all above release characteristics
And then design your release strategies as required.
AND under release characteristic for PO Value (ZPO_GNETW) keep following values
A. <= 400 EUR
B. 400.01- 5000 EUR
C. >5000 EUR
As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
Regards,
Bijju K

Purchase requisition release strategy tab missing

Hi all
I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

hi,
check few reasons:
1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
2. check the release strategy OMGSCK, is there any problem with your release strategy...
3. Check whether you have maintained all the classified field in the document or not..
4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
regards
Priyanka.P

Purchase requisition - release strategy statistic

Anyone knows if exists a standard program/tr/utility for monitoring the use of release strategies
for purchase requisitions ?
In our system there are a lot of release strategies obsolete or used for few cases, so
we would check the effective use of release strategies.
Regards.
Riccardo Galli

hi,
check few reasons:
1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
2. check the release strategy OMGSCK, is there any problem with your release strategy...
3. Check whether you have maintained all the classified field in the document or not..
4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
regards
Priyanka.P

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

ME28 relese strategy Object

Dear All ,
I want to restrict me28 transaction for release strategy for USER login .To restrict the same i need the Object .
How to find out these Objects , so that it can be restricted for USER logon .
(Ex : A manager should have authorization to release with release strategy allowed to him )
Regards

Hi
For this aim you should create roles via PFCG.
And in the role there should be the following transactions:
For PR:
ME54N - Individual Release
ME55 - Collective Release
ME5F - Release Reminder
And for PO:
ME29N - Individual Release
ME28 - Collective Release
and then you should arrange the authorization objects
and for the managers you should manage
release code and release group (M_EINK_FRG).
Best Regards
Reward please if found useful

PO Release Strategy not triggerred for particular Total Net Order Value

Dear,
I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
Please suggest for solution.
Thank you.
Warm Regards.

Dear All,
While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
May I know how the value for this field gets calculated.
Thank you.
Warm Regards.

NUMBER OF CHARACTERISTICS AND VALUES IN RELEASE STRATEGY

Hi there, how R U.
Please, can any body help my with this one ?
How many characteristics may I have in a release estrategy for purchase order an contracts ?, how many values could a characteristic have ?, if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
I hope you can help me.
Have a nice day.

How many characteristics may I have in a release estrategy for purchase order an contracts ?,
You can have as many number of characteristics you want for release strategy, no restirction
how many values could a characteristic have ?
You can have as many as you want, no restiction
if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
Release code you can define only 8 and if oyu want more release code than create new release group and assign more release code
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
the release strategy can hold only 8 release code but every release strategy you can have more than 8 charcteristics and each char can have n number of values and that can be decied at char creation level

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 - Object "ZX NX" already classified with same characterist

Similar Messages

Maybe you are looking for