Support for Application-Period Temporal Tables

System-period temporal tables are great, but "system-time" is not appropriate in many applications. Quoting from an article by Philip Nelson on DB2 Temporal Support - A Practical Introduction:

Temporal support consists of two key concepts : system time and business time. System time support can be thought of as an audit trail of when changes occurred to data (although it may not in itself suffice as an audit trail for regulatory purposes without other safeguards being built in). Business time defines when data is effective from a business point of view.

In DB2 for LUW it is referred to as Application-Time Temporal Support.

Application-time temporal support allows:

• Using the history to provide undo/redo support

• Business applications: Price changes for a future date, adjusting transactions (i.e. adjust effective date due to late delivery), retroactive (transaction entered after event took place), automatic purging or "death of row" on the assigned end date, and many other applications

• Vendor or home grown System management and change control applications: Ability to schedule a policy change in advance, schedule job change, on boarding and off boarding activities in advance (i.e. add/remove application menu access), ability to record a change with proper date and time after it took place

• There are thousands of other examples and applications