DDSHPVAL50

[Former Member]

Hi experts,

The DDSHPVAL50 table is not always cleaned at the end of the help process.

This is has impact for some users with some F4 help who cannot find some object.

Do you have a idea why this table is not cleaned?

Thanks

[Former Member]

Hi experts,

The DDSHPVAL50 table is not always cleaned at the end of the help process.

This is has impact for some users with some F4 help who cannot find some object.

Do you have a idea why this table is not cleaned?

Thanks

[Clemenss]

Hi Marc,

may I suppose that this happens in a custom search help created in your system?

Then you can check the search help exit function group global data.

Otherwise, please give the name of the search help where this happens or at least the context.

Regards,

Clemens

[Former Member]

Hi,

You are right, it's a "Z" help search, but the table DDSHPVAL50 is not used.

I don't uderstant how this table is filled.

Thanks.

[Clemenss]

Hi Marc,

SEARCH HELPs are a quite tricky area. Derived from the formerly used matchcodes, I am sure more than a dozen SAP developers have been upgradfing, correcting and renewing code.

In the Search help exits, deep structures with tables in tables are passed and it is hard to say which part of what has a reference to DDSHPVAL50.

Some developers tend to put values into memory (SET/GET memorry ID ..) in the application to make them available in the search help exit. If this memory is not cleared, it may be used unwanted.

Set a breakpoint in the search help exit function in question or just do an analysis: After GET MEMORY ID ..., this memory ID should be cleared (SET MEMORY with empty data), global data in the search help exit function should be cleared if not used any longer.

Regards,

Clemens

[Former Member]

Hi Clemens,

The problem is unfortunately not recurring and so, it's difficult the reproduce it.

That must make 2 or 3 months that this case is not appeared.

But for information i don't see any 'get/set memory' statement in the search help coding.

Regards,

Marc

[Former Member]

Use report UMG_F4_CLEANUP to remedy this situation