CrossAd WebServices API version 860v1

The CrossAd WebService API offers a way to create and update entities such as orders, customers, contacts etc.

Please refer to Files and Libraries for general documents such as Developers Guide, Release notes etc.

It is strongly recommended to use SoapUI, Swagger or Postman for exploring and testing the services.
Also, when reporting issues with CAI, please reproduce the issue and send the request/response attached to the report.

About this documentation

This documentation is mainly automatically generated using the tool Enunciate.

Services

Namespace http://soap.mc.api_860v1.integration.crossad.atex.com/ (wsdl)
name description
MCOrderService
Namespace http://soap.base.api_860v1.integration.crossad.atex.com/ (wsdl)
name description
BaseService
Namespace http://soap.print.api_860v1.integration.crossad.atex.com/ (wsdl)
name description
OrderService The OrderService offers an API for creating, updating and reading orders in a CrossAd database.
Namespace http://soap.dwl.api_860v1.integration.crossad.atex.com/ (wsdl)
name description
DataWarehouseService
Namespace http://soap.customer.api_860v1.integration.crossad.atex.com/ (wsdl)
name description
CustomerService
Namespace http://soap.adapters.api_860v1.integration.crossad.atex.com/ (wsdl)
name description
AdapterService

The services API is also accessible by a set of client-side libraries that can be downloaded from the files and libraries page.

Data Types

XML

Default Namespace (schema)
type description
nillable
orderServiceUpdate
customField
customListItem
logMessage
MCJob The representation of a job, should be considered read-only. In order to create or update a job there are other representations in the ws-api to use.
MCJobComment The representation of a Job comment, should be considered read-only. In order to create or update connections there are other representations in the ws-api to use.
nillableDate A NillableDate is used for differentiating between three states of an entity field representing a specific instant in time, defined in ISO8601 format using UTC as the reference time zone, when creating or updating data:
  • the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
  • the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
  • the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples: 

 <!-- Use the default date -->
 <!-- <date /> -->
 
 <!-- Explicitly set date to an undefined (null) value -->
 <date nil="true" />
 
 <!-- Use a specific date value -->
 <date>2012-11-29T00:00:00+01:00</date>
Update Examples: 
 <!-- Do not update the date -->
 <-- <date /> -->
 
 <!-- Explicitly reset date to an undefined (null) value -->
 <date nil="true" />
 
 <!-- Update the date to a new value -->
 <date>2013-01-06T00:00:00+01:00</date>

nillableDecimal A NillableDecimal is used for differentiating between three states of an entity field representing a signed decimal value when creating or updating data:
  • the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
  • the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
  • the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples: 

 <!-- Use the default integer value -->
 <!-- <decimal /> -->
 
 <!-- Explicitly set integer to an undefined (null) value -->
 <decimal nil="true" />
 
 <!-- Use a specific integer value -->
 <decimal>12345.67</decimal>
Update Examples: 
 <!-- Do not update the integer -->
 <-- <decimal /> -->
 
 <!-- Explicitly reset integer to an undefined (null) value -->
 <decimal nil="true" />
 
 <!-- Update the integer to a new value -->
 <decimal>123.456</decimal>

nillableLong A NillableLong is used for differentiating between three states of an entity field representing a 64bit signed integer when creating or updating data:
  • the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
  • the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
  • the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples: 

 <!-- Use the default integer value -->
 <!-- <long /> -->
 
 <!-- Explicitly set integer to an undefined (null) value -->
 <long nil="true" />
 
 <!-- Use a specific integer value -->
 <long>1234567890</long>
Update Examples: 
 <!-- Do not update the integer -->
 <-- <long /> -->
 
 <!-- Explicitly reset integer to an undefined (null) value -->
 <long nil="true" />
 
 <!-- Update the integer to a new value -->
 <long>1337</long>

