Shared Objects/Memory (SHMA)

[kmoore007]

I have a question about the "new" shared objects/memory (tcode SHMA). Could it be used to increase performance for accessing a text table like table MAKT?

For example, we have several programs which access the material text table (MAKT) usually with a SELECT SINGLE command. This can cause many database reads for some reports.

Just wondering if this would make sense or not.

Thanks.

[naimesh_patel]

For Text tables, "Reading" the Shared Objects would be easy, but "Updating" would not be that easy.

To update the shared object, you need to open the ojbect for update from all the places from where the text table is being updated. E.g. MAKT from the Material Master (and somewhere else, I don't know).

Shared Objects would be good when you are not dealing with the data which can be directly updated from Production. E.g. Configuration data.

Regards,

Naimesh Patel