tm connect.erp - guideline for basic implementation · 2020. 12. 7. · dvse gmbh carl-benz-weg 1 d...

DVSE GmbH

Carl-Benz-Weg 1

D 22941 Bargteheide

Tel: +49(0)4532 201401

Fax: +49(0)4532 501052

DVSE GmbH

TM CONNECT.ERP - GUIDELINE

FOR BASIC IMPLEMENTATION

P a g e 1 | 54

TM CONNECT.ERP - GUIDELINE FOR BASIC IMPLEMENTATION

Feb 20, 2019

TABLE OF CONTENT

1. History ........................................................................................................................................... 3

2. General references for implementation ....................................................................................... 3

3. General example for an article request ........................................................................................ 3

3.1. Structure .................................................................................................................................. 3

3.1.1. Credentials ....................................................................................................................... 3

3.1.2. MasterData ...................................................................................................................... 3

3.1.3. ErpArticleInformation ...................................................................................................... 3

3.2. Use of GUIDs ............................................................................................................................ 6

4. TM Connect.ERP uses GUIDs to reference objects. This implementation allows objects to be

used more than once. ............................................................................................................................. 6

4.1. Overall availability ................................................................................................................... 8

4.2. Show availability for locations ................................................................................................. 9

4.3. AvailState and where are they displayed ................................................................................ 9

4.4. Price display ........................................................................................................................... 17

4.5. Scale price .............................................................................................................................. 18

4.6. Misleading descriptions for price types and best practice .................................................... 19

4.7. Replacement articles ............................................................................................................. 20

4.8. Sales unit ............................................................................................................................... 23

4.9. Individual availability icons .................................................................................................... 24

5. TM Connect.ERP - General references for implementation ....................................................... 25

5.1. General references for implementation ............................................................................... 25

6. TM Connect.ERP - General example for an article request ........................................................ 25

6.1. General example for an article request ................................................................................. 25

6.1.1. Structure ........................................................................................................................ 25

6.1.1.1. Credentials ............................................................................................................. 25

6.1.1.2. MasterData ............................................................................................................ 25

6.1.1.3. ErpArticleInformation ............................................................................................ 25

7. TM Connect.ERP - Replacement articles .................................................................................... 28

7.1. Replacement articles ............................................................................................................. 28

8. TM Connect.ERP - Overall availability ......................................................................................... 31

8.1. Overall availability ................................................................................................................. 31

9. TM Connect.ERP - Individual availability icons ........................................................................... 32

9.1. Individual availability icons .................................................................................................... 32

P a g e 2 | 54


Feb 20, 2019

10. TM Connect.ERP - Show availability for locations ................................................................... 33

10.1. Show availability for locations ............................................................................................... 33

11. TM Connect.ERP - Price display ................................................................................................ 34

11.1. Price display ........................................................................................................................... 34

11.2. Scale price .............................................................................................................................. 35

11.3. Misleading descriptions for price types and best practice .................................................... 36

12. TM Connect.ERP - Discount code ............................................................................................. 37

12.1. Discount code ........................................................................................................................ 37

13. AvailState and where are they displayed ................................................................................. 40

14. TM Connect.ERP - Sales unit ..................................................................................................... 48

14.1. Sales unit ............................................................................................................................... 48

15. TM Connect.ERP - The use of GUIDs........................................................................................ 49

15.1. The use of GUIDs ................................................................................................................... 49

16. SendOrder ................................................................................................................................. 51

P a g e 3 | 54


Feb 20, 2019

1. HISTORY

Version Datum Autor Bemerkung

1.0 21.03.2018 Jan Iversen

1.0.1 26.03.2018 Benjamin

Sauer

Irreführende Bezeichnungen der Preistypen und Best Practice in

TMConnect.ERP: EK(4)/VK(5) - TaxIncluded - VAT

2. GENERAL REFERENCES FOR IMPLEMENTATION

To exchange price and availability requests and also orders between catalog and ERP system are used

methods in TMConnect.ERP like <GetErpInformation> and <SendOrder>.

3. GENERAL EXAMPLE FOR AN ARTICLE REQUEST

In the following an article is requested. In the response for this article the total availability

“available”, the availability for a location and two prices (purchase-/sales price) will be transmitted.

3.1. STRUCTURE

3.1.1. CREDENTIALS

In this area the customer number <CustomerID>, user name <Username> and the password

<Password> are sent.

3.1.2. MASTERDATA

General information are exchanged in the MasterData area. This information can be referenced. In

the response the articles and availability states are declared which are used later on.

3.1.3. ERPARTICLEINFORMATION

In this area, the transaction data are exchanged. In the response, e.g. the availability or prices for

articles are sent.

Codeblock 1 Request

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<GetErpInformation xmlns="http://topmotive.eu/TMConnect">

<request>

<Credentials>

<CatalogUserCredentials>

<Username>xxx</Username>

P a g e 4 | 54


Feb 20, 2019

<Password>xxx</Password>

<CustomerId>xxx</CustomerId>

</CatalogUserCredentials>

<IsEncrypted>false</IsEncrypted>

</Credentials>

<LanguageCodeIso639_1>de</LanguageCodeIso639_1>

<ContextId>0</ContextId>

<TimeStamp>2017-11-28T08:37:22.6432869+01:00</TimeStamp>

<MasterData>

<ArticleTmfs>

<ArticleTmf>

<Guid>c629c368-1b31-45a7-b63a-06ef929424ac</Guid>

<ArticleIdErp>123456</ArticleIdErp>

<Type>0</Type>

<ArticleIdSupplier>W 712/75</ArticleIdSupplier>

<Supplier>

<SupplierId>4</SupplierId>

<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>

