Is it worth creating secondary index on BKPF table ?

Hello,
One of my clients is using ECC version 5.0. I have a requirement wherein I need to fetch the data from BKPF table based on AWKEY, BUKRS and GJAHR. There is no standard secondary index available.
I have decided to create a secondary index on these fields in the following order:
1) MANDT
2) AWKEY
3) BUKRS
4) GJAHR
I know that creating secondary indexes does improve performance during data retrieval. But when I checked the total number of entries in BKPF table in production system, there are more than 20 lac 2 million records.
I am worried that creation of secondary index will create another table of such a large size in production that has data sorted on the above fields. Also, the RAM of production system is 6 GB.
Please suggest if creation of secondary index is a good measure OR should I recommend the client to increase the system RAM?
Regards,
Danish.
Edited by: Thomas Zloch on Oct 3, 2011 3:01 PM

Hi,
Secondary Index on BKPF-AWKEY has been successfully created in production. The report which used to timeout in foreground as well as in background is now executing in less than 10 seconds !!
Client is very much satisfied with this. But, there is one problem that we are facing now is that when the user is changing an existing billing document via VF02, on SAVE, system takes a very long time to save the changes done.
We monitored the processes via SM50 and found that there was a sequential read on BKPF table.
Before transporting the index in production, system approximately took not more than 5 seconds to save the Billing Document. But now system takes more than 20 minutes just to save the billing document via VF02.
I really don't know what has gone wrong. I can't figure out if I have missed any step while creating the index.
I did the following,
1) Created a Secondary index on BKPF, saved it in the transport request and activated it. Since the index was not existing in database ORACLE, I activated and adjusted the table via SE14. Now, index exists on database as well. Working perfectly in development.
2) Imported the transport request to Production. Checked in SE11. Index was existing and active. Also, index existed in database ORACLE.
Have I missed anything ? Is it required to activate and adjust the database via SE14 in production too ?
Regards,
Danish.

Similar Messages

Can we create secondary index for a cluster table

hi
can we create secondary index for a cluster table

Jyothsna,
There seems to be some kind of misunderstanding here. You <i>cannot</i> create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).
Hope this clarifies things,
Mark

What is the "No database index" means when you Creating Secondary Indexes?

HI,
   I'm Creating Secondary Indexes in the maintenance screen of the table(se11)
   There are three options under "Non-unique Index":
   1.Index on all database systems
   2.For selected database systems
   3.No database index
My questions is :
What do u mean by "No Database Index" and when is it used.
Can anybody plz tell me what's the difference of this three options ?
Here is what i found in the help:
   No database index: The index is not created in the database. If you
   choose this option for an index that already exists in the database,
   it is deleted when you activate this option.

Hi,
It is clear from the help documentation,
Here see what the help document says:
Create the index in the database (selection)
Whether an index improves or worsens performance often depends on the database system. You can therefore set whether an index defined in the ABAP Dictionary should be created in the database.
This makes it easier to install a platform-specific customer system.
You can set this option as follows:
1. Index in all database systems: The index is always created in the database.
2. In selected database systems: The index is created depending on the database system used. In this option, you must specify the databases in which the indexes are to be created. You can do this either on an inclusive (list of systems on which it should be created) or an exclusinve (list of systems on which it should not be created) basis. In either case, you can list up to four different database systems.
3. No database index:: The index is not created in the database. If you set this option for an index that already exists in the database, it is deleted when you activate the table in the ABAP Dictionary.
Note: Unique indexes have an extra function, and must therefore always be created in the database. The database system prevents entries or index fields being duplicated. Since programs may rely on this database function, you cannot delete unique indexes from the database.
Hope it helps you,
Regards,
Abhijit G. Borkar

Can we create secondary indexes in pooled and cluster table?

hello all
can we create secondary indexes in pooled and cluster table?

