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.

Similar Messages

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.

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

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

Rebate Processing - Value Difference -Verfication level and Sales Volume

Dear All ,
We are using standard rebate process - Customer Rebates and we have encountered the following issue .
1. The Rebate agreement was created on 01/12/2010 with validity from 01/12/2001 , valid through 31/03/2010.The Rebate recipient was not activated for Rebate in the month of DEC 2009 and was activated on 15/01/2010 . We have executed VBOF and found that the Accruals are calculated from 15/01/2010 till date which is 25,010 USD ( for the invoices which are created from 15/01/2010) but it is not taken into consideration of the invoices which are created in the month of December 2009.
We have checked and calculated manually the accruals which is amounting to 35,575 USD for the period ( 01/12/2009 to 14/01/2010) . This accrual amount is not updated for the agreement .
Can any one give inputs on this issue.
Thanks in advance .
Regards
Veera
Edited by: veera PV on Mar 6, 2010 11:07 AM
Dear All ,
I have executed the VBOF couple of times and the sales volume is updated correctly now - 51,277.20 USD . but when i selected the agreement and clicked on verfication level it is not showing up all the invoices and the value shown is 43,025.10 USD . There is difference of 8252.10.
Now the issue is how do i get all the invoices in the verfication level.
Can any one give inputs on this .
Thanks in advance to all of you.
Regards
Veera
Edited by: veera PV on Mar 6, 2010 11:08 AM

Hello,
please check this thred Re: VBOF Issue related to updating Old Invoices after activating Rebate Check.
Best regards,
Ivano.

BI Security Implementation and restrictions at Infocube levels

Dear all,
I am trying to update myself on BI security and practical implementations. I read expert guide and other relevant documentation. We have BW security integrated with CRM and Portal.
Please explain or provide me some direction in understanding how BI security works at key figure level.
Is it necessary to set the following InfoObjects as authorization-relevant . Is it MANDATORY to make the following settings as "Authorization-Relevant" before we start the BI Security
 0TCAACTVT
 0TCAIPROV
 0TCAVALID
 0TCAKYFNM
and
 Add 0TCAIFAREA as an external hierarchy characteristic to 0INFOPROV
When I changed above infoobjects to Authorization relevant, BI Portal Users are complaining that they have Access issues. I have to change this setting back.
Can someone explain me the implication of making the above objects as Authorization Relevant. What making these objects, Do I need to complete some steps to make it work.
All users have 0BI_ALL object defined in S_RS_AUTH. I don't know how 0BI_ALL works for users.
I greatly appreciate if anyone can explain how I can achieve the following scenarios:-
1. How Can I restrict user access to all the Characteristics and Key Figures of Infocube ZEN_XXX1 except for Characteristic 0CRM_SALORG.
2. How can I restrict User access to all the Characteristics and Key Figures of Infocube ZEN_XXX1 except for Characteristic 0CRM_SALORG (Sales Organization CRM) and Key Figure ZVOLSU.
3. How can I restrict User Access to all Infocubes EXCEPT ZEN_T001 infocube.
I tried using PFCG but it does not work. 3rd scenario worked fine. I really need help in resolving scenario 1 and 2.
please eMail me if I need to go thru any other step-by-step procedure.
I am trying my best to resolve and at the same time reading other documentation and experimentation.
Waiting for a Positive Reply
Kumar

