This section describes
the behavior of forms that incorporate DateTracking. When you begin to
update or delete a record on a DateTracked form, you are prompted with a number
of choices. This section describes the choices and their effect on the
DateTracked table.The term "today" refers to the effective date set
by the user.
UPDATE RECORD
When a user first alters
a field in a DateTracked block he sees a choice of Update prompts as follows:
- UPDATE - Updated values are written to the
database as a new row, effective from today until 31-DEC-4712. The old
values remain effective up to and including yesterday.
- CORRECTION - The updated values override the
old record values and inherit the same effective dates.
If the user selects
UPDATE, DateTrack checks whether the record being updated starts today. If it
does, a message warns that the previous values will be lost (because DateTrack
can only store information on a day by day basis). DateTrack then changes the mode
for that record to CORRECTION.
Next, if UPDATE was
selected, DateTrack checks whether the record being updated has already had
future updates entered. If it has been updated in the future, the user is
further prompted for the type of update, as follows:
- INSERT (UPDATE_CHANGE_INSERT) - The changes that the
user makes remain in effect until the effective end date of the current
record. At that point the future scheduled changes take effect.
- REPLACE (UPDATE_OVERRIDE) - The user's changes take
effect from now until the end date of the last record in the future. All
future dated changes are deleted.
In most forms, users are
prompted for the update mode for each record they update. In
some forms, they are asked for the update mode for only the first record
they update. Any other rows updated take the same update mode. Users are not
prompted again, until they have committed or cleared any outstanding changes.
When deleting a record,
the user is prompted for the type of delete. There are four options, as
follows:
- END DATE (DELETE) - This is the DateTracked delete. The
record that the user is currently viewing has its effective end date set
to today's date. The record disappears from the form although the user can
re-query it
- PURGE (Zap) - This is the total delete. All records
matching the key value, whatever their date stamps, are deleted
- ALL (Future Change) - This choice causes any future
dated changes to the current record, including a future DateTracked
delete, to be removed. The current record has its effective end date set
to 31-DEC-4712. The record can again be displayed by re-querying
- DELETE NEXT CHANGE (Next Change) - This choice causes
the next change to the current DateTracked record to be removed.
Where another future dated DateTracked row exists for this record, it is
removed and the current row has its effective end date set to the effective
end date of the deleted row
Where no future
DateTracked row exists, but the current row has an end date other than
31-DEC-4712, then this option causes the effective end date to be set to
31-DEC-4712. This means that a date effective end is considered to be a change.
Notice that this option again removes the current row from the form, though it
can be displayed again by re-querying.
INSERT
RECORD
The user is not prompted
for any modes when inserting a record. The effective start date is always set
to today (Effective Date). The effective end date is set as late as possible.
Usually this is 31-DEC-4712, although it can be earlier especially when the
record has a parent DateTracked record.
List of DateTracked Tables
To get a list of the
DateTracked tables used in Oracle Human Resources, select from the data
dictionary where the table name is like <Application Short Name>%F.
Substitute in the HRMS application short code you are interested in (such as
PER or BEN).
For each of the DateTracked tables there is a DateTracked view called <TABLE
NAME> and a synonym pointing to the full table called <TABLE NAME_F>.
e.g. per_all_people_f, per_all_assignments_f, etc.
No comments:
Post a Comment