changeBpAddressBuffered Like 'ChangeBpAddress' this method is used to alter business-partner addresses. The advantage of using this method is that it performs better under higher loads, as well as hides client from the technical details needing to handle Stack Management of the GPA. Important Note: The increase in the performance is due to the business-partners not being directly imported into AVS/3, but stored within a buffer. The client must be aware of a potential 5 minute delay before the changes are visible within AVS/3. Object: /net/dsb/avs3/Bp Method: changeBpAddressBuffered Version: 2.0.0 Fuba: Parameter Name Typ / LängeKann / MussBeschreibung business-partnern.a. m Response Element XML-Fragment ‚bp-change-buffered-response‘ Example Request <?xml version="1.0" encoding="UTF-8"?> <message version="1.0" system="avs/3" > <header> <client>999</client> <avs3-sales-organization>9999</avs3-sales-organization> <avs3-service-provider>123</avs3-service-provider> </header> <body> <business-partner> ... </business-partner> </body> </message> Example Response <?xml version="1.0" encoding="UTF-8"?> <message version="1.0" system="avs/3"> <header> <client>999</client> <avs3-sales-organization>9999</avs3-sales-organization> <avs3-service-provider>123</avs3-service-provider> </header> <body> <bp-change-buffered-response> ... </bp-change-buffered-response> </body> </message> Request Structure Structure <business-partner> <business-partner> <salutation-code action="DELETE"></salutation-code> <prefix action="DELETE"></prefix> <titel-code-academic action="DELETE"></titel-code-academic> <titel-academic action="DELETE"></titel-academic> <titel-code-royal action="DELETE"></titel-code-royal> <titel-royal action="DELETE"></titel-royal> <job-titel action="DELETE"></job-titel> <last-name1 action="DELETE"></last-name1> <last-name2 action="DELETE"></last-name2> <first-name action="DELETE"></first-name> <nick-name action="DELETE"></nick-name> <street action="DELETE"></street> <street-suffix action="DELETE"></street-suffix> <street-number action="DELETE"></street-number> <street-number-suffix action="DELETE"></street-number-suffix> <address-line-1 action="DELETE"></address-line-1> <address-line-2 action="DELETE"></address-line-2> <address-line-3 action="DELETE"></address-line-3> <zipcode action="DELETE"></zipcode> <country-code code-type="ISO" action="DELETE"></country-code> <city action="DELETE"></city> <district action="DELETE"></district> <region-code action="DELETE"></region-code> <region-text action="DELETE"></region-text> <company1 action="DELETE"></company1> <company2 action="DELETE"></company2> <company3 action="DELETE"></company3> <company4 action="DELETE"></company4> <department action="DELETE"></department> <po-box action="DELETE"></po-box> <po-box-zipcode action="DELETE"></po-box-zipcode> <po-box-city action="DELETE"></po-box-city> <po-box-country-code code-type="ISO" action="DELETE"></po-box-country-code> <major-customer-zipcode action="DELETE"></major-customer-zipcode> <address-source action="DELETE"></address-source> <bp-number></bp-number> <eu-sales-tax-number action="DELETE"></eu-sales-tax-number> <date-of-birth action="DELETE"></date-of-birth> <transaction-type>Z2</transaction-type> <valid-from></valid-from> <communication> <communication-type action="DELETE"></communication-type> <communication-value action="DELETE"></communication-value> </communication> <avs-attributes> <sales-organization></sales-organization> <distribution-channel></distribution-channel> <division></division> </avs-attributes> </business-partner> Elementdefinitions Annotation:: For all with “can(k)” marked Elements, exists an addition attribute action. Which content can be either “DELETE” or “UPDATE. In case of DELETE the content of this element will be deleted in the pre-existing business-partner on the AVS/3 System . In case of “UPDATE ” the pre-existing content of this element in the business-partner , will be overwritten. In case of “UPDATE” the pre-existing content of a communicaton entry, it's mandatory to set the 'oldvalue'. Sample.: In case of 'DELETE' the pre existing content has to set in the XML-Tag ... <communication> <communication-type action='DELETE'>WW</communication-type> <communication-value action='DELETE'>test1@tst.de</communicationvalue> </communication> In case of 'UPDATE' the pre-existing content of a communicaton entry, it's mandatory to set the 'oldvalue' ... <communication> <communication-type action='UPDATE'>WW</communication-type> <communication-value action='UPDATE' old-value='test1@tst.de'>test2@tst.de</communicationvalue> </communication> Inserting or updating a communication entry with the communication-default flag. Sample.: <communication> <communication-type>WW</communication-type> <communication-value>test2@tst.de</communication-value> <communication-default>Y</communication-default> </communication> Field LenthTypeText m=Must \ k=can \ (m) = definite must Remark, field supply or recoding salutation-code 2 C salutation k 01 = Mr. 02 = Ms. 99 = unknown further codes are left in a code table if required please ask If a firm address is transferred, is this the salutation of the contact person ( if available) prefix 4 C name prefix k titel-code-academic 4 C Title-academic k Coding see table in enclosure. Attention this table correspond to the base settings of a client. Maybe it must be discussed how far this base settings of the customer have been drifted.. titel-academic 15 C Academic title in clear text (for example Dr.) k titel-code-royal 4 C Title of nobility k Coding see table in enclosure. Attention this table correspond to the base settings of a client. Maybe it must be discussed how far this base settings of the customer have been drifted. titel-royal 15 C Title of nobility in clear text k job-titel 35 C Title of job k last-name1 40 C Lastname1 k If a firm address is transmitted is this the contact person last-name2 40 C Lastname2 k If a firm address is transmitted is this the contact person first-name 40 C Firstname k If a firm address is transmitted is this the contact person nick-name 40 C Nickname k If a firm address is transmitted is this the contact person street 50 C Street k Duty if a street address should be transmitted street-suffix 40 C Street suffix k street-number 10 C House number k Duty if a street address should be transmitted street-number-suffix 10 C House number addition k address-line-1 35 C Address line 1 for UK Address k address-line-2 35 C Address line 2 for UK Address k address-line-3 35 C Address line 3 for UK Address k zipcode 10 C Zipcode k Duty if a street address should be transmitted country-code 3 C contry (KFZ country code) k Coding see table in enclosure city 40 C City k Duty if a street address should be transmitted district 25 C Additon to city (for example district, area….) k region-code 3 C Regions-Code (federal state, province, county) k region-text 25 C Region as cleartext (e.g. County…) k company1 35 C Firm line 1 k company2 35 C Firm line 2 k company3 40 C Firm line 3 k company4 40 C Firm line 4 k department 30 C department k po-box 10 C Po-box k Duty if po-box-zipcode should be transmitted po-box-zipcode 10 C Po-box-zipcode k Duty if a po-box-zipcode should be transmitted po-box-city 40 C Po-box-city k Duty if po-box-zipcode should be transmitted po-box-country-code 3 C Po-box-country k Duty if po-box-zipcode should be transmitted major-customer-zipcode 10 C Major-customer-zipcode k address-source 10 C Address-source Code table, contents states facultyk bp-number 10 C Mandatory bp customer number m eu-sales-tax-number 14 C EG-UST ID number k date-of-birth 10 D Date of birth format: JJJJ-MM-TT k transaction-type 2 C Aktivitäts-Typ m Z2 change adress now ZU Date-Based Address Change BETA valid-from 10 D Date (YYYY-MM-DD) (m) If tansaction-type is 'ZU', then a valid date has to be provided > communication * communication-type 2 C Communication Type m Values Attention : it is always just 1 telephone number, 1 email address and1 fax number receivable! →action C attribute (k) DELETE or UPDATE →old-value 4 C old value(attribute) (k) recommended, if action attribute “UPDATE” * communication-value 50 C Value m Attention : it is always just 1 telephone number, 1 email address and1 fax number receivable! →action C attribute (k) DELETE or UPDATE →old-value 4 C old value(attribute) (k) recommended, if action attribute “UPDATE” * communication-default1 C Default flag k Y to set the new default entry →action C attribute (k) UPDATE > avs-attributes * sales-organization 4 C Verkaufsorganisation im AVS/3 k * distribution-channel 2 C Vertriebsweg im AVS/3 k * division 2 C Sparte im AVS/3 k Response Structure Structure <bp-change-buffered-response> <bp-change-buffered-response> <bp-number></bp-number> <dsb-transaction-id></dsb-transaction-id> </bp-change-buffered-response> Element Definitions Field LengthTypeRemark, field supply or recoding bp-number 10 C bp-number AVS/3 from the Request, if available dsb-transaction-id36 C DSB Transaktion ID. This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.OKMore information