Hello Kumar,
here are my statements:> Is it necessary to set the following InfoObjects
> as authorization-relevant . Is it MANDATORY to make
> the following settings as "Authorization-Relevant"
> before we start the BI Security
> 0TCAACTVT
> 0TCAIPROV
> 0TCAVALID
> 0TCAKYFNM
Be careful when checking 0TCAKYFNM. If you do so EVERY user will be influenced because reporting is based on key figures. But as you need to restrict to certain key figures you will have to check 0TCAKYFNM authorization relevant. As a consequence every user will need key figure authorizations.>
> and
> Add 0TCAIFAREA as an external hierarchy
> characteristic to 0INFOPROV
This is not mandatory but may be helpful if you want to restrict authorizations on InfoArea Level.
> When I changed above infoobjects to Authorization
> relevant, BI Portal Users are complaining that they
> have Access issues. I have to change this setting
> back.
They might complain because they do not have authorizations for any key figure.As I explained above checking this object has impact on every query because every query contains key figures and when you check 0TCAKYFNM users will need the authorizations for this object. >
> Can someone explain me the implication of making the
> above objects as Authorization Relevant. What making
> these objects, Do I need to complete some steps to
> make it work.
>
> All users have 0BI_ALL object defined in S_RS_AUTH. I
> don't know how 0BI_ALL works for users.
0BI_ALL is SAP_ALL on analysis level - you must not assign this to your reporting users!>
> I greatly appreciate if anyone can explain how I can
> achieve the following scenarios:-
>
> 1. How Can I restrict user access to all the
> Characteristics and Key Figures of Infocube ZEN_XXX1
> except for Characteristic 0CRM_SALORG.
Figure out if characteristic 0CRM_SALORG has to be marked as authorization relevant or not. If not - there's nothing to do. If yes - you will have to setup analysis authorizations.
Create an analysis authorization in RSECADMIN like:
ZEN_XXX1_ALL
0CRM_SALORG = *
specify your other auth. relevant characteristics and enter ":" as values
0TCAIPROV = ZEN_XXX1
0TCAACTVT = 03
0TCAVALID = *
Do not forget to allow authorizations for these auth. relevant characteristics in your other infoproviders (where applicable).
Assign the authorization to the users in RSU01 or create a role containing S_RS_AUTH with the analysis auth. as value.

>
> 2. How can I restrict User access to all the
> Characteristics and Key Figures of Infocube ZEN_XXX1
> except for Characteristic 0CRM_SALORG (Sales
> Organization CRM) and Key Figure ZVOLSU.
Create an analysis authorization in RSECADMIN like:
ZEN_XXX1_KEY
0CRM_SALORG = CRM
specify your other auth. relevant characteristics and enter ":" as values
0TCAIPROV = ZEN_XXX1
0TCAACTVT = 03
0TCAVALID = *
0TCAKYFNM = ZVOLSU
And also do not forget to allow authorizations for these auth. relevant characteristics and all key figures in your other infoproviders.
Assign the authorization to the users in RSU01 or create a role containing S_RS_AUTH with the analysis auth. as value.
> 3. How can I restrict User Access to all Infocubes
> EXCEPT ZEN_T001 infocube.
Enter in auth object (PFCG) S_RS_COMP and S_RS_COMP1 your cube ZEN_T001 in field RSINFOCUBE, RSZCOMPTP = REP, ACTVT = 16

>
> I tried using PFCG but it does not work.
Why? What was the problem? Keep in mind that you always will need the three special dimensions since BI 7.0
3rd scenario
> worked fine. I really need help in resolving scenario
> 1 and 2.
>
> please eMail me if I need to go thru any other
> step-by-step procedure.
>
> I am trying my best to resolve and at the same time
> reading other documentation and experimentation.
>
> Waiting for a Positive Reply
>
> Kumar

Select Single * and Select upto one row

Hi all,
Can anybody tell me what is difference between Select single * and select upto one row?
And which one is better?
Thanks in advance.......

According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single is the best one compared to UPto one rows.
Select Single will get the first record from the table which satisfies the given condition.So it will interact once with the database.
UTO 1 rows will get the list of the records for the given match and iwll show the first record from the list.So it will take time to get the record.
SELECT SINGLE VBELN from VBAK
where MATNR = '1M20'.
---Thjis will get the first matched record and will display the record
SELECT VBELN from VBAK
where MATNR = '1M20' upto 1 rows.
---Thjis will get the list of matched records and will display the first record
The Major difference between Select Single and Select UPTO 1 rows is The Usage Of Buffer for each.
Select Single will search for all the satisfied data and bring all that data into Buffer and later it will give to that data to the program.
Select UPTO 1 Rows will end the search after getting the 1st satisfied record and gives that record to the program.
Thus Select Single will take much processing time when compare with Select UPTO 1 rows.
Also
check these threads..
Difference between Select Single and Selct upto 1 row
Difference between Select Single and Select upto 1 row
Difference between select single and select upto one row
Difference between 'select single *' and 'select upto 1 rows'
difference between select single and select up to 1 rows
regards,
srinivas
*reward for useful answers*

