Show TOC

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

Definition

An operation that cancels the relationship between two business partners as bundle.

Technical Data

Entity Type

Service Operation

Release State

Released

Technical Name

BusinessPartnerDataManagementManageBusinessPartnerRelationshipIn.CancelBusinessPartnerRelationshipAsBundle

Mode

Synchronous

Idempotency

No

Change/Update Behavior

Not applicable
Business Context

This operation cancels one or more business partner relationships together with all validity periods.

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

Related Operations

Business-Related Operations

Not applicable

Compensation Operation

Counterpart Operation

Not applicable

Features

This operation attempts to cancel all business partner relationships listed in the request. As a bundle operation, if one or more relationships cannot be cancelled, 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.

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

  • The identifier of the change state (ChangeStateID element). This is needed to ensure that no cancellations are performed based on old, and therefore obsolete, data (optimistic lock concept).

    For more information, see The Change State ID in Update Services .

  • The coded representation of the category (CategoryCode element).

    CategoryCodeis used for identification only so it cannot be changed.

  • One of the following two identifiers for the first business partner: unique identifier (UUID element), or internal identifier (InternalID element)

  • One of the following two identifiers for the second business partner: unique identifier (UUID element), or internal identifier (InternalID element)

  • The business process chain assignment (BusinessProcessChainAssignment element)

    For more information, see Business Process Chain Assignment

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

If a relationship that has been cancelled is to be resumed at a later point in time (for example, a former shareholder becomes a shareholder of the same company again), do not create a new relationship. Instead, update it by adding another validity period to the old relationship. The Update Business Partner Relationship as Bundle or the Update Business Partner Relationship as Bulk operations can be used to do this.

Further processing (if configured): When a business partner relationship is cancelled, Business Add-Ins (BAdIs) are used to raise related local events that inform local applications about the cancellation. Remote applications can be informed about business partner relationship cancellations via the Inform of Business Partner Relationship as Bulk operation.

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

  • BusinessPartnerRelationshipFSBundleCancelConfirmation

  • BusinessPartnerRelationshipFSBundleCancelRequest

Notes on SAP Implementation

Authorization

The user must be authorized to cancel 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 CancelBusinessPartnerRelationshipAsBundle(FSBPR_FND_SE_CANCEL_BNDL) 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.