Performance of MIRO transaction very poor

[Former Member]

Dear Friends,

Right since the implementation of SAP Note dealing with the Secondary Higher Education Cess (in the context of India only) the MIRO transaction has been taking hell lot of a time to complete. With the help of SQL trace (ST12 & SE30) we came to know that it's was during the fetching of data from two tables namely RSEG & RBKP.

When we further analysed these tables we didn't find any index on RSEG and it seems that this could be the root cause of this problem.

I'll welcome your comments/solution on our findings in addition I'd also like to know what indexes have been defined on RSEG in your system.

In waiting of your response,

Alok.

[Former Member]

The primary key of RBKP should be a partial of the primary key for RSEG ?

Check the indexes existing in the ABAP repository. Maybe you just need to implement them to the DB...

Enjoy

[Former Member]

Thanks Brandelik for responding but kindly let me know is there any risk involved in implementing the non-database indexes to database level. In the RBKP table I have following 5 indexes.

1.Vendor: Fields included are as following

MANDT Client

LIFNR Different invoicing party

2. Reference Document Number, Vendor, Company Code

Fields are:

MANDT Client

XBLNR Reference Document Number

LIFNR Different invoicing party

BUKRS Company Code

3. User, Invoice Document Status, IV Category

Fields are:

MANDT Client

USNAM User name

RBSTAT Invoice document status

IVTYP Origin of a Logistics Invoice Verification Document

4. Invoice Document Status, Vendor

Fields are:

MANDT Client

RBSTAT Invoice document status

LIFNR Different invoicing party

5. Created By, Invoice Document Status, IV Type

Fields are:

MANDT Client

ERFNAM Name of the Processor Who Entered the Object

RBSTAT Invoice document status

IVTYP Origin of a Logistics Invoice Verification Document

Out of these five no.1 & 5 are on 'All database systems" and rest three are "No Database Index". ( Here I am referring to the Display Index (SE11)...Non-unique Index description.

Regards,

Alok.

[Former Member]

Hi Alok,

Check OSS with "MIRO" and "performance", you should get responses ...

Hope this helps,

erwan

[KKilhavn]

Risks (disadvantages):

1) Indices take up bytes too, so more database space is needed.

2) Indices must be updated, so your table updates will be a little slower.

Advantages:

1) If an index is used: speed increase when selecting data.

2) If none of the indices are used: no advantages.

The primary issue is whether the indices will be used or not. If they will, the advantages will probably outweigh the disadvantages.

[KKilhavn]

There's always a primary key index, isn't there? Did that OSS Note add a select statement that doesn't specify the primary key?