An operation that creates a business partner as a person, organization, or group.
Entity Type |
Service Operation |
Released |
|
BusinessPartnerDataManagementManageBusinessPartnerIn.CreateBusinessPartner |
|
Synchronous |
|
Yes |
|
Not applicable |
The data about the business partner can be as comprehensive as required for example name, address, bank details, employment, rating, financial statement, and credit standing. The operation can be used for business partners of any type, that is persons, organizations, or groups.
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
To create a business partner, the business process chain assignment (BusinessProcessChainAssignment element) is required. For more information, see Business Process Chain Assignment
The following information may also be provided, for example:
Common data such as the salutation name to be used to personalize a letter (SalutationText element), an indication of whether the business partner is a person (NaturalPersonIndicator element), an indication of whether the business partner is a VIP (VIPIndicator element)
In the case of a person, general data including theName, GenderCode, MaritalStatusCode and OccupationCode elements
In the case of an organization, general data including Name and CompanyLegalFormCode elements
In the case of a group, general data including FormofAddressCode and Name elements
Address information including AddressUsageCode, TelephoneNumber and EmailURI
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:
BusinessProcessChainAssignment
Common
AddressInformation
CommunicationData
Role
BankDetails
PaymentCardDetails
IndustrySector
Identification
TaxNumber
GeneralProductTaxExemption
TextCollection
CreditRating
CreditStanding
Occupation
FinancialStatement
Alias
TaxCompliance
BankRegulations
If the requested indicator (RequestedIndicator element) is set to false (default value), no data is returned for the corresponding node.
The response message contains data about the newly created business partner as determined by the confirmation view. It also includes the identifier of the change state (ChangeStateID element) of the business partner.
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; the relevant authorizations are missing)
PRE.IDE (Identification Error): FSBP_MAIN_ERROR_MSG 004 (Business partner &1 already exists)
For more information about the individual error categories, see the code list for the global data type LogItemCategoryCode.
BusinessPartnerFSCreateConfirmation_V2
BusinessPartnerFSCreateRequest_V2
Authorization
The user must have the authorization to create a business partner. In the SAP back-end system, the following authorization objects are checked:
B_BUPA_GRP
B_BUPA_PGM
B_BUPA_RLT
B_CCARD
Enhancements
You can find the Business Add-In (BAdI) BAdI for CreateBusinessPartner(FSBP_FND_SE_CREATE) for this operation through Transaction SIMGH. Choose . 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.