Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Duplicate Key Trouble

Former Member

‎2006 Oct 03 6:34 PM

0 Likes
731

Hi All

I have beeen aske to create snapshots of certain tables basically freeze a point in time. There are 8 tables I have to do this for. I have done it and it works fine except for 1 table. The other 7 I copied the original tables added a snapshot date field as a key field called SS_date. Then copied the records with a different date for each set.

One Table does not allow me to add the records after the initial set saying the new ones are duplicates even with the ss_dt being different I am stumped as to why. The first table for instance has only 1 key fiels vtgnr which is treaty number. So I copied the table added the ss_dt as a second key field and no problems. The other 6 tables have multiple key fields. Again all I did was copy the table add the ss_dt as a key and made sure it was different for each new set.

The one table that will not allow it is no different than the others in terms of how it is defined etc Anyone have any idea's what the problem might be?

Thanks

Hi All

I have beeen aske to create snapshots of certain tables basically freeze a point in time. There are 8 tables I have to do this for. I have done it and it works fine except for 1 table. The other 7 I copied the original tables added a snapshot date field as a key field called SS_date. Then copied the records with a different date for each set.

One Table does not allow me to add the records after the initial set saying the new ones are duplicates even with the ss_dt being different I am stumped as to why. The first table for instance has only 1 key fiels vtgnr which is treaty number. So I copied the table added the ss_dt as a second key field and no problems. The other 6 tables have multiple key fields. Again all I did was copy the table add the ss_dt as a key and made sure it was different for each new set.

The one table that will not allow it is no different than the others in terms of how it is defined etc Anyone have any idea's what the problem might be?

Thanks

Reply
4 REPLIES 4
Read only

Former Member

‎2006 Oct 03 6:38 PM

0 Likes
696

So the problem table has all of the key fields of the original one plus SS_DATE also as a key. Is that correct?

Rob

Read only

Former Member
In response to Former Member

‎2006 Oct 03 6:59 PM

0 Likes
696

Yes that is correct, If I try to remove a field from being a key in the copied version I get a wack of warning messages and it will not activate. I cannot remember what trans allowed table key modifications etc. That may also be a way to go if I can remember what trans revalidated the table etc

Read only

Former Member
In response to Former Member

‎2006 Oct 03 7:01 PM

0 Likes
696

After the first set if inserts (ones that work), what is the value of SS_DATE? Is it initial?

Rob

Read only

Former Member
In response to Former Member

‎2006 Oct 03 7:08 PM

0 Likes
696

More Info, The field ss_dt has both key field and initial values checked, The first load had sy-datum as the ss_dt. Each adjacent load had a different date for all the tables. The temp fix I have at this point is that for each new date I added a letter to the treaty number. IE if the original treaty number is 2218180 for Sept 22 the it is A2218180 for July 23 this solves the problem for loading the table. But it is a major hassle in the adjustments I have to make to the programs that actually use this table not to mention the additional coding I had to do for table joins. So although it works it is not a long term practical solution