Notify of Business Partner Data Cleansing Case Completion as Bulk

An operation that sends multiple notifications about the completion of Business Partner Data Cleansing Case.

This operation notifies subscribed applications about the successful merge of two or more business partner data records that have been determined to be duplicates. This enables subscribed applications to adjust their references to business partners accordingly.

For more information about the business context, see the Business Partner Data Cleansing Case business object.

Each cleansing case identifies the target and one or more duplicate business partners that have been merged. The outbound message contains the internal and additional identifications of the involved business partners, so the subscribed applications may exchange references to duplicate business partners to the target business partner of the data cleansing case. The subscribed applications are able to adjust their references to business partners accordingly. The message contains the data from the data cleansing case. This includes the following information for every business partner that is a target or a duplicate:

• The unique identifier of the business partner (TargetBusinessPartnerUUID element) or the internal identifier of the business partner (InternalID element)

• All available additional information for the business partner from the identification node

The following data sets of the business partners are referenced using technical identifications:

• Business partner addresses may be referenced using a unique identifier for the address (AddressInformationAddressUUID element) or an identifier of the address (AddressInformationAddressPostalAddressID element)

• Bank details may be referenced using an identification of the bank details (BankDetailsID element)

• Payment cards may be referenced using an identification of the payment card (PaymentCardDetailsID element)

When a duplicate business partner is replaced with the target business partner, references to the previously mentioned data sets become obsolete. This means they have to be replaced with new references that are valid for the target business partner. The business partner data cleansing case notification message contains information that allows applications to replace these technical identifications as well.

Applications can use business partner address usages to reference business partner addresses indirectly. For example, a duplicate business partner has been merged and had two address usages:

• Address usage bank statement address points to address A

• Address usage vacation home points to address B

After the business partner merge, the address usages of the target business partner are used. This can lead to a different address being used after the merge. For example, if the target business partner’s address usage for bank statement address points to address C, after the business partner merge the bank statements are sent to address C instead of address A. To enable applications to detect these kind of situations, the business partner cleansing case notification message also contains the address usages of the involved business partners.

A change pointer is set when a cleansing case is successfully processed, that is, two or more business partners are merged. The outbound agent framework reads the change pointer, composes the outbound message and sends it out. It can do this individually as soon as a change pointer is set. Alternatively, a batch process can periodically read all the change pointers set since the last read, and then send one message consisting of multiple data cleansing cases.

For more information about the bulk operation pattern, see Bulk, Bundle, Collection.

For more information, see Error Handling in Financial Services .

This operation is connected to the Agent Framework (FS-FND-AF) using agent ID BPCN.

For more information, see Agent Framework (FS-FND-AF).

• BusinessPartnerDataCleansingCaseFSCompletionBulkNotification