<ErpArticleInformation>

<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>


<Type>ArticleTmf</Type>

</Item>

<RequestedQuantity>1</RequestedQuantity>

<ConfirmedQuantity xsi:nil="true" />

<SortId>0</SortId>

</ErpInformation>

</ErpArticleInformation>

<TypeId>0</TypeId>

</request>

</GetErpInformation>

</soap:Body>

</soap:Envelope>

Codeblock 2 Response


xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-

utility-1.0.xsd"

xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"

xmlns:tns="http://topmotive.eu/TMConnect"

xmlns:q1="http://microsoft.com/wsdl/types/"

xmlns:q2="http://microsoft.com/wsdl/types/">

<soap:Body>

<GetErpInformationResponse xmlns="http://topmotive.eu/TMConnect">

<GetErpInformationResult>

<MasterData>

<ArticleTmfs>

<ArticleTmf>


P a g e 5 | 54


Feb 20, 2019


<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

<AvailabilityStates>

<AvailabilityState>

<Guid>c629c368-1b31-45a7-b63a-06ef92450700</Guid>

<Type>2</Type>

<ShortDescription>Verfügbar</ShortDescription>

<Description>Verfügbar</Description>

</AvailabilityState>

</AvailabilityStates>

</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>


<SortId>0</SortId>

<Warehouses>

<Warehouse>

<Id>450700</Id>

<Description>Filiale 1</Description>

<IsDefault>true</IsDefault>

<Quantities>

<Quantity>


<AvailabilityState>

<Guid>c629c368-1b31-45a7-b63a-

06ef92450700</Guid>

<Type>AvailabilitySate</Type>


<QuantityPackingUnit>1</QuantityPackingUnit>

</Quantity>

</Quantities>

</Warehouse>

</Warehouses>

<AvailabilityState>




<Prices>

<Price>

<Type>4</Type>

<Description>Einkaufspreis</Description>

<CurrencyCode_Iso_4217>EUR</CurrencyCode_Iso_4217>

<Value>3.6</Value>

</Price>

P a g e 6 | 54


Feb 20, 2019

<Price>

<Type>5</Type>

<Description>Listenpreis</Description>


<Value>5.9</Value>

</Price>

</Prices>

<ConfirmedQuantity>123</ConfirmedQuantity>

</ErpInformation>


<TypeId>0</TypeId>

<Credentials>



<Password>xxxt</Password>




</Credentials>

<StatusId>0</StatusId>

<TimeStamp>2018-03-16T08:27:03.786Z</TimeStamp>

</GetErpInformationResult>

</GetErpInformationResponse>

</soap:Body>

</soap:Envelope>

3.2. USE OF GUIDS

4. TM CONNECT.ERP USES GUIDS TO REFERENCE OBJECTS. THIS

IMPLEMENTATION ALLOWS OBJECTS TO BE USED MORE THAN

ONCE.

Example:

The status "available" only needs to be declared once in the response in the object

<AvailabilityStates>:

Codeblock 3 AvailabilityState


<AvailabilityState>


<Type>2</Type>





Afterwards the AvailabilityStates is referenced by using the GUID in the object <warehouse>

P a g e 7 | 54


Feb 20, 2019

Codeblock 4 AvailabilityState

<Warehouses>

<Warehouse>

<Id>1</Id>

<Description>Warehouse 1</Description>


<Quantities>

<Quantity>


<AvailabilityState>





</Quantity>

</Quantities>

</Warehouse>

<Warehouse>

<Id>1</Id>



<Quantities>

<Quantity>


<AvailabilityState>





</Quantity>

</Quantities>

</Warehouse>

</Warehouses>

P a g e 8 | 54


Feb 20, 2019

4.1. OVERALL AVAILABILITY

The overall availability of an article is sent as <AvaiabilityState> in the <ErpInformation>. A status is

also referenced here which is sent in the area <MasterData>.

Codeblock 5 Main Availability


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>

<Guid>a15f0366-6385-4245-b6fc-2ca54d8d211e</Guid>


</Item>


<ConfirmedQuantity xsi:nil="true"/>

<SortId>0</SortId>

<AvailabilityState>

<Guid>b58b81db-53b0-5883-e811-fa28be0de6f9</Guid>



</ErpInformation>


P a g e 9 | 54


Feb 20, 2019

4.2. SHOW AVAILABILITY FOR LOCATIONS

In order to display several locations in the TM Connect.ERP catalog with one availability, several

<Warehouse> objects must be sent in the response. In the following example, two locations are sent.

The stock (<value>) and the packaging unit are sent for both locations. The fields <ID> and

<Description> are displayed in the catalog.

4.3. AVAILSTATE AND WHERE ARE THEY DISPLAYED

As already mentioned, you can decide for which article you want to send which availability. An article

can have 2 AvailState IDs with different icons and description text, because we expect a GUID for the

article query.

On the picture is an example from another catalog where you can see several prices our customer

sends for his article. He also sends a blue bubble as global availability and behind it he sends the text

"Available in alternative warehouse location" and below you can see the individual warehouse

locations with their own availability states.

For example: response/request, which logismos have to be programmed, how the structure has to

look like

Codeblock 6 Request




P a g e 10 | 54


Feb 20, 2019


<soap:Body>


<request>

<Credentials>







</Credentials>



<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>

<ArticleIdSupplier>0 986 466 346</ArticleIdSupplier>

<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

</ErpInformation>


<TypeId>0</TypeId>

</request>


</soap:Body>

</soap:Envelope>


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Body>





P a g e 11 | 54


Feb 20, 2019

<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>


<AvailabilityState>

<Guid>f98c8f35-a92e-2cbe-e811-1e21829cbd77</Guid>

