Show TOC

Inform of Business Partner as BulkLocate this document in the navigation structure

Definition

An operation that sends information from Business Partner Data Management about business events for multiple business partners.

Technical Data

Entity Type

Service Operation

Release State

Released

Technical Name

BusinessPartnerDataManagementBusinessPartnerEventOut.InformOfBusinessPartnerAsBulk

Mode

Asynchronous

Idempotency

Not applicable

Change/Update Behavior

Not applicable
Business Context

This operation informs subscribed systems about changes to business partner data including the creation of a new business partner. The message includes all the data about the business partner as well as the data that was changed.

Example

A bank clerk uses an application that has embedded service operations to make the following two changes:

  • Create a new business partner

  • Change the master data of an existing business partner who has a new address

The application sends two messages informing subscribed systems about these changes to the master data of business partners. One message informs subscribers about the creation of the new business partner. A separate message informs the subscribers of the change to the address of the existing business partner.

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

Related Operations

Business-Related Operations

Not applicable

Compensation Operation

Not applicable

Counterpart Operation

Not applicable

Features

The outbound message includes all the data about the business partner as well as information about whether data from specific nodes has been created, changed, deleted, or remain unchanged.

For data that was changed or deleted, the previous data for certain elements is held under the nodes called Previous. For example, the coded representation of the person’s occupation (OccupationCode element) is under the node Person and below this is a Previous node with a second OccupationCode element. After a person’s occupation is changed, the first OccupationCode element contains the latest, changed data while the second OccupationCode element contains the value before the change.

The message can be sent almost immediately or it can be scheduled for later such as regularly during a batch operation once a day. In this case, the message contains the latest data on the business partner regardless of how many times the business partner data has actually been changed since the last message from this operation.

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

Error Handling

For more information, see Error Handling in Financial Services .

Agent Framework

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

To ensure a correct version history in the subscribed applications, the agent has to be scheduled to run at least on a daily basis. If the subscribed applications are temporarily unable to process the information, the agent has to be rescheduled to run for every single day using the following agent IDs in the following order:

If errors occur in the subscribed applications (technical errors or errors that require postprocessing), you need to resolve these before starting the agent with the next agent ID. Otherwise, manual corrections might be necessary.

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

Notes on SAP Implementation

Postprocessing of Inconsistent Data

If an information message about new or changed business partners was stopped, was incorrect, or was not processed correctly in the receiver system for a different reason, you can clean up inconsistencies in the business partner data. To create new change pointers, you can run the report Select Info About Business Partner and BP Relationship for Sending..

You then use Agent Framework (FS-FND-AF) to read the change pointers and send new information messages.

Enhancements

You can find the Business Add-In (BAdI) BAdI for InformOfBusinessPartnerAsBulk(FSBP_FND_SE_INFORM_AS_BULK) for this operation through Transaction SIMGH. Choose Start of the navigation path BAdIs for XI Interfaces Next navigation step Mapping and Processing of Service Enhancements Next navigation step Business Partner End of the navigation path. Depending on the application, the BAdIs for XI Interfaces structure could also be available in the IMG of your system such as SAP Policy Management.