getIssuesByOrderNumber

Object: /net/dsb/avs3/SubscriptionOrder
Method: getIssuesByOrderNumber
Version: 2.0.0
Fuba: /DSB/ISM_E_GET_VA_AUFTR

Returns all future issues from the AVS/3 that matches the order-number and the given filter criterias until the given end date.

Filter	Rule
A	All issues will be returned
E	If the subscription is a renewal(REN), it only returns, if X_IN_EXPIRY_PERIOD = true(X). Otherwise if the subscription is a „normal“ one(ABO/ABOS), it only returns if X_IN_DELIVERY_PERIOD = true(X).
C	Only the issues will be returned, that matches the “calculated” filter
P	Only the issues will be returned, that matches the “pa” filter

Parameter

Name	Type / max. length	mandatory?	Description
order-number	AN / 10	M	order number
date-to	AN / 10	M	End date Format YYYY-MM-DD
date-type	AN / 1	-	Type of the date values: 1: On Sale Date 2: Issue Label Run Date (not yet implemented) 3: Technical Issue Date (default)
filter	AN / 1	M	A → All, E → Expiry, C → Calculated, P → Payed

Response Element

issue-result elements

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>
    <order-number>123</order-number>
    <date-to>2011-10-02</date-to>
    <filter>A</filter>
  </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>
   <issue-result>
    ...
    </issue-result>
  </body>
</message>

Response Structure

Structure <issue-result>

<issue-result>
    <order-type>ABO</order-type>
    <!-- 0 ... n -->
    <issue-details>
    …
    </issue-details>
</issue-result>

Element Definitions

Field Name	Length	Type	m = Must k = can (m) = conditional Must	Remark, field supply or encoding
order-type		C	Type of order (REN, ABO, ABOS)
issue-details 0 … n

Structure <issue-details>

<!-- 0 ... n -->
<issue-details>
    <issue>0000000815</issue>
    <publication>00000001</publication>
    <edition>00000001</edition>
    <date-of-publication>2010-07-16</date-of-publication>
    <year-of-issue>2010</year-of-issue>
    <issue-number-in-year>0028</issue-number-in-year>
    <issue-number>00000815</issue-number>
    <distribution-article-number></distribution-article-number>
    <mix-type></mix-type>
    <ean></ean>
    <date-of-first-sale>2010-07-16</date-of-first-sale>
    <date-of-first-shipping>2010-07-22</date-of-first-shipping>
    <description></description>
    <is-payed>false</is-payed>
    <is-calculated>false</is-calculated>
    <is-in-expiry-period>true</is-in-expiry-period>
</issue-details>

Element Definitions

Field Name	Length	Type	Remark, field supply or encoding
issue	10	C	issue
publication	8	C	publication
edition	8	C	edition
date-of-publication	10	D	date of publication im Format YYYY-MM-DD
year-of-issue	4	C	year of issue Format YYYY
issue-number-in-year	4	C	issue number in year
issue-number	9	C	Issue-number of edition in format HHHH/YYYY.
distribution-article-number	13	C	article number not in subscription based Response included
mix-type	2	C	mixtype
ean	18	D	Issues european article number
date-of-first-sale	10	D	Date-of-first-sale- in format YYYY-MM-DD
date-of-first-shipping	10	D	Date-of-first-shipping- in format YYYY-MM-DD
description	50	C	Description
is-payed		B	issue is payed
is-calculated		B	issue is calculated
is-in-expiry-period		B	issue is in expiry period