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

Similar Messages

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

Number of chars in the PR Release strategy

Hello gurus
How many chars are allowed in the PR Release strategy? , Is it possible to set up the PR Release strategy with item wise and overall release.
Thanks
JJ

Hello:
You can calculate this value using the variation calculation. For exapmple: if N is the number of positions and M is the number of characters (or leters) teh Variation is
V(n,m) = n! / (n-m)!
where the operation n! = n * (n-1) * (n-2) .... 3 * 2 * 1
In your case you have 10 positions for cost center and 26 leters plus 10 numbers as characters.
V(36,10) = 36! / (36-10)!
V(36,10) = 36!/26!
V(36,10) = 3635343332313029282726! / 26!
V(36,10) = 363534333231302928*27
V(36,10) = 9.22393E+14 possible cost centers
Best regads,
Jose Luis

Use of greater than, less than and ranges in release strategy

Hi,
We are using release strategy on purchase order level. We have added purchasing group as one of the characteristics of this release strategy. As we have many purchasing groups in place we want to work with ranges of purchasing groups and also make use of the <,> signs. We can enter those signs, but the strategy does not seem to recognize them. The blocking is not working. Whe also have the po value in the startegy and there the signs do work. Probably because this field is numeric.
Is there somebody that has an idea how to solve this?
Regards,
Ed

Jurgen,
This does not work. I can select multiple values for the purchasing group characteristic, but I can not select the option intervals allowed. I assume this only applies to numeric attributes. I can not define purchasing group as a numeric characteristic. The system overwrites this when I refer to the field in EKKO.
Is there an option to use the not equal sign?
Ed

Adding new characteristics and value fields in COPA

I have recently added several new characteristics and one new value field to the operating concern in the development system.
I am not exactly sure how to create the transport. This is the first time I have done a transport in COPA so I was hoping someone out there would have some tips on how this is done.
Also any helpful tips with transporting this type of change is much appreciated.
Thanks,
Laurie Hensiek

Refer to the documentation at http://help.sap.com/saphelp_46c/helpdata/en/c6/f22c7dd435d1118b3f0060b03ca329/frameset.htm
This is under the node Tools>production startup>transport.

Maximum number of characteristics and Key figures used in a Query

Hi Experts,
Any Thought on the maximum number of Characterstics and key figures that can used in a Query. I know it impacts performance query and runs for very long time.
Thanks,
Kumar.

Hi Kumar,
Welcome to SDN.
I really did not think about it till now, sharing my thoughts on this -
1. You can use all the characteristics & Key Figure ( & more)in Query what you have in you Cube.
2. Query is suppose to serve a purpose, to deliver you analytics based on some KPI etc & it will have maximum no of char / key figures which human mind could make some sense of.
3. Performance of query actually is divided into three areas -
a. database time
b. OLAP time
c. Front End time
and if you query on not performing well first look at which area is taking maximum time & the optimize that first & there are various ways to optimize each area.
Hope it helps.
VC

Report for equipment with characteristics and value

Dear friends,
I need to develop a report which contains fields from the equipment master like superior equipment, functional location, asset etc. as well as charcteristics and values maintained in the equipment. (Multi level equipment display) is not acceptable to client. I understand that table AUSP can be utilised for getting the characteristic value, but I am unable to find any fields from equipment master which I can use to pass on to the AUSP table. Kindly let me know if there is any other table which I can use or any other approach I can take.
Thanks and best regds
Arun

Thanks Pete for the quick response. I will check with the Abaper if he could utilise the function modules for developing the report.
best regds
Arun

Characteristics and value selection controls

I'm having difficulty doing the screen selection:
1) characteristics A to be made mandatory only when characteristics B is with a certain value.
2) characteristics C to have a default value as long as characteristics D is without a value. If D has a certain value, C will be defaulted to another value.

Hi,
Please do the following changes to rectify the difficulties
1) Create a selection condition with the following coding and assign it to the characteristics A basic data tab at the class level in CL02
CHAR_B = u2018Xu2019
When Char B has value X then char A will become Mandatory otherwise Non Mandatory
2) Write a procedure with the following coding and assign it in Configuration profile with proper sequence number
$SET_DEFAULT ($SELF, CHAR_C, '1') if not CHAR_D specified,
$DEL_DEFAULT ($SELF, CHAR_C, '1') if CHAR_D specified,
$SET_DEFAULT ($SELF, CHAR_C, '2') if CHAR_D = 'E',
$DEL_DEFAULT ($SELF, CHAR_C, '2') if not CHAR_D = 'E'
Note: The values mentioned in the code to be replaced with actual values
Regards
Brahmaji D
Edited by: Brahmaji Devarapalli on Oct 31, 2011 9:33 AM

Report users & authorization values in release strategy

Hello,
I want a report which displays the user names and their release codes from the authorizations which the users have.
Is there any standard report?
Thank you.

Dear Landra,
There is no standard report to get this data. But you can get this by combining the data of the 2 tables AGR_1251 & AGR_USERS.
1. Goto SE16 --> table AGR_1251. Give Z* for Role, M_EINK_FRG for Object & FRGCO for Field Name and run it.
2. Goto SE16 --> table AGR_USERS. Give Z* for Role and execute it.
Vlookup both the reports in step 1 & 2 to get the list of users having access to a particular Release Code in the system.
Regards,

Setup characteristics and values upto 4 levels in VC