Select single and select upto 1 rows

Hi
What is the difference between select single and select upto 1 rows
Performance wise which one is the best
Regards,
Maya

Hi,
Difference Between Select Single and Select UpTo One Rows
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
reward points if useful
regards,
ANJI

Select single and select upto

what is the difference of select single and select upto statements

HI,
SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.

Value assignment and value assignment type in the specification workbench

Hi all,
There is this section on the specification workbench called u201CProperty Treeu201D, this section contains all the value assignment type, I have two questions on this.
Question 1 u2013
What is exactly the value assignment type? The SAP help portal said it is a structure specification data and information. What exactly does it mean and its usage?
Question 2 u2013
May I know where is the SPRO configuration that actually causes the list of value assignment types appear on the property tree section for this particular specification type which I created.
In another word, I create this new specification with specification type u201CREAL_SUBu201C and specification category u201CSubstanceu201C in the specification workbench transaction. Next thing I know is that the property tree section for this particular specification consists of a list of value assignment type. How does the system assigned these list of value assignment types to this specification i created? Coz I didnu2019t do anything.
Where in SPRO and the logic link it up on this??
Thanks.
YY

Hello all
EH&S contains a number of submodules (PS, DG, IH etc.). Regarding each submodule a basic customizing is delivered by SAP. One example is the specification type. Usually you will find something like
REAL_SUB
LIST_SUB
etc. in the Customizing as discussed. Further more I believe with EH&S 2.7. the specification category come in place (SUBSTANCE as an example). You need to take care regarding this too.
An value assignment type can be grouped in a property tree and a property tree can be linked to a specification type and there are cases known that one specification type is linked only to one property tree (this is a decision regarding business needs and not an IT quesition). Using the EHS& surface you can change the property tree per specification if the set up is done in Customizing. Therefore the property tree is a "view" on the data linked to a specification. (identifeirs etc. are managed different)
A "property" is based on a value assigment type and in many cases on a related EH&S class and characteristic. You will find these types.
A => value assignment type to be used if you need characteristics
B => value assignment type to be used if you need specification listing
C => value assignment type to be used if you need composition
.. etc.
You can mix types. That means you can create a property of type "A" and "C" (take a look in SAP original tree; you will find examples how to do it).
A propetry tree is a "list" of assignment type related to a object (specification). Using the property tree you can maintain necessary data. Therefore ithe property tree itself contains per specification the list of "potential" data structures you can fill with data. I belive SAP Standard is delviering now something like 250 properties (valeu assignment types): To e.g. get an MSDS you need to maintain I would assume at least something like 20 up to 50 properties
The area of customizing regrading property tree, specification types etc. is the most crticial to have a sucessful EH&S project running; any wrong decision gives rise to a high cost later Therefore take your time to understand what effect does which customizing acitivity have later.
Based on the value assignemnt you will create later e.g. a WWI report (like MSDS).
Additionally if necessary you can create customer specific value assignment types by either do a copy from SAP original to "Z" (highly recommended to do so!) or starting from basic.
Starting with EH&S 2.7. you have now more options to "change" EH&S using standard EH&S functionality. Take a look in customizinjg (example: you could create you own "look and feel" of the workbench (you should'nt really do that but it is possible). You can design your own "tab strips" etc.
So once again: the "correct" set up of EH&S in the area of e.g. identifers, speficiation types, property trees etc. is the "core" activity in EH&S customizing and therefore think "twice" before you change the setup up (you need to understand what a change mean)
With best regards
C.B.

Org Specific Purchasing Category Structure and Values

Hi
I have an instance with 2 separate organisations defined under 1 business group. Each organisation requires its own purchasing category structure and values.
I cant seem to be able to achieve setting each org with its own values using a different category set, even when I configure the category set to be controlled by organisation. Let alone each org having its own flexfield segment configuration i.e one has 3 segments 1 has 4.
Is there anyway to achieve this in my current org structure, or do i have to create a business group for each organisation and seperate them that way to achieve this?
Thanks
James

Hi Sandeep
I have setup 2 different category sets, each controlled at org level, and then assigned them as the default category set for purchasing. However when i set it for one org it overwrites whats configured for the other org?
Do you know why i cant seperate them?
Thanks
James

Diff bw select single * and select upto one row

hai,
what is the difference between select single * and select upto one row.

hi,
ex code
Report Z_Difference
Message-id 38
Line-Size 80
Line-Count 0
No Standard Page Heading.
Start-Of-Selection.
Data: w_Single type Posnr,
t_Rows type standard table of Posnr
initial size 0
with header line.
Select single Posnr
from zDifference
into w_Single.
Select Posnr
into table t_Rows
from zDifference
up to 1 rows
order by Posnr descending.
Write :/ 'Select single:', w_Single.
Skip 1.
Write :/ 'Up to 1 rows :'.
Loop at t_Rows.
Write t_Rows.
EndLoop.
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not
using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key,
it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key
supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s)
you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the
second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional
level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause
If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that
are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns
the first record of the result set.
Mainly: to check if entries exist.
You can refer to the below link..
http://www.sap-img.com/abap/difference-between-select-single-and-select-upto-one-rows.htm
rgds
anver
if hlped pls mark points

Regarding select single and select upto 1 rows

hi experts,
plz let me know about difference between select single and select upto 1 rows with small eg...
thnx in advance.

Hi Ravi,
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single is the best one compared to UPto one rows.
Select Single will get the first record from the table which satisfies the given condition.So it will interact once with the database.
UTO 1 rows will get the list of the records for the given match and iwll show the first record from the list.So it will take time to get the record.
SELECT SINGLE VBELN from VBAK
where MATNR = '1M20'.
---Thjis will get the first matched record and will display the record
SELECT VBELN from VBAK
where MATNR = '1M20' upto 1 rows.
---Thjis will get the list of matched records and will display the first record
The Major difference between Select Single and Select UPTO 1 rows is The Usage Of Buffer for each.
Select Single will search for all the satisfied data and bring all that data into Buffer and later it will give to that data to the program.
Select UPTO 1 Rows will end the search after getting the 1st satisfied record and gives that record to the program.
Thus Select Single will take much processing time when compare with Select UPTO 1 rows.
Also
check these threads..
Difference between Select Single and Selct upto 1 row
Difference between Select Single and Select upto 1 row
Thanks,
Reward If Helpful.

Regarding select single and select upto???

HI All,
Cud u pls let me know the differences between select single and select upto??
and which is the better option?? pls its quite urgent..plss plss
plss
Thanx in Advance
Prasad

Hi..,
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Check this example ...
DATA: gv_vbeln TYPE vbak-vbeln,
gv_erdat TYPE vbak-erdat.
SELECT SINGLE vbeln erdat
FROM vbak
INTO (gv_vbeln, gv_erdat)
WHERE erdat = '12/01/2006'.
SELECT vbeln erdat
FROM vbak UP TO 1 ROWS
INTO (gv_vbeln, gv_erdat)
ORDER BY erdat ASCENDING.
ENDSELECT.
*In the example, the select single gets the first record that satisfies the WHERE clause unlike in the UP TO 1 ROWS where it sorts the database records by the earliest date and gets its VBELN.
Try using the ORDER BY clause in SELECT SINGLE .. It gives an error !! U cannot use that with SELECT SINGLE
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Hope u understood !!
reward if it helps u..
sai ramesh

Setup characteristics and values upto 4 levels in VC

Similar Messages

Maybe you are looking for