SPDD Reset as original on a table index

[benoit-schmid]

Hello,

We have SAP tables with added indexes that are detected by SPDD

as an index creation is considered as a modification.

If I choose reset as original or accept proposal, the result is the same.

The index is preserved as far as I have seen.

1. Is there a difference that I have missed?

From my understanding, reset as original should remove the modification.

In this case the created index is considered as a modification.

2. Why is it not deleted if I choose reset as original?

Thanks in advance for your answer.

[martin_E · Accepted solution]

Without seeing the SPPD output, the starting Support Pack / Stack, the target Support Pack / Stack level and so on, I can't be too definite, but ....

It could be as simple as the creation of the index being in response to an OSS correction that is now incorporated in the Support Packs you've just implemented. I've seen similar results when people make changes manually rather than using SNOTE.

hth

[benoit-schmid · Accepted solution]

Hello,

Martin English wrote:
Without seeing the SPPD output, the starting Support Pack / Stack, the target Support Pack / Stack level and so on, I can't be too definite, but ....
It could be as simple as the creation of the index being in response to an OSS correction that is now incorporated in the Support Packs you've just implemented. I've seen similar results when people make changes manually rather than using SNOTE.

I suppose that it does not correspond to indexes provided in a OSS correction as the name of the indexes begin with Z.

Does this answer your questions?

From the transaction se95, can I provide you more informations?

Anyway, would you know:

Why is it not deleted if I choose reset as original?

Thanks in advance for your answers.

[JPReyes · Accepted solution]

Hi Benoit,

It might have been highlighted as overlapping with the updated SAP table/index...  But been a custom index SPDD should not interphere with it.

From my understanding, reset as original should remove the modification.

The index is preserved as far as I have seen

Yes, but again in this case is a custom index and as long as it has not affected SAP original data its should be kept.

Regards, Juan

[benoit-schmid · Accepted solution]

Hello Juan,

Juan Reyes wrote:
It might have been highlighted as overlapping with the updated SAP table/index...  But been a custom index SPDD should not interphere with it.

Do you mean that as far as you have experienced, you never had to perform SPDD for

customer created indexes on standard SAP tables?

Do I have a way of knowing why our table is considered as modified?

Thanks in advance for your answer.

[JPReyes · Accepted solution]

You should talk to the abaper that did the modification. He should be able to talk to you about the nature of it.

Regards, Juan

[benoit-schmid · Accepted solution]

Hello,

Juan Reyes wrote:
You should talk to the abaper that did the modification. He should be able to talk to you about the nature of it.
Regards, Juan

Unfortunately, I know this developer.

But he has no clue on what a SPDD is 🙂

As requested I send the graphics of the SPDD:

Thanks in advance for your answers.

[JPReyes · Accepted solution]

In the image you can appreciate that SP SAPKH60412 does introduce a Z1 index for BKPF (Which already had a Z1 index created long ago) but as you can see the attributes and index fields are Unchanged... so doesn't matter if you reset to original or accept proposed changes.  😄

Regards, Juan

[benoit-schmid · Accepted solution]

Hello Juan,

You are saying that SP 12 has created this index.

You are right but I was wrongly convinced that it was a customer index as it begins with Z.

How can you ensure that Z1 delivered by SAP is identical to our current Z1?

Is it because you have unchanged in general attributes and in Fields?

Thanks in advance for your answers.

[JPReyes · Accepted solution]

You are saying that SP 12 has created this index.

I'm saying that in SPDD you can see a new version of the index created by the SP.

How can you ensure that Z1 delivered by SAP is identical to our current Z1?
Is it because you have unchanged in general attributes and in Fields?

The image shows a comparison between the two versions of the indexes.

Regards, Juan

[Former Member]

Hello Benoit,

Can you explain a little more: Check this Snote:

https://service.sap.com/sap/support/notes/1658376

Also check

SPDD Adjustment for Database indexes during the Upgrade

http://www.sapdev.co.uk/upgrade/sap-spdd.htm

Regards

Alen

[Former Member]

Why you created this index? Can you provide sceenshot from SPDD?

[benoit-schmid]

Hello Roman,

Roman N wrote:
Why you created this index? Can you provide sceenshot from SPDD?

These indexes dates from 2004.

It is a developer that has created them.

As I am not this developer, I can only guess why he has created:

He thought that he could do much better tuning than SAP by noticing

a bad query plan in st05.

I think he did not realize the possible bad impacts of creating a index.

But this is another question 🙂

I do not have a screen shot of the SPDD.

But it just shows the table and the associated indexes.

Which other details would you like?

My question 1. and 2. are still open.

Regards,