Skip to main content
Solved

History table not inserting new records to valid table from raw table

  • September 6, 2024
  • 5 replies
  • 73 views

Forum|alt.badge.img

Dear Support,

I have encountered a strange phenomenon with the history settings and need urgent support.

Situation:

Records which were once flag as new records from the ERP system show up as SCD Is Current is 0. These orders were canceled in the ERP as a next step and flagged correctly in the history raw table table as a type II change (which is correct). However, they do not get inserted into the valid table as new record. Today we realized even more records are missing in the valid table.

 

TX Version: 20.10.40.64.

Please advise on how to proceed. This is causing us major issues in our month end closing reporting. It used to be fine and we only experienced it this week.

 

Thank you.

Oscar

Best answer by Bernarddb

@o.becke i thinks one of the history settings might be wrong. If i'm understanding it correctly you are not getting new records for items that are inserted into your source table:
You probably would want your settings to look like this:
 

If you want to have records reaaper if they are deleted you will need to check the create a new record when a deleted record reappears in the source. And make sure that treat type 2 fields as type 1 when the previous field value is null is check off

 

 

Also if your source is already a historical table. then i would suggest not using the history table in TimeXtender but stay true to the source table.

View original
Did this topic help you find an answer to your question?

5 replies

Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • TimeXtender Xpert
  • 53 replies
  • Answer
  • September 6, 2024

@o.becke i thinks one of the history settings might be wrong. If i'm understanding it correctly you are not getting new records for items that are inserted into your source table:
You probably would want your settings to look like this:
 

If you want to have records reaaper if they are deleted you will need to check the create a new record when a deleted record reappears in the source. And make sure that treat type 2 fields as type 1 when the previous field value is null is check off

 

 

Also if your source is already a historical table. then i would suggest not using the history table in TimeXtender but stay true to the source table.


Forum|alt.badge.img
  • Author
  • Starter
  • 2 replies
  • September 6, 2024

Thanks Bernard. Let me work on that and see how it turns out. I did not have this setting checked. Besides that i have new records valid from 1900-01-01, is this also an issue?


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • TimeXtender Xpert
  • 53 replies
  • September 6, 2024

No that's not an issue, you can choose whatever one you would like ;) i was pointing more at the first options.


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • TimeXtender Xpert
  • 53 replies
  • September 12, 2024

@o.becke Did it fix your issue?


Forum|alt.badge.img
  • Author
  • Starter
  • 2 replies
  • September 12, 2024

Hi Bernard,

Thanks for checking. We have implemented it and saw some changes but some were unexpected. So not sure if everything works as expected. I, however, believe it helps. So we can close this topic. If i identify something related to the settings then I will reach out again.

 

Thank you very much for your support.

Oscar


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings