Extraction of the Master Data During Migration (CNS)
Note
This document describes the extraction of master data during a migration from a legacy system into the Account Management (FS-AM)
system for DataSources that use the Change Notification Service (CNS).
The following master data is extracted during the migration:
Data that is assigned to a migration group and has BW-Relevant
or BW-Extracted
as status
Data that is not assigned to a migration group, but involving productive contracts from a phase before the migration.
When updating table CNS_CP
at the DSAVE
(save contract) timepoint for migrated contracts, the system determines the migration group of the contract, checks if it is being migrated, and transfers it to the change pointer.

Determination of the change pointers at the DSAVE timepoint
The entries for migrated contracts in table CNS_CP
are given value M
as migration status in the GROUP_ID
field.
This ensures that the system does not include the entries in the extraction.
If errors occur during migration and you need to remove a migration group from the source system, you must delete all entries with extraction status M
from table CNS_CP
.
To do this, use the report for deleting and archiving (RBCA_UNDO_MIG_GRP
). Depending on the release, this report calls one of the following function modules:
BANK-TRBK 3.0 or 4.0: BCA_TBBW_MIG_DEL_CNS_CP
FSAPPL 100: BCA_CNS_MIG_DEL_CNS_CP
The (respective) function module deletes the entries from table CNS_CP
in accordance with the migration group status of the incorrect migration group.
For more information, see the report documentation in the system.
If the migration group is labeled as BW-Relevant
, you must change the extraction status of all entries with status M
to status (initial). This ensures that the entries are included again by the extractors.
Depending on the release, use the following reports to do this:
BANK-TRBK 3.0 or BANK-TRBK 4.0: RBCA_PP_SIF_TBBW_CNS_CHG_GR_ID
FSAPPL 100: RBCA_PP_SIF_BCA_CNS_CHG_GR_ID
.
For more information, see the report documentation in the system.
Note
Due to the increased data volume during the migration, it is advisable to increase the number of InfoPackages for the extraction.
Caution
In an existing migration group, errors can occur at a time at which the status of the migration group is already BW-relevant
.
In this case, you must first identify the contracts that were extracted with this migration group (all contracts already have value " " in the GROUP_ID field) and then delete them from table CNS_CP
.
For this case, you need to create a program that identifies and deletes the data records in question in the BW system.
This can result in serious performance problems in the BI system.