Duplicate entries in ESTVH table

[Former Member]

Hello all

I have noticed ,some times while updating the data at same value assignment level  by different users from various locations with in the difference of  minutes / Hours  time. some time duplicate entry were creating in ESTVH table which was not correct.

entry of ESTVH will be created only once that too at the time of intial data maintenance at value assignment

Later always records should be updated in ESTVA table based on data updations.

But some times above mechanism not working and creating duplicate entries which impact the Automatic data updation in other systems due to failure of IDOC distributions due to duplicate entries.

Looked OSS noted in SAP , but not succeeded.

if you have any OSS notes for this from SAP . please share

Bala

[christoph_bergemann]

Hello Balajee

could you solve the isseu? If so; can you please describe appriah cused. Might be helpful for community. Thanks

C.B.

[christoph_bergemann]

Dear Balajee

do you use "Change numbers"? I am not aware of any OSS here. Long long ago strange effects as you are reporting could be detected. So my understanding is ow:

a.) user one mainatained e.g. "density" and created ESTVH data

b.) some minutes/hours later different user ,entered additional data / other data in density; and result was: second entry in table ESTVH

Can you "describe" the actions by the user "better"? Do you sue any kind of custom code in the many "Exits" etc. in CG02??

Was it a "manual" enrty or an entry via e.g. ruelset? did you used inheritance?

C.B:

[Former Member]

Dear Christoph

one case

user from Europe maintained the data in the value assignment first time via Rule set(Customized). so new entry was created in ESTVH table as well as in ESTVA

In hours difference another user from north America was updated the in the same value assignment manually. in this case in ESTVA existing entry should be marked with del flag and new entry should create and Entry in ESTVH should remain same , but it was not happening new entry(Duplicate RECN) was creating in header table and deletion flag was not set to old entry in ESTVA.

this issue was occurring randomly not all the times.

When i debugg this behaviour data flow was through standard exits only..

Bala

[christoph_bergemann]

Dear Bala

mmhh. Strange result; never  seen. Can you please check:

User 1 should maintain property manually (and not using rule set)

User 2: what was the action? If you "update" and you really do update) ESTVA should not ! get del flag. Only "admin" data should change. Only if you "delete" the whole value assignement you will get a "del flag". in ESTVA (and e.g. ESTDU etc. etc.) Why did second user change/update the data record? (as it was derived by rule set)?

In any case. if you "save" a value assignment you can use "exits, badis" etc. with your own program logic. Take a look here for example:

So my quesition was. do you use this (or similar approach)

What about use of change numebrs? are they used in this context?

Can you show the change docs as generated by the system?

PS: user from Europe maintained the data in the value assignment first time via Rule set(Customized => is this a "fresh" specification with primary data and the target property was never ever maintained either by user or by rule set?

C.B.

[christoph_bergemann]

Dear Balajee

is report

RC1PHDEL scheduled? and if yes with which parameter?

C.B.

PS: if you have "strange" effects in tables content: report

RC1SUB_HIERARCHY_SHOW is very very helpful

E.g. check: