Show TOC

Update Business Partner Relationship as BundleLocate this document in the navigation structure

Definition

To update the relationship between two business partners as bundle.

Technical Data

Entity Type

Service Operation

Release State

Released

Technical Name

BusinessPartnerDataManagementManageBusinessPartnerRelationshipIn.UpdateBusinessPartnerRelationshipAsBundle

Mode

Synchronous

Idempotency

Yes

Change/Update Behavior

Field-based updates and explicit list item updates

Business Context

This operation updates one or more business partner relationships. Examples of business partner relationships are contact person, shareholder, and marriage relationship.

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

Related Operations

Business-Related Operations

Not applicable

Compensation Operation

Not applicable

Counterpart Operation

Not applicable

Features

This operation attempts to update all business partner relationships listed in the request. As a bundle operation, if one or more relationships cannot be updated, none of the relationships are updated (“all or nothing” principle).  In this case the response message contains error messages for the corresponding relationships in a log.

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 following nodes, the data from the corresponding node(s) is included:

  • FirstBusinessPartnerCommon

  • FirstBusinessPartnerIdentification

  • SecondBusinessPartnerCommon

  • SecondBusinessPartnerIdentification

  • BusinessProcessChainAssignment

  • ContactPerson

  • Shareholder

  • OtherRelationshipCategory

For each business partner relationship to be updated in the bundle request, the following information is mandatory:

  • The indicator for the complete transmission of the shareholder list (shareholderListCompleteTransmissionIndicato element). When set to true this indicates that all records sent for the node shareholder are to replace those in the database.

  • The indicator for the complete transmission of the other relationship category otherRelationshipCategoryListCompleteTransmissionIndicator element). When set to true, all records sent for the OtherRelationshipCategory node are to replace those in the database.

  • The identifier of the change state (ChangeStateID element)

  • The coded representation of the category (CategoryCode element). CategoryCode is used for identification only, it cannot be changed.

  • One of the following identifiers for the first business partner

    • Unique identifier (UUID element)

    • Internal identifier (InternalID element)

  • One of the following identifiers for the second business partner:

    • Unique identifier (UUID element)

    • Internal identifier(InternalID element)

In addition, the SenderTechnicalID element can be included in the request, to provide a technical identifier of each business partner relationship. This identifier allows the service consumer to determine which log item in the confirmation message corresponds to which requested relationship. In the confirmation message, the SenderTechnicalID element is contained in the ReferenceObjectNodeSenderTechnicalID element.

Note

The operation can add additional validity periods for business partner relationships, change the validity periods of existing business partner relationships, or delete validity periods of existing business partner relationships. It cannot create the first validity period nor delete the last. To create the first validity period, use the Create Business Partner Relationship as Bundle  operation. To delete the last validity period, use the Cancel Business Partner Relationship as Bundle operation.

When a business partner relationship is updated, Business Add-Ins (BAdIs) are used to raise related local events that inform local applications about the update. Remote applications can be informed about business partner relationship creations by the Inform of Business Partner Relationship as Bulk operation.

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

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:

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

  • 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))

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

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

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

  • PRE.IDE (Identification Error): FSBP_MAIN_ERROR_MSG 003 (Business partner relationship does not exist)

  • PRE.TEE.LRE (Lock Request Error):FSBP_MAIN_ERROR_MSG 042 (BP relationship is currently locked by another user account)

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

Message Types
  • BusinessPartnerRelationshipFSBundleUpdateConfirmation

  • BusinessPartnerRelationshipFSBundleUpdateRequest

Notes on SAP Implementation

Authorization

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

  • B_BUPA_RLT

  • B_BUPR_BZT

Enhancements

You can find the Business Add-In (BAdI) BAdI for UpdateBusinessPartnerRelationshipAsBundle(FSBPR_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 Relationship 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.