When you ingress records with business IDs, the ingress job merges the records directly with the existing records even if you specify them as not ready for match. If the business IDs of records that you ingress align with the business ID format defined in Business 360 Console and the same business IDs exist in the MDM SaaS data store, the records are ingressed. Otherwise, the records are rejected.
The records don't go through the match and merge process because the ingress job considers them as existing records. When you use the Source Record API to verify the statuses of the records that you ingress with business IDs, they appear as CONSOLIDATED.
For example, you want to ingress employee records from different source systems into the MDM SaaS data store. Some records include business IDs, and some records don't include business IDs. Few business IDs don't match any existing records, and few business IDs match the existing records.
You can ingress records with business IDs that were used before a data purge, but the business IDs must be lower than the last generated business ID. The business ID format for a business entity must remain consistent before and after the purge. For example, if 999000000008899 was the last generated business ID before the data purge, you can ingress records with business IDs lower than the last generated sequence number 8899, such as 999000000007755.
The MDM SaaS data store shows the master records with their business IDs.
Business ID
First Name
Last Name
Gender
Birth Date
MDM000000000123
Mary
Williams
F
01-01-1991
MDM000000000456
John
Johnsons
M
03-03-2001
The MDM SaaS data store shows the contributing source records with their configured business ID format.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000123
CRM
Mary
Williams
F
01-01-1991
MDM000000000789
SFDC
Mary
W
F
-
MDM000000000456
SAP
John
Johnsons
M
03-03-2001
Business ID of an input record doesn't exist in the MDM SaaS data store
If the business ID of an input record doesn't match the business ID of an existing source or master record, the system considers the input record as a new one and creates a master record. However, if the business ID format contains the prefix that's set for the business ID format defined in Business 360 Console, the system doesn't create a new master record. If you specify custom business IDs for records, ensure that you don't use the prefix assigned to the business ID format defined in the Business 360 Console.
For example, the business ID configuration is numeric, with a length of 15, and a prefix of 999. If you ingress a record with the business ID 1210000, the record is ingressed. However, if you try to ingress a record with the business ID 999000218888912220, the record isn't ingressed because it matches the defined business ID format. The input record doesn't participate in the match process and retains its business ID.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
121000000000001
Billing
Fred
Weasley
M
2-02-1987
After you run an ingress job, the input record becomes a source record and retains its business ID.
The MDM SaaS data store shows the newly added source record.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000123
CRM
Mary
Williams
F
01-01-1991
MDM000000000789
SFDC
Mary
W
F
-
MDM000000000456
SAP
John
Johnsons
M
03-03-2001
121000000000001
(Retains the business ID)
Billing
Fred
Weasley
M
2-02-1987
The ingress job creates a master record that contains the business ID of the input record.
The MDM SaaS data store shows the newly added master record.
Business ID
First Name
Last Name
Gender
Birth Date
MDM000000000123
Mary
Williams
F
01-01-1991
MDM000000000456
John
Johnsons
M
03-03-2001
121000000000001
Fred
Weasley
M
2-02-1987
Business ID of an input record matches the business ID of a master record
The business ID format can either be a defined or custom format. The input record bypasses the match process before merging with the master record. If the business ID of an input record matches the business ID of an existing master record, the ingress job merges the input record with the master record.
The input record contains a business ID that matches an existing master record.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000123
Admin
Mary
Wills
-
02-01-1991
After you run an ingress job, the input record merges with the master record.
The MDM SaaS data store shows that the input record is merged with the existing master record.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000123
CRM
Mary
Williams
F
01-01-1991
Admin
Mary
Wills
02-01-1991
MDM000000000789
SFDC
Mary
W
F
-
MDM000000000456
SAP
John
Johnsons
M
03-03-2001
MDM000000000890
Billing
Fred
Weasley
M
2-02-1987
The ingress job merges the input record with the master record. The record doesn't go through the match and merge process.
The MDM SaaS data store shows the master records.
Business ID
First Name
Last Name
Gender
Birth Date
MDM000000000123
Mary
Wills
F
01-01-1991
MDM000000000456
John
Johnsons
M
03-03-2001
MDM000000000890
Fred
Weasley
M
2-02-1987
Business ID of an input record matches the business ID of a source record
The business ID format can either be a defined or custom format. If the business ID of an input record matches the business ID of a source record, the ingress job merges the input record with the master record to which the source record contributes. The input record doesn't go through the match process before merging with the master record. The job assigns a business ID to the input record based on the defined business ID format.
The input record contains a business ID that matches a source record.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000890
CRM
Fred
W
M
02-02-1987
After you run the ingress job, the input record becomes a source record that contributes to the master record, and a new business ID is assigned to the record.
The MDM SaaS data store shows the source records.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000123
CRM
Mary
Williams
F
01-01-1991
MDM000000000789
SFDC
Mary
W
F
-
MDM000000000412
Admin
Mary
Willis
02-01-1991
MDM000000000456
SAP
John
Johnsons
M
03-03-2001
MDM000000000890
Billing
Fred
Weasley
M
2-02-1987
MDM000000000911
(Autogenerated business ID for MDM000000000890)
CRM
Fred
W
M
02-02-1987
The ingress job merges the input record with the master record. The record doesn't go through the match and merge process.
The MDM SaaS data store shows the master records.
Business ID
First Name
Last Name
Gender
Birth Date
MDM000000000123
Mary
Wills
F
01-01-1991
MDM000000000456
John
Johnsons
M
03-03-2001
MDM000000000890
Fred
W
M
02-02-1987
Input record without a business ID
If an input record doesn't contain a business ID, the input record goes through the match and merge process. The ingress job assigns a business ID to the input record based on the defined business ID format.
The input record doesn't contain a business ID.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
-
CRM
Chase
Wolfinger
Male
05-05-1987
The ingress job creates a master record along with the corresponding source record. The input record goes through the match and merge process. The job assigns a business ID to the input record.
The MDM SaaS data store shows the newly added source record.
Business ID
Source System
First Name
Last Name
Gender
Birth Date
MDM000000000123
CRM
Mary
Williams
F
01-01-1991
MDM000000000789
SFDC
Mary
W
F
-
MDM000000000412
Admin
Mary
Willis
02-01-1991
MDM000000000456
SAP
John
Johnsons
M
03-03-2001
MDM000000000890
Billing
Fred
Weasley
M
2-02-1987
MDM000000000911
CRM
Fred
W
M
02-02-1987
MDM000000000977
(Autogenerated business ID)
CRM
Chase
Wolfinger
Male
05-05-1987
The ingress job creates a master record for the corresponding source record.
The MDM SaaS data store shows the newly added master record.