Hello guruu2019s,
How to define characteristic unto 4 levels in variant configuration example:
Models Model A,Model B,Model C AND IF YOU CHOOSE u2018Model Au2019 IN that MODEL, IT HAS AGAIN SUB CATEGERIES OF Sub Model A1, Sub Model 2, Sub Model 3, ETC,. IF YOU CHOOSE u2018SubModel 1u2019 IT SHOWS THE REQUIRED AVAILBLE ONE. How to setup it in the system?.
Will anyone guide me the procedure how to define in sap system
Full points to the answer,

In a Multi-Level BOM for a Configurable material, you are working with a Parent and Child Relationship, which can be nested to several different levels. I am not sure I understand what you mean by: IF YOU CHOOSE u2018SubModel 1u2019 IT SHOWS THE REQUIRED AVAILBLE ONE. You would start the Configuration at the Top Most Level and work your way down to the lower levels. Please clarify what you are looking for.

Transport request in PR release strategy

Hi Experts,
While configuring characteristics and classes for release strategy in PR, system is not giving prompt for transport request.
What could be the reason? Is it standard functionality or something has to be done at our end.
Kindly suggest
Rgda

Hi,
Check the following SAP notes.
10745
45951
86900
Hope it helps,
Regards,

Release strategy on doc. level isn't working because different values for B

Hi,
At my company we just created a new release strategy (3rd) for PR's. The old strategies were on item level, the new one is on document level. This is the third strategy in the system and with every new PR the strategy is decided based on the creation date (table EBAN field BADAT). For example:
Strategy 1 - BADAT < 2009.01.01
Strategy 2 - BADAT >- 2010.01.01 AND BADAT < 2011.01.01
Strategy 3 - BADAT >2011.01.01
These selection criteria are stored in the class.
This used to work fine between the 1st and 2nd strategy but now it doesn't. Whenever a new line item is added on a different day than the other line(s) the value's for BADAT will be different within the PR and the system isn't able to select a strategy. It's like no value is used for BADAT because there are more than 1 available. As a result the release tab will disappear and the PR will be ready to create a PO from it.
For example:
Line 1 BADAT 15.09.2011
Line 2 BADAT 15.09.2011
No problem releasing the PR
Line 3 BADAT 17.09.2011 added (release strategy reset)
Release tab disappears so no release can be done. However, this PR line 3 can now be converted into an PO without being ever released.
One solution we thought about is using the PR number BANFN. But no ranges are allowed in the class so it doesn't seem to work. Another option is to delete al the old strategies but what will be the consequences for all the old PR's?
We are not sure what to use. Maybe someone else worked out this issue before or has an idea?

Hi,
First of all why you want to release a PR based on Creation date ?
Anyhow, as I understand from the above explanation, since you have created your 3rd strategy @ header/document level. You are facing this issue.
If you have a strategy @ document level then why you want 2 separate strategies @ item level.
Following are the possible solutions as per my understanding
1. You can make the 3rd strategy as item level itself so that the different creation date for different items wont be a problem.
2. You don't have to delete the Old release strategies instead you can remove the characteristics assignment so that release strategy wont be determined @ item level & you can keep the new release @ document level. But in this case you cannot have creation date as a characteristic since it will result in the same issue..
Thanks & Regards,

Purchase order release strategy with multiple characteristics

Hi All,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
Release strategy Type
a few other custom fields
We would like to have PO's with release strategy based on a particular Material Group [say X]. I have created a new Characteristic with respect to CEKKO-MATKL and added this characteristic to the same class.
I have created a new release code [HR] [we need a different person to sign off] and a new release strategy [TR] for which I have assigned the release code HR. In this release strategy, I have set it to get activated for a particular Material Group that does seem to work, but the remaining PO's are not getting triggered for other material groups. For other release strategies, I have left the material group field blank, because they need to be triggered for any material groups except X.
Could you please let me know if I am missing something or is there an alternate approach to this ?
Thank you,
Satish

Hi,
Obviously system will not trigger release strategy in ur case since in the classification data for other strategies u have left it blank excepting X for one strategy.
Since u have added a new characteristic Material group and assigned it to class then system expects an input for Material group for triggering release tab.If this is left blank then system by default will not trigger release strategy tab.
Solution:
First add all existing material groups in values tab of mat group characteristic then maintain the required set of material groups except X in other strategies in classification data.
Hope this is clear to you.
Regards,
Uzair

PR Release Strategy- transport of charact/class/ values using ALE

Does anyone have the information relative to ALE set up for release strategy-
I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
This will be a great help.
Thanks
Raj

Hi Raj,
Please check the below notes for more inrofmation:
86900 - Transport of Release strategies (OMGQ,OMGS)
799345    Transport of release strategy disabled
10745     Copying classification data to another client
45951     Transporting class data: system / client. - has details of what you are looking for.
Hope this helps.
Regards,
Ashwini.

Release strategy problem

I am working on configuration of PO release strategy.
I have two plants in one PO. I included both as values in characteristics and then selected in OMGS (classification) but release strategy is not working when I created purchase order with both plants but works with single plant.
Does anybody know why ?

Hi,
Release strategy for PO with line item charcterstics like Plant, item category, material group etc., gets updated into the structure CEKKO as blank if two different values found in a document. For this type you need to create a assign a value as blank for the Plant.
Ex: Release strategy S1 for plant 1000 with Charctertic value 1000
Release strategy S2 for plant 1100 with charcterstic value 1100
Release strategy S3 for both plants 1000, 1100 with charcterstic value " BLANK"
Regards,
Ramakrishna

NUMBER OF CHARACTERISTICS AND VALUES IN RELEASE STRATEGY

Similar Messages

Maybe you are looking for