Regarding Condition Index

Hi All,
With regards to condition index I have made the required tick in the condition type now when I am going into the master data with regards to creating condition records selecting the condition index tab by giving the input as the condition type, the system says that there are no records found, eventhough I have created the sales order in the system, the access sequence consists of line item and sales order please advise if any other configuration needs to be done for condition index and how do I check if the configuration is complete.
Kind Regards
Atul

Hi Condition indes only Specifies whether the system updates one or more condition indices when maintaining condition records. It depends whether you had created the combination of condition recored to determin if you can find the existing one, please be sure you had created the condition record via vk11.

Similar Messages

Creation of condition index

I created a condition table with one field "KUNRE - Bill-to party" to use as a condition index.
When I tried to access the table via path
IMG > SD > Basic functions > Pricing > Maintain condition index > Maintain condition tables for index
I am getting an error "Table F 904 not Available - Message # VK016"
Can you help in creating a condition index with example.
Thanks,

Hi Rama,
This may help:
http://help.sap.com/saphelp_40b/helpdata/en/93/743387546011d1a7020000e829fd11/content.htm
Cheers

Why do I use condition indexes? How do you activate them?

Hi all
Why do I use condition indexes? How do you activate them?
thanks all

You can create and use condition indices. You can use these indices to display, change and create condition records with reference. This transaction can include condition records with several condition types and tables. For example, you can use a condition index if you want to see all condition records that apply to a particular product regardless of whether the records are prices or discounts. In this case, you can use one of the standard condition indexes. Or you may want to see a list of condition records that contain a particular sales deal and a material from a user-specified list of products. To display this information, you can create your own condition index.
Creating a condition index is similar to creating a condition table. In Customizing for Sales, you select the combination of fields that you want in the index key. The system automatically proposes a list of permitted fields to choose from. The fields you specify for the key can have a maximum combined length of 100 characters.
The activation function displays a list of all available condition indexes and indicates which are active. The system can use a condition index only when it is activated. Before you can use the indexes that are delivered in the standard version, you must first activate them in Customizing for Sales. Some indices are activated automatically during generation. In addition, you must specify one of the following index updating requirements for each condition index:
Requirement 1: The index is updated when the user provides data for all fields in the index
Requirement 2: The index is updated when the user provides data for at least the first index field

Creating a conditional index? How to suggest a new feature?

How can I suggest a new feature in Oracle?
Imagine a table of service requests to be processed, where a column named STATUS can be: 'N': New, 'C': Canceled or 'P': Processed. This will result in a biased distribution where 'P' will represent more than 99% of rows.
I know that Oracle accept indexes created using functions and I can create an index on decode(STATUS,'P',null,STATUS) to make index small. But it will not help a query on STATUS = 'N' condition.
I would like to create a conditional index like:
create index idx01 on service_requests (status) where status <> 'P';
In this example, only status 'N' and 'C' will be indexed resulting in a very small index that can resolve filters like STATUS = 'N'.
Or this:
create index idx01 on some_tables (column1 including null values); to resolve COLUMN1 is NULL
Is there a way to suggest new features like this?