<Type>3</Type>

<ShortDescription>teilweise verfügbar</ShortDescription>


<AvailabilityState>

<Guid>f98c8f35-a92e-2cbe-e811-1e21866ea677</Guid>

<Type>4</Type>

<ShortDescription>auf Anfrage unter Tel: 43 1 203 05

31</ShortDescription>


<AvailabilityState>

<Guid>f98c8f35-a92e-2cbe-e811-1e21824dc177</Guid>

<Type>6</Type>

<ShortDescription>im Alternativlagerort teilweise

verfügbar</ShortDescription>



</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

<AvailabilityState>




<Prices>

<Price>

<Type>4</Type>

<Description>EK</Description>

<Value>11.77</Value>

<RebateValue xsi:nil="true"/>

<Rebate xsi:nil="true"/>

<CurrencySymbol>€</CurrencySymbol>


P a g e 12 | 54


Feb 20, 2019

<PriceUnit xsi:nil="true"/>

<VAT xsi:nil="true"/>

<TaxIncluded>false</TaxIncluded>

</Price>

<Price>

<Type>9</Type>

<Description>WVP</Description>









</Price>

<Price>

<Type>5</Type>

<Description>LVP</Description>

<Value>33.5</Value>








</Price>

<Price>

<Type>1</Type>

<Description>EVP</Description>

<Value>40.2</Value>








</Price>

</Prices>

<Warehouses>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>110</Id>

<Description>TEST-Warehouse1</Description>

<Quantities>

<Quantity>

<Value>0.0</Value>

<PackagingUnit>ST</PackagingUnit>

<MinQuantity xsi:nil="true"/>

<MaxQuantity xsi:nil="true"/>

<AvailabilityState>

<Guid>f98c8f35-a92e-2cbe-e811-

1e21866ea677</Guid>


P a g e 13 | 54


Feb 20, 2019


<QuantityPackingUnit>1.0</QuantityPackingUnit>

</Quantity>

</Quantities>


</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>999</Id>


<Quantities>

<Quantity>

<Value>2.0</Value>




<AvailabilityState>


1e21829cbd77</Guid>




</Quantity>

</Quantities>

<IsDefault>false</IsDefault>

</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>120</Id>


<Quantities>

<Quantity>

<Value>0.0</Value>




<AvailabilityState>


1e21866ea677</Guid>




</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

</ErpInformation>


<TypeId>0</TypeId>



</soapenv:Body>

</soapenv:Envelope>

P a g e 14 | 54


Feb 20, 2019

example of another catalog that provides its own icons (green bubble with W):

Codeblock 8 Request





<soap:Body>


<request>

<Credentials>







</Credentials>



<MasterData>

<ArticleTmfs>

<ArticleTmf>


<ArticleIdErp>P27933</ArticleIdErp>

<Type>0</Type>

<ArticleIdSupplier>E432L</ArticleIdSupplier>

<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

P a g e 15 | 54


Feb 20, 2019

<Item>



</Item>



<SortId>0</SortId>

</ErpInformation>


<TypeId>0</TypeId>

</request>


</soap:Body>

</soap:Envelope>


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>





<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>


<AvailabilityState>

<Guid>ff7f8ae3-9a06-4870-829c-db410304cf26</Guid>

<Type>3</Type>

<Description>1 verfügbar (W-Lagerartikel)</Description>

<Icon>

<Guid>d9995b6c-a3f6-4c44-b2ec-ca7cbab862c9</Guid>

<Type>Icon</Type>

</Icon>


<AvailabilityState>

<Guid>c334fd4b-2259-41cc-97af-dbb641782b0c</Guid>

<Type>3</Type>

<Description>1 verfügbar</Description>

<Icon>

<Guid>ba67fa9d-b1af-4798-8ffc-c392f4da3d20</Guid>

<Type>Icon</Type>

</Icon>



P a g e 16 | 54


Feb 20, 2019

<Icons>

<Icon>


<Source>0</Source>

<Url>http://statics2.carparts-

cat.com/webdata/imageData/theme/41/AvailState/3_w.png</Url>

</Icon>

<Icon>


<Source>0</Source>


cat.com/webdata/imageData/theme/41/AvailState/3.png</Url>

</Icon>

</Icons>

</MasterData>


<ErpInformation>

<Item>



</Item>


<ConfirmedQuantity xsi:nil="true"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>

<SortId>0</SortId>

<AvailabilityState>




<Prices>

<Price>

<Type>5</Type>


<RebateValue xsi:nil="true"


<Rebate xsi:nil="true"




<PriceUnit xsi:nil="true"


<VAT xsi:nil="true"


<TaxIncluded>true</TaxIncluded>

</Price>

</Prices>

<Warehouses>

<Warehouse>

<Id>XXX</Id>

<Quantities>

<Quantity>

<Value>1</Value>

<MinQuantity xsi:nil="true"


<MaxQuantity xsi:nil="true"


P a g e 17 | 54


Feb 20, 2019

<AvailabilityState>

<Guid>31753678-8a30-47f7-9447-

43130cfcc321</Guid>



<Division xsi:nil="true"


<QuantityPackingUnit xsi:nil="true"


</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

</ErpInformation>


<TypeId>1</TypeId>



</soap:Body>

</soap:Envelope>

4.4. PRICE DISPLAY

Via TM Connect.ERP various prices can be sent to the catalogue. The catalog displays the prices in the

order in which they were sent.

Codeblock 10 Price display

<Prices>

<Price>

<Type>4</Type>










</Price>

<Price>

<Type>9</Type>



P a g e 18 | 54


Feb 20, 2019








</Price>

<Price>

<Type>5</Type>










