Create Business Partner Relationship as Bundle

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

This operation creates one or more business partner relationships together with all the relevant validity periods. 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.

This operation attempts to create all business partner relationships listed in the request. As a bundle operation, if one or more relationships cannot be created, none of the relationships are created (“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 created in the bundle request, the following information is mandatory:

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

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

  • Unique identifier (UUID element)

  • Internal identifier (InternalID element)

  • The data required for the identification node (PartyIdentifierTypeCode and BusinessPartnerID elements)

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

  • Unique identifier (UUID element)

  • Internal identifier (InternalID element)

  • The data required for the identification node (PartyIdentifierTypeCode and BusinessPartnerID elements)

• The business process chain assignment (BusinessProcessChainAssignment element). For more information, see Business Process Chain Assignment

• One of the following types of relationship with the associated data:

  • Contact person (ContactPerson element, category code BUR001)

  • Shareholder (Shareholder element, category code BURC01)

  • Other relationship category (OtherRelationshipCategory element)

    Examples of other relationship categories include marriage relationship (category code BUR004) and employee relationship (category code BUR010).

• The validity period for the relationship (ValidityPeriod element).

In addition, the SenderTechnicalID element can be included in the request to provide a technical identifier for 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.

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

• BusinessPartnerRelationshipFSBundleCreateConfirmation

• BusinessPartnerRelationshipFSBundleCreateRequest

For more information, see Error Handling in Financial Services .

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

• 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; error while processing the data)

• PRE.IDE (Identification Error): FSBP_MAIN_ERROR_MSG 005 (Business partner relationship already exists)

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