You can add a version of a record that is effective for a new period.
If you enable contiguity of records in the base object, the
MDM Hub
ensures that the record versions have contiguous effective dates. The
MDM Hub
extends the effective period of the record version that is adjacent to the record version that you add to maintain contiguity.
Configure the staging table column to add new record versions and C_REPOS_TABLE column to ensure contiguity of record versions.
To add record versions during a load batch job, configure the following settings:
TIMELINE_ACTION. Set the value of the TIMELINE_ACTION staging table column to
4
. When you set the property to
4
, the
MDM Hub
can add new record versions. The TIMELINE_ACTION column is mapped from the corresponding landing table column.
TIMELINE_FILL_ON_GAP. Ensures that contiguity between the effective dates of record versions is maintained when you add new record versions. Set the property in the C_REPOS_TABLE of the Operational Reference Store or in the Staging Table properties of the Hub Console.
If set to
true
, when you can add a new record version to the base object, the
MDM Hub
maintains the contiguity between effective periods of record versions. If set to
false
, the
MDM Hub
rejects any addition of record version that breaks the contiguity between effective periods of record versions. The default is