</Price>

<Price>

<Type>1</Type>










</Price>

</Prices>

4.5. SCALE PRICE

In addition to the unit prices, it is also possible to send scale prices via TMConnect. Price type 13 is

used for this. In addition, the scale quantity is sent in the field <PriceUnit>. The application only

displays these prices. There is no calculation of the purchase price in combination with the requested

quantity.

P a g e 19 | 54


Feb 20, 2019

Codeblock 11 Response - Prices

<Prices>

<Price>

<Type>4</Type>



<Value>1.56</Value>

</Price>

<Price>

<Type>13</Type>


<PriceUnit>1</PriceUnit>


<Value>1.65</Value>

</Price>

<Price>

<Type>13</Type>




<Value>1.56</Value>

</Price>

<Price>

<Type>13</Type>




<Value>1.43</Value>

</Price>

<Price>

<Type>5</Type>



<Value>0</Value>

</Price>

</Prices>

4.6. MISLEADING DESCRIPTIONS FOR PRICE TYPES AND BEST PRACTICE

Since these price types ( price types ERP TMConnect ) are partly taken from old stock, the

descriptions can be misleading in places, especially concerning the topic with and without taxes.

In general, TMConnect.ERP also supports the flag <TaxIncluded>. Here is a best practice example for

EK (4) and VK (5) with and without taxes:

Codeblock 12 Response - Prices EK/VK - TaxIncluded - VAT

<Prices>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>5</Type>

<Description>VK Inclusive 21% Mwst</Description>



P a g e 20 | 54


Feb 20, 2019





<VAT>21</VAT>


</Price>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>5</Type>

<Description>VK exclusive Mwst</Description>







<VAT>0</VAT>


</Price>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>4</Type>

<Description>EK Inclusive 21% Mwst</Description>

<Value>8.34</Value>






<VAT>21</VAT>


</Price>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>4</Type>

<Description>EK exclusive Mwst</Description>

<Value>6.89</Value>






<VAT>0</VAT>


</Price>

</Prices>

4.7. REPLACEMENT ARTICLES

Via TM Connect.ERP, information about one or more replacement items can be sent in the response.

This is transmitted via the object <LinkedItemsCollection> within the object <ErpInformation>, in

which information such as availability for the warehouse or prices can also be transmitted.

P a g e 21 | 54


Feb 20, 2019

P a g e 22 | 54


Feb 20, 2019


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

<AvailabilityState>

<Guid>d2d8ca7d-acd3-5985-e811-4b2caa28747f</Guid>



<Prices>

...

</Prices>

<LinkedItemsCollections>

<LinkedItemsCollection>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Role>3</Role>

<LinkedItems>

<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>

<Guid>d2d8ca7d-acd3-5985-e811-4b2c0254787f</Guid>


</Item>



<SortId>0</SortId>

<AvailabilityState>

<Guid>d2d8ca7d-acd3-5985-e811-4b2cb285737f</Guid>



<Prices>

...

</Prices>

<Warehouses>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>1</Id>


<Quantities>

<Quantity>

<Value>2.0</Value>




<AvailabilityState>




<Division>2.0</Division>


</Quantity>

P a g e 23 | 54


Feb 20, 2019

</Quantities>


</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>2</Id>


<Quantities>

<Quantity>

<Value>40.0</Value>




<AvailabilityState>






</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

</ErpInformation>

</LinkedItems>

</LinkedItemsCollection>

</LinkedItemsCollections>

<Warehouses>

...

</Warehouses>

</ErpInformation>

4.8. SALES UNIT

Using TM Connect.ERP, a sales unit at item level can be sent from the ERP system. If the catalog

receives this information, the customer can only place the article in the shopping basket and order

the quantity of the sales unit. The quantity is expected in the <Division> field within the quantity

object.

Codeblock 14 Division

<Quantity>

<Value>2.0</Value>




<AvailabilityState>

P a g e 24 | 54


Feb 20, 2019

<Guid>b58b81db-53b0-5883-e811-fa28e0b115fa</Guid>





</Quantity>

4.9. INDIVIDUAL AVAILABILITY ICONS

If different availability icons should be displayed in the catalogue for an article, an icon object can be

sent in the <MasterData> area of the response for this case. This can be referred in <AvaiabiltyState>

in the area <MasterData>. This function can be used, e.g. to symbolize a particular article status

(sales stop, promotion, etc.).

Codeblock 15 Icon

<MasterData>

...

<Icons>

<Icon>

<Guid>c1c68db3-fc6d-4331-846d-ff5d97cec269</Guid>

<Source>0</Source>



</Icon>

</Icons>

...

</MasterData>

Codeblock 16 Icon - Reference

<AvailabilityState>

<Guid>5bdb64a3-f413-4234-a726-203e5aea9ac9</Guid>

<Type>2</Type>


<Icon>


<Type>Icon</Type>

</Icon>


TM Connect.ERP - Preisanzeige

P a g e 25 | 54


Feb 20, 2019

This page has not yet been translated to English.

5. TM CONNECT.ERP - GENERAL REFERENCES FOR IMPLEMENTATION

5.1. GENERAL REFERENCES FOR IMPLEMENTATION

To exchange price and availability requests and also orders between catalog and ERP system are used

methods in TMConnect.ERP like <GetErpInformation> and <SendOrder>.

6. TM CONNECT.ERP - GENERAL EXAMPLE FOR AN ARTICLE REQUEST

6.1. GENERAL EXAMPLE FOR AN ARTICLE REQUEST

In the following an article is requested. In the response for this article the total availability

“available”, the availability for a location and two prices (purchase-/sales price) will be transmitted.

6.1.1. STRUCTURE

