PDF Export

createBpBuffered

This method is used to create businesspartners and the parameters are identical with the service ,CreateBusinessPartner’. The transferred businesspartners are certainly not transmitted directly into the AVS/3-System but will be stored temporarily in a data base. The advantage of this procedure is that an isolation between AVS/3-System and the web service will be made and due to this the web service for the businesspartner system becomes more robust. Another Advantage is, that the client never take care of the stack management in GPA.

The disadvantage of this procedure is that the business partners are not directly imported in the AVS/3-System and therefore they have a temporal delay about 5 minutes between the transmission of data and to be loaded into the AVS/3-System. To transfer the business partner into the backend system an additional transfer job must be provided. Please request this job from your dsb account manager.

As already mentioned the transferred and returned parameters are for this service identical with the service ,createBp ‘.

  • Object: /net/dsb/avs3/Bp
  • Method: createBpBuffered
  • Version: 2.0.0
  • Fuba:

Parameter

NameType / max. lengthmandatory?Description
business-partnern.a. m XML-Fragment ‚business-partner‘ see below

Response Element

empty Message-Frame

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>
    <input-office>123456789012</input-office>
    <input-user>123456789012</input-user>
    <stack-name></stack-name>
    <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>
  </body>
</message>

Request Structure

This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information