Considerations for excluding source records from the match process
During the ingress process, you can specify source records as not ready for match and exclude them from participating in the match process.
Excluding source records from the match process impacts the statuses of master and patch records in the following ways:
•If you specify a new record as not ready for match, the ingress process excludes the record from participating in the match process. The record remains as a source record in MDM SaaS. To include the record in the match process, you need to ingress the record again and after changing its status to ready for match.
•If a master record contains a single source record, specifying that source record as not ready for match automatically changes the statuses of the master and patch records to not ready for match.
For example, consider a source record S1 and a patch record P1 that contribute to form a master record M1. If you specify the status of S1 as not ready for match, the statuses of M1 and P1 automatically change to not ready for match.
•If multiple source records contribute to a master record, specifying individual source records as not ready for match doesn't impact the statuses of the other source records or the master record they contribute to. However, if you collectively exclude all the source records from the match process, the statuses of the source records and the master record automatically change to not ready for match. The statuses of the patch records depend on the status of the master record.
For example, consider the source records S1, S2, and S3 along with patch records P1 and P2 that contribute to form a master record M1. If you specify S1 as not ready for match, the statuses of S2, S3, P1, P2 and M1 don't change. However, if you specify S1, S2, and S3 as not ready for match, the statuses of M1, P1, and P2 automatically change to not ready for match.