Skip to Content

Characteristics Internal key

Hi ,

Although we have not yet seen data consistency problems caused by that it is thoretically possible as in EHS surrounding the “characteristic” is used as “speaking” key whereas the “real” key is the internal characteristics number:

M000 comparison it can be seen that SAP solved that problem by renaming the “wrong” instance BUT before doing so we would need to analyze the side effects on existing data.

In TCGA6 no entries available with SAP_EHS_1011_001_ADVICE_OBS

I know that the “obs” one is not to be used, that’s why it has been introduced.

But before making the existing one “obs” you will have to ensure that there was no data maintained yet on the internal technical key…



cabn.png (154.8 kB)
m000.png (169.0 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 23, 2017 at 06:32 PM

    Dear Satya

    i need to read a "lot between the lines"... please improve your question/doubts

    This is my interpretation

    1.) you have received an update of property tree (e.g. using content)

    2.) you have installed an SP

    During this action you realized that for some internal keys the external keys was the same and now they are different.

    I believe we need to split this topic using many "subtopics"

    1.) is there data ? (in old characteristic)

    2.) what effect might be on e.g. WWI layouts

    3.) etc.

    If i remember correct: the data is stored usign ESTVA and AUSP. in AUSP the "external key" is used (if i remember correct).

    For WWI: it is clear that you need a new report symbol

    For all the othere doubts out there. not sure about; can you please explain better what has happened ...


    Add comment
    10|10000 characters needed characters exceeded