6.1.1.1. CREDENTIALS

In this area the customer number <CustomerID>, user name <Username> and the password

<Password> are sent.

6.1.1.2. MASTERDATA

General information are exchanged in the MasterData area. This information can be referenced. In

the response the articles and availability states are declared which are used later on.

6.1.1.3. ERPARTICLEINFORMATION

In this area, the transaction data are exchanged. In the response, e.g. the availability or prices for

articles are sent.

Codeblock 17 Request





<soap:Body>


<request>

<Credentials>







</Credentials>




<MasterData>

P a g e 26 | 54


Feb 20, 2019

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

</ErpInformation>


<TypeId>0</TypeId>

</request>


</soap:Body>

</soap:Envelope>



xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-

utility-1.0.xsd"

xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"

xmlns:tns="http://topmotive.eu/TMConnect"

xmlns:q1="http://microsoft.com/wsdl/types/"

xmlns:q2="http://microsoft.com/wsdl/types/">

<soap:Body>



<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

P a g e 27 | 54


Feb 20, 2019

</ArticleTmfs>


<AvailabilityState>


<Type>2</Type>





</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>


<SortId>0</SortId>

<Warehouses>

<Warehouse>

<Id>450700</Id>

<Description>Filiale 1</Description>


<Quantities>

<Quantity>


<AvailabilityState>

<Guid>c629c368-1b31-45a7-b63a-

06ef92450700</Guid>




</Quantity>

</Quantities>

</Warehouse>

</Warehouses>

<AvailabilityState>




<Prices>

<Price>

<Type>4</Type>



<Value>3.6</Value>

</Price>

<Price>

<Type>5</Type>



<Value>5.9</Value>

</Price>

</Prices>

<ConfirmedQuantity>123</ConfirmedQuantity>

P a g e 28 | 54


Feb 20, 2019

</ErpInformation>


<TypeId>0</TypeId>

<Credentials>



<Password>xxxt</Password>




</Credentials>





</soap:Body>

</soap:Envelope>

7. TM CONNECT.ERP - REPLACEMENT ARTICLES

7.1. REPLACEMENT ARTICLES

Via TM Connect.ERP, information about one or more replacement items can be sent in the response.

This is transmitted via the object <LinkedItemsCollection> within the object <ErpInformation>, in

which information such as availability for the warehouse or prices can also be transmitted.

P a g e 29 | 54


Feb 20, 2019


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

<AvailabilityState>

<Guid>d2d8ca7d-acd3-5985-e811-4b2caa28747f</Guid>



<Prices>

...

</Prices>

<LinkedItemsCollections>

<LinkedItemsCollection>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Role>3</Role>

<LinkedItems>

<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>

P a g e 30 | 54


Feb 20, 2019

<Guid>d2d8ca7d-acd3-5985-e811-4b2c0254787f</Guid>


</Item>



<SortId>0</SortId>

<AvailabilityState>




<Prices>

...

</Prices>

<Warehouses>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>1</Id>


<Quantities>

<Quantity>

<Value>2.0</Value>




<AvailabilityState>






</Quantity>

</Quantities>


</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>2</Id>


<Quantities>

<Quantity>

<Value>40.0</Value>




<AvailabilityState>






</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

</ErpInformation>

P a g e 31 | 54


Feb 20, 2019

</LinkedItems>

</LinkedItemsCollection>

</LinkedItemsCollections>

<Warehouses>

...

</Warehouses>

</ErpInformation>

8. TM CONNECT.ERP - OVERALL AVAILABILITY

8.1. OVERALL AVAILABILITY

The overall availability of an article is sent as <AvaiabilityState> in the <ErpInformation>. A status is

also referenced here which is sent in the area <MasterData>.

Codeblock 20 Main Avaiability


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

P a g e 32 | 54


Feb 20, 2019

<AvailabilityState>

<Guid>b58b81db-53b0-5883-e811-fa28be0de6f9</Guid>



</ErpInformation>


9. TM CONNECT.ERP - INDIVIDUAL AVAILABILITY ICONS

9.1. INDIVIDUAL AVAILABILITY ICONS

If different availability icons should be displayed in the catalogue for an article, an icon object can be

sent in the <MasterData> area of the response for this case. This can be referred in <AvaiabiltyState>

in the area <MasterData>. This function can be used, e.g. to symbolize a particular article status

(sales stop, promotion, etc.).

Codeblock 21 Icon

<MasterData>

...

<Icons>

<Icon>


<Source>0</Source>



</Icon>

</Icons>

...

</MasterData>

Codeblock 22 Icon - Referenz

<AvailabilityState>

<Guid>5bdb64a3-f413-4234-a726-203e5aea9ac9</Guid>

<Type>2</Type>


<Icon>


<Type>Icon</Type>

</Icon>


P a g e 33 | 54


Feb 20, 2019

10. TM CONNECT.ERP - SHOW AVAILABILITY FOR LOCATIONS

10.1. SHOW AVAILABILITY FOR LOCATIONS

In order to display several locations in the TM Connect.ERP catalog with one availability, several

<Warehouse> objects must be sent in the response. In the following example, two locations are sent.

The stock (<value>) and the packaging unit are sent for both locations. The fields <ID> and

<Description> are displayed in the catalog.

Codeblock 23 Warehouses

<Warehouses>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>1</Id>


<Quantities>

<Quantity>

<Value>2.0</Value>




<AvailabilityState>






</Quantity>

</Quantities>


</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>2</Id>


<Quantities>

<Quantity>

<Value>68.0</Value>




<AvailabilityState>




P a g e 34 | 54


Feb 20, 2019



</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

11. TM CONNECT.ERP - PRICE DISPLAY

