PDF Export

getNewOrders (Version 3)

  • Object: /net/dsb/avs3/SubscriptionOrder
  • Method: getNewOrders
  • Version: 3.0.0
  • Fuba: /DSB/ISM_E_SEL_NEUERF

This method expects a date, time and a publication. This given point in time is used to determine all subscriptions which have been stored or created. Those are then returned from this method. This search takes place within the active and inactive subscriptions. If no 'return-address-type' is in the request, the 'WE' is sent back as default.

Furthermore date and time of day of the latest entry will be returned. This point in time can then be used for the next inquiry.

Important hint:

It is possible to customize which attributes (order or business-partner) are returned in the response. This is maintained in the customizing table /DSB/JET_MERK_RE or /DSB/JET_MERK_GP in AVS/3. Please get in touch with customer service if you would like to add additional values. All values are returned if the wildcard (*) is set.

Parameter

NameType / LengthOpt. / Mandat.Description
bodyn.a. m Description of XML-Fragments see below

Response Element

Description of XML-Fragment see below

This method alone makes sense only in few cases. Normally it is about to investigate all active subscriptions and to transfer them to the client. Therefore an alternative to this method is available that receives the same return structure in a data file.

This data contains then all active subscriptions for the client. This all the active subscriptions will be transferred it can of course be found out on the opposite location what subscribers have quit.

Both services (deliver data per file or per web service) can be used unattached from each other but also combined. Following scenarios are conceivable: - The opposite side is only interested in new accesses of subscriptions ⇒ the web service can be used alone.

  • All active subscriptions have to be transferred to the opposite side at the same time new subscriptions have not to be transferred very contemporary (> 24 h) ⇒ Transmission of data per file is enough.
  • All active subscriptions have to be transmitted to the opposite side and at the same time new subscriptions have to transmitted contemporary (> 24 h)⇒ Transmission of data per file and transmission of all new subscriptions per web service.

In case that both procedures are used at the same time, it must be observed that both data transmissions run synchronized otherwise it can arise a data loss. One possibility to guarantee this, is not to delete the per web service transmitted subscriptions, in general in a fixed period of time (like for example 1 week).

Example Request

<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>
    <from-date>2004-09-07</from-date>
    <from-time>22:10:59</from-time>
    <publication>00010729</publication>
    <return-address-type>AG</return-address-type>
    <return-address-type>RE</return-address-type>
    <return-address-type>WE</return-address-type>
    <return-address-at-time>L</return-address-at-time>
    <return-extended-communication-data>Y</return-extended-communication-data>
    <return-renewal-payment-data>Y</return-renewal-payment-data>
    <return-renewal-issue-remaining>N</return-renewal-issue-remaining>
    <return-current-suspension-data>N</return-current-suspension-data>
    <return-extended-premium-data>N</return-extended-premium-data>
  </body>
</message>

Example Response

<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>
    <next-date>2004-06-14</next-date>
    <next-time>11:53:57</next-time>
    <client>999</client>
    <new-subscription>
      <order-number>4270055033</order-number>
      <publication>00000187</publication>
      <edition>00000187</edition>
      <mix-type>01</mix-type>
      <issue-nr-from>0004/2004</issue-nr-from>
      <issue-nr-to/>
      <valid-to>0000-00-00</valid-to>
      <end-reason/>
      <promotion-source>505Q32</promotion-source>
      <pr-source-var/>
      <reference-doc>WEBWEB1106</reference-doc>
      <cust-order-nr>1050691121569</cust-order-nr>
      <cust-order-date>20030418</cust-order-date>
      <subscr-phase/>
      <price-group/>
      <price-key>CP01</price-key>
      <business-partner>
        <role>WE</role>
        <bp-number>1003698418</bp-number>
        <full-salutation>Sehr geehrter Herr Tester</full-salutation>
        <first-name>Martin</first-name>
        <full-last-name>Tester</full-last-name>
        <name-addition/>
        <titel/>
        <salutation>Herr</salutation>
        <company1/>
        <company2/>
        <company3/>
        <zipcode>94036</zipcode>
        <street>GleiwitzerStr.3C</street>
        <po-box-zipcode/>
        <po-box/>
        <po-box-city/>
        <major-cust-zip/>
        <city>Passau</city>
        <district/>
        <country-code>DE</country-code>
        <country>Deutschland</country>
        <phone-number>0851-8519784</phone-number>
        <fax-number/>
        <email-address>hallo@web.de</email-address>
      </business-partner>
      <order-attribute>
        <type>EMAIL</type>
        <value>hallo@web.de</value>
      </order-attribute>
      <order-attribute>
        <type>ARCHIV</type>
        <value>123456789</value>
      </order-attribute>
    </new-subscription>
  ...
  </body>
</message>

Request Structure

Response Structure

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