nillableShort A NillableShort is used for differentiating between three states of an entity field representing a 16bit signed integer when creating or updating data:
  • the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
  • the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
  • the entity is defined with a value to store or update existing data with.

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples: 

 <!-- Use the default integer value -->
 <!-- <short /> -->
 
 <!-- Explicitly set integer to an undefined (null) value -->
 <short nil="true" />
 
 <!-- Use a specific integer value -->
 <short>8080</short>
Update Examples: 
 <!-- Do not update the integer -->
 <-- <short /> -->
 
 <!-- Explicitly reset integer to an undefined (null) value -->
 <short nil="true" />
 
 <!-- Update the integer to a new value -->
 <short>-1</short>

nillableString A NillableStrong is used for differentiating between three states of an entity field representing a string of characters when creating or updating data:
  • the entity is left-out (completely undefined), meaning it should be initialized to a suitable default value in a create operation, and not affect existing data in an update operation.
  • the entity is explicitly defined as NIL to reset existing data to a uninitialized state (usually null in the database).
  • the entity is defined with a value to store or update existing data with.
    (The string value could be empty, but it is the same as null in an Oracle database)

NOTE: It is not allowed for a nillable to be both NIL and have a non-null value, or to have a null value and be defined as not NIL.

Create Examples: 

 <!-- Use the default string value -->
 <!-- <string /> -->
 
 <!-- Explicitly set string to an undefined (null) value -->
 <string nil="true" />
 
 <!-- Use a specific string value -->
 <string>Novice</string>
Update Examples: 
 <!-- Do not update the string -->
 <-- <string /> -->
 
 <!-- Explicitly reset string to an undefined (null) value -->
 <string nil="true" />
 
 <!-- Update the string to a new value -->
 <string>Expert</string>

stamp The representation of an event, should be considered read-only.
adserverAdapter
adserverAdspace Class representing inventory for a unit.
adserverAdspaceVariant Class representing inventory for a unit.
adserverInterval
adserverInventory Class representing inventory for a unit.
adserverInventoryDetail Class representing inventory for a unit during the specified time(from startDate to endDate).
adserverInventoryRequest
adserverInventoryResponse
adserverKeyValue
adserverMapEntity Class respresenting a map-able entity. Could contain anything, both in crossad and in any adserver. Should be stored with the key in db.
adserverMappable Class respresenting a mappable entity. Key is the unique, together with the sourceSystem, name of this entity that should be stored in db. It contains mapEntities A typical use is for addon:s that should be mapped. An addon is of some type(single-select, multiselect, tree etc).
adserverMappablesResponse
adserverPriority
adserverProduct Class representing inventory for a unit.
adserverProductsResponse
adserverSection Class representing inventory for a unit.
mappableResponse
bransch
businessUnit
category
countryCode
DBVersion
legalPerson
operator
prodFlow
prodStatus
programLanguage
stopCode
salesgroup
salesman
address
addressAMD Models the intention to update an extra customer-address. Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - N/A.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cuadrAdrid

budgetCu
budgetCuAMD Models the intention to update a customer-budget. Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = bcPeriod and bcLpcode

budgetInc
budgetIncAMD This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = buiYear

contact
contactAMD Note! There is no unique id for one contact re-used among customers. So some redundancy exist.

Models the intention to update a customer-contact. Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cucoContid

creditReportingBureau
creditReportingBureauRiskAssessment
custActivity Activity record

Key(s) = saplActid

custActivityAsset
custExtSystem
custdealH
custdealHAMD This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cdhDealno, cdhHistlevel, cdhLpcode

custdealU
custdealUAMD This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cduDealId, cduDatemin, cduIntervalmin

custextsysno
custextsysnoAMD

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cesnCuescode

customer The complete representation of a customer.
customerAgency
customerAgencyAMD This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cuagAgencyno and cuagCategory

customerBrand Brand (Swedish: varumärke), e.g. "Pepsodent", "GB Glace" etc
customerBrandAMD Models the intention to update a customer-brand. Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. /NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - N/A.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cubdId

customerBransch
customerBranschAMD

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - N/A
D - Delete

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cubrBransch