11.1. PRICE DISPLAY

Via TM Connect.ERP various prices can be sent to the catalogue. The catalog displays the prices in the

order in which they were sent.

Codeblock 24 Price display

<Prices>

<Price>

<Type>4</Type>










</Price>

<Price>

<Type>9</Type>










</Price>

<Price>

<Type>5</Type>


P a g e 35 | 54


Feb 20, 2019









</Price>

<Price>

<Type>1</Type>










</Price>

</Prices>

11.2. SCALE PRICE

In addition to the unit prices, it is also possible to send scale prices via TMConnect. Price type 13 is

used for this. In addition, the scale quantity is sent in the field <PriceUnit>. The application only

displays these prices. There is no calculation of the purchase price in combination with the requested

quantity.

Codeblock 25 Response - Prices

<Prices>

<Price>

<Type>4</Type>



<Value>1.56</Value>

</Price>

<Price>

<Type>13</Type>




<Value>1.65</Value>

P a g e 36 | 54


Feb 20, 2019

</Price>

<Price>

<Type>13</Type>




<Value>1.56</Value>

</Price>

<Price>

<Type>13</Type>




<Value>1.43</Value>

</Price>

<Price>

<Type>5</Type>



<Value>0</Value>

</Price>

</Prices>

11.3. MISLEADING DESCRIPTIONS FOR PRICE TYPES AND BEST PRACTICE

Since these price types ( price types ERP TMConnect ) are partly taken from old stock, the

descriptions can be misleading in places, especially concerning the topic with and without taxes.

In general, TMConnect.ERP also supports the flag <TaxIncluded>. Here is a best practice example for

EK (4) and VK (5) with and without taxes:

Codeblock 26 Response - Prices EK/VK - taxincluded - VAT

<Prices>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>5</Type>

<Description>VK Inclusive 21% Mwst</Description>







<VAT>21</VAT>


</Price>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>5</Type>

<Description>VK exclusive Mwst</Description>







P a g e 37 | 54


Feb 20, 2019

<VAT>0</VAT>


</Price>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>4</Type>

<Description>EK Inclusive 21% Mwst</Description>

<Value>8.34</Value>






<VAT>21</VAT>


</Price>

<Price>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Type>4</Type>

<Description>EK exclusive Mwst</Description>

<Value>6.89</Value>






<VAT>0</VAT>


</Price>

</Prices>

12. TM CONNECT.ERP - DISCOUNT CODE

12.1. DISCOUNT CODE

Discount codes can be sent via TM Connect.ERP. These are displayed in the article list as well as in

the shopping cart of the catalogue.

Where exactly it is entered can be found in the TMConnect documentation under:

4.2.11. ErpInformation

StatusInformation → List<KeyValueItem> → List of KeyValue elements. Each one describes a status

information (e.g. "out of stock" or "not returnable")

P a g e 38 | 54


Feb 20, 2019

Codeblock 27 discount code

<MainElement><soap:Envelope

xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"



<soap:Body>


<request>

<SessionId>a1850f70-1d5a-4ca3-ae9c-945dcbae1782</SessionId>

<ExternalSessionId>a1850f70-1d5a-4ca3-ae9c-

945dcbae1782</ExternalSessionId>

<AdditionalIds>

<KeyValueItem>

<Key>2</Key>

<Value>12</Value>

</KeyValueItem>

</AdditionalIds>

<Credentials>


<Username>pusnik1</Username>

<Password>GIrUckbfNlENxdgJBEb9QA==</Password>

<CustomerId>33343</CustomerId>


<IsEncrypted>true</IsEncrypted>

<Salt>a1850f70-1d5a-4ca3-ae9c-945dcbae1782</Salt>

</Credentials>




<MasterData>

<ArticleTmfs>

<ArticleTmf>

<Guid>01371d59-5e6b-42f4-94ca-3690943f4ee5</Guid>


<Type>0</Type>

<ArticleIdSupplier>8671002052</ArticleIdSupplier>

<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>


<ErpInformation>

<Guid>033e3658-ec07-4ac2-b5ac-223e27743f82</Guid>

<Item>



</Item>



<SortId>0</SortId>

</ErpInformation>

P a g e 39 | 54


Feb 20, 2019


<TypeId>0</TypeId>

</request>


</soap:Body>

</soap:Envelope><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Body>

<GetErpInformationResponse xmlns="http://topmotive.eu/TMConnect"

xmlns:i="http://www.w3.org/2001/XMLSchema-instance">



<Notifications />

<ControlIndicators />


<AdditionalIds />

<Credentials>


<Username>pusnik1</Username>

<Password>GIrUckbfNlENxdgJBEb9QA==</Password>

<CustomerId>33343</CustomerId>


<IsEncrypted>true</IsEncrypted>

<Salt>a1850f70-1d5a-4ca3-ae9c-945dcbae1782</Salt>

</Credentials>

<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>

<ArticleIdSupplier>8671002052</ArticleIdSupplier>

<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>


<AvailabilityState>

<Guid>ac80d976-d940-4a50-ba78-a7612c21231b</Guid>

<Type>1</Type>

<Description>Unknown</Description>



</MasterData>


<ErpInformation>

<Guid>033e3658-ec07-4ac2-b5ac-223e27743f82</Guid>

<Item>



</Item>


<ConfirmedQuantity i:nil="true" />

<SortId>0</SortId>

<AvailabilityState>

P a g e 40 | 54


Feb 20, 2019

<Guid>ac80d976-d940-4a50-ba78-a7612c21231b</Guid>



<StatusInformation>

<KeyValueItem>

<Key>PRICECODE</Key>

<Value><span style="background-color:

green;color:white;padding:2px 4px;border-radius:3px;">BA

77</span></Value>

</KeyValueItem>

<KeyValueItem i:nil="true" />

</StatusInformation>

<Prices>

<Price>

<Type>1</Type>

<Description>Motrio Price</Description>

<Value>0</Value>

<RebateValue i:nil="true" />

<Rebate i:nil="true" />

<PriceUnit i:nil="true" />

<VAT i:nil="true" />


</Price>

</Prices>

</ErpInformation>


<TypeId>0</TypeId>



</s:Body>

</s:Envelope></MainElement>

13. AVAILSTATE AND WHERE ARE THEY DISPLAYED

As already mentioned, you can decide for which article you want to send which availability. An article

can have 2 AvailState IDs with different icons and description text, because we expect a GUID for the

article query.

On the picture is an example from another catalog where you can see several prices our customer

sends for his article. He also sends a blue bubble as global availability and behind it he sends the text

"Available in alternative warehouse location" and below you can see the individual warehouse

locations with their own availability states.

For example: response/request, which logismos have to be programmed, how the structure has to

look like

P a g e 41 | 54


Feb 20, 2019






<soap:Body>


<request>

<Credentials>







</Credentials>



<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>

P a g e 42 | 54


Feb 20, 2019



<SortId>0</SortId>

</ErpInformation>


<TypeId>0</TypeId>

</request>


</soap:Body>

</soap:Envelope>


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Body>





<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>


<AvailabilityState>

<Guid>f98c8f35-a92e-2cbe-e811-1e21829cbd77</Guid>

<Type>3</Type>

<ShortDescription>teilweise verfügbar</ShortDescription>


<AvailabilityState>

<Guid>f98c8f35-a92e-2cbe-e811-1e21866ea677</Guid>

<Type>4</Type>

<ShortDescription>auf Anfrage unter Tel: 43 1 203 05

31</ShortDescription>


<AvailabilityState>


<Type>6</Type>

<ShortDescription>im Alternativlagerort teilweise

verfügbar</ShortDescription>



</MasterData>


<ErpInformation>

P a g e 43 | 54


Feb 20, 2019

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

<AvailabilityState>




<Prices>

<Price>

<Type>4</Type>










</Price>

<Price>

<Type>9</Type>










</Price>

<Price>

<Type>5</Type>


<Value>33.5</Value>








</Price>

<Price>

<Type>1</Type>


<Value>40.2</Value>




P a g e 44 | 54


Feb 20, 2019





</Price>

</Prices>

<Warehouses>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>110</Id>


<Quantities>

<Quantity>

<Value>0.0</Value>




<AvailabilityState>


1e21866ea677</Guid>




</Quantity>

</Quantities>


</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>999</Id>


<Quantities>

<Quantity>

<Value>2.0</Value>




<AvailabilityState>


1e21829cbd77</Guid>




</Quantity>

</Quantities>


</Warehouse>

<Warehouse>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Id>120</Id>


<Quantities>

<Quantity>

<Value>0.0</Value>



P a g e 45 | 54


Feb 20, 2019


<AvailabilityState>


1e21866ea677</Guid>




</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

</ErpInformation>


<TypeId>0</TypeId>



</soapenv:Body>

</soapenv:Envelope>

example of another catalog that provides its own icons (green bubble with W):






<soap:Body>


<request>

<Credentials>







</Credentials>


P a g e 46 | 54


Feb 20, 2019


<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

</MasterData>


<ErpInformation>

<Guid>00000000-0000-0000-0000-000000000000</Guid>

<Item>



</Item>



<SortId>0</SortId>

</ErpInformation>


<TypeId>0</TypeId>

</request>


</soap:Body>

</soap:Envelope>


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>





<MasterData>

<ArticleTmfs>

<ArticleTmf>



<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>


<AvailabilityState>

P a g e 47 | 54


Feb 20, 2019


<Type>3</Type>

<Description>1 verfügbar (W-Lagerartikel)</Description>

<Icon>


<Type>Icon</Type>

</Icon>


<AvailabilityState>

<Guid>c334fd4b-2259-41cc-97af-dbb641782b0c</Guid>

<Type>3</Type>


<Icon>


<Type>Icon</Type>

</Icon>



<Icons>

<Icon>


<Source>0</Source>


cat.com/webdata/imageData/theme/41/AvailState/3_w.png</Url>

</Icon>

<Icon>


<Source>0</Source>



</Icon>

</Icons>

</MasterData>


<ErpInformation>

<Item>



</Item>


<ConfirmedQuantity xsi:nil="true"


<SortId>0</SortId>

<AvailabilityState>




<Prices>

<Price>

<Type>5</Type>


<RebateValue xsi:nil="true"


<Rebate xsi:nil="true"



P a g e 48 | 54


Feb 20, 2019


<PriceUnit xsi:nil="true"


<VAT xsi:nil="true"



</Price>

</Prices>

<Warehouses>

<Warehouse>

<Id>XXX</Id>

<Quantities>

<Quantity>

<Value>1</Value>

<MinQuantity xsi:nil="true"


<MaxQuantity xsi:nil="true"


<AvailabilityState>

<Guid>31753678-8a30-47f7-9447-

43130cfcc321</Guid>



<Division xsi:nil="true"


<QuantityPackingUnit xsi:nil="true"


</Quantity>

</Quantities>


</Warehouse>

</Warehouses>

</ErpInformation>


<TypeId>1</TypeId>



</soap:Body>

</soap:Envelope>

14. TM CONNECT.ERP - SALES UNIT

14.1. SALES UNIT

Using TM Connect.ERP, a sales unit at item level can be sent from the ERP system. If the catalog