Hi,
Yes, you can.
Refer the below links
[http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm|http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm]
[http://help.sap.com/saphelp_40b/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm|http://help.sap.com/saphelp_40b/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm]
Regards,
SB

Guidelines to create secondary index

Hi Guys,
I'm trying to get a guidelines to create an optimize secondary index. For eg, how to analyze the list of fields should be included into the secondary index. What can be done and not.
Pls place your comment.
Thanks in advance.

Hi,
Basically index are provided to improver performance. i.e with index select on database tables retrieves data much faster.
If you are writting select statement on the table where in where clause you have non-primary keys then it takes longer to retriev data from Database table.
If you have select in dbtable on non-primary key you can create Secondary index with keys as per your where clause which result in faster Database table access.
But remember not to create too many secondary indexes on same table which could result in slow / degrage performance..
and also check this link :
http://help.sap.com/saphelp_470/helpdata/en/cf/21eb20446011d189700000e8322d00/frameset.htm
Regards
Appana

Creating secondary index

Hi all,
Plz explain me how to create secondary index.
How to generate interactive report using ALV.
Thanks in advance
Venkat

GO to Resuse library ther 'SE83' there you will find interavtive alv demo programs.
GO to SE11 and open the table. you will find 'Indexes' button in application tool bar to create indexes for table.
Regards,
Wasim Ahmed
Message was edited by: Wasim Ahmed

Is it possible to created secondary indexes on ODS in Production

Hi,
Is it possible to created secondary indexes on ODS in Production System. I need to create secondary indexes on ODS but it is already in production. Hence Can I directly create secondary indexes without transportation from dev to production?

Hi,
Secondary Indexes for DSO can be transported. For the transport the DSO objects needs to be transported (R3TR ODSO <technical name>.
Additionally, secondary Indexes are necessary quite often for DSO tables, which can be transported. In few cases you need indexes on other BW tables, but they cannot be transported. Never create additional Indexes on InfoCube tables (like E- and F-Fact tables and Dimension tables)
Thanks & B.R.
Vince

How to create secondary indexes in DB2e from MI

Hello,
we need to create secondary indexes in the DB2e SyncBO tables for a SynBO containing several thousands entries.
We create it manually and works fine, but we have to distribute
this to every user (about 300).
Is there a way to distribuite this index creation for an
application from a central location (WebConsole)?
Or,
is there any attribute in the SyncBO definitions for creating indexes on selected fields in teh database?
Thanks in advance and best regards,
Angel

Hi,
I found the way to create the indexes. In the metadata
function of the SyncBO builder, you can mark any field
as index (either in the header or in the detail tables).
This creates a secondary index in the database per marked
field.
Regards,
Angel

How to create Secondary Index?

Hello All
Can anyone let me know how to create secondary indexes?
I hope Primary Indexes are being created automatically?V can'nt able to create this.
regards
balji

Hi,
1) Go to Se11 select table /BI0/A<ODS>00 > Utilities> Data bse Object --> Check.
2) If you are using ODS Active table in any Start routine ,Make sure that the order of objects to be seleccted (select statement) should be in same order of index fields.
In Query, Use RSRT to know the SQL statement of the Query .and follow same logic explained above.
3) No need to create Secondary Index for Cube.
4) IT recreates the Index.
With rgds,
Anil Kumar Sharma .P

Indexes for bkpf table

Hi all ,
I created secondary indexes as per given thread bu vikrant , but hw to use this index in program.
reply me.
bye ,
jyotsna

Continue your thread here: error when selecting bkpf table
Thread locked.

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

Creation of secondary index on RSPCPROCESSLOG table

Hello guys,
We have detected severe performance issues while executing the transaction ST03n in our BW 3.5 System.
Looking in the OSS notes we found the note "SAP Note 841324 - ST03N: poor performance for process chain profile" where it recommends the creation of a secondary index in the table RSPCPROCESSLOG with the following features:
Create another secondary index on the RSPCPROCESSLOG table with the
following fields:
- INSTANCE
- TYPE
Can you please let us know what is the step by step to proceed with the creation of this secondary index?
Thanks for your help.
Kind regards

Please ask questions about Oracle Text (formerly interMedia text) in the Oracle Text forum. You will get a quicker, more expert answer there.

Secondary index on vbfa table