Note that AMD_TYPE MODIFY has no effect, this is because all properties are part of the key.

customerCategory
customerCreate Represents the intention to create a new complete customer.
customerEan
customerEanAMD The CustomerEanUpdate data object represents the intention to update an EAN code associated with the customer.

Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. (NillabString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cueanId + cueanReferens

customerEdi
customerEdiAMD This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cuediEdicode

customerINetAddress
customerINetAddressAMD This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - N/A Either you got the id or you dont.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = naAddrdetno

customerOutputFilter
customerProdFlow
customerProdFlowAMD The CustomerProdFlowUpdate data object represents the intention to update a production flow associated with the customer.

Most fields/elements in this object are optional and when left out, the corresponding property will be left unchanged. If a value is provided, the corresponding property will be updated to that specified value.

In some cases, when the property is "nillable", i.e. (NillabString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cupfPrflowcode

customerProfile
customerRiskClass
customerSearchInput
customerSearchResultItem Simple customer object. Returned by searchmethods as "findCustomersByAttributes"
customerType
customerUpdate Models the intention to update a customer. Most fields/elements in this object are optional and when left out, the corresponding customer property will be left unchanged. If a value is provided, the corresponding customer property will be updated to that specified value. In some cases, when the property is "nillable", i.e. / NillableString, NillableDate, NillableShort, NillableLong or NillableDecimal) it is possible to clear/reset the value of a property (effectively setting the associated database field value to null) by setting the nil attribute to true and not providing any value.
customerperlp In a crossAd setup there is normally several legalPersons configured. Representing different papers etc. The LegalPersonMappings makes it possible to configure customer related things like responsible salesman and more per legalPerson.
customerperlpUpdate In a crossAd setup there is normally several legalPersons configured. Representing different papers etc. The LegalPersonMappings makes it possible to configure customer related things like responsible salesman and more per legalPerson.
parInfo PostensAdressRegister PAR (F_ParInfo)
parInfoSearchResult
pagination
peneplan
peneplanAMD
popHeading
searchCustomerParInfoInput
searchModifiedActivitiesInput Input for searching customer activities that have been modified between dates.
searchModifiedCustomersInput Input for searching customers that have been modified between dates.
searchModifiedCustomersResultItem Simple customer object. Returned by search-methods as "searchCustomersModifiedBetween"

Logic for detecting customer creation and deletion. 

 Create: 
 - cuhWhat    = "CU_CUSTNO" 
 - cuhCustno  = New customer no. 
 - cuhOldvalue= Null 
 - cuhNewvalue= New customer no.
 
 Delete: 
 - cuhWhat    = "CU_CUSTNO" 
 - cuhCustno  = Null 
 - cuhOldvalue= Deleted customer no.
 - cuhNewvalue= Null
synonym
synonymAMD

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
D - Delete
.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = cusSynonym

Note that AMD_TYPE MODIFY has no effect, this is because all properties are part of the key.

netSaleRow Representation of a netSaleRow.
onlineRow Representation of a row in table F_WHOUSEONLINE.
adspace
MCAdspaceSize Adspace variant-size for online orderlines (F_BANNERSIZE)
MCAdvertiser The representation of an advertiser, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
MCAdvertiserProfile Stores profile data per legal person for a customer of the order.
MCJobOrderLine The representation of a connection between an Orderline and a Job, should be considered read-only. In order to create or update connections there are other representations in the ws-api to use.
MCLastOrdersInput Input filter for fetching last orders
MCLineItem
businessModel
MCLineItemPricelist The complete representation of a LineItemProduct, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
MCLineItemProduct The complete representation of a LineItemProduct, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
MCLineitemOrderline Lineitem orderline, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
MCOnlineOrderLineAddon Addon for online orderlines
MCOnlineOrderLineAddonValue Addon for online orderlines
MCOnlineOrderLineAdspace Adspace (variant) for online orderlines
MCOnlineOrderLineProduct Product for online orderlines
MCOnlineOrderLineSection Section for online orderlines
MCOnlineOrderline Online orderline, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
MCOrder The complete representation of an order, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
MCOrderCreate The complete representation of a multichannel-order creation..
MCOrderDiscount Discount
MCOrderExclusion
MCOrderExclusionDetail
MCOrderGroupedVolumes
MCOrderGroupedVolumesDetail
MCOrderSummary Object that holds summary of an order
MCOrderUpdate The complete representation of a multichannel-order for update.
MCOrderlineDateInfo Orderline date
MCPrice Abstract superclass of price.

MCPriceDetail PriceDetail
MCPriceOrderSummary OrderSummary multi-channel order price.
MCPriceSummary Summary multi-channel order price.
network
orderStats Order statistics
orderlineStats Order statistics
section
lineitemOrderlineProperties Represents the editable properties of an Orderline with type LINETEM

MCAdvertiserAMD Represents the intention to create a new multichannel advertiser

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field(s) are mandatory.
Key(s) = custno

MCAdvertiserProfileUpdate The profiles are generated by the system, and cannot be manually added or removed.
Values can be updated
MCJobAMD Represents the intention to create/update a order job

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field, delCorrectionCode and delComment are mandatory.
Key(s) = mcjId

MCJobOrderLineAMD Represents the intention to create/update job/orderline connection

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field(s) are mandatory.
Key(s) = mcjolId

MCOnlineOrderLineAddonAMD Addon for online orderlines
MCOnlineOrderLineAdspaceAMD Adspace (variant) for online orderlines

This is a AMD-object, i.e. This object is used for ADD or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - NOTE! Not allowed, you can only add and remove adspaces..
D - Delete

If action is "Delete", only key-field, delCorrectionCode and delComment are mandatory.
Key(s) = advId

MCOnlineOrderLineProductAMD Product for online orderlines
MCOnlineOrderLineSectionAMD Section for online orderline
MCOrderlineAMD Represents the intention to create a new multichannel Orderline

An orderline can be one of these types: ONLINE or LINEITEM, this is determined by the type-property.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field are mandatory.
Note!Depending on system settings delCorrectionCode and delComment may also be mandatory when deleting an orderline.
Key(s) = index

MCOrderlineDateInfoAMD Represents the intention to create a new dateInfo object connected to lineitem

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field are mandatory.
Key(s) = date

onlineOrderlineProperties Represents the editable properties of an Orderline with type ONLINE

metaData Contains information how the CrossAd Integration Webservice is configured... READ-ONLY data
property
abstractOrderPrice Represents a summary of the total order value (gross and net) and partial sums for applied discounts (incl. customer deal), commissions and VAT.

Used as base class for total order value and shared value between order customers

agreementInfo
chargesCriteria
customerPrice Summary of customer price-calculation, Reflects the customer price in WE.
customerPriceDetails Detailed information about a customer price-calculation.
discountDetail Discount mapping in an order

Key = Discount

discountDetailAMD Discount mapping in an order

Key = Discount

discountType
externalJobAsset
externalOrderItem
externalOrderSamling
externalPage
issueDateDetail IssueDate mapping in an order

Key = odIssueDate

issueDateDetailAMD IssueDate mapping in an order

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = odIssueDate

issueLimit
issueLimitAMD Issue Limit mapping representation in an OFFER order.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = orPacode and orPricelist

jobAMD Represents the intention to create/update a order job

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete

If action is "Delete", only key-field, delCorrectionCode and delComment are mandatory.
Key(s) = mcjId

jobOrderChargeAMD
jobOrderDetAMD
lastOrdersInput Input filter for fetching last orders
levelDiscountDetail Level-discount detail with both the defined discount (% or amount) and the calculated counterpart, in addition to the corr.code, level, sort order, type and component (space/color).
options
order The complete representation of an order, should be considered read-only. In order to create or update an order there are other representations in the ws-api to use.
orderCreate Represents the intention to create a new complete order, including order details such as placements and services.
orderDetailProductionUpdate Represents the intention to update the production status for a given product detail. This is only valid if the order has been split on multiple issues and/or editions/zones. TODO: Should it be possible to identify a detail by its material number rather than the date/prodcode/edition/zone?
orderKund The orderKund representation.

It contains the customer related mappings of the order. In order to create or update an orderKund there are other representations in the ws-api to use.

orderKundAMD Represents the intention to create a new orderKund representation.

It contains the customer related mappings of the order.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = okCustno

orderKundPerLp The orderKundPerLp representation.

It contains the LegelPerson related customer commission for an orderKund

orderKundPerLpAMD Represents the intention to create a new orderKundPerLp representation.

It contains the customer commission related mappings of the order.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = okCustno

orderMaterialInfo
orderPrice Partial amounts for row-level gross, discounts, net and also late order discounts.
individually presented for issue volume, issue color and services/insertions.
orderPriceMainSummary Main order summary, reflecting the order summary in MBooker main order window.
orderPriceSecondarySummary Secondary order summary, reflecting the order summary in MBooker price window.
orderPriceShareStatus Information about the validity of customer sharing of an order.
orderPriceSummaryDetails Partial amounts for row-level gross, discounts, net and also late order discounts.
individually presented for issue volume, issue color and services/insertions.
orderProductionUpdate Represents the intention to update one or many production-related properties of an order. This maps more or less to what a user can accomplish in MProd.
orderSalesmenShare The OrderSalesmen representation.

It contains the Salesmen related mappings of the order. In order to create or update an Salesmen share amount for order.

orderSalesmenShareAMD The OrderSalesmen representation.

It contains the Salesmen related mappings of the order. In order to create or update an Salesmen share amount for order.

orderSummary Object that holds summary of an order
orderUpdate Encapsulates data about a print order that is to be updated.
packageDetail Package mapping representation in an order.

Keys = orPacode and orPricelist

packageDetailAMD Package mapping representation in an order.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = orPacode and orPricelist

packet
placement
placementDetail Placement mappings in an order

Key = orPlcode

placementDetailAMD Placement mappings in an order

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = orPlcode

product
productionCodeAMD Production codes can be added to the order to be used to know what should be done in production. But it can also be used for other purpose.

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = opPrflowcode

productionCodeDetail Production codes can be added to the order to be used to know what should be done in production. But it can also be used for other purpose.
salesAmount Object that holds summary for the amounts in F_Order_Kund
salesAmountInput Input for filtering record in F_Order_Kund that should be summarized.
searchModifiedOrdersInput Input for searching orders that have been modified between dates.
searchModifiedOrdersResultItem Simple order object. Returned by search-methods as "searchOrdersModifiedBetween"
service
serviceDetail
serviceDetailAMD Services can be added to the order and can be e.g. insertions or some extra that you charge the customer for. Service can be on the same order as the print order or it can be a "service order".

This is a AMD-object, i.e. This object is used for ADD, MODIFY or DELETE actions.
Type of action is determined by the AMD_TYPE attribute. Possible values are:
A - Add
M - Modify
D - Delete
AM - Add if non existing, else Modify.

If action is "Delete", only key-field(s) are mandatory.
Key(s) = ocServcode and ocOcdate

inData Encapsulates ad-data for inEntry. Model from InData.sef V72
inDataWrapper Wrapper for inData
utData Encapsulates ad-data from inEntry. Model from UtData.sef V72
orderAMD
paymentDetailAMD
subscriptionOrderCreate Subscription order creation
subscriptionOrderLineitemProductAMD
subscriptionOrderOnlineProductAMD
subscriptionOrderPrintFixedSizeAMD
subscriptionOrderUpdate Subscription order update
Namespace ws.integration.crossad.atex.com (schema)
type description
caiFault All SOAP-based WebService operations in the WS API may generate a SOAP 1.2 fault. The Detail element will contain a caiFault element with detailed, application specific information.
logMessage