receives this information, the customer can only place the article in the shopping basket and order

the quantity of the sales unit. The quantity is expected in the <Division> field within the quantity

object.

P a g e 49 | 54


Feb 20, 2019

Codeblock 32 Division

<Quantity>

<Value>2.0</Value>




<AvailabilityState>






</Quantity>

15. TM CONNECT.ERP - THE USE OF GUIDS

15.1. THE USE OF GUIDS

TM Connect.ERP uses GUIDs to reference objects. This implementation allows objects to be used

more than once.

Example:

The status "available" only needs to be declared once in the response in the object

<AvailabilityStates>:

Codeblock 33 AvaiabiltyState


<AvailabilityState>


<Type>2</Type>





P a g e 50 | 54


Feb 20, 2019

Afterwards the AvailabilityStates is referenced by using the GUID in the object <warehouse>

Codeblock 34 AvaiabiltyState

<Warehouses>

<Warehouse>

<Id>1</Id>



<Quantities>

<Quantity>


<AvailabilityState>





</Quantity>

</Quantities>

</Warehouse>

<Warehouse>

<Id>1</Id>



<Quantities>

<Quantity>


<AvailabilityState>





</Quantity>

</Quantities>

</Warehouse>

</Warehouses>

P a g e 51 | 54


Feb 20, 2019

16. SENDORDER

In this are user data is exchanged. The user has the possibility to send a message to the wholesaler.

This message is sent in <UserDefindedData>.





<soap:Body>

<SendOrder xmlns="http://topmotive.eu/TMConnect">

<request>

<AdditionalIds>

<KeyValueItem>

<Key>2</Key>

<Value>12</Value>

</KeyValueItem>

</AdditionalIds>

<Credentials>




<CustomerId>XXX</CustomerId>



</Credentials>




<MasterData>

<ArticleTmfs>

<ArticleTmf>

<Guid>5450129a-f426-452f-b5f8-a4c1b44395d5</Guid>


<Type>0</Type>


<Supplier>


<PoolId>0</PoolId>

</Supplier>

</ArticleTmf>

</ArticleTmfs>

<Vehicles />

<SelectionListItems />

</MasterData>

<OrderCollection>

<Guid>a89a61c8-c125-45f4-a0d0-5bcf5e4503ab</Guid>

<Status>0</Status>

<CreateDate>0001-01-01T00:00:00</CreateDate>

<Orders>

<Order>

<Guid>3d04585f-2606-4a50-abca-fc92faf563b6</Guid>

<OrderIds />

<UserDefinedData>

<UserDefinedData>

<Type>1</Type>

<Value>THIS IS A TEST ORDER DVSE. PLEASE NO DELIVERY !!!

P a g e 52 | 54


Feb 20, 2019

</Value>

</UserDefinedData>

</UserDefinedData>

<Items>

<OrderPosition>

<Guid>d50191d2-91ea-4a70-8aee-ce60eadf4662</Guid>

<Item>



</Item>



<SortId>0</SortId>

<GroupId>0</GroupId>

</OrderPosition>

</Items>

<SelectionLists />

</Order>

</Orders>

</OrderCollection>

</request>

</SendOrder>

</soap:Body>

</soap:Envelope>

In the field <OrderID> the OrderID generated from the ERP system can be transmitted. It is shown in

the order history in the catalog

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"


<SendOrderResponse xmlns="http://topmotive.eu/TMConnect">

<SendOrderResult>


<ErrorCode>0</ErrorCode>

<Notifications/>

<ValidationMessages/>

<TimeStamp>0001-01-01T00:00:00</TimeStamp>

<MasterData>

<Articles/>

<ArticleTmfs>

<ArticleTmf>


<AdditionalIdentifiers/>


<Type>0</Type>


<ProductGroups/>

<Supplier>


</Supplier>

</ArticleTmf>

</ArticleTmfs>

<RepairTimes/>

<ItemsCollections/>

<Tours/>

P a g e 53 | 54


Feb 20, 2019

<Vehicles/>

<Customers/>

<TextBlocks/>

<DispatchTypes/>

<SelectionListItems/>

<AvailabilityStates/>

<Icons/>

<Addresses/>

</MasterData>

<OrderCollection>

<Guid>a89a61c8-c125-45f4-a0d0-5bcf5e4503ab</Guid>


<Status>500</Status>

<CreateDate>2018-05-17T15:47:22.8146207+02:00</CreateDate>

<OrderIds>

<OrderId>

<Type>2</Type>

<Description>Lorem ipsum</Description>

<Value>Lorem ipsum 12345</Value>

</OrderId>

</OrderIds>

<Orders>

<Order>

<Guid>3d04585f-2606-4a50-abca-fc92faf563b6</Guid>


<OrderIds/>

<UserDefinedData>

<UserDefinedData>

<Type>1</Type>

<Value>THIS IS TEST ORDER DVSE. PLEASE NO DELIVERY

!!!</Value>

</UserDefinedData>

</UserDefinedData>

<Items>

<OrderPosition>

<Guid>d50191d2-91ea-4a70-8aee-ce60eadf4662</Guid>


<Item>



</Item>



<Prices/>

<SortId>0</SortId>

<GroupId>0</GroupId>

<UserDefinedData/>

<LinkedEntities/>

<SelectionLists/>

</OrderPosition>

</Items>

<SelectionLists/>

</Order>

</Orders>

</OrderCollection>

</SendOrderResult>

P a g e 54 | 54


Feb 20, 2019

</SendOrderResponse>

</s:Body>

</s:Envelope>

tm connect.erp - guideline for basic implementation · 2020. 12. 7. · dvse gmbh carl-benz-weg 1 d...

Documents