This is version 1 2 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

Converting Date Sensitive information#

Multiple records for the same object may be loaded, as long as they are for different effective dates. For example, if you wish to load a Department with two date-effective records, you would create two records on the interface file for the same DEPARTMENT_CODE, but would differentiate them with two different EFFECTIVE dates. The day that the change occurred would be used to specify the effective date of the second record.

When the conversion routine inserts the second record it will alter the expiry date of the first record already on the software table. The new expiry date will be set to the effective date of the current record minus one day. If the value of the expiry date of the existing record was after the expiry date of the new record, a gap in time of the date-sensitive table will be created. In order to resolve the gaps in time that are generated by loading these effective date-sensitive records in the software tables, an additional script must be run. Each date-sensitive table has a date adjustment script that can be accessed from the Utility menu of the Conversion Application. These adjustment scripts MUST be run for each date-sensitive table that is loaded with conversion data. These scripts will adjust the records within the P2K tables, not the interface tables. The expiry date of each record is altered to fill in the gaps generated by the effective date records. Since the effective date cannot be altered, record number one in the diagram will not be changed. Instead, a new record will be created to fill the gap in time. The new record will have an effective date of the Beginning of time, and an expiry date of the day prior to the effective date of record number one.