Show TOC

Update Business PartnerLocate this document in the navigation structure

Definition

An operation that updates a business partner as a person, organization, or group.

Technical Data

Entity Type

Service Operation

Release State

Released

Technical Name

BusinessPartnerDataManagementManageBusinessPartnerIn.UpdateBusinessPartner

Mode

Synchronous

Idempotency

Yes

Change/Update Behavior

Field-wise updates and explicit list item updates/deletions

Business Context and Use

The business partner data can be as comprehensive as required. For example, it can include address, bank details, employment, rating, financial statement, and credit standing.

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 following information is needed to request an update of the data of a business partner:

  • The identification of the business partner to be updated in the back-end system, which can either be its internal ID or UUID (InternalID element or UUID element).

  • The encoded state of the business partner on which the update is requested (ChangeStateID element). For more information, see The Change State ID in Update Services .

This service operation supports delta updates using complete transmission indicators (CTI) and action codes. This enables the user to decide whether to:

  • Transfer all the data for the business partner at object or node level

  • Send only changed data specifying action codes, such as insert, update, or delete

To transfer all data at object or node level, set the relevant ListCompleteTransmissionIndicator to True. This means that after the update, the object or node data for which the ListCompleteTransmissionIndicator is set is restricted to the data transferred, including the action codes transferred. To send only changed data, use the appropriate action codes for data elements (individual rows) of a node. The back-end system will only update the data element as it is indicated, for example:

  • 01 = Create

  • 03 = Delete

  • 06 = No Action

In addition, the specification of the confirmation view (ConfirmationViewSpecification node) may also be provided. This determines the nodes that are included in the confirmation message. If the requested indicator (RequestedIndicator element) is set to true for one or more of the nodes, the data from the corresponding node(s) is included.

The confirmation also contains a new ChangeStateID after the update, which can be used by the receiver to update the business partner data again.

Message Types

  • BusinessPartnerFSUpdateRequest_V1

  • BusinessPartnerFSUpdateConfirmation_V1

Error Handling

For more information, see Error Handling in Financial Services .

The following main error messages are recorded in the log of the response message:

  • PRE.IDE (Identification Error): FSBP_MAIN_ERROR_MSG 002 (Business partner does not exist or authorization is missing)

  • DCE.VME (Value Mapping Error):

    • FSBP_MAIN_ERROR_MSG 013 (Error occurred during mapping (inbound))

    • FSBP_MAIN_ERROR_MSG 014 (Error occurred during mapping (outbound))

  • PRE.AUE (Authorization Error): FSBP_MAIN_ERROR_MSG 021 (Cannot execute the operation; the relevant authorizations are missing)

  • PRE (Processing Error): FSBP_MAIN_ERROR_MSG 001 (Cannot execute the operation; error while processing the data)

  • FOE.SVE (Scheme Violation Error): FSBP_MAIN_ERROR_MSG 011 (Error during validation (inbound))

  • PRE.TEE.LRE (Lock Request Error): FSBP_MAIN_ERROR_MSG 041 (Business partner &1 is currently locked by another user account)

  • CON.LRC (Late Request Conflict): FSBP_MAIN_ERROR_MSG 071 (Business partner has been changed in the meantime)

For more information about the individual error categories, see the code list for the global data type LogItemCategoryCode.

Notes on SAP Implementation

Authorization

The user must be authorized to update a business partner. The following authorization objects are checked in the SAP back-end system:

  • B_BUPA_GRP

  • B_BUPA_PGM

  • B_BUPA_RLT

  • B_CCARD

Enhancements

The Business Add-In (BAdI) BAdI for BAdI for UpdateBusinessPartner (FSBP_FND_SE_UPDATE) 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.