Description | Manage Accounts |
Name | ManageCustomerIn |
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 |
Deployment Unit Description | Foundation |
Endpoint Activation | By Scoping of Process Component | Operations |
Release Status | Released |
An interface to migrate customer master data from a source system or file.
The web service interface Manage Customer In enables you to connect external applications to your SAP Business ByDesign system and to create and edit accounts and their assigned contacts in your system. The web service interface Manage Customer In is relevant if your company wants to access and manage business partner data from external applications.
The web service interface Manage Customer In offers the operations MaintainBundle_V1 and CheckMaintainBundle_V1.
Here is an example of a simple web service request:
<n0:CustomerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>00000000000102dcade9bcb0aa000c68</ID> </BasicMessageHeader> <Customer actionCode="01"> <CategoryCode>1</CategoryCode> <CustomerIndicator>true</CustomerIndicator> <Person> <GivenName>Frank</GivenName> <FamilyName>Sent</FamilyName> </Person> </Customer> </n0:CustomerBundleMaintainRequest_sync_V1>
Existence of referenced business documents:
The following business documents are only referenced and will not be created by the service operations. They must exist in the system already at the time the web service is called:
Sales organizations
Bank directory entries
For this web service, the change state ID does not apply to the ContactPerson, Relationship, CommunicationArrangement, DirectResponsibility, SalesArrangement, and PaymentData node elements.
You can find general information about Web services, their structure and consumption in the Web Services documentation. Please open the Web Services document in a new window.
Possible scenarios include the following:
Create Accounts
The MaintainBundle_V1 operation is used to create private and corporate accounts.
Update Accounts
The MaintainBundle_V1 operation is used to update existing private and corporate accounts.
Here is an example web service request to create a private account:
<n0:CustomerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <!-- Create person account --> <BasicMessageHeader> <ID>1234567890ABCDEF0123456789ABCDEF</ID> <UUID>12345678-90AB-CDEF-0123-456789ABCDEF</UUID> </BasicMessageHeader> <Customer actionCode="01" addressInformationListCompleteTransmissionIndicator="true" bankDetailsListCompleteTransmissionIndicator="true" communicationArrangementListCompleteTransmissionIndicator="true" directResponsibilityListCompleteTransmissionIndicator="true" operatingHoursInformationListCompleteTransmissionIndicator="true" paymentCardDetailsListCompleteTransmissionIndicator="true" relationshipListCompleteTransmissionIndicator="true" salesArrangementListCompleteTransmissionIndicator="true" taxNumberListCompleteTransmissionIndicator="true" generalProductTaxExemptionListCompleteTransmissionIndicator="true" contactPersonListCompleteTransmissionIndicator="false" paymentDataListCompleteTransmissionIndicator="true" textListCompleteTransmissionIndicator="true"> <!-- Pay attention on LCTI of contact person -> "false"! --> <ObjectNodeSenderTechnicalID>001</ObjectNodeSenderTechnicalID> <!-- ChangeStateID is only relevant for changing <ChangeStateID>20101201082957.5189460</ChangeStateID> --> <!-- The UUID cannot be changed <UUID>12345678-90AB-CDEF-0123-456789ABCDEF</UUID> --> <InternalID>CPSENT</InternalID> <CategoryCode>1</CategoryCode> <ProspectIndicator>false</ProspectIndicator> <CustomerIndicator>true</CustomerIndicator> <LifeCycleStatusCode>2</LifeCycleStatusCode> <!-- General data --> <Person> <FormOfAddressCode>0002</FormOfAddressCode> <AcademicTitleCode>0003</AcademicTitleCode> <GivenName>Frank</GivenName> <MiddleName>MiddleName</MiddleName> <FamilyName>Sent</FamilyName> <BirthName>Sent</BirthName> <NickName>NichName</NickName> <NameFormatCountryCode>US</NameFormatCountryCode> <GenderCode>1</GenderCode> <BirthDate>1970-01-01</BirthDate> <NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode> <OccupationCode>0017</OccupationCode> </Person> <VerbalCommunicationLanguageCode>EN</VerbalCommunicationLanguageCode> <ContactAllowedCode>3</ContactAllowedCode> <LegalCompetenceIndicator>true</LegalCompetenceIndicator> <!-- Only relevant for companies <DunAndBradstreetNumberID>270865562</DunAndBradstreetNumberID> <GlobalLocationNumberID>812015562</GlobalLocationNumberID> --> <ABCClassificationCode>A</ABCClassificationCode> <NielsenRegionCode>01</NielsenRegionCode> <IndustrialSectorCode>11</IndustrialSectorCode> <!-- Maintain adress --> <AddressInformation actionCode="01" addressUsageListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>002</ObjectNodeSenderTechnicalID> <AddressUsage actionCode="01"> <ObjectNodeSenderTechnicalID>003</ObjectNodeSenderTechnicalID> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <DefaultIndicator>false</DefaultIndicator> </AddressUsage> <Address actionCode="01" telephoneListCompleteTransmissionIndicator="true"> <PreferredCommunicationMediumTypeCode>LET</PreferredCommunicationMediumTypeCode> <EmailURI>mail@customer.com</EmailURI> <FacsimileFormattedNumberDescription>+1 7164824867</FacsimileFormattedNumberDescription> <PostalAddress> <CountryCode>US</CountryCode> <RegionCode>RegionCode</RegionCode> <CountyName>CountyName</CountyName> <CityName>Buffalo</CityName> <AdditionalCityName>AddCityName</AdditionalCityName> <DistrictName>DistrName</DistrictName> <StreetPostalCode>14204</StreetPostalCode> <CompanyPostalCode/> <StreetPrefixName>StrPrefixName</StreetPrefixName> <AdditionalStreetPrefixName>AddPrefixName</AdditionalStreetPrefixName> <StreetName>Seneca Street</StreetName> <StreetSuffixName>StreetSuffixName</StreetSuffixName> <AdditionalStreetSuffixName>AddStrSuffixName</AdditionalStreetSuffixName> <HouseID>145</HouseID> <CareOfName>CareOf2</CareOfName> <POBoxDeviatingCountryCode>US</POBoxDeviatingCountryCode> <POBoxDeviatingRegionCode>CA</POBoxDeviatingRegionCode> <POBoxPostalCode>23457</POBoxPostalCode> <POBoxDeviatingCityName>DevCityName</POBoxDeviatingCityName> <POBoxID>POBoxID</POBoxID> <POBoxIndicator>true</POBoxIndicator> <!-- <TaxJurisdictionCode></TaxJurisdictionCode> Only available for some countries (e.g. US) --> <TimeZoneCode>UTC</TimeZoneCode> </PostalAddress> <Telephone> <ObjectNodeSenderTechnicalID>004</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+12 34567890</FormattedNumberDescription> <MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator> </Telephone> <Telephone> <ObjectNodeSenderTechnicalID>005</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 7164824863</FormattedNumberDescription> <MobilePhoneNumberIndicator>false</MobilePhoneNumberIndicator> </Telephone> <WebURI>http://www.customer.com/</WebURI> </Address> </AddressInformation> <!-- Create relations to existing business partners --> <Relationship actionCode="01"> <ObjectNodeSenderTechnicalID>006</ObjectNodeSenderTechnicalID> <RelationshipBusinessPartnerInternalID>CP100110</RelationshipBusinessPartnerInternalID> <RoleCode>BURC01-1</RoleCode> <!-- "is Shareholder of" --> </Relationship> <!-- Create account collaboration business document settings --> <!-- Payment Processing --> <CommunicationArrangement actionCode="01"> <ObjectNodeSenderTechnicalID>007</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>11</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationMediumTypeCode>PRT</CommunicationMediumTypeCode> <OutputRequestFormTemplateCode>F0007</OutputRequestFormTemplateCode> <OutputCopyNumberValue>5</OutputCopyNumberValue> </CommunicationArrangement> <!-- Sales Order Processing Out--> <CommunicationArrangement actionCode="01"> <ObjectNodeSenderTechnicalID>008</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>27</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationMediumTypeCode>INT</CommunicationMediumTypeCode> <EMailURI>b.bb@bbb.bb</EMailURI> </CommunicationArrangement> <!-- Assign employees as directly responsible for the account --> <DirectResponsibility actionCode="01"> <ObjectNodeSenderTechnicalID>009</ObjectNodeSenderTechnicalID> <PartyRoleCode>145</PartyRoleCode> <EmployeeID>MDEC3626</EmployeeID> </DirectResponsibility> <!-- Maintain account sales data--> <SalesArrangement> <ObjectNodeSenderTechnicalID>010</ObjectNodeSenderTechnicalID> <SalesOrganisationID>CP100110</SalesOrganisationID> <DistributionChannelCode>02</DistributionChannelCode> <Incoterms> <ClassificationCode>CFR</ClassificationCode> <TransferLocationName>FRA</TransferLocationName> </Incoterms> <DeliveryPriorityCode>1</DeliveryPriorityCode> <CompleteDeliveryRequestedIndicator>true</CompleteDeliveryRequestedIndicator> <CurrencyCode>USD</CurrencyCode> <CustomerGroupCode>01</CustomerGroupCode> <CashDiscountTermsCode>1001</CashDiscountTermsCode> </SalesArrangement> <InvoicingBlockingReasonCode>03</InvoicingBlockingReasonCode> <CustomerTransactionDocumentFulfilmentBlockingReasonCode>91</CustomerTransactionDocumentFulfilmentBlockingReasonCode> <CustomerBlockingReasonCode>05</CustomerBlockingReasonCode> <!-- Add bank accounts --> <BankDetails actionCode="01"> <ObjectNodeSenderTechnicalID>17</ObjectNodeSenderTechnicalID> <ID>BD01</ID> <BankInternalID>76</BankInternalID> <!--Bank routing IDs are not necessary because of the identification with the internal ID --> <BankRoutingID>Token 723</BankRoutingID> <BankRoutingIDTypeCode>Tok</BankRoutingIDTypeCode> <BankStandardID>Token 725</BankStandardID>--> <BankAccountID>12345678</BankAccountID> <BankAccountIDCheckDigitValue>90</BankAccountIDCheckDigitValue> <BankAccountTypeCode>10</BankAccountTypeCode> <BankAccountHolderName>Frank Sent</BankAccountHolderName> <!--<BankAccountStandardID>Token 730</BankAccountStandardID>--> <ValidityPeriod> <StartDate>1999-01-24</StartDate> <EndDate>9999-01-24</EndDate> </ValidityPeriod> <!--Only relevant for China --> <n2:BankDirectoryBranchID xmlns:n2="http://sap.com/xi/AP/Globalization">0006</n2:BankDirectoryBranchID> <n2:GoldenTaxRelevanceIndicator xmlns:n2="http://sap.com/xi/AP/Globalization">false </n2:GoldenTaxRelevanceIndicator>--> </BankDetails> <!-- Add payment card --> <PaymentCardDetails actionCode="01"> <ObjectNodeSenderTechnicalID>012</ObjectNodeSenderTechnicalID> <ID>CARD_1</ID> <PaymentCardTypeCode>2</PaymentCardTypeCode> <PaymentCardID schemeAgencyID="HTTPS://WWW.COMPUTOP.DE">0538261015836111</PaymentCardID> <PaymentCardHolderName>Frank Sent</PaymentCardHolderName> <PaymentCardExpirationDate>2999-01-24</PaymentCardExpirationDate> <DefaultIndicator>true</DefaultIndicator> <BlockingReasonCode>1</BlockingReasonCode> <StreetName>Seneca Street</StreetName> <HouseID>145</HouseID> <PostalCode>14204</PostalCode> <CityName>Buffalo</CityName> <RegionCode>RegionCode</RegionCode> <CountryCode>US</CountryCode> </PaymentCardDetails> <!-- Maintain payment data --> <PaymentData actionCode="01" paymentFormListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>013</ObjectNodeSenderTechnicalID> <CompanyID>1000</CompanyID> <AccountDeterminationDebtorGroupCode>4010</AccountDeterminationDebtorGroupCode> <AccountDebtorExternalID>DID100</AccountDebtorExternalID> <PaymentBlockingReasonCode>2</PaymentBlockingReasonCode> <PaymentBlockExpirationDateTime>2016-03-28T12:00:00.1234567Z</PaymentBlockExpirationDateTime> <PaymentForm actionCode="01"> <PaymentFormCode>02</PaymentFormCode> <!-- Credit card--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>05</PaymentFormCode> <!-- Bank Transfer--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>06</PaymentFormCode> <!-- Check--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>13</PaymentFormCode> <!-- Direct Debit (Authorization for Payer’s Bank)--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>16</PaymentFormCode> <!-- Bill of Exchange Receivable Without Acceptance--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>17</PaymentFormCode> <!-- Bill of Exchange Receivable with Acceptance--> </PaymentForm> <CreditLimitAmount currencyCode="EUR">1000</CreditLimitAmount> <DirectDebitBankDetailsID>BD01</DirectDebitBankDetailsID> <DirectDebitValidityPeriod> <StartDate>1999-01-24</StartDate> <EndDate>2999-01-24</EndDate> </DirectDebitValidityPeriod> <PaymentCardDetailsID>CARD_1</PaymentCardDetailsID> <PaymentCardValidityPeriod> <StartDate>1999-01-24</StartDate> <EndDate>2999-01-24</EndDate> </PaymentCardValidityPeriod> <BillOfExchangeBankDetailsID>BD01</BillOfExchangeBankDetailsID> <PaymentAdviceRequiredIndicator>true</PaymentAdviceRequiredIndicator> <FirstPaymentInstructionCode>20</FirstPaymentInstructionCode> <BankChargeBearerCode>SHA</BankChargeBearerCode> </PaymentData> <!-- Maintain account tax numbers --> <TaxNumber actionCode="01"> <ObjectNodeSenderTechnicalID>014</ObjectNodeSenderTechnicalID> <CountryCode>DE</CountryCode> <TaxIdentificationNumberTypeCode>1</TaxIdentificationNumberTypeCode> <PartyTaxID>DE123456789</PartyTaxID> </TaxNumber> <!-- Maintain account tax exemption details --> <GeneralProductTaxExemption actionCode="01"> <ObjectNodeSenderTechnicalID>015</ObjectNodeSenderTechnicalID> <CountryCode>DE</CountryCode> <RegionCode>08</RegionCode> <TaxTypeCode listID="">1</TaxTypeCode> <ReasonCode>7</ReasonCode> </GeneralProductTaxExemption> <!-- Maintain account contact hours --> <OperatingHoursInformation actionCode="01" recurringDayProgrammeListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>016</ObjectNodeSenderTechnicalID> <RoleCode>A</RoleCode> <RecurringDayProgramme operatingHoursListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>017</ObjectNodeSenderTechnicalID> <WeekdaySelection> <MondayIndicator>true</MondayIndicator> <TuesdayIndicator>true</TuesdayIndicator> <WednesdayIndicator>true</WednesdayIndicator> <ThursdayIndicator>true</ThursdayIndicator> <FridayIndicator>true</FridayIndicator> <SaturdayIndicator>false</SaturdayIndicator> <SundayIndicator>false</SundayIndicator> </WeekdaySelection> <OperatingHours> <ObjectNodeSenderTechnicalID>018</ObjectNodeSenderTechnicalID> <TimePeriod> <StartTime>09:00:00</StartTime> <EndTime>18:00:00</EndTime> </TimePeriod> </OperatingHours> </RecurringDayProgramme> </OperatingHoursInformation> <!-- Add account notes, financial data notes or internal/external sales notes --> <Text actionCode="01"> <ObjectNodeSenderTechnicalID>019</ObjectNodeSenderTechnicalID> <TypeCode>10034</TypeCode> <ContentText>English Text</ContentText> </Text> <!-- Maintain customer attachmens like documents, images, links... --> <AttachmentFolder DocumentListCompleteTransmissionIndicator="true" ActionCode="01"> <!-- Link attachment--> <Document ActionCode="01"> <VisibleIndicator>true</VisibleIndicator> <CategoryCode>3</CategoryCode> <TypeCode>10001</TypeCode> <Name>SAP AG</Name> <AlternativeName>SAP AG Homepage</AlternativeName> <Description languageCode="EN">Hyperlink to SAP AG</Description> <ExternalLinkWebURI>http://www.sap.com/</ExternalLinkWebURI> </Document> <!-- File attachment--> <Document ActionCode="01"> <VisibleIndicator>true</VisibleIndicator> <CategoryCode>2</CategoryCode> <TypeCode>10001</TypeCode> <MIMECode>image/jpg</MIMECode> <Name>Image</Name> <AlternativeName>Picture</AlternativeName> <Description languageCode="EN">Picture for customer card</Description> <FileContent ActionCode="01"> <BinaryObject mimeCode="image/png" characterSetCode="" format="" fileName="" uri="">AQIDBAUGBwgJAA==</BinaryObject> </FileContent> </Document> </AttachmentFolder> <DuplicateCheckApplyIndicator>false</DuplicateCheckApplyIndicator> <!-- Only relevant for Switzerland <EnterpriseIdentificationNumber>Token 1057</EnterpriseIdentificationNumber> <n1:EnterpriseIdentificationSupplementCode xmlns:n1="http://sap.com/xi/AP/Globalization">1</n1:EnterpriseIdentificationSupplementCode> --> <!--Only relevant for China <n1:TaxPayerCategoryCode xmlns:n1="http://sap.com/xi/AP/Globalization">001</n1:TaxPayerCategoryCode> --> </Customer> </n0:CustomerBundleMaintainRequest_sync_V1>
In case the business option "Multichannel for Document Output" is enabled above the section with "CommunicationArrangement" is invalid and has to be replaced by "CommunicationArrangementMultiChannel" as shown below:
<!-- Payment Processing --> <CommunicationArrangementMultiChannel actionCode="01" > <ObjectNodeSenderTechnicalID>007</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>11</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationChannel communicationEmailListCompleteTransmissionIndicator="true" > <CommunicationMediumTypeCode>PRT</CommunicationMediumTypeCode> <OutputRequestFormTemplateCode>F0007</OutputRequestFormTemplateCode> <OutputCopyNumberValue>5</OutputCopyNumberValue> </CommunicationChannel> </CommunicationArrangementMultiChannel> <!-- Sales Order Processing Out--> <CommunicationArrangementMultiChannel actionCode="01" > <ObjectNodeSenderTechnicalID>008</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>27</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationChannel communicationEmailListCompleteTransmissionIndicator="true" > <CommunicationMediumTypeCode>INT</CommunicationMediumTypeCode> <CommunicationEmail> <EmailURI>to@sap.com</EmailURI> </CommunicationEmail> <CommunicationEmail> <RecipientFieldTypeCode>CC</RecipientFieldTypeCode> <EmailURI>cc@sap.com</EmailURI> </CommunicationEmail> </CommunicationChannel> </CommunicationArrangementMultiChannel>
Here is an example web service request to create a corporate account:
<n0:CustomerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <!-- Creating a corporate account --> <BasicMessageHeader> <ID>1234567890ABCDEF</ID> <UUID>12345678-90AB-CDEF-0123-456789ABCDEF</UUID> </BasicMessageHeader> <Customer actionCode="01" addressInformationListCompleteTransmissionIndicator="true" bankDetailsListCompleteTransmissionIndicator="true" communicationArrangementListCompleteTransmissionIndicator="true" directResponsibilityListCompleteTransmissionIndicator="true" operatingHoursInformationListCompleteTransmissionIndicator="true" paymentCardDetailsListCompleteTransmissionIndicator="true" relationshipListCompleteTransmissionIndicator="true" salesArrangementListCompleteTransmissionIndicator="true" taxNumberListCompleteTransmissionIndicator="true" generalProductTaxExemptionListCompleteTransmissionIndicator="true" contactPersonListCompleteTransmissionIndicator="true" paymentDataListCompleteTransmissionIndicator="true" textListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>01</ObjectNodeSenderTechnicalID> <!--Only relevant for changing <ChangeStateID>20101201082957.5189461</ChangeStateID>--> <InternalID>CP100110</InternalID> <!--The UUID cannot be changed--> <!--<UUID>12345678-90AB-CDEF-0123-456789ABCDEF</UUID>--> <CategoryCode>2</CategoryCode> <!-- Code 2 marks as coorperate account --> <ProspectIndicator>false</ProspectIndicator> <CustomerIndicator>true</CustomerIndicator> <LifeCycleStatusCode>2</LifeCycleStatusCode> <!-- General information --> <Organisation> <CompanyLegalFormCode>14</CompanyLegalFormCode> <FirstLineName>Silverstar Wholesale Corp</FirstLineName> <SecondLineName>Name Second Line</SecondLineName> </Organisation> <ContactAllowedCode>1</ContactAllowedCode> <LegalCompetenceIndicator>true</LegalCompetenceIndicator> <DunAndBradstreetNumberID>111164750</DunAndBradstreetNumberID> <GlobalLocationNumberID>111164750</GlobalLocationNumberID> <ABCClassificationCode>A</ABCClassificationCode> <NielsenRegionCode>01</NielsenRegionCode> <IndustrialSectorCode>11</IndustrialSectorCode> <!-- Maintain company adress information--> <AddressInformation actionCode="01" addressUsageListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>02</ObjectNodeSenderTechnicalID> <AddressUsage actionCode="01"> <ObjectNodeSenderTechnicalID>03</ObjectNodeSenderTechnicalID> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <DefaultIndicator>false</DefaultIndicator> </AddressUsage> <Address actionCode="01" telephoneListCompleteTransmissionIndicator="true"> <CorrespondenceLanguageCode>EN</CorrespondenceLanguageCode> <PreferredCommunicationMediumTypeCode>LET</PreferredCommunicationMediumTypeCode> <EmailURI>customer01@bydmail.com</EmailURI> <FacsimileFormattedNumberDescription>+1 7164824867</FacsimileFormattedNumberDescription> <PostalAddress> <CountryCode>US</CountryCode> <RegionCode>RegionCode</RegionCode> <CountyName>CountyName</CountyName> <CityName>Buffalo</CityName> <AdditionalCityName>AddCityName</AdditionalCityName> <DistrictName>DistrName</DistrictName> <StreetPostalCode>14204</StreetPostalCode> <POBoxPostalCode>23456</POBoxPostalCode> <CompanyPostalCode/> <StreetPrefixName>StrPrefixName</StreetPrefixName> <AdditionalStreetPrefixName>AddStrPrefixName</AdditionalStreetPrefixName> <StreetName>Seneca Street</StreetName> <StreetSuffixName>StrSuffixName</StreetSuffixName> <AdditionalStreetSuffixName>AddStrSuffixName</AdditionalStreetSuffixName> <HouseID>145</HouseID> <CareOfName>CareOf</CareOfName> <POBoxDeviatingCountryCode>DE</POBoxDeviatingCountryCode> <POBoxDeviatingRegionCode>01</POBoxDeviatingRegionCode> <POBoxDeviatingCityName>DevCity</POBoxDeviatingCityName> <POBoxID>box</POBoxID> <POBoxIndicator>true</POBoxIndicator> <TaxJurisdictionCode>AL</TaxJurisdictionCode> <TimeZoneCode>UTC</TimeZoneCode> </PostalAddress> <Telephone> <ObjectNodeSenderTechnicalID>04</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+12 34567890</FormattedNumberDescription> <MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator> </Telephone> <Telephone> <ObjectNodeSenderTechnicalID>05</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 7164824863</FormattedNumberDescription> <MobilePhoneNumberIndicator>false</MobilePhoneNumberIndicator> </Telephone> <WebURI>http://www.company.com/</WebURI> </Address> </AddressInformation> <!-- Maintain relations to existing business partners --> <Relationship actionCode="01"> <ObjectNodeSenderTechnicalID>06</ObjectNodeSenderTechnicalID> <RelationshipBusinessPartnerInternalID>C_1281</RelationshipBusinessPartnerInternalID> <RoleCode>BUR001-1</RoleCode> </Relationship> <!-- Manage account contact person relations --> <ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>07</ObjectNodeSenderTechnicalID> <DefaultContactPersonIndicator>true</DefaultContactPersonIndicator> <FormOfAddressCode>0002</FormOfAddressCode> <AcademicTitleCode>0002</AcademicTitleCode> <GivenName>Frank</GivenName> <MiddleName>MiddleName</MiddleName> <FamilyName>Sent</FamilyName> <BirthName>BirthName</BirthName> <NickName>NickName</NickName> <GenderCode>1</GenderCode> <BirthDate>1999-01-24</BirthDate> <NonVerbalCommunicationLanguageCode>DE</NonVerbalCommunicationLanguageCode> <OccupationCode>0004</OccupationCode> <BusinessPartnerFunctionTypeCode>0028</BusinessPartnerFunctionTypeCode> <BusinessPartnerFunctionalAreaCode>0003</BusinessPartnerFunctionalAreaCode> <VIPReasonCode>A</VIPReasonCode> <MaritalStatusCode>1</MaritalStatusCode> <WorkplacePreferredCommunicationMediumTypeCode>INT</WorkplacePreferredCommunicationMediumTypeCode> <WorkplaceEmailURI>mr.test@test.com</WorkplaceEmailURI> <WorkplaceFacsimileFormattedNumberDescription>+1 7164824867</WorkplaceFacsimileFormattedNumberDescription> <WorkplaceTelephone> <ObjectNodeSenderTechnicalID>08</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 7164824863</FormattedNumberDescription> <MobilePhoneNumberIndicator>false</MobilePhoneNumberIndicator> </WorkplaceTelephone> <WorkplaceWebURI>http://www.contact.com/</WorkplaceWebURI> <WorkplaceFunctionalTitleName>Manager</WorkplaceFunctionalTitleName> <WorkplaceDepartmentName>ContactDepartment</WorkplaceDepartmentName> <WorkplaceBuildingID>Buff01</WorkplaceBuildingID> <WorkplaceFloorID>100</WorkplaceFloorID> <WorkplaceRoomID>R101</WorkplaceRoomID> <!--Private Address--> <AddressInformation actionCode="01"> <Address actionCode="01" telephoneListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>09</ObjectNodeSenderTechnicalID> <EmailURI>private@contact.com</EmailURI> <FacsimileFormattedNumberDescription>+98 76543210</FacsimileFormattedNumberDescription> <PostalAddress> <CountryCode>US</CountryCode> <RegionCode>RegionCode</RegionCode> <CountyName>CountyName</CountyName> <CityName>Buffalo</CityName> <AdditionalCityName>AddCityName</AdditionalCityName> <DistrictName>DistrName</DistrictName> <StreetPostalCode>14204</StreetPostalCode> <POBoxPostalCode>23457</POBoxPostalCode> <CompanyPostalCode/> <StreetPrefixName>StrPrefixName</StreetPrefixName> <AdditionalStreetPrefixName>AddPrefixName</AdditionalStreetPrefixName> <StreetName>Seneca Street</StreetName> <StreetSuffixName>StreetSufixName</StreetSuffixName> <AdditionalStreetSuffixName>AddStrSuffixName</AdditionalStreetSuffixName> <HouseID>145</HouseID> <CareOfName>CareOf2</CareOfName> <POBoxDeviatingCountryCode>DE</POBoxDeviatingCountryCode> <POBoxDeviatingRegionCode>02</POBoxDeviatingRegionCode> <POBoxDeviatingCityName>DevCityName</POBoxDeviatingCityName> <POBoxID>POBoxID</POBoxID> <POBoxIndicator>true</POBoxIndicator> <TaxJurisdictionCode>AL</TaxJurisdictionCode> <TimeZoneCode>UTC</TimeZoneCode> </PostalAddress> <Telephone> <ObjectNodeSenderTechnicalID>10</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 7164824863</FormattedNumberDescription> <MobilePhoneNumberIndicator>false</MobilePhoneNumberIndicator> </Telephone> </Address> <AddressUsage actionCode="01"> <ObjectNodeSenderTechnicalID>11</ObjectNodeSenderTechnicalID> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <DefaultIndicator>false</DefaultIndicator> </AddressUsage> </AddressInformation> </ContactPerson> <!-- Manage account collaboration business document settings.--> <!-- Payment Processing--> <CommunicationArrangement actionCode="01"> <ObjectNodeSenderTechnicalID>12</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>11</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationMediumTypeCode>PRT</CommunicationMediumTypeCode> <OutputRequestFormTemplateCode>F0007</OutputRequestFormTemplateCode> <OutputCopyNumberValue>5</OutputCopyNumberValue> </CommunicationArrangement> <!-- Sales Order Processing Out--> <CommunicationArrangement actionCode="01"> <ObjectNodeSenderTechnicalID>13</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>27</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationMediumTypeCode>INT</CommunicationMediumTypeCode> <EMailURI>b.bb@bbb.bb</EMailURI> </CommunicationArrangement> <!-- Customer Invoice Processing Out--> <CommunicationArrangement actionCode="01"> <ObjectNodeSenderTechnicalID>14</ObjectNodeSenderTechnicalID> <CompoundServiceInterfaceCode>28</CompoundServiceInterfaceCode> <EnabledIndicator>true</EnabledIndicator> <CommunicationMediumTypeCode>FAX</CommunicationMediumTypeCode> <FacsimileFormattedNumberDescription>9876543210123456789</FacsimileFormattedNumberDescription> </CommunicationArrangement> <!-- Assign employees as directly responsible for the account--> <DirectResponsibility actionCode="01"> <ObjectNodeSenderTechnicalID>15</ObjectNodeSenderTechnicalID> <PartyRoleCode>145</PartyRoleCode> <EmployeeID>MDEC3626</EmployeeID> </DirectResponsibility> <!-- Maintain account sales data --> <SalesArrangement> <ObjectNodeSenderTechnicalID>16</ObjectNodeSenderTechnicalID> <SalesOrganisationID>P1110</SalesOrganisationID> <DistributionChannelCode>02</DistributionChannelCode> <Incoterms> <ClassificationCode>CFR</ClassificationCode> <TransferLocationName>FRA</TransferLocationName> </Incoterms> <DeliveryPriorityCode>1</DeliveryPriorityCode> <CompleteDeliveryRequestedIndicator>true</CompleteDeliveryRequestedIndicator> <CurrencyCode>USD</CurrencyCode> <CustomerGroupCode>01</CustomerGroupCode> <CashDiscountTermsCode>1001</CashDiscountTermsCode> </SalesArrangement> <InvoicingBlockingReasonCode>03</InvoicingBlockingReasonCode> <!-- 03: Pricing incomplete --> <CustomerTransactionDocumentFulfilmentBlockingReasonCode>91</CustomerTransactionDocumentFulfilmentBlockingReasonCode> <!-- 91: Customer request --> <CustomerBlockingReasonCode>05</CustomerBlockingReasonCode> <!-- 05: Always Prospect --> <!-- Add bank accounts --> <BankDetails actionCode="01"> <ObjectNodeSenderTechnicalID>17</ObjectNodeSenderTechnicalID> <ID>BD01</ID> <BankInternalID>76</BankInternalID> <!--Bank routing IDs are not necessary because of the identification with the internal ID <BankRoutingID>Token 723</BankRoutingID> <BankRoutingIDTypeCode>Tok</BankRoutingIDTypeCode> <BankStandardID>Token 725</BankStandardID>--> <BankAccountID>12345678</BankAccountID> <BankAccountIDCheckDigitValue>90</BankAccountIDCheckDigitValue> <BankAccountTypeCode>10</BankAccountTypeCode> <BankAccountHolderName>Silverstar Wholesale Corp</BankAccountHolderName> <!--<BankAccountStandardID>Token 730</BankAccountStandardID>--> <ValidityPeriod> <StartDate>1999-01-24</StartDate> <EndDate>9999-01-24</EndDate> </ValidityPeriod> <!--Only relevant for China <n2:BankDirectoryBranchID xmlns:n2="http://sap.com/xi/AP/Globalization">0006</n2:BankDirectoryBranchID> <n2:GoldenTaxRelevanceIndicator xmlns:n2="http://sap.com/xi/AP/Globalization">false </n2:GoldenTaxRelevanceIndicator>--> </BankDetails> <!-- Add payment cards --> <PaymentCardDetails actionCode="01"> <ObjectNodeSenderTechnicalID>012</ObjectNodeSenderTechnicalID> <ID>CARD_1</ID> <PaymentCardTypeCode>2</PaymentCardTypeCode> <PaymentCardID schemeAgencyID="HTTPS://WWW.COMPUTOP.DE">0538261015836111</PaymentCardID> <PaymentCardHolderName>Frank Sent</PaymentCardHolderName> <PaymentCardExpirationDate>2999-01-24</PaymentCardExpirationDate> <DefaultIndicator>true</DefaultIndicator> <BlockingReasonCode>1</BlockingReasonCode> <StreetName>Seneca Street</StreetName> <HouseID>145</HouseID> <PostalCode>14204</PostalCode> <CityName>Buffalo</CityName> <RegionCode>RegionCode</RegionCode> <CountryCode>US</CountryCode> </PaymentCardDetails> <!-- Manage company specific account payment data --> <PaymentData actionCode="01" paymentFormListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>19</ObjectNodeSenderTechnicalID> <CompanyID>1000</CompanyID> <AccountDeterminationDebtorGroupCode>4010</AccountDeterminationDebtorGroupCode> <AccountDebtorExternalID>DID100</AccountDebtorExternalID> <PaymentBlockingReasonCode>2</PaymentBlockingReasonCode> <PaymentBlockExpirationDateTime>2016-03-28T12:00:00.1234567Z</PaymentBlockExpirationDateTime> <PaymentForm actionCode="01"> <PaymentFormCode>02</PaymentFormCode> <!--Credit card--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>05</PaymentFormCode> <!--Bank Transfer--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>06</PaymentFormCode> <!--Check--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>13</PaymentFormCode> <!--Direct Debit (Authorization for Payer’s Bank)--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>16</PaymentFormCode> <!--Bill of Exchange Receivable Without Acceptance--> </PaymentForm> <PaymentForm actionCode="01"> <PaymentFormCode>17</PaymentFormCode> <!--Bill of Exchange Receivable with Acceptance--> </PaymentForm> <CreditLimitAmount currencyCode="EUR">1000</CreditLimitAmount> <DirectDebitBankDetailsID>BD01</DirectDebitBankDetailsID> <DirectDebitValidityPeriod> <StartDate>1999-01-24</StartDate> <EndDate>2999-01-24</EndDate> </DirectDebitValidityPeriod> <PaymentCardDetailsID>CARD_1</PaymentCardDetailsID> <PaymentCardValidityPeriod> <StartDate>1999-01-24</StartDate> <EndDate>2999-01-24</EndDate> </PaymentCardValidityPeriod> <BillOfExchangeBankDetailsID>BD01</BillOfExchangeBankDetailsID> <PaymentAdviceRequiredIndicator>true</PaymentAdviceRequiredIndicator> <FirstPaymentInstructionCode>20</FirstPaymentInstructionCode> <!--<SecondPaymentInstructionCode>Tok</SecondPaymentInstructionCode> <ThirdPaymentInstructionCode>Tok</ThirdPaymentInstructionCode> <FourthPaymentInstructionCode>Tok </FourthPaymentInstructionCode>--> <BankChargeBearerCode>SHA</BankChargeBearerCode> </PaymentData> <!-- Maintain account tax numbers --> <TaxNumber actionCode="01"> <ObjectNodeSenderTechnicalID>21</ObjectNodeSenderTechnicalID> <CountryCode>US</CountryCode> <TaxIdentificationNumberTypeCode>1</TaxIdentificationNumberTypeCode> <PartyTaxID>12124444</PartyTaxID> </TaxNumber> <!-- Maintain tax exemption details --> <GeneralProductTaxExemption actionCode="01"> <ObjectNodeSenderTechnicalID>22</ObjectNodeSenderTechnicalID> <CountryCode>DE</CountryCode> <RegionCode>08</RegionCode> <TaxTypeCode listID="">1</TaxTypeCode> <ReasonCode>7</ReasonCode> </GeneralProductTaxExemption> <!-- Maintain account contact hours --> <OperatingHoursInformation actionCode="01" recurringDayProgrammeListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>23</ObjectNodeSenderTechnicalID> <RoleCode>A</RoleCode> <RecurringDayProgramme operatingHoursListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>22</ObjectNodeSenderTechnicalID> <WeekdaySelection> <MondayIndicator>true</MondayIndicator> <TuesdayIndicator>true</TuesdayIndicator> <WednesdayIndicator>true</WednesdayIndicator> <ThursdayIndicator>true</ThursdayIndicator> <FridayIndicator>true</FridayIndicator> <SaturdayIndicator>false</SaturdayIndicator> <SundayIndicator>false</SundayIndicator> </WeekdaySelection> <OperatingHours> <ObjectNodeSenderTechnicalID>23</ObjectNodeSenderTechnicalID> <TimePeriod> <StartTime>09:00:00</StartTime> <EndTime>18:00:00</EndTime> </TimePeriod> </OperatingHours> </RecurringDayProgramme> </OperatingHoursInformation> <!-- Maintain customer attachments like documents, images, links... --> <AttachmentFolder DocumentListCompleteTransmissionIndicator="true" ActionCode="01"> <!-- Link attachment --> <Document ActionCode="01"> <VisibleIndicator>true</VisibleIndicator> <CategoryCode>3</CategoryCode> <TypeCode>10001</TypeCode> <Name>SAP AG</Name> <AlternativeName>SAP AG Homepage</AlternativeName> <Description languageCode="EN">Hyperlink to SAP AG</Description> <ExternalLinkWebURI>http://www.sap.com/</ExternalLinkWebURI> </Document> <!-- File attachment --> <Document ActionCode="01"> <VisibleIndicator>true</VisibleIndicator> <CategoryCode>2</CategoryCode> <TypeCode>10001</TypeCode> <MIMECode>image/jpg</MIMECode> <Name>Logo</Name> <AlternativeName>Company Logo</AlternativeName> <Description languageCode="EN">The Company`s logo</Description> <FileContent ActionCode="01"> <BinaryObject mimeCode="image/png" characterSetCode="" format="" fileName="" uri="">AQIDBAUGBwgJAA==</BinaryObject> </FileContent> </Document> </AttachmentFolder> <!-- Add account notes, financial data notes or internal/external sales notes --> <Text actionCode="01"> <ObjectNodeSenderTechnicalID>24</ObjectNodeSenderTechnicalID> <TypeCode>10034</TypeCode> <ContentText>English Text</ContentText> </Text> <DuplicateCheckApplyIndicator>false</DuplicateCheckApplyIndicator> <!--Only relevant for Switzerland--> <!--<EnterpriseIdentificationNumber>Token 1057</EnterpriseIdentificationNumber> <n1:EnterpriseIdentificationSupplementCode xmlns:n1="http://sap.com/xi/AP/Globalization">1 </n1:EnterpriseIdentificationSupplementCode>--> <!--Only relevant for China <n1:TaxPayerCategoryCode xmlns:n1="http://sap.com/xi/AP/Globalization">001 </n1:TaxPayerCategoryCode>--> </Customer> </n0:CustomerBundleMaintainRequest_sync_V1>
Here is an example web service request to add a new contact person to an existing corporate account:
<glob:CustomerBundleMaintainRequest_sync_V1> <BasicMessageHeader> <!-- unique message ID for idem potency --> <ID>00163E028B321ED1A3F2321E995E7378</ID> </BasicMessageHeader> <!-- Add new contact to existing account "CP100110", do not change account (action code 06 = "no action") --> <!-- this sample xml contains not all elements, please check WSDL to get the full list of elements --> <Customer actionCode="06" addressInformationListCompleteTransmissionIndicator="false" bankDetailsListCompleteTransmissionIndicator="false" communicationArrangementListCompleteTransmissionIndicator="false" directResponsibilityListCompleteTransmissionIndicator="false" operatingHoursInformationListCompleteTransmissionIndicator="false" paymentCardDetailsListCompleteTransmissionIndicator="false" relationshipListCompleteTransmissionIndicator="false" salesArrangementListCompleteTransmissionIndicator="false" taxNumberListCompleteTransmissionIndicator="false" generalProductTaxExemptionListCompleteTransmissionIndicator="false" contactPersonListCompleteTransmissionIndicator="false" paymentDataListCompleteTransmissionIndicator="false" textListCompleteTransmissionIndicator="false"> <!-- handle for log items --> <ObjectNodeSenderTechnicalID>001</ObjectNodeSenderTechnicalID> <!-- Provide account ID or UUID --> <InternalID>CP100110</InternalID> <!-- Create Contact person (action code 01 = "create") --> <ContactPerson actionCode="01" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="false"> <ObjectNodeSenderTechnicalID>208</ObjectNodeSenderTechnicalID> <!-- The contact will be created with the given UUID, the UUID can be used to create additional ship-to/bill-to relationships between the account and the contact --> <BusinessPartnerContactUUID>12345678-90AB-CDEF-0123-456789ABCD90</BusinessPartnerContactUUID> <!-- InternalID is empty => the system picks automatically an ID from the internal number range --> <BusinessPartnerContactInternalID></BusinessPartnerContactInternalID> <DefaultContactPersonIndicator>true</DefaultContactPersonIndicator> <GivenName>Frank</GivenName> <FamilyName>Sent</FamilyName> <GenderCode>1</GenderCode> <BirthDate>1999-01-24</BirthDate> <NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode> <!-- UUID of account address to which the workplace address shall be assigned to (if required create new account address as well) --> <WorkplaceBusinessAddressUUID>12345678-90AB-CDEF-0123-456789ABCDEF</WorkplaceBusinessAddressUUID> <WorkplacePreferredCommunicationMediumTypeCode>INT</WorkplacePreferredCommunicationMediumTypeCode> <WorkplaceEmailURI>frank.sent@test.com</WorkplaceEmailURI> <WorkplaceFacsimileFormattedNumberDescription>+1 7164824863</WorkplaceFacsimileFormattedNumberDescription> <WorkplaceTelephone> <ObjectNodeSenderTechnicalID>209</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 716482483</FormattedNumberDescription> <MobilePhoneNumberIndicator>false </MobilePhoneNumberIndicator> </WorkplaceTelephone> <WorkplaceFunctionalTitleName>Manager</WorkplaceFunctionalTitleName> <WorkplaceDepartmentName>ContactDepartment</WorkplaceDepartmentName> <WorkplaceBuildingID>Buff01</WorkplaceBuildingID> <WorkplaceFloorID>100</WorkplaceFloorID> <WorkplaceRoomID>R101</WorkplaceRoomID> <!-- Contact personal/privat address --> <AddressInformation actionCode="01"> <ObjectNodeSenderTechnicalID>210</ObjectNodeSenderTechnicalID> <Address actionCode="01" telephoneListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>211</ObjectNodeSenderTechnicalID> <EmailURI>private@contact.com</EmailURI> <PostalAddress> <CountryCode>US</CountryCode> <CityName>Buffalo</CityName> <StreetPostalCode>14204</StreetPostalCode> <StreetName>Seneca Street</StreetName> <!-- further postal address elements see WSDL --> </PostalAddress> <Telephone> <ObjectNodeSenderTechnicalID>212</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+12 345642</FormattedNumberDescription> <MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator> </Telephone> </Address> <!-- Address usage XXDEFAULT = "main privat address" --> <AddressUsage actionCode="01"> <ObjectNodeSenderTechnicalID>213</ObjectNodeSenderTechnicalID> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <DefaultIndicator>false</DefaultIndicator> </AddressUsage> </AddressInformation> <!-- Create contact with status 2 = "active" --> <LifeCycleStatusCode>2</LifeCycleStatusCode> </ContactPerson> <Relationship actionCode="01"> <ObjectNodeSenderTechnicalID>300</ObjectNodeSenderTechnicalID> <!-- UUID of contact person, for further relationships (e.g. bill-to, ship-to) --> <RelationshipBusinessPartnerUUID>12345678-90AB-CDEF-0123-456789ABCD80</RelationshipBusinessPartnerUUID> <!-- Role code CRMH04-1 = "Has the Bill-To Party" --> <RoleCode>CRMH04-1</RoleCode> </Relationship> </Customer> </glob:CustomerBundleMaintainRequest_sync_V1>
Here is an example web service request to update a corporate account and a contact person assigned to the corporate account:
<glob:CustomerBundleMaintainRequest_sync_V1> <BasicMessageHeader> <!-- Unique message ID for idem potency --> <ID>00163E028B321ED1A3F2321E995E7378</ID> </BasicMessageHeader> <!-- Update account "CP100110" (action code 02 = "update") --> <!-- This sample xml contains not all elements, please check WSDL to get the full list of elements. All elements, which are not included in the web service request, will not be changed in the target system. --> <Customer actionCode="02" addressInformationListCompleteTransmissionIndicator="false" bankDetailsListCompleteTransmissionIndicator="false" communicationArrangementListCompleteTransmissionIndicator="false" directResponsibilityListCompleteTransmissionIndicator="false" operatingHoursInformationListCompleteTransmissionIndicator="false" paymentCardDetailsListCompleteTransmissionIndicator="false" relationshipListCompleteTransmissionIndicator="false" salesArrangementListCompleteTransmissionIndicator="false" taxNumberListCompleteTransmissionIndicator="false" generalProductTaxExemptionListCompleteTransmissionIndicator="false" contactPersonListCompleteTransmissionIndicator="false" paymentDataListCompleteTransmissionIndicator="false" textListCompleteTransmissionIndicator="false"> <!-- handle for log items --> <ObjectNodeSenderTechnicalID>001</ObjectNodeSenderTechnicalID> <!-- Provide InternalID to identify the account --> <InternalID>CP100110</InternalID> <!-- Category code 2 means "corporate account" --> <CategoryCode>2</CategoryCode> <!-- The account is a customer, not a prospect --> <ProspectIndicator>false</ProspectIndicator> <CustomerIndicator>true</CustomerIndicator> <!-- The account shall be "active" (status code = '2') --> <LifeCycleStatusCode>2</LifeCycleStatusCode> <Organisation> <!-- The company form 14 = "C Corporation" --> <CompanyLegalFormCode>14</CompanyLegalFormCode> <FirstLineName>Silverstar Wholesale Corp</FirstLineName> </Organisation> <!-- <ContactAllowedCode>1</ContactAllowedCode> <LegalCompetenceIndicator>true</LegalCompetenceIndicator> <DunAndBradstreetNumberID>?</DunAndBradstreetNumberID> <GlobalLocationNumberID>?</GlobalLocationNumberID> <ABCClassificationCode>A</ABCClassificationCode> <NielsenRegionCode>01</NielsenRegionCode> <IndustrialSectorCode>11</IndustrialSectorCode> --> <!-- Update existing account address; provide address UUID as key! --> <AddressInformation actionCode="02" addressUsageListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>002</ObjectNodeSenderTechnicalID> <UUID>12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <!-- The same address is used as main address, ship-to and bill-to address --> <!-- Address usage XXDEFAULT = "main address" --> <AddressUsage actionCode="04"> <ObjectNodeSenderTechnicalID>003</ObjectNodeSenderTechnicalID> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <DefaultIndicator>false</DefaultIndicator> </AddressUsage> <AddressUsage actionCode="04"> <ObjectNodeSenderTechnicalID>004</ObjectNodeSenderTechnicalID> <AddressUsageCode>SHIP_TO</AddressUsageCode> <!-- this ship-to address is the default ship-to address --> <DefaultIndicator>true</DefaultIndicator> </AddressUsage> <AddressUsage actionCode="04"> <ObjectNodeSenderTechnicalID>005</ObjectNodeSenderTechnicalID> <AddressUsageCode>BILL_TO</AddressUsageCode> <!-- this bill-to address is the default bill-to address --> <DefaultIndicator>true</DefaultIndicator> </AddressUsage> <!-- Account postal address --> <Address actionCode="04" telephoneListCompleteTransmissionIndicator="true"> <CorrespondenceLanguageCode>EN</CorrespondenceLanguageCode> <PreferredCommunicationMediumTypeCode>LET</PreferredCommunicationMediumTypeCode> <EmailURI>customer01@bydmail.com</EmailURI> <FacsimileFormattedNumberDescription>+1 7164824867</FacsimileFormattedNumberDescription> <PostalAddress> <CountryCode>US</CountryCode> <CityName>Buffalo</CityName> <StreetPostalCode>14204</StreetPostalCode> <StreetName>Seneca Street</StreetName> <!-- further postal address elements see WSDL --> </PostalAddress> <!-- Account address telephone --> <Telephone> <ObjectNodeSenderTechnicalID>006</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 7164824863</FormattedNumberDescription> <MobilePhoneNumberIndicator>false</MobilePhoneNumberIndicator> </Telephone> <Telephone> <ObjectNodeSenderTechnicalID>007</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+12 34567890</FormattedNumberDescription> <MobilePhoneNumberIndicator>true</MobilePhoneNumberIndicator> </Telephone> <WebURI>http://www.company.com</WebURI> </Address> </AddressInformation> <!-- Update contact person "CC02"; provide BusinessPartnerContactUUID or BusinessPartnerContactInternalID as key! --> <ContactPerson actionCode="02" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="false"> <ObjectNodeSenderTechnicalID>208</ObjectNodeSenderTechnicalID> <BusinessPartnerContactUUID>12345678-90AB-CDEF-0123-456789ABCD80</BusinessPartnerContactUUID> <BusinessPartnerContactInternalID>CC02</BusinessPartnerContactInternalID> <DefaultContactPersonIndicator>true</DefaultContactPersonIndicator> <GivenName>Frank</GivenName> <FamilyName>Sent</FamilyName> <GenderCode>1</GenderCode> <BirthDate>1999-01-24</BirthDate> <NonVerbalCommunicationLanguageCode>EN</NonVerbalCommunicationLanguageCode> <!-- UUID of account address to which the workplace address shall be assigned to --> <WorkplaceBusinessAddressUUID>12345678-90AB-CDEF-0123-456789ABCDEF</WorkplaceBusinessAddressUUID> <WorkplacePreferredCommunicationMediumTypeCode>INT</WorkplacePreferredCommunicationMediumTypeCode> <WorkplaceEmailURI>mr.test@test.com</WorkplaceEmailURI> <WorkplaceFacsimileFormattedNumberDescription>+1 7164824863</WorkplaceFacsimileFormattedNumberDescription> <WorkplaceTelephone> <ObjectNodeSenderTechnicalID>209</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+1 7164824863</FormattedNumberDescription> <MobilePhoneNumberIndicator>false</MobilePhoneNumberIndicator> </WorkplaceTelephone> <WorkplaceFunctionalTitleName>Manager</WorkplaceFunctionalTitleName> <WorkplaceDepartmentName>ContactDepartment</WorkplaceDepartmentName> <WorkplaceBuildingID>Buff01</WorkplaceBuildingID> <WorkplaceFloorID>200</WorkplaceFloorID> <WorkplaceRoomID>R201</WorkplaceRoomID> <!-- Update existing privat address; provide address UUID as key! --> <AddressInformation actionCode="02"> <ObjectNodeSenderTechnicalID>210</ObjectNodeSenderTechnicalID> <UUID>12345678-90AB-CDEF-0123-456789ABCD50</UUID> <Address actionCode="04" telephoneListCompleteTransmissionIndicator="true"> <ObjectNodeSenderTechnicalID>211</ObjectNodeSenderTechnicalID> <EmailURI>franksent.private@contact.com</EmailURI> <PostalAddress> <CountryCode>US</CountryCode> <CityName>Buffalo</CityName> <StreetPostalCode>14204</StreetPostalCode> <StreetName>Seneca Ave</StreetName> <!-- further postal address elements see WSDL --> </PostalAddress> <Telephone> <ObjectNodeSenderTechnicalID>212</ObjectNodeSenderTechnicalID> <FormattedNumberDescription>+12 345642</FormattedNumberDescription> <MobilePhoneNumberIndicator>true </MobilePhoneNumberIndicator> </Telephone> </Address> <!-- Address usage XXDEFAULT = "main privat address" --> <AddressUsage actionCode="04"> <ObjectNodeSenderTechnicalID>213</ObjectNodeSenderTechnicalID> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <DefaultIndicator>false</DefaultIndicator> </AddressUsage> </AddressInformation> <LifeCycleStatusCode>2</LifeCycleStatusCode> </ContactPerson> </Customer> </glob:CustomerBundleMaintainRequest_sync_V1>
Here is an example web service request to create an account "Test Company Inc" along with the contact responsible "Test Contact". This contact is then associated to an employee for groupware subscription.
<n0:CustomerBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID/> <UUID/> </BasicMessageHeader> <Customer actionCode="04" addressInformationListCompleteTransmissionIndicator="true" bankDetailsListCompleteTransmissionIndicator="true" communicationArrangementListCompleteTransmissionIndicator="true" directResponsibilityListCompleteTransmissionIndicator="true" operatingHoursInformationListCompleteTransmissionIndicator="true" paymentCardDetailsListCompleteTransmissionIndicator="true" relationshipListCompleteTransmissionIndicator="true" salesArrangementListCompleteTransmissionIndicator="true" taxNumberListCompleteTransmissionIndicator="true" generalProductTaxExemptionListCompleteTransmissionIndicator="true" contactPersonListCompleteTransmissionIndicator="true" paymentDataListCompleteTransmissionIndicator="true" textListCompleteTransmissionIndicator="true"> <CategoryCode>2</CategoryCode> <CustomerIndicator>true</CustomerIndicator> <LifeCycleStatusCode>2</LifeCycleStatusCode> <Organisation> <FirstLineName>Test Company Inc</FirstLineName> </Organisation> <ContactPerson actionCode="04" workplaceTelephoneListCompleteTransmissionIndicator="true" addressInformationListCompleteTransmissionIndicator="true"> <FamilyName>Test Contact</FamilyName> <LifeCycleStatusCode>2</LifeCycleStatusCode> <ResponsibleEmployee actionCode="04"> <ResponsibleEmployeeUUID>00163e03-390f-1ed2-a391-b1a36530b88f</ResponsibleEmployeeUUID> <PartyRoleCode>597</PartyRoleCode> <GroupwareSubscription>true</GroupwareSubscription> </ResponsibleEmployee> <responsibleEmployeeListCompleteTransmissionIndicator>true</responsibleEmployeeListCompleteTransmissionIndicator> </ContactPerson> </Customer> </n0:CustomerBundleMaintainRequest_sync_V1>
Description | Maintain accounts |
Name | MaintainBundle_V1 |
Synchronous | yes |
Release Status | Released |
To create, update, or delete customer master data
The request message of the operation MaintainBundle_V1 contains a BasicMessageHeader node element as well as a Customer node element that contains the account data to be created or updated. The detailed structure of the customer node will be explained in the following sub-chapters. The customer node can occur multiple times in the request message – this means that multiple accounts 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 account-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as account InternalID and account UUID.
The Customer node element contains all general account information such as ID, UUID, names, and other identifications.
The data for this node is related to General data on the account UI.
For private accounts, the CategoryCode is 1. For corporate accounts, the CategoryCode is 2.
The following elements are relevant for corporate accounts only:
Organization node element
DunAndBradstreetNumberID, GlobalLocationNumberID, NielsenRegionCode and IndustrialSectorCode node elements
The Person node element is relevant for private accounts only.
The elements ProspectIndicator and CustomerIndicator correspond to the Prospect checkbox on the UI.
The InternalID element corresponds to the Account ID on the UI - the UUID element is not visible on the UI, but can be retrieved using query and read web services.
The PeppolParticipantID element corresponds to the same field on the UI, it needs to be entered with the following format:
<IdentifierType>:<IdentifierValue>
The element CreateFromBusinessPartnerIndicator can be used to assign the role customer to existing business partners.
If this element is supplied with value "true", then the following constraints have to be considered:
The actionCode attribute in message node Customer shall have value "02" (Update) or "04" (Save), otherwise an error message is returned.
If the actionCode attribute in message node Customer has value "02" or "04" and the elements InternalID or the UUID are filled, then the system assigns the role customer to the business partner with the given InternalID or UUID.
If the actionCode attribute in message node Customer has value "04" and the elements InternalID and UUID are both empty, then the system creates a new customer using internal numbering.
The AddressInformation node element can be used to create and change account 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).
Validity Period sub node of address information and address usage allows you to enter validity period for the address and the usage types. It enables you to maintain time bound addresses. Address usage validity has to be within the validity of the address information.
Example
<AddressInformation addressUsageListCompleteTransmissionIndicator="true"> <AddressInformationValidityPeriod> <StartDate>2010-01-01</StartDate> <EndDate>2015-12-31</EndDate> </AddressInformationValidityPeriod> <AddressUsage> <AddressUsageCode>XXDEFAULT</AddressUsageCode> <AddressUsageValidityPeriod> <StartDate>2010-01-01</StartDate> <EndDate>2015-12-31</EndDate> </AddressUsageValidityPeriod> </AddressUsage>... </AddressInformation>
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 Relationship node element can be used to create, change, and delete relations to an existing business partner.
The data of the Relationship node corresponds to the Relationships data on the UI.
The ContactPerson node element can be used to create and change account contact person relations.
The ContactPerson node element is relevant for corporate accounts only. Data of this 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 account.
Existing contact persons can be assigned to accounts using the Relationship and ContactPerson node elements:
Relationship node element: Provide the RelationshipBusinessPartnerUUID or RelationshipBusinessPartnerInternalID elements to identify the related contact and set RoleCode BUR001-1.
ContactPerson node element: Provide elements BusinessPartnerContactUUID or the BusinessPartnerContactInternalID to identify the related contact. In addition, the actionCode must be set to 04 (save).
Contact person relations can be removed from an account using the Relationship and ContactPerson node elements.
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.
By default, the contact person workplace address refers to the main/default account address of the account to which the contact person is assigned. If an account has multiple account addresses, the workplace address of the contact person can be related to an account address of your choice. To assign a contact person workplace address, enter the AddressInformation UUID of the account address in the WorkplaceBusinessAddressUUID element of the contact person.
The Main Private Address and additional Private Addresses can be provided in the AddressInformation sub-node element of the ContactPerson node element. The Main Private Address is the address with the AddressUsageCode = XXDEFAULT. All other Private Addresses do not have an AddressUsage at all.
If changes to the WorkplaceTelephone are to be performed, the workplaceTelephoneListCompleteTransmissionIndicator must be set to true, and the complete list has to be transmitted.
The CommunicationArrangement node element can be used to create and change account collaboration business document settings.
The data for this node element is related to Communication - Collaboration data on the account UI.
Relation between UI and request message:
User Interface | Request Message |
---|---|
Business Document Name | CompoundServiceInterfaceCode |
Active checkbox | EnabledIndicator |
Output Channel | CommunicationMediumTypeCode |
Template | OutputRequestFormTemplateCode |
Print Queue ID | PrintQueueIdentifier |
Number of Copies | OutputCopyNumberValue |
Fax | FacsimileFormattedNumberDescription |
EMailURI | |
Transformation | TransformationID |
Possible values for Business Document Type Codes are listed below:
Business Document Name | CompoundServiceInterfaceCode |
---|---|
Advanced Shipping Notification Outbound | 10 |
Dunning Outbound | 108 |
Remittance Advice Outbound | 11 |
Service Confirmation | 1347 |
Sales Order Confirmation | 27 |
Customer Invoice / Credit Memo | 28 |
Service Request | 337 |
Sales Quote | 46 |
Customer Return | 585 |
Service Order Confirmation | 89 |
Customer Contract Confirmation | 992 |
If communication arrangements are to be created together with an account in a single web service request, the Customer - InternalID element has to be supplied. If you want to use internal numbering for account IDs, create the customer first without communication arrangements and add communication arrangements in a second web service request.
The element TransformationID is used in E-invoicing scenarios and can only be filled for certain Business Document Types.
The node CommunicationArrangementMultiChannel replaces the node CommunicationArrangement in case the business option "Multichannel for Document Output" is enabled.
Relation between UI and request message:
User Interface | Request Message |
---|---|
Business Document Name | CompoundServiceInterfaceCode |
Active checkbox | EnabledIndicator |
Output Channel Settings (row of table) | CommunicationChannel |
Output Channel | CommunicationMediumTypeCode |
Template | OutputRequestFormTemplateCode |
Duplicate | DuplicateIndicator |
Print Queue ID | PrintQueueIdentifier |
Number of Copies | OutputCopyNumberValue |
Fax | FacsimileFormattedNumberDescription |
Channel Settings (row of table) | CommunicationEmail |
Recipient Type | RecipientFieldTypeCode |
EMailURI | |
Transformation | TransformationID |
Note that the EnabledIndicator is only meaningful for business documents for which it is possible to toggle the "Active" flag on the User Interface.
The element TransformationID is used in E-invoicing scenarios and can only be filled for certain Business Document Types.
The valid Recipient Type Codes are listed below:
User Interface | Request Message |
---|---|
To | TO |
Cc | CC |
Bcc | BCC |
For a given Business Document all Output Channels can only be changed jointly, i.e. communicationChannelListCompleteTransmissionIndicator = true is mandatory.
The DirectResponsibility node element can be used to assign employees as directly responsible for the account.
Data for this node element is related to Contacts – Responsibilities on the account UI.
The most common party role codes are the following:
Party Role Code | Description |
---|---|
142 | Employee Responsible - Sales |
143 | Employee Responsible - Marketing |
144 | Service Performer - Sales Orders |
145 | Service Performer - Service |
Example
<Customer actionCode="06"> <InternalID>CPSENT</InternalID> <DirectResponsibility actionCode="01"> <ObjectNodeSenderTechnicalID>009</ObjectNodeSenderTechnicalID> <PartyRoleCode>145</PartyRoleCode> <EmployeeID>MDEC3626</EmployeeID> </DirectResponsibility> </Customer>
This xml snippet assigns the employee with the ID P0123 as a Sales Responsible to the account with ID A10001.
The SalesArrangement node element can be used to create and change account sales data.
Data for this node element is related to Sales Data on the account UI. The data contained in the Document Block section of the account UI corresponds to the CustomerBlockingReasonCode, CustomerTransactionDocumentFulfilmentBlockingReasonCode and InvoicingBlockingReasonCode elements in the request message.
The BankDetails node element can be used to add bank accounts to accounts.
Data for this node element is related to Financial Data – Bank Data – Bank Accounts on the UI.
To add a bank account, you must provide the relevant bank from the bank directory.
Bank directory entries are identified according to the following algorithm:
If the BankUUID is supplied, it is used to identify the bank directory entry; all other bank IDs are not checked.
If the BankInternalID is supplied, it is used to identify the respective bank directory entry; bank routing ID and bank standard ID is not checked.
Identify the bank directory entry by BankRoutingID, BankRoutingIDTypeCode and BankStandardID.
If only the BankRoutingID and BankRoutingIDTypeCode are supplied, the system queries bank directory entries based on the bank routing information. If there are multiple bank directory entries with the same bank routing information, the system queries for a lead bank directory entry. If no lead bank directory entry is available, an arbitrary bank directory entry is selected and a warning message stating that the reference is not uniquely determined is returned as log item.
If only the BankStandardID is supplied, the bank directory entry is determined based on the bank standard ID. If there are multiple bank directory entries with the same bank standard ID, the system queries for a lead bank directory entry. If no lead bank directory entry is available, an arbitrary bank directory entry is selected and a warning message stating that the reference is not uniquely determined is returned as a log item.
The PaymentCardDetails node element can be used to add and assign payment cards to accounts.
Data for this node element is related to Financial Data – Bank Data – Credit Cards on the UI.
If the payment card provided in the web service request already exists, the payment card is assigned to the account. If the payment card does not exist, it is created by the web service.
If an update or deletion of existing PaymentCardDetails is to be performed, the ID or the combination of PaymentCardTypeCode and PaymentCardID must be provided. During a delete operation, only the assignment between account and payment card master data is deleted. The payment card master data itself is not deleted.
The element PaymentCardID is the identifier of the payment card and is a token provided by the payment service provider that represents the payment card. The attribute schemeAgencyID of element PaymentCardID must always be filled with the URL of the payment service provider that has provided the token (PaymentCardID). Examples for schemeAgencyIDs are HTTP://WWW.PAYMETRIC.COM or HTTPS://WWW.COMPUTOP.DE.
The element PaymentCardTypeCode is the type code for the payment card. The following are example code values:
Payment card type code | Description |
---|---|
1 | American Express |
2 | VISA |
3 | Master Card |
4 | Diners Club |
Note: The element PaymentCardID must not contain the plain text credit card number due to PCI Data Security Standard compliance.
Note: To create payment cards, the payment service provider (PSP) that provides the token for the payment card must be set up as a supplier in the system and its DUNS number must be maintained.
The PaymentData node element can be used to create and change company-specific account payment data.
Data for this node element is related to Financial Data - Payment Data on the UI.
The Payment Methods list is modeled as list of PaymentFormCodes in the request message. The Direct Debit payment method and the corresponding SEPA Mandates cannot be maintained with this service. The Direct Debit (Authorization for Payer's Bank) payment method, however, is supported by this service.
The PaymentCardDetailsID and DirectDebitBankDetailsID elements of the request message correspond to the ID fields of the BankDetails and PaymentCardDetails nodes.
The following data cannot be maintained with this web service:
Dunning Block Reason
Dunning Block Expiry Date
Doubtful Debtor
Direct Debit and SEPA Mandates
Dunning information
Note: To maintain payment data, the LifeCycleStatusCode of the related account must be 2 (Active).
The TaxNumber node element can be used to maintain account tax numbers.
Data for this node element is related to Financial Data – Tax Data on the UI.
The GeneralProductTaxExemption node element can be used to maintain tax exemption details.
Data for this node element is related to Financial Data – Tax Data on the UI.
The OperatingHoursInformation node element can be used to maintain account contact hours.
Data for this node element can be found on the account UI as Communication – Contact Hours.
On the UI, Calling Hours, Visiting Hours and Goods Receiving Hours are displayed separately - in the web service request message type, these elements are provided as RoleCode.
The values are:
Role code | Description |
---|---|
A | Calling Hours |
C | Visiting Hours |
B | Goods Receiving Hours |
Each row in the first table on the user interface corresponds to an entry in the RecurringDayProgramme-WeekdaySelection element in the request message. Each row in the second table on the user interface corresponds to an entry in the RecurringDayProgramme-OperatingHours element.
If an update operation on the RecurringDayProgramme or the RecurringDayProgramme-OperatingHours node is to be performed, the recurringDayProgrammeListCompleteTransmissionIndicator/operatingHoursListCompleteTransmissionIndicator must be set to true, and the complete list must be transmitted.
The Text node element can be used to maintain account notes, financial data notes, and internal and external sales notes.
Data for this node element can be found as Notes on the account UI. Possible text type codes include the following:
Type code | Description |
---|---|
10034 | Account note |
10039 | Financial data note |
10065 | Internal sales note |
10066 | External sales note |
If an update operation on the Text node is to be performed, the textListCompleteTransmissionIndicator must be set to true, and the complete list has to be transmitted. Notes in accounts can be changed by the creator only.
Note: If a web service call is performed using a communication user, then created texts cannot be changed afterwards through the UI, because it is not possible to log on with the communication user.
The AttachmentFolder node element can be used to add and remove account attachments.
Data for this node can be found on the account UI as attachments. On the user interface, files and links can be created. In the web service request, links and files are differentiated through the CategoryCode:
Category code | Description |
---|---|
2 | Document |
3 | Link |
The different types of attachments are differentiated by the TypeCode:
Type code | Description |
---|---|
10001 | Standard attachment |
10016 | Business partner image |
10017 | Business card |
To create link attachments, document elements must be as follows:
Element | Value |
---|---|
VisibleIndicator | true |
CategoryCode | 3 |
TypeCode | <none> |
AlternativeName | <Document Title> |
ExternalLinkWebURI | <link URI> |
Description | <Comment> |
To create file attachments, document elements must be as follows:
Element | Value |
---|---|
VisibleIndicator | true |
CategoryCode | 2 |
TypeCode | <none> |
Name | <Document Title> |
AlternativeName | <Document Title> |
Description | <Comment> |
It is a term used in the sales arrangement for an account. The complete delivery request indicator indicates that a delivery has to be a complete delivery.
Release | Change Description | Details |
1902 | segment CommunicationArrangementMultiChannel is added | This segment should be used when business feature MultiChannel-Output is scoped |
1905 | segment CommunicationArrangement is changed | field PrintQueueId is added |
2002 | Supporting TransformationID for E-Invoicing | The CommunicationArrangement node and the CommunicationChannel node are enhanced with the element TransformationID. |
2202 | New Additional Identifier | The Customer node is enhanced with the element PeppolParticipantIdentifier |
Description | Check accounts |
Name | CheckMaintainBundle_V1 |
Synchronous | yes |
Release Status | Released |
To check if customer 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.