I have very expensive statement running against VBFA table. It comes from a customer report and doing SQL:
SELECT /*+ FIRST_ROWS */ "VBELV"
FROM "VBFA"
WHERE "MANDT" = :A0 AND "VBELN" = :A1 AND ROWNUM <= :A2
It has execution plan:
SELECT STATEMENT ( Estimated Costs = 96.009 , Estimated #Rows = 41 )
|
--- COUNT STOPKEY
|
INDEX RANGE SCAN VBFA~0
As you can see it is very expensive statement because VBFA is huge table and because I have only VBFA~0 index with columns:
UNIQUE Index VBFA~0
COLUMN DISTINCT VALUES
MANDT      1
VBELV       1.589.207
POSNV      4.184
VBELN       3.202.114
POSNN       58.173
VBTYP_N    18
In order to improve performance of this report , would you recomend creating secondary index and would it be on columns: MANDT, VBELN, VBELV
I have not seen this type of secondary index in SAP community (most of the time I see sec.index on mandt, vbeln and posnn columns) so that is why I want to double check it before I deploy it.
Regards,
Andrija

Hi,
Indexes speed up access to rows in a table. They can be created for a single column or for a series of columns.
MANDT AND VBELN does not have index then create indexes on these columns.
The explain statement can be used to check the effect of creating or deleting indexes (see index) on the choice of search strategy for the specified SQL statement. You can also estimate the time needed by the database system to process the specified SQL statement. The specified QUERY or SINGLE SELECT statement is not executed while the EXPLAIN statement is being executed.
To be frank to analyze you shd generate trace file and you need to analyze.
Oracle claims that <b>first_rows_n</b> optimization results in faster response time for certain queries, we must remember that the performance is achieved via a change to the costing.
Use the FIRST_ROWS hint when you need only the first few hits of a query. When you need the entire result set, do not use this hint as it might result in poorer performance.
So collect stats,Analyze table create index your query will execute faster.
Analyze in trace file generated.Want to know indexes are used or not have a look on Explain Plan.
Regards
Vinod

Secondary Index for the table MSEG

Hi folks,
One of my report is comparetively very slow when it is executed in the production server. when i chked, a query related to the MSEG table is taking more time to execute. I want to create a secondary index for that table. Could any body tell me the procedure of creating the seconday index for the table MSEG, as i am not aware of that.
Thanks in advance,
Shyam.

Dear shyam,
Search SDN before posting any thread their are 10k threads available for your question anyhow for your reference here is one link
http://help.sap.com/search/highlightContent.jsp
Cheers
fareed

Use secondary index in internal tables.

what are the uses of secondary index in internal table?

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb47446011d189700000e8322d00/content.htm
Creating Secondary Indexes
Proceed as follows to create a secondary index on a table:
In the field maintenance screen for the table, choose Goto --> Indexes.
1. If you went to the field maintenance screen of the table in display mode, only correct the index (and not the table).
If indexes already exist on the table, a list of these indexes is displayed. Choose Create. A dialog box appears in which you must enter the three-place index identifier. If there are no indexes, go directly to the dialog box.
2. Enter the index identifier and choose Continue.
You will go to the maintenance screen for indexes.
3. Enter an explanatory short text in the field Short text.
Choose TabFields.
4. A list of all the fields of the table is displayed.
5. Select the fields which you want to copy to the index.
6. Choose Copy.
The selected fields are copied to the index.
7. If the values in the index fields already uniquely identify each record of the table, select Unique index.
A unique index is automatically created on the database during activation because a unique index also has a functional meaning (prevents double entries of the index fields).
8. If it is not a unique index, leave Non-unique index selected. In this case you can use the corresponding radio buttons to define whether the index should be created automatically on the database for all database systems, for selected database systems or for no database system.
9. If you chose For selected database systems, you must specify these systems.
You have two possibilities here:
List of inclusions: The index is only created automatically during activation for the database systems specified in the list. The index is not created on the database for the other database systems.
List of exclusions: The index is not created automatically on the database during activation for the specified database systems. The index is automatically created on the database for the other database systems.
Click on the arrow symbol behind the radio buttons. A dialog box appears in which you can define up to 4 database systems. Use the corresponding radio buttons to decide whether this list should be treated as a list of inclusions or exclusions.
10. Activate the index with Index ® Activate. The activation log tells you about the flow of the activation. Call it with Utilities ® Act.log. If an error occurred when activating the secondary index, you will automatically go to this log.
The secondary index is automatically created on the database during activation if the corresponding table has already been created there and index creation was not excluded for the database system.
Reward points if useful.

Is it worth creating secondary index on BKPF table ?

Similar Messages

Maybe you are looking for