How can I suggest a new feature in Oracle?
Imagine a table of service requests to be processed, where a column named STATUS can be: 'N': New, 'C': Canceled or 'P': Processed. This will result in a biased distribution where 'P' will represent more than 99% of rows.
I know that Oracle accept indexes created using functions and I can create an index on decode(STATUS,'P',null,STATUS) to make index small. But it will not help a query on STATUS = 'N' condition.
I would like to create a conditional index like:
create index idx01 on service_requests (status) where status <> 'P';
In this example, only status 'N' and 'C' will be indexed resulting in a very small index that can resolve filters like STATUS = 'N'.
Or this:
create index idx01 on some_tables (column1 including null values); to resolve COLUMN1 is NULL
Is there a way to suggest new features like this?
A new feature isn't needed. Oracle provides the equivalent of that 'conditional index' by allowing you to create, and index, VIRTUAL columns.
This code uses a VIRTUAL column and then creates an index on it.
drop table test_status
create table test_status (col1 number,
status varchar2(1),
special_status generated always as (decode(STATUS,'P',null,STATUS)
create index idx01 on test_status (special_status)

What is the mean of condition index in pricing condition

hi
my question is what is the mean of conditon index in pricing condition type what is the use of it give me ascenario.

hi nag
A customer-defined list of conditions that allows quicker access to condition records or a group of condition records.
<a href="https://forums.sdn.sap.com/click.jspa?searchID=4774296&messageID=3962335">condition index</a>
Condition Index can be created for particular condition type to maintain condition record. The condition index along with the condition update field in condition type (T.Code: V/06) restricts the usage of condition type for limited sales orders, condition base value or condition value.
Features of condition Index:
When checked this specifies whether the system updates one or more condition indices when maintaining condition records.
This makes it possible to list or maintain condition records independently of condition type and condition table
Message was edited by:
Prashanth Goud

Help for conditional indexing in LV 2012?

Not that I need it, but I could not find any help on the new LV 2012 Conditional Indexing feature. It appears in the contextual menu, but the contextual help does not provide any hint of what this is, and it's nowhere to be found in the Help:
Solved!
Go to Solution.

Sorry it took so long to get back. I had to download LV2012. I think I still need to download the patch. And also setup all of my setting and addons. VIPM will be busy for the rest of the day.
Anyways, your benchmark is flawed. Add outputs to the arrays and you will get radically different results. I think some of your loops didn't exactly iterate the 10000 times since there was no output. And I have no clue what you were trying to show with the second benchmark.
I didn't edit the labels yet. So for those who haven't looked at the VI, "x/y" is the time for pre-allocating and keeping only what is needed. "x/y 2" is the same except with another data type. "x/y 3" is using the build array. "x/y 4" is using the new conditional indexing feature. Each one is looped 10000 times and the average is given (in ms).
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Conditional Indexing Benchmark Results.PNG ‏3 KB
benchmarking.vi ‏24 KB

XSLT-like conditional indexes

Is there a plan to introduce conditional indexes the way it's done in XSLT?
Something like this:
<xsl:key name="action" match="/*/ENTRY[(@Operation='notify' or @operation='notify')]/DATA" use="@action"/>

From the top of my head:
1. Index by attribute value when another attribute of the same element has particular value[s], or evaluation of another attribute has particular value[s]. Combining of two indexes is not the same at all.
2. Index by element or attribute when path is important and there are other elements/attributes with the same name or exactly the same element, but located differently in tree.
I didn't look into documentation too deep, but it seems I never saw Berkeley DB XML supports full text search index. Does it?

Regarding sy-index and sy-tabix

Hi,
What is the major difference between sy-index and sy-tabix ,
can you give me one good example with code..
Regards,
Reddy.

Hi,
SY-TABIX - Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY_INDEX - In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
sy-tabix is the tab index - the index of the record in the internal table you are accessing,
sy-index is the loop counter.
If you use a condition in LOOP the sy-index will go from 1 to n, but sy-tabix will refer to the line in the internal table.
Hope this helps u.
Thanks,
Ruthra

Regarding LOB index

Hi,
I am having a SQL loader mapping where in I am loading data from a CSV file to Oracle target table.
My target table is having a CLOB column. Now, due to this a LOB index has also been created for this column.
My CSV is having 1 million records and when I execute the mapping it gets hang and doesnot load anything.
I think that due to that LOB index the execution is taking so long. Is there any way that I can disable this index during run-time. I tried but it gave me error: ORA-22864: cannot ALTER or DROP LOB indexes.
Can anyone of you suggest any alternate to this.
Thanks!!!!

Hey Fren,
We have Secondary index to shorten the search time and thus to increase the proficiency in selecting the accurate records from numerous fields available for the option...
That means, we can say that Secondary Index can act as an Extension to the Primary Key fields available to Shorten the Search time.....
But if you use 'OR' condition and give a SELECT Query in your report it will act as the reverse effect of Secondary index......
Instead you can create the Secondary Index including the key fields with some extension to the same...
Means For example,
Table 1:
Field1 [x] CHAR 10
Field2 [x] CHAR 10
Field3 [ ] NUMC 10
Field4 [ ] CHAR 10
Field5 [ ] CHAR 10
Field6 [ ] NUMC 10
Field7 [ ] CHAR 10
Field8 [ ] CHAR 10
Field9 [ ] NUMC 10
Field10 [ ] CHAR 10
Field11 [ ] CHAR 10
Field12 [ ] NUMC 10
Field13 [ ] CHAR 10
Field14 [ ] CHAR 10
Field15 [ ] NUMC 10
Field16 [ ] CHAR 10
Field17 [ ] CHAR 10
Field18 [ ] NUMC 10
Field19 [ ] CHAR 10
Field20 [ ] CHAR 10
Field21 [ ] NUMC 10
Field22 [ ] CHAR 10
Field23 [ ] CHAR 10
Field24 [ ] NUMC 10
So you can have Field 3 Field4 Field5 Field6 as your secondary index.....
Thats it,
Thank you,
Inspire If Needful,
Warm Regards,
Abhi

Regarding Renaming INDEX Partitions

Hi All,
I have the following syntax for renaming table partitions/subpartitions :
ALTER TABLE SMTP_MSG_TRAFFIC_FCT RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310;
ALTER TABLE SMTP_MSG_TRAFFIC_FCT RENAME SUBPARTITION FOR (20100310,19) TO BASE_FACT_20100310_MAILBOX;
I want to do the same thing for renaming the index partitions/subpartitions :
ALTER INDEX SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310;
ALTER TABLE SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME SUBPARTITION FOR (20100310,19) TO BASE_FACT_20100310_MAILBOX;
But I get the following error:
SQL> ALTER INDEX SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310;
ALTER INDEX SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310
ERROR at line 1:
ORA-14006: invalid partition name
Is it possible to rename the partition in this way? Or can I set any parameter that will ensure that when the base table partition name changes, it will also change the index partition name?
Thanks & Regards,
Aniket

yes its possible:
SQL>ALTER INDEX index_name RENAME PARTITION index_partiton_name TO new_index_partition;
You are getting error because :
a partition name is expected but not present as you typed,
enter an appropriate partition name, will solve the problem.
Edited by: adnanKaysar on Mar 18, 2010 12:32 PM

Regarding "Delete Index" process in the process chain.

Hi Gurus
In the process chain, I have Delete Index -> Load Info pacakge -> Create Index process in the above order.
I am loading few records, so no need to delete indexes everytime. Can i remove the "Delete Index" process from the Chain without deleting the Create Index process. Or do I have to delete both.
Could you please clarify my doubt if possible in detail.
Thanks,
Regards,
aarthi

With the numbers you provided, you probably don't need to have the steps. With Oracle (not sure about all the other DB flavors) there are some other considerations:
Not having the indexes when loading the data can improve the load time since the bitmap indexes are not very efficient with respect to inserts/updates. The more dimensions you have, the more indexes there will be and the more noticable the impact of having the indexes present when loading.
The drop index process only drops the F fact table indexes. If you compress your cubes regularly so that you don't have many uncompressed requests, the index rebuild time will remain small, but if you have many uncompressed requests in your cube, the index rebuild time can begin to exceed whatever time you might save on the load with indexes deleted.
With bitmap indexes present, you can also occasionally receive a ORA-0600 deadlock error during the load process, and that can be prevented by dropping the indexes before loading or chose the load option packet by packet so that two packets are not trying to update the same index block at the same time.
Another concern in shops where reporting on the cube might occur during the load process - if you drop indexes prior to a load, any one trying to run a query on teh cube could have poor query performance since all the indexes will be missing onthe F fact table, this agina becomes more apparent the more data you have in the uncompressed fact table.
So it really comes down to your environment, but certainly drop the indexes any time you have large loads.

Regarding Secondary Index in a Table

hi
if i create a secondary index in a table is it obligatory or optional to have first field as MANDT (Client field) if the table is client dependent & how many secondary indexes(MAXIMUM) can be created for a table.
Regards

Hi,
Check the below Link
How to transport a secondary index on P master data table?
Hope this helps you.
Regards,
Anki Reddy

Regarding deleting index

Hi Friends,
If I delete the whole content of an Infocube and then do the reload,is it require to delete the index seperately.
If I don't delete the index how is it going to impact the load?
Regards,
Debjani...

It doesn't mean that Indexes will delete permanently .. Structure will remain same!
When you delete data from cube it also deletes the generated indexes which are existed .. there is no point of having indexes on deleted records .. it's logical
even it doesn't hold any data it allows you to create index and generate stats(ex. create a dummy cube and try to generate)
For the moment I don't have any document for it.. I will let know
For your 2nd ques.
Only for huge loads droping index will be usefull which will improve the loading performance!
For daily delta load with less volume of data you need not to drop Indexes .. if you do so it will take lot of time to rebuild the indexes(on whole data)

Regarding Condition record in CRM using field MATKL (Material Group)

Hi All
Currently we are working in SAP CRM 5.2 and it has been connected with backend ECC 6.0.
This scenario is about Pricing which has been maintained in ECC and inturn flows to CRM with few filters in place.
There are few customized Condition Tables in ECC with combination of Sales org./ material group for which discount has been maintained. A proper condition record is also available for this Condition table and it has been assigned to a access sequence and inturn assigned to a condition type.
All these procedures, condition types, access sequence has flown from ECC to CRM. And all the condition tables are active in IMG (Basic Functions / Pricing / Define Settings for Pricing / Create Condition Tables)
When i check in
(SAP menu / Master Data / Prices and Conditions / SAPCND/GCM - Maintain Conditions )
Application - CRM,
Maintenance group - PRODDISCOU,
Maintenance context - GCM
Here for the above mentioned combination when i select the Key Combination (Condition Table) and enter the customized table number (Sales org. / Material Group) iam getting a dump which says the following.
Error analysis
Short text of error message:
Implementation of Method ATTRIBUTE_CONVERSION for BAdI /SAPCND/ROLLNAME for filter MATKL is missing
Program............. "/SAPCND/CL_MNT_COND_MAINT_UI==CP"
Screen.............. "/SAPCND/SAPLCOND_MAINTAIN 0100"
Screen line......... 8
Information on where terminated
Termination occurred in the ABAP Program "/SAPCND/CL_MNT_COND_MAINT_UI==CP" -
in "ON_FCODE_SELECT".
The main program was "/SAPCND/GENERAL_COND_MAINT ".
In the source code you have the termination point in line 622
of the (Include) program "/SAPCND/CL_MNT_COND_MAINT_UI==CM005".
Please let me know the solution, Request you to do the needful aSAP.
Regards
*Ramesh*

Hi Ramesh,
Have you checked the following note?
Note 441083 - Transferring conditions for material group MATKL to CRM
Kind regards,
Johan Wigert

Query regarding condition type value calculation in VA05

Dear Gurus,
We had maintained one condition type Z*** where we had declared the condition type as follows:
Condition class - Prices
Calculation type - Quantity
Plus/Minus - A (positive).
We had maintained the condition table as :
Price = 200 USD per 10 EA
Lower limit = uppler limit = 0.
When we are calculating the price in the sales document, the system is taking the price of 10 units as 200 USD correctly.
But in VA05 screen, the confirmed net value for 10 units is shown as 10*200 = 2000 USD which is wrong.
Can anybody throw a light on how the confirmed net value for VA05 screen is calculated.
regards,
Krishna

If it is representing the value of the condition type, then it is a new field customised by your technical team. Standard VA05 doesnot represent the value of any condition type. So please check with your developer, may be there is a problem in their program.

Regarding Condition Index

Similar Messages

Maybe you are looking for