Dear EHS community
Now using EHS classic for a long time a issue has been detected in EHS standard import. During maintenance of EHS data normally using CG02 the system is always using the default "Data origin" specified in customizing to be stored in EHS tables (e.g. ESTRH, ESTRI etc.). In standard process to import specification data one can define a different "Data origin". Now we are using an import file with default" data origin and executed the import. Now a strange effect has been detected (and not always) for update of identifiers. For the import purpose you must nominate at least one identifier. If the identifier is found then normally no update happens but only the value assignment data is inserted (or updated). If the identifier is not found it get be inserted on spec level in ESTRI. Now during the update the "Data origin" of the identifier present in the system (and which matched to identifier on file level) was changed but not the identifier as such. Any data record on value assignment level received the defautl data origin. Actually there is no explanation for this behaviour. If Default "Data origin" would be "SAP" (as the term) this value has been change to "Space". Any explanation of this effect is appreciated (or and idea regarding that).
C.B.
PS: analysis of change logs in EHS etc. executed so far clearly indictae that an "Update" happened on the identifier; but only the field SRSID is effected; EHS import is quite old and therefore very stable;
PPS: I found a thread taking about the import file:
Example shown thre is like:
+BS
+BV $ESTRH
SRSID EH&S
SUBID 000000385000
SUBCAT REAL_SUB
AUTHGRP EHS_PS
+EV
+BV $ESTRI
SRSID EH&S
IDTYPE NAM
IDCAT EHS_OLD
IDENT XY0002
ORD 0001
+EV
+BV SAP_EHS_1013_001
$ESTVA-SRSID EH&S
SAP_EHS_1013_001_VALUE N09.00101280
+EV
If you compare SAP helpt normally only at the"begining pof the file you will find "SRSID" Here this field is nominated often. On Level of ESTRH as well as ESTRI.
PPS: e.g. refer to: TCG56 EHS: Data Origin - SAP Table - ABAP