Skip to Content

Creating an index for VBAP (ERDAT)

Hi all,

For an in-house (“Z”) program, we need to access the VBAP table by the column ERDAT (Record creation date) (using a range, in fact). The point is that, of course, there is no index with that column, so the response times are, to put it mildly, not the best…

So, I have two questions, if I may:

  • 1)How convenient is to create our own DB index for this (huge!) table?
  • 2)I have thought of creating an extension index. Is this option the most adequate?

Thanks in advance,

Luis

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Dec 01, 2017 at 10:49 PM

    EDIT: According to SAP Help, extension index is the way to go.

    We did create a secondary index for VBAP-ERDAT with no issues. But the items mentioned by Michelle should be considered, of course. This was a non-HANA system on Oracle DB, if it matters.

    As a side note, if it's a huge table you might want to consider archiving as well.

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 01, 2017 at 08:46 PM

    Can you select the data from VBAK? There is an index for the order date. If so, join VBAK and VBAP. That should improve your run time.

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks.

      Did you create your index as a Secondary Index or as an Extension Index? Also, Did you experience any significant slow down when the index was being created? Any disruption in user's apps or something like that?

      Thanks again,

      Luis