| Description | Manage Channel Partners |
| Name | ManageChannelPartnerIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Business Partner Data Management |
| Process Component Name | BusinessPartnerDataManagement |
| Process Component Namespace | http://sap.com/xi/AP/FO/BusinessPartner/Global |
| Deploymnent Unit Description | Foundation |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Deprecated |
An inbound service interface to migrate partner master data from a source system or file.
The Web service interface Manage Channel Partner In enables you to connect external applications to your solution and to create and migrate partners and their assigned contacts in your system. Using this service interface, you can also create users and perform organizational assignments for partner contacts. The Web service interface Manage Channel Partner In is relevant if your company wants to access and manage business partner data from external applications.
The Web service interface Manage Channel Partner In offers the operations MaintainBundle_V1 and CheckMaintainBundle_V1.
Here is an example of a simple Web service request, which creates a new partner 'information system' and its main contact:
Show full documentation
Show full documentation
<n0:ChannelPartnerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0aa000c68</ID>
</BasicMessageHeader>
<ChannelPartner actionCode="01" addressInformationListCompleteTransmissionIndicator="true" directResponsibilityListCompleteTransmissionIndicator="true" contactPersonListCompleteTransmissionIndicator="true" textListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<Organisation>
<CompanyLegalFormCode>01</CompanyLegalFormCode>
<FirstLineName>Information</FirstLineName>
<SecondLineName>Systems</SecondLineName>
</Organisation>
<VerbalCommunicationLanguageCode>EN</VerbalCommunicationLanguageCode>
<LegalCompetenceIndicator>true</LegalCompetenceIndicator>
<IndustrialSectorCode listID="0005">54</IndustrialSectorCode>
<AddressInformation actionCode="01" addressUsageListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<AddressUsage actionCode="01">
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<AddressUsageCode>XXDEFAULT</AddressUsageCode>
<DefaultIndicator>true</DefaultIndicator>
</AddressUsage>
<Address actionCode="01" telephoneListCompleteTransmissionIndicator="true">
<CorrespondenceLanguageCode>EN</CorrespondenceLanguageCode>
<PreferredCommunicationMediumTypeCode>INT</PreferredCommunicationMediumTypeCode>
<EmailURI>contact@infosystem.com</EmailURI>
<FacsimileFormattedNumberDescription>2313</FacsimileFormattedNumberDescription>
<PostalAddress>
<CountryCode>IN</CountryCode>
<RegionCode listID="IN">10</RegionCode>
<CityName>Bangalore</CityName>
<DistrictName>Bangalore</DistrictName>
<StreetPostalCode>560066</StreetPostalCode>
<POBoxPostalCode>560066</POBoxPostalCode>
<StreetName>EPIP</StreetName>
<HouseID>138</HouseID>
</PostalAddress>
<WebURI>http://www.infosystem.com</WebURI>
</Address>
</AddressInformation>
<ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>6</ObjectNodeSenderTechnicalID>
<DefaultContactPersonIndicator>true</DefaultContactPersonIndicator>
<FormOfAddressCode>0001</FormOfAddressCode>
<GivenName>Kiran</GivenName>
<FamilyName>Savarakar</FamilyName>
<GenderCode>2</GenderCode>
<BirthDate>1979-01-24</BirthDate>
<NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode>
<OccupationCode>0024</OccupationCode>
<BusinessPartnerFunctionTypeCode>0008</BusinessPartnerFunctionTypeCode>
<BusinessPartnerFunctionalAreaCode>0023</BusinessPartnerFunctionalAreaCode>
<WorkplaceTelephone>
<ObjectNodeSenderTechnicalID>25</ObjectNodeSenderTechnicalID>
<FormattedNumberDescription>+918292228453</FormattedNumberDescription>
<MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator>
</WorkplaceTelephone>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<MaritalStatusCode>1</MaritalStatusCode>
</ContactPerson>
<DuplicateCheckApplyIndicator>false</DuplicateCheckApplyIndicator>
</ChannelPartner>
</n0:ChannelPartnerBundleMaintainRequest_sync_V1>
The following sample response returns the InternalID and the UUID of the customer thus created:
<n0:ChannelPartnerBundleMaintainConfirmation_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<ChannelPartner>
<ReferenceObjectNodeSenderTechnicalID>1</ReferenceObjectNodeSenderTechnicalID>
<ChangeStateID>20140829171819.1653200</ChangeStateID>
<InternalID>0001082240</InternalID>
<UUID>00163e06-551f-1ed4-8bf4-0ed2c72f1a07</UUID>
</ChannelPartner>
<Log/>
</n0:ChannelPartnerBundleMaintainConfirmation_sync_V1>
The following business documents must exist in the system at the time the Web service is called.
Sales organizations
Job definitions
These documents are only referenced by the service operations, and not created by them.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include:
Create partner and its contacts
The MaintainBundle_V1 operation can be used to create a partner and the corresponding partner contacts. It also can be used to assign the partner contacts to the org structure, and to create users with the appropriate access rights for the partner contacts.
<n0:ChannelPartnerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0aa000c68</ID>
</BasicMessageHeader>
<ChannelPartner actionCode="01" addressInformationListCompleteTransmissionIndicator="true" directResponsibilityListCompleteTransmissionIndicator="true" contactPersonListCompleteTransmissionIndicator="true" textListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<Organisation>
<CompanyLegalFormCode>01</CompanyLegalFormCode>
<FirstLineName>Information</FirstLineName>
<SecondLineName>Systems</SecondLineName>
</Organisation>
<VerbalCommunicationLanguageCode>EN</VerbalCommunicationLanguageCode>
<LegalCompetenceIndicator>true</LegalCompetenceIndicator>
<IndustrialSectorCode listID="0005">54</IndustrialSectorCode>
<AddressInformation actionCode="01" addressUsageListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<AddressUsage actionCode="01">
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<AddressUsageCode>XXDEFAULT</AddressUsageCode>
<DefaultIndicator>true</DefaultIndicator>
</AddressUsage>
<Address actionCode="01" telephoneListCompleteTransmissionIndicator="true">
<CorrespondenceLanguageCode>EN</CorrespondenceLanguageCode>
<PreferredCommunicationMediumTypeCode>INT</PreferredCommunicationMediumTypeCode>
<EmailURI>contact@infosystem.com</EmailURI>
<FacsimileFormattedNumberDescription>2313</FacsimileFormattedNumberDescription>
<PostalAddress>
<CountryCode>IN</CountryCode>
<RegionCode listID="IN">10</RegionCode>
<CityName>Bangalore</CityName>
<DistrictName>Bangalore</DistrictName>
<StreetPostalCode>560066</StreetPostalCode>
<POBoxPostalCode>560066</POBoxPostalCode>
<StreetName>EPIP</StreetName>
<HouseID>138</HouseID>
</PostalAddress>
<WebURI>http://www.infosystem.com</WebURI>
</Address>
</AddressInformation>
<ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>6</ObjectNodeSenderTechnicalID>
<DefaultContactPersonIndicator>true</DefaultContactPersonIndicator>
<FormOfAddressCode>0001</FormOfAddressCode>
<GivenName>Kiran</GivenName>
<FamilyName>Savarakar</FamilyName>
<GenderCode>2</GenderCode>
<BirthDate>1979-01-24</BirthDate>
<NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode>
<OccupationCode>0024</OccupationCode>
<BusinessPartnerFunctionTypeCode>0008</BusinessPartnerFunctionTypeCode>
<BusinessPartnerFunctionalAreaCode>0023</BusinessPartnerFunctionalAreaCode>
<WorkplaceTelephone>
<ObjectNodeSenderTechnicalID>25</ObjectNodeSenderTechnicalID>
<FormattedNumberDescription>+918292228453</FormattedNumberDescription>
<MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator>
</WorkplaceTelephone>
<ContactOrganisationalAssignment>
<ValidityPeriod>
<StartDate>1999-01-24</StartDate>
<EndDate>1999-01-24</EndDate>
</ValidityPeriod>
<StaffableOrganisationalCentreID>ORGID</StaffableOrganisationalCentreID>
<JobID>JOBID</JobID>
</ContactOrganisationalAssignment>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<MaritalStatusCode>1</MaritalStatusCode>
</ContactPerson>
<ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>7</ObjectNodeSenderTechnicalID>
<DefaultContactPersonIndicator>false</DefaultContactPersonIndicator>
<FormOfAddressCode>0001</FormOfAddressCode>
<GivenName>Simaran</GivenName>
<FamilyName>Gopal</FamilyName>
<GenderCode>2</GenderCode>
<BirthDate>1981-01-24</BirthDate>
<NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode>
<OccupationCode>0024</OccupationCode>
<BusinessPartnerFunctionTypeCode>0003</BusinessPartnerFunctionTypeCode>
<BusinessPartnerFunctionalAreaCode>0011</BusinessPartnerFunctionalAreaCode>
<WorkplaceTelephone>
<ObjectNodeSenderTechnicalID>25</ObjectNodeSenderTechnicalID>
<FormattedNumberDescription>+918291738451</FormattedNumberDescription>
<MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator>
</WorkplaceTelephone>
<AddressInformation actionCode="01">
<ObjectNodeSenderTechnicalID>9</ObjectNodeSenderTechnicalID>
<Address actionCode="01" telephoneListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>21</ObjectNodeSenderTechnicalID>
<EmailURI>simaran@infosystem.com</EmailURI>
<FacsimileFormattedNumberDescription>2313</FacsimileFormattedNumberDescription>
<PostalAddress>
<CountryCode>IN</CountryCode>
<RegionCode listID="IN">10</RegionCode>
<CityName>Bangalore</CityName>
<DistrictName>Bangalore</DistrictName>
<StreetPostalCode>560066</StreetPostalCode>
<POBoxPostalCode>560066</POBoxPostalCode>
<StreetName>EPIP</StreetName>
<HouseID>138</HouseID>
</PostalAddress>
</Address>
<AddressUsage actionCode="01">
<ObjectNodeSenderTechnicalID>10</ObjectNodeSenderTechnicalID>
<AddressUsageCode>XXDEFAULT</AddressUsageCode>
<DefaultIndicator>true</DefaultIndicator>
</AddressUsage>
</AddressInformation>
<ContactOrganisationalAssignment>
<ValidityPeriod>
<StartDate>1999-01-24</StartDate>
<EndDate>1999-01-24</EndDate>
</ValidityPeriod>
<StaffableOrganisationalCentreID>ORGID</StaffableOrganisationalCentreID>
<JobID>JOBID</JobID>
</ContactOrganisationalAssignment>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<MaritalStatusCode>1</MaritalStatusCode>
</ContactPerson>
<DirectResponsibility actionCode="01">
<ObjectNodeSenderTechnicalID>10</ObjectNodeSenderTechnicalID>
<PartyRoleCode>142</PartyRoleCode>
<EmployeeID>201678</EmployeeID>
</DirectResponsibility>
<DuplicateCheckApplyIndicator>false</DuplicateCheckApplyIndicator>
</ChannelPartner>
</n0:ChannelPartnerBundleMaintainRequest_sync_V1>
Update partner and its contacts
The MaintainBundle_V1 operation can be used to update a partner and the corresponding partner contacts. Following options are supported for partner update scenario:
1. Enhance:
• Contact
• Contact personal address
2. Modify:
• Partner
• Contact
3.Replace:
• Partner
• Partner Address
Here is an example web service request to add a new contact person to an existing partner:
<n0:ChannelPartnerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0aa000c68</ID>
</BasicMessageHeader>
<ChannelPartner actionCode="06" addressInformationListCompleteTransmissionIndicator="false" directResponsibilityListCompleteTransmissionIndicator="false" contactPersonListCompleteTransmissionIndicator="false" textListCompleteTransmissionIndicator="false">
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<InternalID>CP100110</InternalID>
<ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>6</ObjectNodeSenderTechnicalID>
<DefaultContactPersonIndicator>true</DefaultContactPersonIndicator>
<FormOfAddressCode>0001</FormOfAddressCode>
<GivenName>Kiran</GivenName>
<FamilyName>Savarakar</FamilyName>
<GenderCode>2</GenderCode>
<BirthDate>1979-01-24</BirthDate>
<NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode>
<OccupationCode>0024</OccupationCode>
<BusinessPartnerFunctionTypeCode>0008</BusinessPartnerFunctionTypeCode>
<BusinessPartnerFunctionalAreaCode>0023</BusinessPartnerFunctionalAreaCode>
<WorkplaceTelephone>
<ObjectNodeSenderTechnicalID>25</ObjectNodeSenderTechnicalID>
<FormattedNumberDescription>+918292228453</FormattedNumberDescription>
<MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator>
</WorkplaceTelephone>
<ContactOrganisationalAssignment>
<ValidityPeriod>
<StartDate>1999-01-24</StartDate>
<EndDate>1999-01-24</EndDate>
</ValidityPeriod>
<StaffableOrganisationalCentreID>ORGID</StaffableOrganisationalCentreID>
<JobID>JOBID</JobID>
</ContactOrganisationalAssignment>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<MaritalStatusCode>1</MaritalStatusCode>
</ContactPerson>
<ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>7</ObjectNodeSenderTechnicalID>
<DefaultContactPersonIndicator>false</DefaultContactPersonIndicator>
<FormOfAddressCode>0001</FormOfAddressCode>
<GivenName>Simaran</GivenName>
<FamilyName>Gopal</FamilyName>
<GenderCode>2</GenderCode>
<BirthDate>1981-01-24</BirthDate>
<NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode>
<OccupationCode>0024</OccupationCode>
<BusinessPartnerFunctionTypeCode>0003</BusinessPartnerFunctionTypeCode>
<BusinessPartnerFunctionalAreaCode>0011</BusinessPartnerFunctionalAreaCode>
<WorkplaceTelephone>
<ObjectNodeSenderTechnicalID>25</ObjectNodeSenderTechnicalID>
<FormattedNumberDescription>+918291738451</FormattedNumberDescription>
<MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator>
</WorkplaceTelephone>
<AddressInformation actionCode="01">
<ObjectNodeSenderTechnicalID>9</ObjectNodeSenderTechnicalID>
<Address actionCode="01" telephoneListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>21</ObjectNodeSenderTechnicalID>
<EmailURI>simaran@infosystem.com</EmailURI>
<FacsimileFormattedNumberDescription>2313</FacsimileFormattedNumberDescription>
<PostalAddress>
<CountryCode>IN</CountryCode>
<RegionCode listID="IN">10</RegionCode>
<CityName>Bangalore</CityName>
<DistrictName>Bangalore</DistrictName>
<StreetPostalCode>560066</StreetPostalCode>
<POBoxPostalCode>560066</POBoxPostalCode>
<StreetName>EPIP</StreetName>
<HouseID>138</HouseID>
</PostalAddress>
</Address>
<AddressUsage actionCode="01">
<ObjectNodeSenderTechnicalID>10</ObjectNodeSenderTechnicalID>
<AddressUsageCode>XXDEFAULT</AddressUsageCode>
<DefaultIndicator>true</DefaultIndicator>
</AddressUsage>
</AddressInformation>
<ContactOrganisationalAssignment>
<ValidityPeriod>
<StartDate>1999-01-24</StartDate>
<EndDate>1999-01-24</EndDate>
</ValidityPeriod>
<StaffableOrganisationalCentreID>ORGID</StaffableOrganisationalCentreID>
<JobID>JOBID</JobID>
</ContactOrganisationalAssignment>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<MaritalStatusCode>1</MaritalStatusCode>
</ContactPerson>
</ChannelPartner>
</n0:ChannelPartnerBundleMaintainRequest_sync_V1>
Here is an example web service request to update a partner and a contact person assigned to the partner:
<n0:ChannelPartnerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0aa000c68</ID>
</BasicMessageHeader>
<ChannelPartner actionCode="02" textListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<InternalID>CP10000</InternalID>
<Organisation>
<CompanyLegalFormCode>01</CompanyLegalFormCode>
<FirstLineName>Information_Change</FirstLineName>
<SecondLineName>Systems_Change</SecondLineName>
</Organisation>
<VerbalCommunicationLanguageCode>ES</VerbalCommunicationLanguageCode>
<LegalCompetenceIndicator>true</LegalCompetenceIndicator>
<IndustrialSectorCode listID="0005">21</IndustrialSectorCode>
<ContactPerson actionCode="02" workplaceTelephoneListCompleteTransmissionIndicator="true">
<ObjectNodeSenderTechnicalID>6</ObjectNodeSenderTechnicalID>
<DefaultContactPersonIndicator>true</DefaultContactPersonIndicator>
<FormOfAddressCode>0001</FormOfAddressCode>
<GivenName>Kiran</GivenName>
<FamilyName>Savarakar</FamilyName>
<GenderCode>2</GenderCode>
<BirthDate>1979-01-24</BirthDate>
<NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode>
<OccupationCode>0024</OccupationCode>
<BusinessPartnerFunctionTypeCode>0008</BusinessPartnerFunctionTypeCode>
<BusinessPartnerFunctionalAreaCode>0023</BusinessPartnerFunctionalAreaCode>
<WorkplaceTelephone>
<ObjectNodeSenderTechnicalID>25</ObjectNodeSenderTechnicalID>
<FormattedNumberDescription>+918292228453</FormattedNumberDescription>
<MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator>
</WorkplaceTelephone>
<ContactOrganisationalAssignment>
<ValidityPeriod>
<StartDate>1999-01-24</StartDate>
<EndDate>1999-01-24</EndDate>
</ValidityPeriod>
<StaffableOrganisationalCentreID>ORGID</StaffableOrganisationalCentreID>
<JobID>JOBID</JobID>
</ContactOrganisationalAssignment>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<MaritalStatusCode>1</MaritalStatusCode>
</ContactPerson>
</ChannelPartner>
</n0:ChannelPartnerBundleMaintainRequest_sync_V1>
| Description | Maintain partners |
| Name | MaintainBundle_V1 |
| Synchronous | yes |
| Release Status | Deprecated |
To create, update, or delete partner master data
The request message of the operation MaintainBundle_V1 contains a BasicMessageHeader node element as well as a Channel Partner node element that contains the partner data to be created or updated. The detailed structure of the Channel Partner node will be explained in the following sub-chapters. The Channel Partner node can occur multiple times in the request message – this means that multiple Channel Partners can be created and updated through a single web service request.
The response message type of the operation MaintainBundle_V1 contains log items, processing information and an channel partner-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as account InternalID and account UUID.
The Channel Partner node element contains all general partner information such as ID, UUID, names, and other details.
The data for this node is related to General data on the partner UI.
For Channel Partner the CategoryCode is 2.
The InternalID element corresponds to the Partner ID on the UI - the UUID element is not visible on the UI, but can be retrieved using query and read web services.
Note: Please be aware of the fact that the element DuplicateCheckApplyIndicator means that a duplicate check is performed if the current solution supports the check and if the check is activated in the Business Configuration.
The AddressInformation node element can be used to create and change partner addresses.
Data for the AddressInformation node element is related to Communication Addresses data on the account UI. The elements of the Address sub-node element in the request message are located in the Address- and Communication details section on the UI.
The AddressUsage sub-node element corresponds to the usages in the table of addresses on the account UI. The usages are modeled as a list of AddressUsageCodes in the request message:
| User Interface | AddressUsageCode |
|---|---|
| Main address | XXDEFAULT |
| Ship-To address | SHIP_TO |
| Bill-To address | BILL_TO |
| Remittance Advice To address | PAY001 |
The Telephone sub-node element allows two entries at maximum - one with MobilePhoneNumberIndicator = true and one with MobilePhoneNumberIndicator = false. This corresponds to the Phone and Mobile fields on the user interface. The DefaultIndicator element is not relevant for the usage code XXDEFAULT. In case of multiple addresses, instances have the same usage code (for example, two ship-to addresses); one address has to be indicated as the default address for that particular address usage - which means the DefaultIndicator has to be true for exactly one of these addresses. On the user interface, the default address for a given usage has the value Yes (Standard).
If changes to node element Telephone are requested, the telephoneListCompleteTransmissionIndicator has to be set to true (and the complete list has to be transmitted).
Note: An address that has been saved cannot be deleted, and hence instances of the AddressInformation node element cannot be deleted in this case, either.
The ContactPerson node element can be used to create and change partner contact person relations.
The ContactPerson node is related to Contacts data on the UI (Business Address, Business Communication and Details sections).
The ContactPerson node element creates or updates a contact person and directly assigns it to the corresponding partner.
Existing contact persons can be assigned to accounts using the Relationship and ContactPerson node elements:
ContactPerson node element: Provide elements BusinessPartnerContactUUID or the BusinessPartnerContactInternalID to identify the related contact. In addition, the actionCode must be set to 04 (save).
The WorkplaceTelephone sub-node element allows two entries at maximum - one with MobilePhoneNumberIndicator = true and one with MobilePhoneNumberIndicator = false. This corresponds to the Phone and Mobile fields on the account UI.
The Create User Indicator denotes the creation of an Identity user which creates a user with logon details in the system, if the indicator is set then only the user is created in the system
The DirectResponsibility node element can be used to assign employees as directly responsible for the account.
The most common party role codes are the following:
| Party Role Code | Description |
|---|---|
| 142 | Employee Responsible - Sales |
| UUID-Content is used to identify the records for employees responsible for a partner. It is used for technical reasons only and can be ignored. |
Note that Identity node is currently not supported in this Service.
| Description | Check maintain partners |
| Name | CheckMaintainBundle_V1 |
| Synchronous | yes |
| Release Status | Deprecated |
To check if channel partner master data can be created, updated, or deleted without errors.
The web service request and response message types for the CheckMaintainBundle_V1 operation are the same as those of the Maintain Bundle_V1 operation. The explanations given can therefore also be applied to the CheckMaintainBundle_V1 operation.
